Short answer

Before requesting a quotation, describe the result the website should achieve, the people who will use it, the pages and features you need, the materials available, the decision-makers and the constraints. You do not need to know the names of technologies. It is enough to explain clearly what should happen and what is still unknown.

Why a short brief is better than a vague “I need a website”

A quotation is a decision about the scope of work, not a guess at the price of a domain and a visual design. “A company website” might mean a simple site with contact details, an extensive offering with multiple service categories, or a site intended to support campaigns, recruitment or sales. These options involve different numbers of decisions, pieces of content, integrations, tests and responsibilities after launch.

A brief does not need to resemble a tender document. Its purpose is to identify things that later lead to scope changes: missing copy, unclear user roles, unspecified forms, no agreed approver and “small” features raised only once the project is under way. The earlier you name them, the easier it is to establish priorities and recognise which elements are needed at launch and which belong in a sensible next phase.

It is also a way to compare proposals fairly. Two prices without a list of assumptions do not tell you whether both providers are pricing the same work. Ask for the proposal to record the scope, exclusions, materials supplied by the client, approval stages and acceptance process. That prevents a cheaper proposal from being mistaken for a more comprehensive one.

Start with decisions, not a list of design references

Visual references are useful, but they do not answer the most important question: why should someone visit the website, and what should they do next? First, describe one primary goal. For a service business, that might be a relevant enquiry, booking a call or providing clear information before contact. For another organisation, an application, reservation or recruitment may matter more.

Next, write down who makes the decision on the audience's side. This does not require a detailed marketing persona. You just need to know what problem brings them to the site, what they need before getting in touch and what might hold them back. This provides a basis for planning the order of content, evidence, answers to objections and a clear CTA.

W3C recommends unique, informative page titles, headings that create a structure and link text that describes the destination. This is practical advice for a brief too: the clearer the information, the less you need to compensate with appearance or guesswork.

Brief matrix: what to prepare before the conversation

AreaQuestion for the website ownerA sufficient answer to get started
GoalWhat should someone do after arriving?One primary action, such as enquiring about a service; supporting actions are optional.
AudienceWho is looking for a solution, and what do they need to understand?2–3 audience groups and their most important questions or concerns.
OfferingWhat exactly needs to be described?A list of services/products, priority areas and what you do not offer.
StructureWhich pages are essential at launch?A list of pages with their purposes: services, about, projects, contact, guides.
Content and evidenceWho supplies the materials, and when?The person responsible for copy, photos, logo and legal details, plus a handover date.
FeaturesWhat needs to work, rather than just look good?A form, booking, CMS, integrations, language versions — or a deliberate decision not to include them.
ApprovalWho approves, and how many revision rounds are realistic?One decision-maker, a method for collecting feedback and response deadlines.

Goal and audience: two sentences that organise the rest

A good starting point is a simple sentence: “The website should help [whom] understand [which solution] and take [which action].” This example is not finished website copy, but a test of direction: “The website should help local business owners check whether their site is ready for AI-assisted search and start a URL check.”

If you cannot write that sentence, the project first needs a conversation about the offering, not a wireframe. One website can serve several needs, but trying to treat every one as the most important often results in a menu without hierarchy and CTAs without context. Write down the main journey, then identify additional paths.

Scope: distinguish the launch site from a development phase

The most useful brief separates three layers. The first is the essential launch minimum: pages, contact, mobile support, basic metadata and service content. The second is conditional elements — such as additional languages, an extensive catalogue or a connection to an external system — that need confirmation. The third is ideas for later: automations, a knowledge centre, campaigns and tests.

Do not treat this list as a promise that every idea will be implemented. It is a list of decisions. For features, also record what success means and who provides access. “Contact form” is not a complete scope without information about the recipient, required fields and privacy consent. Likewise, “CRM integration” requires the system's name, access, the data passed from the form and an error scenario.

Materials: do not hide the gaps

The most common obstacle is not code, but a lack of approved information. In the brief, mark the status of each item: ready, to be prepared, to be confirmed or not needed. This applies to the logo, photos, service descriptions, completed projects, price lists, company details, contact addresses, privacy policy and form consents.

Do not put invented customer reviews, results, certificates or prices into the project just to fill the layout. If evidence does not exist or requires permission, the website should be designed without that claim, or with a clearly marked space to complete before publication. Google says content should primarily help people and be reliable, rather than being created solely to attract traffic.

A brief to copy before requesting a quotation

  1. Company and offering: what we do, whom we serve and what we do not offer.
  2. The website's primary goal: the single most important user action.
  3. Audience: who visits the website and what they ask before getting in touch.
  4. Launch scope: the pages, features and languages needed.
  5. Materials: what is ready, what is missing and who will prepare it.
  6. Existing website: its URL, elements to preserve and problems to solve.
  7. Constraints: deadline, budget context, technical and legal requirements.
  8. Approval: decision-maker, feedback process and responsibility for publication.

Finish with three questions for the provider: what assumptions the quotation makes, what it excludes and how both parties will know a stage has been accepted. This does not replace a contract, but it reduces the risk of “done” meaning something different to each side.

How to assess the quotation you receive

Do not start with the total. Check whether the document addresses the goal, lists pages and features, identifies materials to be provided by each side and separates optional costs or tasks. Pay attention to the scope of testing: responsiveness, forms, links, basic indexing settings and access handover. If something is unresolved, an explicit “to be agreed” is better than a seemingly precise promise.

Compare the collaboration process too. Who is responsible for information architecture, writing content, photography, analytics implementation and post-launch maintenance? Is there a stage where you can stop or change direction before everything is built? The answers help you choose a scope that fits the problem, not just the proposal with the shortest list of items.

Sources and further reading

W3C WAI — Writing for Web Accessibility: unique titles, meaningful heading structure, understandable links and clear language.

Google Search Central — Creating Helpful, Reliable, People-First Content: content should serve the audience, not only attract traffic.

Want to clarify your starting point?

GEO Check lets you check the technical and content foundations of an existing website before you expand or rebuild it.

Check your website with GEO Check ↗