How to Write a Website Brief Agencies Can Price

November 16, 2026
Two colleagues sketching a website layout at a table

Two agencies can quote very different prices for a five-page website and both be right. One may assume the client supplies finished copy in one language. The other may include interviews, writing, translation and migration. A useful brief gives both teams the same job to estimate. Start with a real customer request and follow it all the way to the person who handles it.

Describe one enquiry from start to finish

Imagine a furniture maker asking for a quote form. A visitor chooses a room, uploads a sketch and gives the installation postcode. A sales coordinator receives the request and assigns it to a showroom. Now the agency can ask what file types are allowed, which locations are served and who needs access to the sketch. “Add a contact form” leaves all three decisions open.

Write the route as a short story and ask the person at the receiving end to read it. A showroom manager might tell you that customers rarely know their room measurements at the first enquiry. Making dimensions mandatory would stop a good lead before it reached the team. That one conversation gives the designer a better brief than a long list of form fields.

Count the content as well as the templates

A single project template might hold thirty case studies. Designing the template is one job. Finding the photos, clearing permissions, editing thirty descriptions and entering them in two languages is another. In the brief, list the number of entries, the languages, where the source material lives and who will make it ready. Give the agency one representative example to inspect.

Be as specific about the awkward material as the finished material. “We have photos” could mean twenty approved images in one folder or eight years of phone photos scattered across colleagues’ devices. Send one project with its current description and image credits. If preparing that example takes an afternoon, you have learned something about the schedule before anyone commits to a launch date.

Separate launch requirements from open decisions

For the furniture maker, sending the enquiry to a named showroom might be essential on day one. Automatically creating a deal in the CRM might be a later step. If the CRM decision is open, ask for a separate price and state the temporary workflow. Include the name of the person who can approve that decision and the date they need to decide.

Give bidders the same assumptions

Put the assumptions where the agency can respond to them. For the showroom example, a short note could say: “Our team supplies the English text for six service pages. Please price Latvian translation separately. Our sales lead approves the copy in one consolidated round. Include migration of ten completed projects and quote a unit price for each additional one.” A bidder can now point to the exact assumption that changes its estimate.

Keep a copy of these assumptions alongside the chosen quote. At handover, the same list answers practical questions: who supplies the last translation, who can accept the migrated projects, and which change was deliberately left for a later release.

Plan which pages the customer journey actually needs.

Ask every agency to price the same test

Finish with a concrete acceptance test. For example, a visitor on a phone can send a sample sketch, sees confirmation in their chosen language and gets a useful error if the file is too large. The right showroom receives the enquiry and can open the sketch. Ask each agency what its price covers for that journey, what it assumes you will supply and what would cost extra. That makes the differences between quotes much easier to explain.

Questions we would settle before requesting quotes

Should we share our budget?

A working range helps, especially if there is a firm ceiling. Say whether that amount includes photography, copy and ongoing costs. Ask what the agency would deliver inside the range and what it would postpone. That answer is more useful than a price for a version you could never commission.

Do we need wireframes before approaching an agency?

A rough sketch is welcome if it explains a difficult step, such as choosing a showroom. For an ordinary service page, an example of the content and a description of the visitor’s next action are usually enough to start the discussion.

What if the project includes an online store?

Include a sample order and a small export of the actual catalogue. A product count tells the agency little about variants, stock or fulfilment. One representative product family makes those questions much easier to price.

Prepare a sample product family for the brief.

Author

Kristians Krauklis

Founder of quo build
Built and ran e-commerce businesses before building websites for them — which means the work comes from experience, not assumption.