Brief vs spec: why skipping them costs you more

The most expensive line in any project never shows up in the estimate. It’s rework. And rework almost always traces back to one moment: nobody wrote down, plainly, what was being built. The deal was sealed over a call, a few emails, a handshake. A month later the client is looking at the result thinking “this isn’t what I pictured,” and the studio is thinking “this is exactly what we agreed.” Both of them are right.

A brief and a spec are how you avoid that. Two documents that turn “build us a nice website” into a list of decisions you can attach a price and a date to. Below: what each one is, how they differ, what they need to contain, and how to write a brief even if you’ve never touched a line of code.

Two documents, two different jobs

People mix them up constantly. They sit at different stages and answer different questions.

The brief is about your business. It covers the why and the who: your customers, what you want them to do once they land on the site, where you stand against competitors, what examples you’d point to. You write most of it yourself. Nobody knows your business the way you do.

The spec, short for technical specification, is about the build. It covers the what and the how: which pages exist, what sits on each one, which forms collect what, where an enquiry travels after someone hits send, which outside systems plug in. The studio writes this, working from your brief and checking back with you as it goes.

Think of the brief as a map of the ground and the spec as the route drawn across it. One shows you the terrain; the other shows you which way to walk through it. Skip either and you’re guessing.

With both on the table, the worst sentence in client work goes away: “but I assumed that was included.” Anything left out is visible before you sign, not discovered at handover.

Why skipping them always costs more

Cutting the brief and spec to save time doesn’t save anything. It just moves the cost to the end of the project, where it’s bigger and harder to swallow. A few of the usual ways that bill arrives.

The designer builds what they think you meant. If they read it wrong, fixing it isn’t a quick edit, it’s redoing the work. And someone covers that: you in cash, or the schedule in lost weeks.

There’s also the matter of the quote. With no spec to measure against, a studio is guessing. So it either pads the number to cover everything it can’t see, and you overpay, or it quotes low to win you and bills the gaps later. You know the line: “ah, that part’s separate.”

Then there are the dates. Most delays don’t come from a slow developer. They come from decisions nobody made in time. Each “let’s figure that out later” is the project sitting still, waiting on you.

And when something does go sideways, with nothing written down, there’s no way to settle who was right. The spec is the thing both sides can open and read. That alone is worth the afternoon it takes to write.

All of this lands on the final number. We went into it in what actually drives the price of a website: the fewer unknowns at the outset, the tighter the estimate, and quite often the lower one.

What goes in the brief

A brief doesn’t need to be long. Two pages of straight answers beat twenty of throat-clearing. Here’s the short list that earns its keep:

1. Your business. What you do, who buys from you, how orders reach you today.
2. What the site is for. The one thing a visitor should do: send an enquiry, buy, call, grab a price list. One clear action beats ten half-hearted ones.
3. Who it’s for. Your audience, the device they show up on, what they actually care about. A B2B site and a shop for walk-in retail end up looking nothing alike.
4. Content. Do you already have the text, the photos, a logo, brand colours, or does some of that need making from scratch?
5. Examples. Three to five sites you like, with a line on why. And one or two you can’t stand, which usually tells us more.
6. Budget and timeline. Rough is fine. This isn’t bargaining, it’s a way to aim the proposal. A €650 project and a €6,000 one get answered very differently.

Still deciding between a single landing page and a full site? Read landing page vs multi-page site first, then fill in the brief for whichever you land on.

What goes in the spec

The spec takes the brief and sharpens it to the point where the work can actually be built and priced. A solid one usually covers:

• the structure: every page, and what each one holds;
• the building blocks of each page, so you know what the home page, a service page, and a product card are each made of;
• functionality: forms, filters, a cart, a customer account, more than one language;
• integrations such as your CRM, payment, delivery, analytics, and messaging apps, plus what data moves between them.

Two more deserve their own line. First, technical requirements: how the site behaves on a phone, how fast it loads, the baseline SEO, the domain and hosting. Second, and this is the one people forget, a section that spells out what is not being done in this phase.

That last section saves more grief than any other. Firm boundaries on the page (“the client loads the products,” “the ERP link is a later phase”) are what keep a project from drifting into the limbo where it’s forever “nearly finished” and never quite shipped.

Writing a brief when you’re not technical

Here’s the part that surprises people: a brief needs no tech knowledge at all. It needs clear answers about your business, and you’re the only one who has those. A few things that help.

Write the way you’d say it out loud. “I want people to send an enquiry and have it drop straight into my Telegram” is a complete, usable requirement. Turning that into technical language is our job, not yours.

Describe the problem, not the fix. Instead of “put a slider at the top,” say what you’re trying to get across: “I need visitors to see we’ve been at this twelve years and have two hundred jobs behind us.” The slider, or whatever replaces it, we sort out together.

And lean on examples. One screenshot of a site you admire spares you an hour of trying to explain it in words. Where you genuinely don’t know yet, write “undecided” and move on. That’s far more useful than a guess that gets torn out and redone two weeks later.

A studio worth hiring won’t hand you a blank file and wish you luck. We usually fill the brief in together on a call, then write the spec and pass it back for your sign-off, so you see the whole shape of the thing before anyone starts building. Where this sits in the larger process is laid out in website development stages.

Who writes what, at a glance

Document	Who writes it	Answers
Brief	You, often alongside the studio	Why the site, for whom, what comes first
Spec	The studio, from your brief	What exactly gets built, and how

The hours you put into the brief and spec aren’t a wait before the real work starts. That is the work. It’s the stretch where the project quietly gets cheaper, more predictable, and a lot easier on your nerves.

No finished brief yet? You don’t need one to talk. A few sentences will do: what your business does, what you want the site to accomplish, roughly when you’d like it live. We’ll take it from there and ask the rest.