How I Plan a Small Business Website Before Writing Any Code

When a small business owner messages me about a new website, the first thing they usually send is a design they like. Sometimes it is a competitor's site, sometimes a template, sometimes a screenshot from Instagram. That is useful, but it is not where I start. Before I open my code editor, I spend time planning what the site needs to do, who it is for and what goes on each page.

Skipping this step is the most common reason a website project drags on for weeks or ends up being rebuilt a year later. Here is the planning process I follow for almost every small business site I build, and the questions I ask before I write a single line of code.

Start with one clear goal

I ask every client the same question first: what should a visitor do after landing on your website? The answer is usually one of a few things:

• Call or send a WhatsApp message
• Fill in a contact or quote form
• Book an appointment
• Buy a product
• Visit a physical shop or office

Most sites have a main goal and one or two smaller ones. A plumber wants calls. A clinic wants bookings. A consultant wants form enquiries. Once I know the main goal, every page decision gets easier, because I can ask whether something helps the visitor reach that action or just gets in the way.

If a client tells me the goal is "to look professional", I dig a little deeper. Looking professional is important, but it is a means, not the end. Usually the real goal is that people trust them enough to get in touch.

Know who the visitors are

Next I want to understand the people who will actually use the site. I keep this simple. I ask the owner to describe their last three or four customers: where they found the business, what they asked about first and what made them decide.

This tells me a lot. If most customers find the business on their phone through Google Maps, the mobile layout and the phone button matter more than anything on desktop. If customers always ask about prices first, the site needs a clear pricing section or at least a starting price. If they ask whether the business serves their area, the service areas should be easy to find.

I also ask what questions the owner answers again and again on the phone. Those answers almost always belong on the website.

Map out the pages before the design

With the goal and the visitors in mind, I write a simple sitemap. For most small businesses it looks something like this:

• Home: what you do, who you do it for, proof that you are good at it and a clear way to get in touch
• Services: one page per main service if each one is something people search for on its own
• About: the people behind the business, with real photos
• Work or reviews: examples, testimonials or case studies
• Contact: form, phone, WhatsApp, address and map if relevant

I resist adding pages just because other sites have them. A five page site where every page has a purpose works better than a fifteen page site full of thin content. It is also cheaper to build and easier for the owner to keep up to date.

Separate service pages are worth it

One thing I push for is a separate page for each main service. If a plumber offers boiler installation, leak repairs and drain cleaning, people search for each of those differently. One page per service gives each one its own title, description and content, which helps with search and makes it easier for a visitor to find exactly what they need.

Gather the content early

The biggest delay in small business website projects is almost never the code. It is waiting for content. Logos, photos, service descriptions, prices, team bios and testimonials all take time to collect.

So I ask for content during planning, not after the design is done. I send a short list of what I need for each page. If the client does not have something yet, we decide together whether I write a first draft, whether we use a placeholder for launch or whether that section waits.

I am careful about photos. Real photos of the team, the shop, the work and the products build far more trust than generic stock images. Even photos taken on a decent phone in good light are usually better than a stock photo that visitors have seen on ten other sites.

Sketch the layout on paper

Before any design software, I sketch rough wireframes. Boxes for the header, the hero, sections and buttons. Nothing pretty. The point is to decide the order of information on each page.

For a home page, a typical order looks like this:

1. A short headline that says what the business does and where
2. A main button for the primary goal, such as "Call now" or "Get a quote"
3. The main services, each linking to its page
4. Proof: reviews, numbers that are true, or photos of real work
5. A short section on how working together goes
6. Common questions
7. A final call to action and contact details

Sketching on paper takes maybe an hour and saves days of back and forth later, because the client can react to the structure before anyone gets attached to colours and fonts.

Decide what the owner needs to edit

This question shapes the technical side more than anything else. I ask the owner what they expect to change after launch and how often.

If they only need to update a phone number once a year, a simple static site is fine and very fast. If they want to add blog posts, portfolio items, products or job listings regularly, they need an admin panel. In that case I plan which parts are editable from day one, so the database and the admin are built around their real needs instead of being bolted on later.

I also ask who will be doing the editing. An owner who is comfortable with computers and a staff member who has never used a CMS need very different admin screens.

Plan the basics for search and speed

A few decisions are much easier to make at the start than to fix later:

• Page titles and URLs: I plan a short, readable URL and a title for each page, based on what people actually search for
• Local details: business name, address and phone written the same way everywhere, matching the Google Business Profile
• Image sizes: photos resized and compressed before upload, so the site stays fast on mobile data
• Forms and email: where form messages go and how they are sent, so they land in the inbox and not in spam
• Analytics: what we want to measure, like form submissions and phone clicks, so tracking is set up at launch

None of this is complicated, but if it is not planned, it tends to get forgotten until a client asks why their site does not show up on Google or why they never receive form messages.

Agree on scope in writing

The last step of planning is writing down what is included. Number of pages, features, who provides content, how many rounds of changes, and what happens after launch. I keep it to a page or two in plain language.

This is not about being strict. It protects both sides. The client knows exactly what they are getting, and I know exactly what I am building. When a new idea comes up halfway through, which always happens, we can look at the list together and decide whether it fits now or goes into a second phase.

What this looks like in practice

For a typical small business site, planning takes a day or two of conversations and a few hours of my own work. Then the build goes faster and smoother, because most decisions are already made. There are fewer surprises, fewer redesigns and a much better chance the site actually brings in calls and enquiries.

If you are planning a website for your business and want a second opinion on your page list or goals, send me a message. I am happy to look at what you have and tell you honestly what I would change.