Planning a website for an established service business

An established business brings more to a website project than a logo and a list of services. There are customers who already know the team, work the company wants more of and existing arrangements that still need to function.

Website planning connects those things before the design and build. It gives the people doing the work a basis for recommending the pages, content and functions, then checking whether they deliver the agreed job.

This guide suits a substantive marketing website: one that helps prospective customers assess the business and start a useful conversation. A small site whose main job is confirming contact details may need a simpler plan. If you are still deciding which build approach suits the job, compare custom websites, templates and AI builders.

Decide which work the website should help you win

Start with the next stage of the business, rather than giving every current service equal space.

You may want larger projects, recurring arrangements or more direct customers. Keep that aim specific enough for the designer to act on. “Grow the business” leaves the important choices open: which work, for whom and within what practical limits?

Review recent enquiries, quotes and customer questions with the people who sell and deliver the service. Separate evidence of what customers currently ask for from your decision about what to promote next.

A capability can remain available without becoming a major sales message. For example, repairs for existing customers may need clear support instructions rather than a public offer inviting new repair jobs.

Make those priorities explicit. Otherwise, copying the old service list into a better-looking website can preserve exactly the mix you wanted to change.

If the business itself is still deciding what it wants to be known for, resolve that direction before committing to the website's main message. Our repositioning guide covers that broader decision.

Work backwards from the customer's decision

Consider what a suitable prospect needs to understand before making contact. The answer usually reaches beyond the name of the service.

They may need to know whether you handle the whole job, work from supplied specifications or coordinate other providers. A project photograph can show the finish while leaving those responsibilities unclear.

Plan the explanation and its proof together. If you want to be chosen for managing a complicated job, show what your team actually managed. A list of equipment demonstrates a different kind of capability; it need not become a menu the customer must choose from.

Then decide the useful next action. An experienced returning customer arranging familiar work may need a quick contact route. A new buyer may need room to describe the problem and ask for a recommendation.

Neither route requires the visitor to do your technical assessment first. Ask for information they can reasonably provide and that changes the first response. Keep expert recommendations with the people responsible for making them.

Those decisions give the page plan a reason. The homepage introduces the company and priority work; service pages explain the actual offers; relevant projects support the claims. Other pages earn their place through a distinct customer or business need.

Example: a fitout company planning for larger projects

Consider a fictional commercial fitout company that wants more complete office-fitout projects. It also handles small follow-up repairs for existing customers, but does not want to advertise a general repairs service.

For this example, customers appoint their own designer. The fitout company coordinates the agreed site works. Its website must explain that division before “complete fitout” suggests design is included.

That first work-priority decision now affects the explanation, proof, contact route and upkeep. It also leaves the developer meaningful questions to resolve, including how the proposed editing and enquiry flow should work.

The company does not need to choose a portal, new CRM or a particular CMS to complete this initial plan. If a later requirement justifies one, assess it against the customer task and agree its scope.

Agree who supplies the knowledge and who writes the website

A plan needs people as well as pages. Identify who can confirm the service facts, supply genuine project material and approve its public use.

One person can coordinate the collection without being expected to know every answer. The operations lead may check responsibilities while the marketing lead gathers photographs and confirms permissions.

Check the material against the work you want to promote. A folder full of old projects can be accurate but poorly matched to the new direction. A strong recent example may need a factual account and permission before it can appear.

Keep proof and illustration separate. Use genuine work to support project claims. An illustration can explain a process, but should not imply that a pictured job was completed for a customer.

Copywriting responsibility also belongs in the scope. With SOL, we write the agreed website pages from your business information, rough notes and source material. You supply the knowledge and check factual accuracy; you do not need to arrive with finished sales copy.

Mark missing inputs against the decision they affect. An uncleared project photograph holds that use of the photograph. An unresolved service inclusion holds the affected promise. Neither should disappear beneath a general “content to come” note.

Describe the tasks before choosing the tools

