The non-technical founder's guide to briefing a dev agency
What to prepare before a call — goals, audience, must-haves, budget range — and how to avoid scope creep.
The short answer
A good brief answers: what success looks like, who it is for, what must exist at launch, what can wait, budget range, and timeline. You do not need a technical spec — you need clarity on business outcomes and honest constraints.
Agencies that skip questions and quote in one email are often guessing. Agencies that ask hard questions are protecting both sides from scope creep.
What to prepare before the first call
Bring these — documents or bullet notes are fine:
- Business goal — “More qualified leads from Google” beats “we need a website.”
- Audience — Who visits, where they are, what they need to believe before contacting you.
- Competitors / references — 3–5 sites you like (layout/feel, not copy).
- Must-have features — Forms, booking, payments, languages, login, blog, integrations.
- Nice-to-have later — Phase 2 list keeps v1 focused.
- Content status — Who writes copy, who supplies photos, existing brand assets.
- Budget range — Even rough (₹1–2L vs ₹5L+) saves wasted calls.
- Timeline — Hard deadline (trade show) vs flexible.
How requirements documents work
After discovery, a good agency produces a written scope (SOW or proposal):
- In scope — Pages, features, integrations, rounds of revision, training.
- Out of scope — Explicit exclusions prevent “I thought that was included.”
- Milestones — Design approval, development, content, UAT, launch.
- Payment schedule — Tied to milestones, not 100% upfront.
- Change request process — How extra work is priced and approved.
- Ownership — Who owns code, domain, hosting, and accounts at end.
How to avoid scope creep
Both sides share responsibility:
- Freeze v1 scope in writing before build starts.
- Use a shared change log — New ideas go to Phase 2 unless budget/timeline adjusted.
- One decision-maker on your side — Too many stakeholders = conflicting feedback loops.
- Respond to feedback in batches — Not daily one-line WhatsApp changes.
- Accept that “small tweaks” add up — Three small features can be a week of dev.
Questions a good agency should ask you
If they never ask these, be cautious:
- What happens after someone submits the form?
- Who updates content post-launch?
- Any compliance, accessibility, or language requirements?
- Existing systems to integrate (CRM, ERP, payment gateway)?
- What does success look like 90 days after launch?
- What failed last time you tried to build or redesign?
Red flags in agency responses
- Fixed price with no discovery for complex projects.
- No mention of hosting, SSL, or maintenance after launch.
- Portfolio only templates, no live client sites to verify.
- Promises #1 Google ranking as part of web build.
- Unclear IP — you might not own your own site files.
Next steps
Draft a one-page brief using the prepare list above.
Use our website cost and website vs web app guides to sanity-check scope before sending RFPs.
Need help with this?
We build what this guide describes.
Tell us about your business and timeline — honest scope and quote, usually within one business day.
Contact Zulo Labs