Planning
How to Plan a Business Website Before Anyone Writes Code
A practical way to work out what your website needs to do, who it is for and which pages it should have — before design or development begins.
Most website problems don’t start in the code. They start earlier, when a project begins with “we need a new website” and nobody has agreed what the website is actually for. A little planning at the start saves time, money and frustration later — and it makes every design and development decision easier.
Start with the goal, not the pages
Before listing pages, write down what a successful website would change for your business. Be specific. “Look more professional” is a reasonable wish, but it is hard to design for. “Get more wholesale enquiries from retailers” or “let customers order online instead of messaging us” gives the whole project a direction.
Most business websites have one main goal and a few supporting ones. Decide which is which. When two ideas compete for space on the homepage later, the main goal settles the argument.
Know who will visit and why
Think about the different people who will arrive on your website and what each of them wants to do. A restaurant might have diners checking the menu, families planning an event and companies looking for catering. A manufacturer might have buyers comparing suppliers and job applicants looking for information.
- Who are they, and what are they trying to find or do?
- What questions do they usually ask you by phone, email or WhatsApp?
- What would make them trust you enough to get in touch or buy?
- Are they mostly visiting on a phone, or at a desk?
The questions customers already ask you are a valuable planning tool. If people keep asking about delivery times, minimum orders or opening hours, the website should answer those questions clearly.
Map the pages and how they connect
With goals and visitors in mind, sketch a simple sitemap: the list of pages and how they are grouped. Keep it as small as you can while still answering the important questions. Every extra page needs content, maintenance and a reason to exist.
Then think about journeys. If a new visitor lands on the homepage, what is the shortest sensible path to the action you want them to take? If they land on a product or service page from a search engine, can they still find their way to contact you?
List the features — and mark the essentials
Write down the functionality you need: contact forms, online payments, booking, a store locator, a blog, multiple languages. Then mark each one as essential for launch or nice to have later. This single step does more to keep a project on budget than almost anything else.
Choose the platform last
Custom development, Shopify and WordPress are all good choices for the right project. The right one depends on what you sell, how often you update content and which features you need — which is exactly why the platform decision comes after planning, not before.
Write it down in one page
Finally, summarise everything in a short brief: the main goal, the key visitors, the page list, the essential features and any important dates. It doesn’t need to be polished. A clear one-page brief helps any developer give you an accurate estimate and keeps everyone working towards the same result.