Blog
How to write a project brief a developer can actually quote from
Published 2026-08-03 · Updated 2026-08-03
Five things in the brief, and the quote comes back fast and accurate instead of vague.
What does a brief actually need?
- The problem, in plain language — what breaks or what’s missing today, not a solution you have already decided on.
- Who uses it and how many — one admin and 50 customers is a very different build than 20 staff and 5,000 customers.
- A list of must-haves versus nice-to-haves — the single biggest driver of both price and timeline.
- Anything it needs to connect to — a payment gateway, an existing database, another company’s API. This is usually where the real cost lives.
- Examples of sites or products you like, and specifically what you like about them — saves several rounds of back-and-forth.
Tell me about your project.
A couple of sentences about the problem is enough. WhatsApp is fastest.