Homepages for Established Local Businesses: Creating a Homepage Brief from Five Customer Questions

A homepage brief becomes easier to write when it starts with questions a customer needs answered. For an established local business, five are especially useful: can you help with my need, is the service available to me, why should I trust you, how does the work begin, and what should I do next?

Use those questions to organize facts, evidence and decisions before choosing a layout. The result should be a practical brief a designer and business owner can work from, with assumptions clearly separated from information ready to publish.

Collect real questions before filling in the brief

Review the questions asked during recent first enquiries, appointments or estimate discussions. Speak with the person who answers the phone as well as the person who approves website copy. An owner’s preferred message and a customer’s actual uncertainty may be different.

Use anonymized notes rather than copying private customer details into the brief. Include more than successful purchases: suitable enquiries that did not progress can reveal questions about scope, timing or process that the homepage failed to answer.

If you speak directly with customers, ask about a recent situation: what they needed, what they looked for and what was unclear. GOV.UK’s guidance on in-depth interviews encourages open questions and concrete examples. Avoid asking someone to invent an ideal website or endorse a layout you already prefer.

Group the questions by decision. A repeated question deserves attention, but frequency is not the only criterion. A rarely asked question about whether a service is available may prevent an unsuitable enquiry altogether.

1. Can you help with the job I have?

Write a short answer naming the work the business actually provides. Add the type of customer, project or item where that changes suitability. List important exclusions separately so the headline does not become a paragraph of qualifications.

For an established business, check whether the answer reflects today’s offer. A website may still lead with a once-central service because that is how the business became known. The guide to rewriting a headline around current positioning helps resolve that mismatch.

The brief should capture the leading service, the secondary services that remain available and the page where each can be explained in detail. The homepage introduces the structure; it need not contain every service specification.

An answer such as “We provide a complete range of quality solutions” does not give the designer enough direction. An answer naming the real work makes the content, imagery and link destinations easier to plan.

2. Is this service available to me?

Clarify the practical conditions that determine fit: service area, collection or delivery arrangements, appointments, premises access and any relevant limits. Separate where the business is based from where it provides the service.

The exact answer depends on the offer. A customer visiting a shop needs different information from someone requesting work at their property. A business doing both should not imply that one address explains every arrangement.

Record stable facts ready for publication and details that must be confirmed individually. If availability changes frequently, the brief should identify where the current answer is maintained and what the homepage can state reliably.

For an example of placing coverage information across a customer journey, see where plumbing websites should show service areas. The same planning principle applies to other local businesses: summarize the useful boundary, then link to enough detail to resolve the question.

3. Why should I trust you with this work?

Pair each important claim with evidence that supports it. Relevant completed work, an accurate explanation of the process and genuine customer feedback can help a visitor judge fit. A long history is useful when its relationship to the current service is clear.

In the brief, list the evidence available, who owns it and whether it is ready to publish. Record the context for photographs: what the work involved, what the business did and whether identifying details may be shown.

A project photo can demonstrate a type of work without proving every claim about quality, speed or customer satisfaction. Avoid attaching unsupported performance statements to it. Testimonials should keep their genuine meaning rather than being rewritten to endorse a new service.

If the business lacks suitable recent photography, mark that as a content requirement. A clearly identified illustrative image can support a draft, but it should not be presented as a completed customer project.

4. What happens before I commit?

Describe the first stages from the customer’s point of view. Do they send information, arrange a visit, receive an assessment or discuss an estimate? What do they need to prepare? Which details affect the next decision?

An established team may consider this obvious because it explains the process every day. A new visitor may not know whether a call starts an informal discussion or an appointment, whether photographs help, or whether a quote requires an inspection.

Write only the process the business can follow consistently. If timing varies, explain what determines it and when the customer will receive a clearer answer. A fixed response promise should not be added merely to make a CTA sound reassuring.

Place important process information near the relevant service or contact action. Do not assume that a large FAQ at the bottom will repair an unclear opening.

5. What should I do next, and what should I send?

