Part One: Foundations
Chapter 1A Word Before We Start
We regularly meet business owners who are quietly disappointed by their website, and they have never said it out loud. They spent real money. They sat through the workshops, approved the colours, wrote the About page late at night (or used AI) to get it ready.
The website launched. Everyone they showed it to said it looked great. And then, slowly, nothing happened. The enquiries did not change. The phone rang about as often as before. The site became the thing you send people to after you have already convinced them, rather than the channel that does the convincing.
If that is your experience, then the problem often is that nobody ever wrote down what the website was supposed to do. Not what it should look like. Not what pages it should have. What it should do, in the same way that a team member does their job. Which visitors it is meant to attract, retain, and convert. What it is meant to tell them. What it is meant to get them to do. And what it was meant to take off your desk once they do it.
Then there's the feedback loop. What are the metrics that matter that need to be tracked. What page speed is optimal across desktop and mobile. The frequency of how often one reviews and optimises.
This guide is our attempt at Qode to write that job description down for you, in public, for free. It is what we walk our clients through before we quote anything, because a client who understands this asks better questions and gets a better outcome. We would rather you read all 17 chapters and never contact us than hire us without understanding what you are buying.
So there are a few things you can expect.
This is an opinionated guide. We will tell you which pages to cut and which numbers to stop reporting. You can agree or disagree. All of the advice here comes from watching businesses spend money on the wrong problems.
This is not a design guide. There is very little here about typography, logo, or colour. Don't get us wrong. Those matter. But they are downstream of the decisions in this book, and they are the part everybody already argues about.
This guide assumes you are not a large company. No brand team, no in-house developers, no budget to rebuild every two years. Everything here is written to be affordable at your size. That constraint is the point, not an apology.
Finally, this guide is honest about limits. Some of what follows will not apply to you. One business that sells one type product to one kind of buyer needs a much simpler system than a professional services firm with five services that depends on a referral network. Read past the parts that are not yours - we won't be offended.
Start with the next chapter. It is the shortest one.
Have a question about this chapter? Get in touch.