DEV Community

Cover image for Why I stopped using intake forms and built a conversational interview tool instead
Danial Pourgolab
Danial Pourgolab

Posted on

Why I stopped using intake forms and built a conversational interview tool instead

Every freelance developer I know has a version of this story. You build exactly what the brief said. The client looks at it and says "this isn't quite right." You both go back to the brief and find one vague sentence that somehow proves both of you right.
Nobody's lying. They described what they could picture in their head. You built what was actually written down. The gap became your problem.
I spent a long time trying to fix this with better intake forms. Longer forms, more fields, more specific questions. It didn't work. Clients fill out three fields and leave the rest blank. The ones who do fill everything out still use words like "modern" and "clean" without defining what those mean for their specific project.
The kickoff call doesn't fix it either. Everyone agrees on the call and remembers it differently six weeks later.
The actual problem
Clients don't know what they want until they see the wrong thing built. This isn't a client problem, it's a communication format problem. A form asks questions in isolation. A conversation follows up when an answer is vague. Those are fundamentally different things.
When a client says "make it easy to use," the right response isn't to write that down. It's to ask: easy for who, doing what, on what device, compared to what they're using now. And keep asking until the answer is something you could actually test.
Forms can't do that. A trained conversation can.
What I built
I got tired of solving this manually on every project, so I built a tool that does the interview for you. You send the client a link. An AI asks them questions about their project, follows up when answers are vague, and generates a structured brief you can scope and quote from.
It's called ReqBrief. There's a live demo on the site where you can play the client role yourself and see what the output looks like, no signup needed: reqbrief.com
What's actually changed
The brief stops being a document the client fills out and becomes a record of a real conversation. When a "that was obviously included" moment happens, you have something to point to that's much harder to reinterpret.
Curious if others have found different ways to solve this. The intake form feels like an industry default that nobody's really questioned.

Top comments (0)