Website brief template

A free, no-email brief template built around the six questions developers ask anyway. Fill it in one pass and every quote you get back is comparable.

Most briefs get bad replies because they answer none of the questions a developer needs to price risk. This template is built around the six that matter — it is the expanded version of the brief guide, and the same structure the brief form here walks through. Copy it into a doc, fill what you can, leave the rest honest ("not sure yet" is a usable answer).

The fields, with guidance

Project

One sentence, plain. If it takes two, you have two projects.

Example: A new marketing site for an accounting firm, replacing a 2019 WordPress site.

Goal

The business outcome, not the deliverable. What changes when this succeeds?

Example: Generate 10–15 qualified enquiries a month; look credible to 50+ CEO prospects.

Scope

Pages, features, integrations — as a list. Rough is fine; complete is essential.

Example: 6 pages (Home, Services, About, 2 service pages, Contact), blog, intake form routing to two emails.

Constraints

Platform, tools, brand, deadline — anything locked.

Example: Stay on WordPress; brand guidelines exist; live before Oct 1 (trade show).

Budget band

A range you can actually spend. Stated budgets get real quotes; hidden ones get guesses.

Example: $6,000–9,000 including content support.

Content responsibility

Who writes copy, sources images, enters data. The most common unpriced item in web projects.

Example: You draft from our notes; we supply photography; developer enters everything.

What exists already

Current site, analytics, access, history — including previous developers and attempts.

Example: Live site + GA4 + Search Console access available; last redesign abandoned in March.

Timeline

The real deadline and what happens if it slips.

Example: Launch Oct 1; slip costs trade-show presence, so quote a rush plan separately.

Copy this block

PROJECT:
Goal:
SCOPE:
  Pages:
  Features:
  Integrations:
CONSTRAINTS (platform / tools / brand / deadline):
BUDGET BAND:
CONTENT (who writes / who enters / who approves):
WHAT EXISTS ALREADY (links / access / history):
TIMELINE (real deadline and why):

Plain text on purpose — pastes cleanly into email, docs and project tools.

Eight fields. A developer can quote it in one pass — and you can compare the replies on substance instead of vibes. When you are ready, the brief form here asks these in order, and a scoped quote comes back within two business days.

Quarterly, and only when the numbers move

Get the rate report before you negotiate.

Updated rate bands across the major stacks and regions, plus what changed and why. No other email.