How to Brief a Development Agency: A Practical Template
What to include in a project brief so an agency can give you an accurate scope and price — with a simple template.
A vague brief produces a vague quote — and a vague quote tends to either undershoot (and grow during the project) or overshoot (with padding for unknowns). A clear brief, even an imperfect one, gets you a much more accurate estimate and a faster start.
You don't need a formal spec document. You need to answer a handful of specific questions, which this guide walks through.
Why a Vague Brief Costs You Time and Money
"Build me an app like X" gives an agency almost nothing to scope against — X might have taken a team of twenty engineers two years. The gap between a vague brief and a useful one is usually a short conversation, but having the basics ready in writing first saves a round-trip.
What to Include in Your Brief
These are the essentials — you don't need polish, just answers.
- What the product does, in plain language, and who it's for
- What exists already — a live app, a prototype, designs, or nothing yet
- The single most important thing that needs to work (the 'core loop')
- Any hard constraints — a launch date, a budget range, specific technologies you need to use
- What 'done' looks like for this engagement specifically
What You Don't Need to Specify
You generally don't need to specify the exact tech stack, database schema, or implementation details — a competent team will make and explain those recommendations as part of scoping. Over-specifying implementation details upfront can sometimes lock in choices that don't fit the actual requirements.
A Simple Brief Template
A few sentences against each of these points is enough to start a real conversation:
- Product: [what it does, who it's for, in 2-3 sentences]
- Current state: [nothing / prototype / live product — link if applicable]
- Core loop: [the one thing that has to work well]
- Constraints: [deadline, budget range, must-use technologies, if any]
- Definition of done: [what does success for this engagement look like]
Frequently Asked Questions
Do I need to know my budget before reaching out?
A rough range helps, but it's not required — describing the scope is usually enough for an agency to come back with a price, which you can then compare against your budget.
What if my requirements change after the project starts?
That's normal and expected on most projects. A clear initial brief just makes it easier to see what's changed — and to scope and price the change accordingly.
Can I send you an existing spec document instead of this template?
Yes — any existing documentation is useful. The template is for founders who don't have one yet, not a requirement if you already have something more detailed.
Related Reading
AI App Rescue
Take your Lovable, Bolt, or Cursor prototype to production. We fix auth, database architecture, and performance in 2 weeks.
Ready to send us your brief?
Use the template above, or just tell us what you're building in your own words — we'll ask follow-up questions where needed.
Get in Touch