Choose one primary action for the main audience, then define its destination and expected outcome. “Email photos for an initial assessment” tells a different story from “Book a confirmed appointment.” The interface should match the actual process.

Record the minimum information needed for a useful first conversation. For a repair enquiry that might include the item, a description of the problem and photographs. For a planned installation it may involve the location and approximate scope. Use the business’s actual requirements.

Name the person responsible for receiving enquiries and maintaining the contact details. If the route depends on an existing booking provider or other external service, identify it in the brief so its behavior and integration can be checked.

A custom backend, customer portal, payment system or automated quote is a separate functional requirement. Do not let a button label silently add it to a homepage design project.

Turn the five answers into a page outline

The questions are a planning framework, not a rule that the homepage must have five equal sections. Some answers can share a section; detailed information may belong on another page.

Customer question	Homepage role	Material to prepare
Can you help with my job?	Headline, supporting sentence and service introduction	Current offer, priority and scope
Is it available to me?	Short practical statement with a route to detail	Verified area and access arrangements
Why should I trust you?	Relevant work and evidence beside the claim	Approved photographs, context and genuine feedback
What happens before I commit?	Brief explanation of the first steps	Real process, inputs and conditions
What should I do next?	Primary CTA and contact expectations	Destination, requested information and responsible person

Use the homepage content checklist to review the remaining details, then the website navigation guide to connect the homepage with service pages, work and contact information.

Write a brief the designer can act on

Bring the answers together in a compact document. This is a reusable planning template; replace the prompts with verified information:

• Business and current page: name, URL and what has changed since the page was written.
• Main audience and situation: who is arriving and what they need to decide.
• Homepage objective: the specific understanding or action the page should support.
• Leading offer: the headline direction, supporting explanation and essential boundary.
• Evidence: approved work, images and feedback linked to the claims they support.
• Page outline: the purpose of each section and its next useful destination.
• Primary action: label, URL or contact method, expected response and required input.
• Content responsibilities: who provides each missing fact or asset and who approves it.
• Project constraints: agreed pages, existing tools, deliverables, timing and budget.
• Review question: how you will check whether the revised page is understandable.

For a fictional restoration workshop, the objective could be: “A new local homeowner understands that we restore wooden furniture, checks the collection area and knows which photographs to email for assessment.” That is specific enough to guide the first screen, evidence and contact route. It is an example brief, not a promise about conversion results.

Label unresolved assumptions. “Collection radius to confirm with owner” belongs in working notes; an invented radius should never reach the published page.

Validate the brief before visual refinement

Ask the business owner and the person handling enquiries to review the facts together. Resolve conflicting statements about scope, availability and process before they become polished page sections.

Then turn the outline into a simple draft and use the homepage comprehension test with someone unfamiliar with the business. Check whether the intended offer and next step are understood. A brief is useful when it supports a decision, and it can be revised when the evidence changes.

Keep the agreed facts and approval responsibilities with the handover. That makes it easier to update the page when services, coverage or contact arrangements change.

Common questions about homepage briefs

Can these five questions replace a full website brief?

They provide a focused starting point for the homepage. A larger project still needs a page inventory, technical requirements, existing integrations, accessibility considerations, content responsibilities and an agreed scope.

Should the homepage display the questions as an FAQ?

Only where that format helps the reader. Their main purpose is to organize the brief. A clear headline, service introduction, process section and CTA can answer them naturally without repeating all five as headings.

What if customers ask for information the business cannot publish yet?

Record the missing decision, its owner and how it affects the page. Explain genuine case-by-case conditions where useful, but do not fill gaps with guessed prices, response times or availability.

Bring a focused homepage brief to SavianoDesign

SavianoDesign’s Web Design service can turn a clear brief into responsive page layouts, with HTML, CSS and JavaScript implementation agreed as part of the project. Existing booking systems or other dependencies are assessed individually.

View the Web Design portfolio, then send SavianoDesign your homepage brief. Your current URL, the five answers and any unresolved content questions are a practical starting point.