How ReqBrief started: the fight that happens on every client project
Every agency and freelancer knows this moment. You build exactly what the brief said. The client looks at it and says "this isn't quite right, it should work more like this." Now you're arguing about whether it was in scope, and the brief itself is vague enough that you're both technically right.
I got tired of that fight, so I built ReqBrief. Instead of sending a client a static form to fill out alone, you send them a link to a short AI interview. It asks real questions, and if an answer is vague, it asks a follow-up until the answer is actually specific enough to build from. At the end, you get a structured brief you can scope and quote from.
It's free right now during early access. There's a live demo on the site if you want to try it yourself as the client, no signup needed: reqbrief.com
Happy to answer questions about how it works or why I built it this way.
I like that you're treating ambiguity as the real problem rather than poor documentation.
Most project issues don't happen because clients refuse to provide requirements—they happen because both sides think they understand the same words differently. Turning vague requirements into shared understanding before work begins is a much more valuable outcome than generating another brief.
Good to see you here too. You're pointing at the same distinction you raised before, and I think you're right that it matters more than I initially treated it.
The interview format actually leans toward the shared-understanding side more than a document ever could, since the client is being asked follow-up questions in the moment their picture is still forming, not reviewing something after the fact. But I'll be honest, the current output is still a document at the end. Whether that document is enough to carry the shared understanding forward, or whether the value is really in the conversation itself and the brief is just a receipt of it, is something I'm still thinking through.
That's the part I found myself thinking about as well.
I have a perspective on where that distinction could lead over time, but it's probably easier to explain properly than to compress into a thread.
If you'd find it useful, what's the best email to reach you on?