“We need a CMS” is a starting request. “Our marketing coordinator needs to add approved projects without changing the page layout” gives the provider something to design and demonstrate.

Use that level of detail for both customers and staff. Identify the task, the person doing it, the information involved and what should happen afterwards.

If an enquiry goes to the office, decide who takes responsibility until the right person follows it up. If staff edit a service, confirm who approves a changed claim and how the correction reaches the public site.

An existing inbox, booking tool or customer system may already do its job well. Give the provider its purpose and known constraints, then ask them to assess the connection. Changing the website does not automatically justify replacing everything behind it.

The designer and developer should recommend the structure and technology, check feasibility and explain the trade-offs. Your job is to make the business requirement clear and confirm whether the recommendation meets it.

Bring design references too, with a reason for each. You might like how one site explains a complex offer or how another presents project detail. That is more useful direction than asking for a copy of the whole site.

Plan the changeover and the checks after it

For a rebuild, identify what customers and staff still rely on before retiring the old website. Useful pages, downloads, contact routes, email and connected services need deliberate treatment.

Ask the responsible provider to assess the old addresses and any technical transfer work. Preserve relevant search, enquiry and outcome records before the change, with gaps recorded honestly. Those records give the later review a starting point.

Agree what you will inspect on the working preview. A customer should be able to understand the priority offer, find relevant proof and make contact. The receiving team should get a usable request. Staff editing should work as agreed.

Your provider owns its contracted technical checks. Ask for the results and unresolved issues, while your team confirms business facts and customer responsibilities. Looking through the design does not replace either review.

Then distinguish launch acceptance from commercial success. Launch checks establish whether the agreed website works. Later review asks whether it supports the work you wanted to win.

Agree who maintains enquiry assessments and sales outcomes, when they review them and who can approve resulting changes. Visits, contact actions, suitable opportunities and won work answer different questions. Unknown sources and pending decisions should stay visible.

These decisions can develop together as the provider checks the plan. The order explains their dependencies; it is not a fixed production timetable or a requirement to settle every detail alone.

Choose the planning task you need next

Use the guides below for the detailed work. Each produces a different part of the plan, so start with the decision that is still unresolved.

Set the direction and scope

• How to write a useful website brief: turn business priorities, constraints and open questions into a brief a provider can work from.
• Which pages does your business website need? Build a page plan that separates public pages, reusable layouts and content entries.
• One website, different customer groups: decide which information stays shared and when a different buying situation needs its own route.

Work through the content and customer experience

• What to prepare for your new website: collect useful material with its intended use, factual reviewer, permission and outstanding gaps.
• What should be on a service business homepage? Work through an annotated opening-to-enquiry explanation, including what belongs deeper in the site.
• What belongs on a service page? Explain one offer through its scope, responsibilities, proof and next action.
• What should your team be able to edit? Specify real editing tasks, controls and the demonstration needed to assess the setup.
• What should your website enquiry form ask? Choose what to ask now, what can wait and who takes responsibility for the response.

Prepare for launch and later decisions

• What to keep when rebuilding your website: decide what to retain, update, merge or retire, with a destination and responsible person.
• How to check your website before approving launch: turn key customer and staff tasks into observable acceptance checks.
• How to tell whether your website is working: connect suitable enquiries and later outcomes to maintained records and practical review decisions.

Bring the plan into the website discussion

You can start with the decisions you know and the questions you need help answering. Include the available budget, any genuine deadline and the people who can approve the work.

Before committing, review the provider's recommendation against those priorities. Confirm the pages, copy, functions, content responsibilities and ongoing arrangements in writing. A suggested feature is not included simply because it appeared in the initial discussion.

Our Web Development service brings research, agreed-page copy, design and development together. We can work through the website plan with you and put the recommended build into an agreed scope. Ongoing SEO and other continuing work are separate choices.

Bring your current website and tell us which work you want it to help win.