A practical guide to building a credible first website that converts, not just exists: what a small business site is really for, the page structure that turns visitors into enquiries, writing copy about the customer instead of yourself, and publishing something you own and can keep improving.
New businesses, freelancers, creators, local services, and founders launching their first web presence without a developer or designer.
- A clear read on what a first website is actually for
- A page structure that turns visitors into enquiries
- A publishable site you own and can keep improving
Most first websites are online brochures that sit there looking fine and doing nothing. The goal of a first business website is narrower and more useful than "have a website": it is to turn the people who land on it into enquiries, bookings, or customers. That comes down to a few decisions about purpose, structure, and words, and almost none of it is about design. This guide is about building the useful kind yourself.
A first business website exists to earn one action from a visitor: an enquiry, a booking, a call, a purchase. It is not a place to list everything about you; it is a path that takes a stranger from "who is this" to "I want to talk to them" and makes the next step obvious. Decide that single action first, because every page, headline, and button is either helping the visitor take it or getting in the way.
The common failure is treating the site as a brochure: an "about us", a wall of services, a gallery, and no clear reason for anyone to do anything. A brochure informs; a business website converts. The difference is not more content or better design; it is that a converting site is built backwards from the one action you want, so a visitor is never more than a glance away from taking it.
So before choosing colors or writing a word, finish this sentence: when someone leaves my site having decided to work with me, the thing they did was ___. Book a call, request a quote, buy the thing, join the list. That answer is the site’s job, and it makes every later decision easy.
A first site does not need many pages; it needs the right ones in the right order. A visitor arrives with three questions in sequence, and the site works when it answers them in that order and then asks for the action.
A local physiotherapist replaced a five-page brochure site, home, about, services, team, contact, with a single page: a headline naming the pain they fix, three patient results with real outcomes, a plain list of what a first appointment involves and costs, and a "book an appointment" button repeated three times. Enquiries went up, because the visitor was walked straight from "is this for me" to "book" without wandering through pages that answered questions nobody asked.
The single biggest lever on a first site is not the design; it is whether the words are about the customer’s problem or about you. Most first sites talk about the business, "we are passionate, we were founded in", when the visitor only cares about their own situation.
The practical rule is that the first thing a visitor reads should be about them, not you. Open with their problem or the result they want, prove you can deliver it, then tell them exactly what to do next. Your history, your values, your team are fine deeper down for the people who want them, but they are not what earns the enquiry, and putting them first is why so many capable businesses have websites that convert nobody.
A first website is not a one-time project; it is version one of something you will keep improving as you learn what your visitors respond to. So two things matter beyond launch: that you can publish it properly on your own domain, and that you can keep editing it yourself without going back to anyone.
This is where describing the site you want and getting it built beats both a rigid template and waiting for a developer: you can go from a clear idea to a fast, published page on your own domain quickly, keep the editable result, and grow it from a brochure into a booking flow or a real app when the business is ready. Describe who you help, the one action, and the proof you have, and get a first website that is built to convert and yours to keep improving.
The minimum that earns one action: a headline naming who you help and the result, proof you can deliver it (real results or named testimonials), enough detail to feel informed, and a clear next-step button repeated at each decision point. A first site needs the right few pages, or even one, not many.
Usually because it is a brochure, not a path to an action. It informs but never clearly asks the visitor to do the one thing you want, or the copy is about your business instead of the visitor’s problem. Decide the single action first, write about the customer, and put a clear ask at every natural decision point.
Not anymore, and design is rarely the reason a site fails to convert. What matters is the structure and the words, deciding the one action, answering the visitor’s three questions in order, and writing about their problem. You can describe the site and publish a fast page on your own domain yourself, then keep improving it.
A website is your public presence whose job is to convert visitors into enquiries; an app has users, data, and logic behind a login. Many first websites later need app features, bookings, a customer portal, a form that feeds a real system, so it helps to build on something that can grow from a converting page into that without a rebuild.