Here's a secret from the developer's side of the table: when you send a vague brief, you get a padded quote. Not because anyone's trying to gouge you, but because uncertainty is risk, and developers price risk in. The clearer your brief, the safer the developer feels, and the sharper the price they can offer.
You don't need to speak tech to write a great brief. You just need to be clear about a few human things.
Lead with the why, not the what
Don't open with 'I need a website with five pages.' Open with what you're actually trying to achieve: 'I run a dental clinic and I'm losing bookings because patients can't schedule online.' That single sentence tells a good developer more than a feature list ever could — and often leads to a smarter, cheaper solution than the one you'd have asked for.
Cover these and you're ahead of 90% of briefs
- What problem you're solving, and for whom
- What a successful outcome looks like to you
- Examples of sites or apps you admire (and why)
- Your rough budget range and any hard deadline
That budget line scares people, but sharing a range isn't weakness — it's a filter. It lets a developer tell you honestly what's possible and steer you toward the best use of your money, instead of guessing in the dark.
Clarity isn't extra work. It's the cheapest way to get a better project.
If you'd like a template to start from, or a second pair of eyes on a brief you're drafting, just reach out — happy to help even if we never work together.