FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 1 of 6

Before you ask for quotes

Settle five things first: the goal, the pages, who edits, the deadline and a budget range. Put them on one page and every quote you get back becomes easier to compare.

6 min readUpdated 2026-11-16
All chaptersChapter 1 of 6
  1. 01Before you ask for quotes
  2. 02Choosing the platform
  3. 03Budget and what drives cost
  4. 04Comparing quotes and agencies
  5. 05Contract, ownership and handover
  6. 06After launch

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 isThe brief should stressA sign it is working
More demo or call bookingsClear offer, proof, a short path to the booking formMore booked calls from the site
Ranking for search termsPage list built around topics, content you can publish oftenMore pages getting impressions and clicks
Looking credible for a raise or a launchDesign quality, case studies, a tight storyFeedback from the people you are pitching
Shipping campaign pages without a developerA section library and a CMS your team can use aloneYour team publishes a page without help
Leaving an old platformURL inventory, redirects, content moved as isNo 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.

PageKindContent todayNotes
HomeUniqueOld copy, needs a rewriteMain goal lives here
PricingUniqueReadyPlans change twice a year
Case studiesTemplate6 written, more plannedTeam adds new ones
BlogTemplateAbout 40 posts on the old siteMove all, keep URLs
Webinar landing pagesTemplate or section libraryNone yetMarketing 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 launchAsk the builder forWatch out for
A founder fixes typos a few times a yearSimple text and image editing, a short training videoPaying for a page builder nobody will use
A marketer publishes posts every weekA CMS with clear fields, image rules, preview before publishPosts that need a developer to format
A team ships new landing pages every monthA library of ready sections they can stack into new pagesEvery new page becoming a design request
Several people edit at onceRoles and publishing rights per personEveryone sharing one admin login
Nobody on your team will touch itA support plan or hourly help from the builderA 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.

HeadingWhat to write
About youTwo or three sentences on the company and who buys from you
The goalOne sentence, plus which goal wins if there are two
PagesUnique pages, template pages with rough counts, and the current URL list if you have one
Who editsNames or roles, what they change and how often
ContentWhat is ready, what needs writing, what needs moving
ToolsAnything the site must connect to
PlatformA preference with a reason, or "open to advice"
DeadlineThe date and why it matters
BudgetA range
ExamplesTwo 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.

Takeaways

What to remember from chapter 1.

  • Write one page before you ask for quotes: goal, pages, who edits, deadline, budget range.
  • Split pages into unique layouts and CMS template pages. They cost very differently.
  • Who edits after launch shapes the platform and the build more than almost anything else.
  • Say what content is missing. Writing copy is real work and belongs in the quote.
  • Send the same brief to everyone, so the quotes can be compared.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.