The short answer
Before you ask anyone for a price, write a one-page brief. It needs five things: the one goal the site must meet, a list of pages, who will edit the site after launch, a real deadline, and a budget range. Unknowns are fine. Mark them as unknown and move on.
The brief is not paperwork for the agency. It is how you make quotes comparable. If three teams quote from three different guesses about your project, the prices tell you nothing. If they all quote from the same page, the differences start to mean something. We go deeper on the format in how to write a website brief. This chapter is about the decisions behind it.
Start with one goal
A site can do many things, but a project needs one main job. Pick the one that would make the project a success if nothing else changed. Everything else on the brief is judged against it.
| If the main goal is | The brief should stress | A sign it is working |
|---|---|---|
| More demo or call bookings | Clear offer, proof, a short path to the booking form | More booked calls from the site |
| Ranking for search terms | Page list built around topics, content you can publish often | More pages getting impressions and clicks |
| Looking credible for a raise or a launch | Design quality, case studies, a tight story | Feedback from the people you are pitching |
| Shipping campaign pages without a developer | A section library and a CMS your team can use alone | Your team publishes a page without help |
| Leaving an old platform | URL inventory, redirects, content moved as is | No lost pages, no broken links |
Write the goal as one sentence. For example: "Crumb's new site should get product teams to book a 20 minute demo, and our marketing lead should be able to add a landing page without a developer." That is two goals. That is fine, as long as you say which one wins when they clash.
List the pages
You do not need a final sitemap. You need a list good enough for someone to count the work. Split it into two kinds of page, because they cost very differently.
- Unique pages. Pages with their own layout: home, pricing, about, a product page, contact.
- Template pages. Many pages that share one layout and are filled from a CMS: blog posts, case studies, job posts, integrations, locations.
For template pages, give a rough count and say who writes them. Fifty blog posts moved from an old site is a different job from a blog template your team fills later.
| Page | Kind | Content today | Notes |
|---|---|---|---|
| Home | Unique | Old copy, needs a rewrite | Main goal lives here |
| Pricing | Unique | Ready | Plans change twice a year |
| Case studies | Template | 6 written, more planned | Team adds new ones |
| Blog | Template | About 40 posts on the old site | Move all, keep URLs |
| Webinar landing pages | Template or section library | None yet | Marketing makes these monthly |
If you are redesigning, export a list of every URL on the current site too. It is the starting point for redirects, and it stops pages from going missing. Our redirect map tool helps once you have that list.
Decide who edits, and how often
This is the question buyers skip most often, and it changes the platform, the build and the price. Picture the site six months after launch. Who changes it, how often, and how comfortable are they with tools?
| After launch | Ask the builder for | Watch out for |
|---|---|---|
| A founder fixes typos a few times a year | Simple text and image editing, a short training video | Paying for a page builder nobody will use |
| A marketer publishes posts every week | A CMS with clear fields, image rules, preview before publish | Posts that need a developer to format |
| A team ships new landing pages every month | A library of ready sections they can stack into new pages | Every new page becoming a design request |
| Several people edit at once | Roles and publishing rights per person | Everyone sharing one admin login |
| Nobody on your team will touch it | A support plan or hourly help from the builder | A complex CMS you pay for and never use |
Write down names or roles, not just "the team". "Emma in marketing, weekly blog posts, never touches layout" tells a builder exactly what to set up.
Content you have and content you need
Content is the most common reason a website project runs late. Builders can only build what they have, and waiting for copy is where weeks disappear. Be honest about what exists.
- Copy for every unique page, or a note that you need it written
- Logo files, brand colours and fonts, and whether you hold the font licence
- Photos and illustrations, and whether you have the rights to use them
- Case studies, quotes and client logos you have permission to show
- Product details, pricing and legal pages such as privacy and terms
- Existing posts or CMS items to move, and roughly how many
- Tools the site must connect to: CRM, email, booking, analytics
If copy is missing, say so in the brief. Writing it is real work, and it should be in the quote, not discovered halfway through the project.
Set a real deadline and a range
Give a date and say why it matters. "Live before our launch event on 12 March" is a real deadline. "As soon as possible" is not, and it makes quotes vague, because nobody knows what can be traded away to hit it.
Then give a budget range. Many buyers hold this back to see what comes in. It usually backfires. Without a range, one team quotes the smallest version of your project and another quotes the biggest, and you end up comparing two different projects. A range lets each team tell you what fits inside it and what does not.
Decision rule If the deadline is fixed, let the scope move. If the scope is fixed, let the date move. If both are fixed, the budget has to cover extra people, and you should ask how the quote handles that.
If you have no idea what a range should be, our cost calculator gives a starting point based on Kookies' own prices. It is our pricing, not a market survey, but it shows how pages, CMS and extras add up.
The one-page brief
Here is the shape we suggest. Copy the headings and fill in what you know.
| Heading | What to write |
|---|---|
| About you | Two or three sentences on the company and who buys from you |
| The goal | One sentence, plus which goal wins if there are two |
| Pages | Unique pages, template pages with rough counts, and the current URL list if you have one |
| Who edits | Names or roles, what they change and how often |
| Content | What is ready, what needs writing, what needs moving |
| Tools | Anything the site must connect to |
| Platform | A preference with a reason, or "open to advice" |
| Deadline | The date and why it matters |
| Budget | A range |
| Examples | Two sites you like and one you do not, with a reason for each |
Send the same brief to everyone you ask. When the replies come back, the questions they ask about it are an early test. A team that asks good questions about your editors and your content usually plans better than one that sends a price within the hour.


