How Specific Should a Website Brief Be for a Trade Business?

By Blackbird Marketing

A trade business's website brief is specific enough when an agency can understand what the business does, who it needs to reach, what the website must achieve and what constraints it must work within. It does not need to specify every colour, page layout or technical choice.

In short: Your brief should remove uncertainty about the business, audience, services, priorities, content, budget and practical requirements. Leave the agency room to recommend the structure and design, but be clear about the decisions that affect cost, leads and search visibility.

This distinction matters. A vague brief can lead to a website that looks acceptable but gives the agency little direction on services, locations, customer enquiries or commercial priorities. An over-prescriptive brief can prevent useful professional advice and make the project harder to improve when the original assumptions are tested.

Start with the business decision, not the design

The first test is simple: can the agency tell why the website is being built or changed? “We need a more modern website” describes an opinion, not a measurable business need.

A stronger brief explains the problem the current site creates and the change the new site should support. For example, the website may need to present several services more clearly, generate enquiries for a particular type of work, make it easier for visitors to call, or provide a better foundation for local SEO and paid advertising.

You do not need to promise a particular number of leads. Instead, describe the action that matters and how you will recognise improvement.

• What should a suitable visitor do on the site?

• Which enquiries are commercially useful to the business?

• Which services or customer types deserve priority?

• What is not working on the existing website?

• Are there deadlines linked to a launch, rebrand, new service or advertising campaign?

If the business has several services, rank them rather than listing them as equal priorities. A website brief that says “we want everything promoted” leaves the agency to guess how the navigation, homepage and page hierarchy should work.

What a specific website brief should contain

A practical brief should give the agency enough information to make sensible recommendations. The following sections cover the information that most affects scope and outcome.

1. Business and customer context

Explain what the business does in plain language, where it operates, who makes the buying decision and what type of enquiry is a good fit. For a trade business, this may include the work it wants more of, the properties it usually works on and whether the customer is a homeowner, landlord, developer or another business.

Include the questions customers ask before contacting you, as well as the concerns that can stop them enquiring. These could relate to disruption, access, workmanship, paperwork, materials, timescales or whether the business handles a particular type of job.

Avoid unsupported claims such as “we are the leading local provider”. Give the agency facts it can use to communicate value accurately, such as the types of work undertaken, areas served, relevant project experience and any qualifications or memberships that you are prepared to publish.

2. Services and commercial priorities

List the services the website must cover, then identify which ones matter most commercially. The agency needs to know whether each service requires its own page, belongs under a broader category, or is only a supporting offering.

Be specific about the enquiry you want. “More roofing leads” may be too broad if the real priority is planned roof replacement rather than small repairs. Equally, do not describe a specialist service on the brief unless the business genuinely provides it and can fulfil the resulting enquiries.

For each priority service, provide:

• The customer problem it addresses.

• The type of property or project involved.

• The locations the business actually serves.

• Important exclusions or jobs it does not take on.

• The next action the visitor should take.

• Any existing page, brochure or job information that can be reused.

This detail helps the agency distinguish between a page that needs to attract search traffic and a page that mainly supports a referral or an existing sales conversation.

3. Audience and buying questions

Do not stop at demographic descriptions. “Homeowners aged 35 to 65” tells a designer little about the page a visitor needs. Explain what prompts the enquiry, what the person already knows and what they need to decide before contacting the business.

For instance, a planned improvement project may require examples of previous work, a clear explanation of the process and an indication of what affects cost. A more urgent problem may require immediate clarity about the relevant service and the quickest appropriate contact route. The website brief should tell the agency which of these buying situations it must support.

If different audiences need different information, say so. A landlord, homeowner and commercial property manager may use the same service but ask different questions about access, records, scheduling and responsibility.

4. Content, evidence and responsibilities

Content is one of the most common sources of uncertainty in a website project. State who will supply or approve the written copy, photographs, project details, testimonials, logos and legal information. If material is missing, identify it early rather than treating it as a minor final task.

Useful content inputs can include:

• Accurate service descriptions and terminology used by customers.

• Frequently asked questions from real enquiries.

• Photographs that the business has permission to use.

• Short project summaries with the problem, work completed and result described factually.

• Areas served and any location-specific limitations.

• Existing brochures, leaflets, adverts or pages that must be retained or reviewed.

Be clear about claims that need checking. A website brief should not ask an agency to imply guarantees, fixed timescales, qualifications or outcomes that the business cannot substantiate.

5. Search, marketing and technical requirements

Tell the agency whether the website needs to support local SEO, paid campaigns, social traffic, email activity or another marketing channel. These requirements can influence page structure, landing pages, tracking, forms and the way services are grouped.

Specify known technical needs without assuming the solution. Examples include a contact form, call tracking, analytics, a connection to a booking or CRM system, editable service pages, multiple users, accessibility requirements or integration with an existing platform.

Also provide access details and constraints where relevant: the current domain, hosting arrangement, content management system, analytics account and any third-party tools. The agency should confirm what access it needs rather than relying on assumptions.

