Back to blog
Websites

Website brief — a quote-ready template and practical specification

Published: 2026-10-128 minKrzysztof Jaroński

“I need a modern website for our company. Please send a quote.”

That message shows up often — and it is rarely enough to set scope honestly. Without goals, unique page types, content status and integrations, a contractor is guessing. One quote assumes a simple brochure site. Another assumes migration, a CMS, two languages and a CRM connection. Both answer the same sentence.

A website brief does not have to be a technical document. It is an organised description of purpose, offer, audience, features and constraints. From that you can get a meaningful quote or a clear list of follow-up questions — instead of comparing numbers built on assumptions.

Below: how a brief differs from a specification, a copy-paste template, and — most importantly — how each answer tends to change project scope. For the wider process see how to build a website step by step. Individual website development is described separately.

Contents

Website brief vs specification — what is the difference?

A brief describes purpose, context, requirements and constraints: why the site exists, who it is for, what it should include, what v1 will not cover, and which decisions are already made.

A specification tightens scope: page types, form states, migration rules, CMS roles, integrations and acceptance criteria. It often appears after a conversation with the contractor — the brief is the input, not the final delivery document.

You do not need to pick the technology, framework or hosting yourself. A good brief says *what* should work and *why*. *How* belongs to the contractor, as long as business and maintenance constraints are clear.

If you compare several quotes, the same brief plus the same questions produce comparable answers. More in how to choose a website contractor.

Website brief — ready template to copy

Copy the list and fill it in. Empty fields beat vague slogans — the contractor will ask; guesswork in a quote is worse.

WEBSITE BRIEF

1. Company name and industry:
2. What the company does (2–5 sentences):
3. Who the offer is for (audiences):
4. Why a new site is needed (no site / outdated / offer change / other):
5. Primary site goal (enquiries, phone, booking a call…):
6. Key services / products to present:
7. Current site / domain (URL or “none”):
8. Planned pages (working list):
9. Required features (form, blog, CMS, search, calculator…):
10. Integrations (CRM, calendar, newsletter, payments, other):
11. Existing content (ready / partial / to be written):
12. Photos / logo / brand assets (what exists, what is missing):
13. Language versions (PL / EN / other; are texts ready?):
14. Analytics and measurement (GA4, Search Console, events — if known):
15. Timeline (soft / hard; reason):
16. Rough budget (optional):
17. What can wait for later (backlog):

Already have a basic project scope?

You do not need a technical specification. Describe the site’s purpose, offer and key features — we will refine the rest before quoting.

Let's talk about your website

How individual answers affect the quote

This is not a price list. It is a map of which brief phrases usually mean more design, content or engineering work.

Page count vs unique layouts

“I want 10 pages” says little about complexity. Ten nearly identical service pages differ from a home page, three services, case studies, a blog, careers and a logged-in area.

Helpful question: how many unique layouts are there? One service template reused with different copy is cheaper to design than every page with its own layout, calculator or gallery.

Ready copy vs content production

“Client will provide content” is often only true halfway through. If copy is written in parallel with design, iteration count rises. If offers must be written from scratch, say so — that is separate work, not a free side task.

Distinguish sales PDFs to shorten vs no service descriptions vs migrating hundreds of existing posts. Each loads the schedule differently.

A form vs a process with integrations

“I need a form” may mean a simple email form, CRM + webhook + autoresponder, file uploads, several paths, or post-submit automation. The more rules and systems on the other side, the more tests and delivery ownership. Describe *what should happen after Submit*. When email is enough, and when the site should join a CRM, calendar or automation, see a company website with integrations.

New site vs migrating an existing one

“We already have a site” opens migration: copy move, URL changes, a 301 map, same domain or not. Without redirects, Google links, cards and emails break after launch. See also new site or modernising the old one?.

One language or several

“We need EN” is not a menu toggle. Are EN texts ready? Same structure or a shorter EN offer? Who keeps both versions current? Each language needs content, navigation, meta and often its own URLs — not only an “EN” label.

CMS and later editing

If the team will add services or articles after launch, say *what* will be edited and by whom. A CMS “just in case” without an editorial process raises launch cost and then sits unused. The opposite promise — “everything is clickable” without roles — turns every phone-number change into a contractor ticket.

CRM, calendar and other integrations

An integration usually means API or account access, field mapping, error handling, tests and ownership after launch. “Connect our CRM” without the system name or whether an account exists cannot be quoted precisely — only estimated or scoped as a separate stage.

Sample filled brief

The example below is a fictional B2B services company. Format illustration only — not a DevSentinel case study.

WEBSITE BRIEF — sample (fiction)

