How to Write a Website Brief That Keeps Quotes Fair
A bad brief means an inflated quote and rework. Goals, page structure, functionality, design, integrations, speed and SEO, with a fill-in template.
Short answer: a brief isn’t “I want a pretty website” — it’s the document by which a studio can give an exact price and timeline, and you can accept the work. A good brief answers 8 blocks: goals and metrics, an audit of the current site, page structure, functionality, content, design expectations, integrations and technical requirements (speed, SEO, accessibility), plus acceptance criteria. Here’s how to write one yourself.
Why you need it
A clear brief saves 20–40% of budget: the vendor doesn’t pad for “unknowns”, there are fewer edits, and the timeline is predictable. A brief also reveals who estimates properly and who guesses — unreliable studios bail on the first question about structure.
Block 1. Goals and metrics, not “pretty”
Start from the business, not pictures. Write down:
- Why the site exists: collect leads, sell products, inform, enter a new market/language.
- One main metric: leads/month, conversion, revenue, organic share.
- Who the customer is and what they must do on the site (the target action).
Wording that saves weeks
Bad: “a modern stylish website”. Good: “the site must deliver ≥ 40 leads/month from search and ads at ≥ 2% conversion; the main action is submitting a quote request”. From this brief it’s immediately clear what matters more: speed, forms or the catalogue.
Block 2. Audit of the current site (if any)
What to keep, fix, remove: rankings and traffic from Search Console, weak pages, speed (Lighthouse), mobile usability, what’s broken in the lead inbox. This protects against “rebuild everything from scratch” when 70% can be saved. Related — redesign without losing SEO.
Block 3. Page structure
Map the site and give each page one goal:
| Page | Job | Required elements |
|---|---|---|
| Home | hook + route into a service | offer, benefits, cases, CTA |
| Service / product | convert | scope, “from” prices, FAQ, form |
| Cases | prove | challenge → solution → number |
| About | trust | team, details, certifications |
| Blog | traffic | categories, search, subscription |
| Contact | lead | map, tap-to-call, messengers |
Block 4. Functionality: what must work
List it item by item, not “and everything”:
- forms (which fields, where they go, spam protection), live chat, callback;
- cost calculator, catalogue filters/search, client dashboard;
- multilingual and locales (languages, currencies);
- payment and delivery (for a store);
- admin roles and permissions — who edits what.
Block 5. Content and CMS
- Who writes text and where photos come from — you, the studio, or copywriting in the package.
- What you edit yourself — then you need an admin panel: editing pages and blocks without a developer. In our model that is a Standard-tier feature (in Lite the edits are ours to make). Why it matters — in the headless vs WordPress guide and on the corporate site page.
- Migrating old content (page count, products, articles) — on its own line.
Block 6. Design: expectations and references
- 3–5 reference sites “like / don’t like” and why.
- Brand: is there a guide, logo, brand colors.
- Style: minimal/premium/dark; do you need animation and 3D (this affects price and speed — see animations that convert).
- Design concept before code: lock that you approve it.
Block 7. Technical requirements
Speed. Lighthouse 90+ and green Core Web Vitals (LCP ≤ 2.5s, INP ≤ 200 ms, CLS ≤ 0.1) on key pages.
Responsive. Flawless mobile version (mobile-first), support from 320 px.
SEO base. Clean URLs, canonical, sitemap, robots, meta tags, structured data, hreflang for multilingual.
Integrations. CRM, telephony, analytics (GA4 + goals), payments — with each loop described.
Accessibility. Contrast, alt, tap targets ≥ 44 px, prefers-reduced-motion.
Security and backups. HTTPS, automatic backups, role separation.
Block 8. Integrations (as a separate table)
| System | Why | Data |
|---|---|---|
| CRM (HubSpot/Pipedrive/custom) | no lost leads | contact, deal, source |
| ERP | live stock and prices | catalogue, warehouse |
| Telephony | call recording in the record | number, duration |
| Payment/delivery | order intake | status, receipt |
| GA4 + Search Console | measure results | events, queries |
How it’s built under the hood — connecting your site to a CRM and ERP.
Block 9. Acceptance criteria and deadlines
Write directly in the brief what counts as “done”:
- pages built to the approved design, cross-browser;
- Lighthouse ≥ 90 on 3 key pages (attach the report);
- forms deliver the lead to the CRM, goals fire in GA4;
- content migrated, meta filled, sitemap returns 200;
- the team trained to edit, access and source code handed over;
- a bug warranty (e.g. 6–12 months).
What kills a brief
“Make it like a competitor but better” with no specifics.
No target actions or metrics → nothing to test against.
Functionality described as “and stuff”, “various things”.
Not stating who provides text and photos → the project stalls at content.
No acceptance criteria → a “done / not done” argument at the end.
A mini brief template (copy and fill)
1. Project: company X website. Goal: ≥ N leads/month, conversion ≥ Y%. 2. Audit: current site — rankings, speed, issues. 3. Structure: home, 4 services, cases, about, blog, contacts. 4. Functionality: forms → CRM, calculator, multilingual (EN/UK), search. 5. Content: copy by studio, photos by client, migrate 12 pages. 6. Design: references A/B/C, dark theme, GSAP animations, concept before code. 7. Technical: Lighthouse 90+, green CWV, hreflang, GA4+goals, structured data. 8. Integrations: CRM, telephony, payments. 9. Acceptance: Lighthouse report, form test, access and source handover, 12-month warranty. 10. Budget and stages: fixed quote, weekly demos.
I’m not technical — why do I need a brief then?
A brief doesn’t have to be a technical treatise. Describe the goals, structure and “what must work”. A good studio turns that into a spec and asks smart questions — and that’s how you judge who you’re dealing with.
Who writes the brief — the client or the studio?
Ideally together: you give the goals and business context, the studio formalizes structure, functionality and criteria. It’s often a free step before the contract. At DEXA we start with a 30-minute brief and lock the quote and spec ourselves.
What does development cost from such a brief?
It depends on functionality. Benchmarks: landing from $699 (₴29,000), corporate site from $1,325 (₴55,000), store from $3,614 (₴150,000), custom CRM from $3,614 (₴150,000). A quote for your brief is on the pricing page and in the what a website costs in 2026 guide.
What matters in production
A good brief translates a business goal into the language of pages, functions and acceptance criteria. Fill in the 9 blocks above — and you get an accurate quote, a predictable timeline and a site that solves the job, not just “exists”.
Get a brief and quote for your site → — in a free brief we’ll turn your goals into a spec and give a fixed price. Read next: how to choose a web studio and landing vs multi-page site.
corporate · Lite from $1,325 (₴55,000) · corporate · Standard from $2,145 (₴89,000) · corporate · Premium from $3,494 (₴145,000)
Need the same solution for your business?
A company website with bespoke design and motion: services, cases, team, languages and an admin panel. We build the structure around what your clients search for on Google.
- From 5 pages: services, cases, team, prices
- Lite — a custom layout without complex motion
- Standard — bespoke design, GSAP, two languages, an admin panel
Get a free website audit in 48 hours
Speed, SEO, conversion — a 12-page report with a prioritized fix plan. No obligation, no spam: we show what to improve even if you never hire us.
