From 17+ years of hands-on engineering · 7 min read
What to Plan Before Building a New Business Website
A good business website starts before colours, fonts or page layouts. The most useful early work is deciding who the site is for, what those people need to understand and what action the business wants them to take. Clear answers make design faster, reduce unnecessary pages and help the finished website produce better enquiries.
In this guide
Start with one main business result
A website can support enquiries, direct sales, bookings, recruitment, local visits or customer support. It may do several of these, but one result should guide the first version. Without that priority, every department asks for equal attention and the homepage becomes a list of unrelated messages.
I ask what a useful visitor should do after understanding the business. That action might be requesting a quote, booking a call, buying a product or visiting a location. The answer influences the navigation, content order, forms and the information worth measuring after launch.
- Name the most valuable visitor action
- Decide which products or services matter first
- Choose how success will be measured
Describe the people the website needs to help
Useful website content is written for a real person with a question, not for an abstract target market. What problem brought them to the site? What makes them uncertain? What must they know before contacting you? A first-time buyer may need more explanation than an existing customer looking for support.
You do not need expensive research to begin. Sales calls, enquiry emails, search terms and common objections already contain valuable language. Collecting those examples helps me design pages around the questions customers actually ask.
- List common customer questions
- Record the words customers use
- Separate new prospects from existing customers
Plan pages around decisions, not company departments
Most business websites need a clear homepage, focused service or product pages, an about page that builds trust and a contact route. Extra pages should exist because they help a customer decide or complete a task. Copying an internal company structure often creates navigation that makes sense to staff but not to visitors.
For each proposed page, write one sentence explaining its job. If two pages have the same job, they may be one stronger page. If a page has no clear next step, it may need a better purpose before design begins.
Gather proof and practical details early
Customers look for evidence before they contact an unfamiliar business. Useful proof includes real work, specific experience, testimonials you are allowed to publish, qualifications, delivery details and clear answers about what happens next. Claims such as quality service are less convincing than concrete facts.
Practical details also prevent delays. Confirm the business name, contact information, service areas, pricing approach, privacy requirements and who can approve content. Decide who owns the domain, hosting, analytics and any accounts the website will use.
- Approved testimonials and project examples
- Accurate contact and location details
- Domain and account ownership
- One person responsible for approvals
Agree on scope before visual design
The first release should contain enough to achieve the main goal without carrying every future idea. Write down the required pages, forms, integrations, languages and content responsibilities. Put later ideas in a separate list so they are not forgotten or allowed to quietly expand the current budget.
A clear scope does not remove flexibility. It gives each new request a visible cost in time and money. When I plan a website directly with a client, I explain those trade-offs before they become rushed decisions near launch.