Write a website design brief for an accurate studio quote

Open with the problem your business needs solved

Your studio does not need a long company history before learning why you need a website. Start with what has changed and what the current experience fails to explain. Perhaps your services have narrowed, your projects deserve better documentation, or prospects repeatedly ask whether you work in their region. Describe the situation using evidence you already have.

A hypothetical property maintenance company might write: “Our current site mixes residential repairs and commercial maintenance. We want commercial property managers to understand our scheduled service and request a conversation. Residential emergency work is outside this project.” This gives the studio an audience, an offer, an action, and a scope boundary.

Avoid goals such as “look professional” without a practical definition. Explain what buyers need to understand or trust. If you have enquiry records, recurring sales questions, or current page examples, attach a small selection with personal information removed. The brief should distinguish observed problems from your proposed solutions.

Describe the buying situation without inventing a persona

Use what you know about real customers. Identify the job they need done, who approves the purchase, and what delays a decision. A made-up name, lifestyle, or personality profile adds little when the important question concerns insurance documentation, service coverage, or project timing. Mark uncertain assumptions for discussion instead of presenting them as research.

Record how prospects reach you. A recommendation from an existing client creates a different starting point from an unfamiliar visitor arriving through search. Both visitors need a usable website, but they might need different amounts of explanation. Include the source of your best enquiries when you have reliable records.

For US and European buyers, specify the markets you intend to serve rather than writing “international.” List working languages, service area, relevant time zones, and how remote collaboration happens. If local credentials or project examples matter to buyers, identify the evidence available and who verifies the wording.

Attach a content inventory to a provisional page map

List the pages you expect, then explain the purpose of each. Treat this as a starting point for discussion. A studio should challenge unnecessary pages or identify a missing buyer question. For every page, name the content owner and attach existing text, images, and supporting documents. Give files descriptive names rather than sending an unexplained folder.

Mark content as approved, draft, or missing. A draft service description needs review time. A photograph needs publication permission and a suitable original file. A customer quotation needs accurate wording and permission. If an item is unavailable, say so. An honest empty content slot is easier to plan around than an invented testimonial.

Include information outside the main page copy: navigation labels, contact details, form instructions, confirmation messages, document downloads, and social preview images. For a migration, provide the current URL list and identify important pages. Ask the studio to document what stays, what moves, and which redirects need verification.

Review existing content before carrying it into a new site.

Explain what each reference should teach the designer

Choose a few references and annotate them. “We like the way this page separates project photographs from technical details” is useful. “Make something like this” leaves layout, typography, imagery, interaction, and content scope unresolved. Separate what you admire from what would suit your business and your available material.

Include a negative reference when the objection is specific. For example, say you want to avoid text over busy photography because your service descriptions need to remain readable. Avoid collecting dozens of unrelated sites and asking the designer to average them. Contradictory preferences need a decision, not a larger inspiration folder.

Supply brand files and describe their status. Identify the current logo, fonts, colors, and any rules already approved. If a brand refresh is part of the request, state this separately. A website brief should make clear whether the studio is applying an existing identity or proposing changes requiring another approval process.

Turn approved project material into a useful website case study.

Write functional requirements as short scenarios

Describe what a visitor or editor does from start to finish. For a consultation request, write the fields, where the request goes, what the visitor sees afterward, and how your team follows up. For a download, explain whether the document opens freely or requires information. For appointments, identify the scheduling provider and the account owner.

Add failure cases. What should happen when someone misses a required field, enters an invalid email address, or submits while delivery fails? The web.dev accessible forms guidance supports associated labels, understandable input requirements, and useful error feedback. Ask for these details as part of the working experience rather than optional visual polish.

Describe editing needs through common tasks. “Our office manager needs to update team biographies and add project photographs” gives a studio something to demonstrate. “We need a CMS” does not specify the job. Include permissions, training, and who takes over when the usual editor is unavailable. Keep passwords out of the brief.

Name the approver and make timing dependencies visible

Choose one person to consolidate feedback and one person with final approval authority. They might be the same person. List other reviewers and their responsibility, such as checking service accuracy or brand use. Uncoordinated comments from several stakeholders make approval ambiguous and increase the chance of redesigning already approved work.

Provide the desired launch date and the reason behind the date. A trade show, a new office, and an arbitrary preference create different scheduling constraints. List dependencies such as photography, translation, legal copy, domain access, and internal approvals. Give each dependency an owner and expected date. Ask the studio to identify which items block production.

Set review windows using a named time zone. Agree on how feedback arrives and how missing a window affects the schedule. At 48HRS, the first complete version follows within 48 hours of the agreed production start. That start requires an approved brief, final content and assets, the necessary access, and payment. An intro call or an incomplete folder does not start the clock.

Define approval through observable checks

Replace “everything should work” with a short acceptance sequence. Open agreed pages on desktop and phone, follow the main navigation, inspect images and text, submit the contact form, receive the message, and check the confirmation. Include direct entry to an inner page so the review does not assume every visitor starts at the homepage.

Ask who checks titles, descriptions, redirects, and crawlable links. Google’s SEO Starter Guide explains the role of descriptive titles and understandable site structure. These are concrete implementation items. A brief should not turn them into a promise of a particular search position or a fixed number of leads.

Specify handover expectations before choosing a supplier. Request access to the agreed accounts, an editing demonstration, a list of ongoing subscriptions, and a way to request support. Separate a launch defect from a new feature request. This makes the final approval and the post-launch relationship easier to manage.

Send a brief with open questions still visible

You do not need to settle every design decision before speaking to a studio. Send the known facts, the working scope, your budget boundary, and a short list of unresolved choices. Ask for recommendations with reasons. A useful brief creates a better conversation without pretending you have already performed the studio’s design work.

A compact final brief might read: “We sell scheduled maintenance to commercial property managers. The first release needs a service explanation, two permitted project examples, company information, and a call request. We supply draft copy and original photos. One director approves. Please recommend the page structure and identify missing content before quoting.” This example is hypothetical and contains no promised outcome.

Before sending, remove duplicated references, outdated assets, and unexplained attachments. Keep one current version with a named owner. Bring this document to a 48HRS intro call and ask which assumptions affect scope or timing. The next useful step is a written proposal grounded in the decisions you have made.

Common questions