A website specifications document is the document that describes your web project before it launches: context, objectives, audiences, sitemap, features, technical constraints, budget and timeline. It acts as a shared reference between the company and its provider, from the first quote all the way to going live.
According to Insee (2023 data), 69% of French companies with 10 employees or more have a website, yet most creation projects still start without a proper scoping document.
Nexus Synergy, a WordPress and SEO agency, has delivered more than 150 websites: this guide draws on the specifications outline we ask our clients for, and what we actually read in it before pricing a project.
Writing a website specifications document means putting down in black and white who you are, what the site needs to produce, for whom, with which features, within which budget and by when. At Nexus Synergy, a WordPress and SEO web design agency, this document directly shapes the accuracy of the firm quote we return within 24 hours.
More than 150 delivered sites have taught us one thing: a project succeeds or fails before the first mockup. This guide details the sections to cover, the level of detail worth including depending on your type of site, the oversights that blow up budgets and, an angle rarely covered, how an agency reads your document from the other side of the table.
What is a website specifications document actually for?
A website specifications document serves three functions: framing the need, obtaining comparable quotes and acting as a referee during delivery. Without it, each provider responds to a different project, the one they imagined from your three sentences of email.
Comparing offers illustrates the problem well. You consult three agencies with an oral brief, you receive proposals at $2,500, $7,000 and $15,000. Which ones are comparing the same thing? None. A written document forces every candidate to price the same scope, meaning the same pages, the same features and the same additional services. According to Insee (2023), 69% of companies with 10 employees or more have a website: nearly all of them will go through a creation or redesign project again, and therefore through this exercise.
In practice, the document helps you to:
- Clarify: putting your objectives into words forces you to decide what really matters
- Compare: quotes built on the same scope finally become readable
- Secure: if a disagreement arises mid-project, the document is the reference
- Speed up: a well-informed provider prices fast and starts fast
Our conviction after dozens of tenders received: a project without a specifications document isn't faster, it's simply unclear for longer, and that fuzziness gets paid for in change orders.
Who should write the specifications: you, the agency or both?
Writing the specifications document falls first to the project owner, because no one else knows your business, your customers and your priorities. But the final document is almost always built by two parties, with the provider translating your needs into functional and technical choices.
Should you write everything alone before consulting? No. You don't need to know whether your site will run on WordPress, which host to choose or how to structure a product database. Your job is to describe the need; ours is to propose the answer. Honestly, be wary of the provider who prices your project without asking a single question: either they've built in margin everywhere, or they'll discover the problems along the way, at your expense.
The split that works on our projects:
- You: context, objectives, audiences, content, examples of sites you like, budget, deadline
- The provider: technical choices, SEO architecture, hosting, security, methodology
- Both: final sitemap, functional scope, timeline and validation milestones
At Nexus Synergy, the discovery phase, the first step in our four-stage process (discovery, design, production, launch), exists precisely to co-write this document when it doesn't exist. A client arrives with two pages of notes and leaves with complete scoping validated on both sides.
The essential sections of a website specifications document
Eight sections are enough to cover a website creation or redesign project. The order matters, because a rushed reader (and agencies are) has to understand your project within the first two pages. The table below sums up the expected content of each section and the mistake we run into most often in the documents we receive.
| Section | Expected content | Common mistake |
|---|---|---|
| Context and company | Activity, offering, market, competitors, existing site if there is one | Three pages of company history, not a word about competitors |
| Site objectives | 2 to 3 quantified, prioritized objectives (quote requests, sales, brand awareness) | Ten objectives stacked with no hierarchy or success metric |
| Audiences | Concrete profiles, visit context (mobile, urgency, comparison) | "Everyone" as the target, so in reality no one |
| Sitemap and content | Page plan, who writes what, content and media to migrate | Forgetting to specify who produces the text and the visuals |
| Features | Prioritized list: essential, desirable, considered for later | Classing everything as priority 1, which needlessly inflates the quote |
| SEO and performance | Target queries, 301 redirect plan if redesigning, LCP and INP targets | Treating SEO as an option after going live |
| Budget and timeline | Owned budget range, realistic deadline, validation milestones | Hiding the budget out of fear of paying more |
| Selection criteria | Provider scoring grid, expected deliverables and references | Choosing on price alone, without looking at delivered sites |
Three rules make these sections usable:
- Prioritize: every objective and every feature carries an explicit level of importance
- Quantify: "generate 20 quote requests per month" can be measured, "gain visibility" cannot
- Own it: budget and deadline appear in the document, not in the unsaid
On the budget section, give at least a realistic range. To calibrate it, read our guide on how much a website costs: price gaps almost always come down to scope, never magic.
What an agency actually reads in your specifications document
An agency doesn't price pages, it prices uncertainties: every fuzzy area in your specifications turns into a safety margin in the quote. That's why two documents of the same length can produce quotes that differ twofold.
What we look at first isn't what clients imagine. The feature list comes later. Before it, we look for four signals:
- The main objective: a site meant to generate leads isn't designed like an institutional showcase
- The status of the content: text ready, to rewrite or to create, that's the number one cause of timeline slippage
- The existing setup: current URLs, Google positions to preserve, tools to connect (CRM, booking, newsletter)
- The budget-deadline pairing: it tells us whether the requested scope is realistic or whether trade-offs will be needed
When these four points are clear, our firm quote goes out within 24 hours, because there's nothing left to guess. When they're missing, the pricing waits for a scoping call, and you lose a week. On our WordPress website creation projects, precise 3-page specifications regularly beat 30-page briefs copied from a template found online. Precision beats volume, and by a wide margin.
The forgotten sections that blow up budgets
Budget overruns rarely come from the classic sections: they come from what the website specifications document doesn't mention. After 150 projects, about half of them redesigns, we keep finding the same blind spots.
The most expensive one: 301 redirects, meaning the rules that send each old URL to the new one after an address change. A redesign without a redirect plan can wipe out years of SEO in a few weeks. Around 50% of our projects are redesigns or takeovers, and the 301 plan is systematic there; our guide on the website redesign details this mechanism. If your document doesn't mention it, no low-cost provider will do it for you.
The other recurring oversights:
- Structural SEO: target queries, internal linking and markup are designed within the sitemap, not after going live
- The performance target: demand a measurable threshold, such as an LCP (the time to display the main content) under 1.5 s
- AI visibility: in 2026, 48% of Google queries trigger an AI Overview, and a poorly structured site will never be cited there
- Maintenance: updates, backups and security have a recurring cost, from $150 per month with us, to budget from the start
- Ownership: domain name, hosting and licenses must stay in your name, write it down in black and white
A figure to frame what's at stake with performance: NovaTech's redesign took the Lighthouse score from 34 to 98 and load time from 6.2 s to 0.9 s, for +127% conversions in 3 months. None of this was in their first brief. We added it together, and that's what changed the result.
Short 2-page version or full brief: which format to choose?
The right specifications format depends on the type of site, not on your urge to do things well. A 30-page brief for a 6-page brochure site is as counterproductive as a 5-line brief for an online store.
For a brochure site (from $3,000 for a custom build, delivered in 4 to 6 weeks with us), a 2-page version is enough if it contains the essentials: context in 5 lines, 2 quantified objectives, audiences, page list, 3 reference sites you like, content status, budget and deadline. If you're unsure about the scope of this format, our article what is a brochure website lays the groundwork. A corporate site ($5,000 to $15,000, 6 to 10 weeks) deserves a full document, with a detailed sitemap and specifications per template. For a WooCommerce online store (from $8,000, 8 to 14 weeks), the full brief becomes non-negotiable: catalog, shipping, payment, VAT and logistics flows generate too many edge cases to stay oral.
The minimum content of the 2-page version:
- Page 1: context, prioritized objectives, audiences and main competitors
- Page 2: page list, ranked features, content, budget, deadline
An honest caveat to close on: an over-locked specifications document can backfire on you. Freezing every detail before hearing the provider's proposals means paying for change orders as soon as a better idea comes up. Leave open areas, marked as such.
The traps that make a specifications document counterproductive
Some documents undermine the very project they were meant to protect. We receive them every month, and the flaws repeat so consistently that you could predict them before opening the PDF.
The first trap: the generic template filled in without sorting. Templates downloaded online list dozens of questions, and many don't concern your project. The result is a long, diluted document where what matters gets lost. Filling in every box is not a goal. The second: hiding the budget. Announcing a range doesn't push prices up, above all it rules out from the start the providers unable to deliver within your envelope, so it saves you weeks. We'd rather lose an out-of-budget project in 24 hours than discover it at the third meeting.
The other flaws that keep coming back:
- Imposing the tech without mastering it: demanding this plugin or that framework locks the provider into your choices, not into your need
- Making everything priority 1: with no hierarchy, the agency prices the maximum and the quote climbs
- Providing amateur mockups: describe the effect you're after, show references, but leave the design to the designers
- Leaving out validation milestones: without return dates on your side, the timeline is worthless, because the first delay often comes from the client
A solid specifications document doesn't describe a site: it describes an expected result, the constraints that frame it and the room left for the provider's expertise. It's that combination that produces good projects.
Frequently asked questions about a website specifications document
How do you write a specifications document for a website?
Start with substance, not form: note your context, 2 or 3 quantified objectives, your audiences and competitors, then list the pages, the features ranked by priority, the content status, your budget and your deadline. Eight sections are enough for a standard project. First write a short 2-page version, have it read by a colleague outside the project to test its clarity, then expand only the parts that deserve it. The provider will fill in the technical sections during the scoping phase. A precise 3-page document beats a generic 30-page template filled in halfway.
How long should a brochure site specifications document be?
Two to five pages are enough for a classic brochure site of 5 to 10 pages. This format covers the context, the prioritized objectives, the audiences, the page list, the features, the content, the budget and the deadline, without drowning the reader. The 20-page briefs for a simple brochure site come from good intentions, but they dilute the useful information and slow down quotes. Reserve long documents for the projects that justify them: multilingual corporate sites, business platforms or e-commerce with complex logistics. The rule we apply at Nexus Synergy: if a section helps neither to price nor to design, it comes out of the document.
Should you state your budget in the specifications document?
Yes, at least as a range. A serious provider doesn't raise their price because they know your envelope: they adjust the proposed scope to fit within it, or they honestly tell you the project isn't feasible at that level. Hiding the budget produces the opposite of the intended effect, because you receive incomparable offers, from single to quintuple, and you lose weeks sorting them. The range also serves as a test: a candidate who promises a complete online store for $1,500 when the others quote $8,000 mainly reveals what they won't do.
Who should write the specifications, the client or the agency?
The client writes the base, the agency completes it. You alone know your business, your customers, your commercial priorities and your internal constraints: that material can't be invented by a third party. The provider then brings the functional and technical translation, the SEO architecture, the hosting choices and the methodology. Many agencies, ours included, build this co-writing into a discovery phase at the start of the engagement: you arrive with your notes, you leave with a structured document validated on both sides. Be wary, on the other hand, of the provider who prices without asking anything: they guess, and you'll pay for their guessing mistakes.
What's the difference between a functional and a technical specifications document?
The functional specifications document describes what the site must do from the user's point of view: pages, journeys, forms, client area, checkout funnel. The technical specifications document describes how the site will do it: chosen CMS, hosting, languages, security, compatibilities and integrations with your existing tools. For a small or mid-sized business, the two parts fit in a single document, with the functional part written by you and the technical part completed by the provider. Splitting the two is only justified on large projects with a formal tender. With WordPress powering 43.5% of websites according to W3Techs (2026), the technical part also often converges toward proven standards.
Is a specifications document necessary for a website redesign?
Yes, and it's even more sensitive than for a creation, because a redesign can destroy the existing setup. The document must inventory what the current site already has: indexed URLs, Google positions, content that generates traffic, connected tools. It must then impose a 301 redirect plan to transfer each old address to the new one, or risk losing the SEO you've built up. Add a quantified baseline (traffic, conversions, speed) that will serve as a comparison point after going live. At Nexus Synergy, about 50% of projects are redesigns and this part shapes the final result: Maison Laurent gained +450% organic traffic in 8 months after a redesign scoped this way.
Your project deserves serious scoping before the first quote. Nexus Synergy offers a first SEO and performance audit in three parts (technical, SEO, AI visibility), then returns a firm quote within 24 hours based on your specifications, even a rough one. Tell us about your project: we'll tell you what's missing from your document, and what to take out of it.