Search structure is worth addressing early. If several pages may target similar services or locations, ask how the proposed site structure will avoid confusion and duplication. For a related consideration, see how to check whether two trade service pages compete in search.

6. Budget, timing and approvals

A budget range is more useful than asking for the cheapest possible website. It helps the agency distinguish between a smaller brochure site, a larger service-led build and work that includes copywriting, SEO, migration or integrations.

If there is no agreed budget, explain what is fixed and what can change. For example, the number of initial pages may be flexible, while the launch date or required enquiry system is not. Ask the agency to show which assumptions would increase or reduce the cost.

Give a target date only when there is a real reason for it, and explain the dependency behind it. Content delays, approval time, access problems and changes to scope can all affect delivery. A useful brief identifies who can approve decisions and how feedback will be gathered, rather than assuming that several people will respond consistently.

How to tell whether the brief is specific enough

Before sending the document, test it against the decisions an agency will need to make. If two competent agencies could read it and form completely different views of the required website, it needs more detail.

Use these checks:

1. The service check: Could someone identify the priority services, the jobs that are out of scope and the type of enquiry wanted?

2. The customer check: Could the agency explain why a target visitor would arrive and what information would help that person act?

3. The content check: Is it clear what material exists, what needs creating and who will approve it?

4. The scope check: Does the brief identify required features, integrations, pages and migration work without prescribing irrelevant technical details?

5. The measurement check: Is there a practical way to judge whether the site supports the intended business action?

6. The constraint check: Has the brief stated genuine limits around budget, timing, brand, platform, access or compliance?

If the answer to one of these is no, add information or mark the issue as an open question. An honest unknown is more useful than a confident but inaccurate instruction.

What should remain open for the agency?

A brief should describe the outcome and constraints, not pretend to know every professional solution. This is particularly important when the business owner knows the trade well but does not work in web design, content structure or technical SEO.

It is reasonable to specify brand preferences, essential information, required functions and disliked features. It is less useful to dictate a particular menu structure, page count, platform or animation without explaining why it is needed.

For example, “the site must make it easy for visitors to enquire about three priority services” gives the agency a clear requirement. “Put all three services in separate homepage sections with a slider and five buttons” specifies a solution that may not be the most effective way to meet it.

Ask the agency to explain its recommendations and the trade-offs involved. A good response should make clear what is included, what is assumed, what requires further discovery and what could be added later.

Questions to ask when comparing agency responses

The brief is only half of the decision. When agencies respond, compare how they have understood the problem rather than comparing headline prices alone.

• Have they identified the priority customer and service correctly?

• Have they distinguished essential requirements from optional improvements?

• Is the proposed page structure understandable to someone who knows the business but not web terminology?

• Who is responsible for copy, images, approvals, hosting and ongoing changes?

• How will existing search visibility, useful URLs and tracking be handled?

• What happens if the business changes a requirement after work starts?

• What will the business be able to edit after launch?

• How will the agency review whether the website is ready to improve further?

Be wary of a response that repeats the brief without challenging unclear priorities. Be equally wary of a proposal that introduces a long list of features without linking them to the business problem.

For example, Blackbird Marketing describes its website design work as an SEO-ready process covering review, planning, building and launch or improvement. That published approach is relevant when a trade business wants its brief to cover both the website itself and the search foundations it may need afterwards. The business's published business website service information is the appropriate place to confirm whether its offering fits the project.

Common mistakes that make a brief weaker

Writing for the agency instead of the customer

Technical language can hide the actual requirement. Describe what the customer must be able to understand or do, then let the agency recommend the most suitable implementation.

Confusing a visual preference with a business requirement

It is fine to share examples of websites you like, but explain what you like about them. Is it the clarity of the services, the amount of project evidence, the navigation or the way the enquiry route is presented? A visual example alone is open to interpretation.

Including every possible idea

Long wish lists often obscure the few features that matter. Separate “must have”, “useful if affordable” and “future idea”. This makes quotations easier to compare and gives the agency a sensible way to phase work.

Leaving approvals until the end

If no one owns decisions, a project can stall even when the design and build are progressing. Name the person who can approve content, brand decisions and launch requirements, and agree how consolidated feedback will be provided.

Assuming the agency knows the business already

Do not rely on the agency to infer specialist services, local coverage, preferred terminology or unsuitable enquiries from a short company description. Include the detail that affects the customer journey, even if it seems obvious internally.

A practical final test

Read the brief as if you were preparing a proposal. You should be able to answer five questions without guessing:

1. What does the business want the website to change?

2. Which customers and enquiries matter most?

3. What must the website contain or connect to?

4. What information, budget and time constraints apply?

5. Which decisions still need professional advice?

If the brief answers those questions, it is probably specific enough to start a productive agency conversation. It can still change after discovery; specificity is not the same as locking every decision before the project begins.

Ready to turn the brief into a practical website plan? If you know the business priorities but need help shaping the website around them, contact Blackbird Marketing about its business website service.

View Business Websites