Solutions · For your workflow
A project inquiry form that asks about the problem first.
Studios and agencies lose good projects to bad forms: budget asked before trust, service menus that don’t match how clients think, and “describe your project” boxes that produce nothing usable. A project inquiry form should sound like the first ten minutes of a good call.
Problem first, then branch
Open with what the prospect wants to take off their plate. Branch on the answer, so a redesign gets redesign questions and a “not sure yet” gets one clarifying question instead of a dead end. This is how Loomwork’s form works in the template.
See the form.
AI, automation, and digital studios taking project inquiries. Goal: Reviewed qualified inquiries per visitor.
Qualification signals
- Workflow the studio automates
- Tools within delivery capabilities
- Repeatable workflow
What would you like to take off your team’s plate?
Branch: what happens today · where requests arrive · who approves
Which tools are involved?
How often does this happen?
Where does it break down, and what would success look like?
Who is involved? Budget (optional)
Name, company, work email
What happens next
Brief to Slack with Good fit / Not a fit / Not sure; plain confirmation to the respondent; owner offers a workflow-mapping call.
What Formwink could learn
Which unclear-scope inquiries turn out qualified, which tool stacks precede won projects, whether a clarifying question changes qualified conversion.
Service fit before budget
Check the things you can actually assess from a form: is this a service you offer, are the tools ones you deliver with, does it repeat often enough to be worth automating. Budget is a scoping question. Formwink keeps service fit separate from commercial qualification, so an unknown budget stays unknown rather than disqualified.
Common questions
Why not ask for budget first?
Because it is the question most likely to end the conversation before you have earned it, and it is the weakest signal on the form. Whether the work is what you do, on tools you deliver with, at a frequency worth the build — those are assessable from a form. Budget is a scoping question, and “help me scope a first project” is a legitimate answer.
What if the prospect does not know what they need?
That path gets its own branch and one clarifying question, not a dead end. An unclear request is not an unqualified customer — in the sample data behind how Formwink learns, several “not sure yet” inquiries were later marked qualified.
Can this replace a contact form?
For project work, usually — a contact form produces a paragraph someone has to interpret. Keep a plain contact route for press, support, and everything that is not an inquiry.
Put this form to work
Every connector states how it connects, which way data moves, and whether it exists yet — three separate facts.
Keep exploring
Templates
Studio project inquiry template
The Loomwork form: problem-first, branching, service fit before budget.
Solutions · For your workflow
Website project brief
Get a brief complete enough to scope without a discovery call.
Solutions · For your workflow
Client intake form
Structure the first conversation so the right clients get a fast, informed reply.
Build my project inquiry form
Formwink is in beta. Everyone who applies gets an invite — fit only orders who we talk to first.