1. Company name and industry: Norda Process Consulting — B2B process consulting
2. What the company does: we help mid-size manufacturers tidy sales and order-handling processes; workshops + light reporting automation.
3. Audience: owners and ops directors in 50–250 person companies in PL; no micro-businesses or product startups.
4. Why a new site: 2018 brochure site; referrals work, but we lack a site for new-client conversations.
5. Primary goal: “Book a diagnostic call” form + phone.
6. Key services: sales-process audit, team workshops, KPI reporting rollout.
7. Current site / domain: yes — same domain; keep a few service URLs if possible.
8. Planned pages: home, 3 services, about, case studies (6 text cases), contact, privacy.
9. Features: form with conversation topic; CMS for services and cases; no blog in v1.
10. Integrations: email inbox + HubSpot copy (account exists); no online calendar in v1.
11. Content: service copy in a PDF; cases to rewrite; no meta/FAQ yet.
12. Assets: AI logo + team photos; no plant photos — agreed stock.
13. Languages: PL only in v1; EN later (copy not ready).
14. Analytics: GA4 + Search Console on the company account; form submit event.
15. Timeline: conversations in November; soft launch in Q1 — no hard event.
16. Budget: scope first, then fit; ranges on a call.
17. Later: blog, EN, lead-qualification calculator.

What you do not need to know before talking to a contractor

You do not need to decide:

  • a specific stack or framework,
  • a CMS name “because everyone uses it”,
  • hosting and CDN details,
  • exact repository or CI/CD architecture.

Those choices should follow requirements: who edits content, which integrations exist, scale, security and maintenance. If a contractor pushes a technology before asking about editing and processes, verify them — do not rush to “learn frameworks”.

What materials do you need at the start?

Usually enough for a quote:

  • company and offer description,
  • site goal and primary conversion,
  • page / feature list (even draft),
  • current site and migration notes,
  • languages,
  • integrations (system name if known),
  • timeline and optional rough budget,
  • a decision-maker for follow-up questions.

Before implementation starts, add among other things:

  • approved copy or a delivery schedule,
  • logo and visuals or a decision to proceed without them,
  • domain / hosting / analytics access at the agreed moment (not in the first brief email),
  • company details, policies, permissions for case studies.

Do not send passwords or full admin access in the brief. Scope and quote first; hand over access securely later.

Should you share a budget?

A budget helps shape v1 and separate “must have now” from the backlog. It is not a condition for first contact.

If you prefer not to share a number, state quality constraints instead: e.g. “v1 without CMS and without EN” or “we depend on migration and 301s”. That is often more useful than an empty field. We do not publish a price table here — DevSentinel quotes individually because scopes differ.

How to send the brief to a contractor

Example message:

Hello,
we are planning a new company website. Below is a brief with goals, scope and open questions. Please send:

1. follow-up questions,
2. a v1 vs later scope proposal,
3. a quote only after clarification.

[paste brief]

Kind regards

You can send the same pack to several contractors — then you compare answers, not guesses. Selection checklist: how to choose a website contractor.

What happens after you send the brief?

A sensible sequence:

  1. Needs check — is the brief complete, is the goal measurable.
  2. Follow-up questions — migration, content, integrations, editing.
  3. Scope refinement — v1 vs backlog, acceptance criteria.
  4. Quote — scope, assumptions, exclusions, timing, terms.
  5. Acceptance — contract / order as agreed.
  6. Project start — materials, milestones, communication.

A brief does not replace a conversation. It shortens it and prevents quoting in the dark.

For concept directions (direction templates, not your finished site) see the showroom. Ready to discuss scope? Go to website development.

FAQ

What should a website brief include?

Purpose, audiences, offer, planned pages and features, current site status, content, languages, integrations, timeline and — optionally — budget and backlog. The clearer the post-Submit outcome, the fewer guesses in the quote.

Are a brief and a website specification the same thing?

No. A brief covers business goals and requirements. A specification tightens delivery scope. Clients usually start with a brief; detailed specification is built with the contractor.

Do I need to know the website technology?

No. Describe editorial needs, features and constraints. The contractor picks the stack to fit — not the other way around.

Do I have to share a budget?

Not required. It helps set a realistic v1. A clear now/later split is a good alternative.

Is a brief enough for an exact quote?

Often enough for a rough quote or a question list. An exact quote usually needs migration, content, integrations and acceptance criteria clarified.

How should I describe website features?

Instead of buzzwords (“blog”, “form”, “CMS”), describe behaviour: who publishes, how much content, what happens after submit, whether existing posts must migrate.

What should I prepare before commissioning a website?

A short brief, a decision-maker, materials or a delivery plan, and domain / current-site information. Technical access comes when implementation starts. Also useful: the step-by-step process and guidance on SEO and enquiries. For format choice see landing page or company website.

Can I send the same brief to several contractors?

Yes — that is a good way to get comparable quotes. Add the same questions about tests, ownership and post-launch support.

Related materials