Most website projects start in the wrong place. A designer shows three homepage concepts, the owner picks a favourite, and the words are squeezed in at the end. The result often looks lovely and says very little.
Sites that sell are built the other way around. The design serves the message, and the message comes from customers. This is the process we follow, with the reasons behind each step.
Contents6 sections
Start with customers, not colours
Before anyone opens a design tool, we collect what customers actually say. Short interviews with the owner and whoever answers the phone. A sample of recorded sales calls. Your reviews and your competitors’ reviews, which are a goldmine of what people care about and what disappoints them.
Then the search side: which queries already bring visitors, what people in your area search for and what the sites ranking above you do well. By the end we know the questions a customer needs answered before they will pick up the phone.
Plan the pages and the paths
Research turns into a sitemap: a page for every core service and area, proof pages, contact paths. For each page we write down who it is for, the one question it answers and the action it asks for. We explain the thinking in more detail in how website structure affects sales.
Write before you design
Next comes a copy document with the real words for every key page: headlines, the promise, the proof, the answers to objections, the calls to action. Designing around real text reveals problems early. A headline that needs three lines, a service with nothing specific to say, a missing price range.
Lorem ipsum hides every problem a website has.
Owners often find this stage the most useful, because it forces decisions about the offer that were never written down.
Design that makes the message easy to take in
Only now does visual design start, and it starts on a phone screen. Hierarchy first: what should the eye see first, second and third on each page? Then brand, typography and real photography. Components are designed once and reused, so the site stays consistent as it grows.
Accessibility is part of the design brief from day one: contrast, focus states, readable type sizes. It is far cheaper than fixing it later, and in Ontario it is a legal requirement for organizations with 50 or more employees.
Build, test, then launch
- Pages load quickly on mobile data, with compressed images.
- Every form and phone link is tested and reaches a real inbox or CRM.
- Conversion and call tracking fire correctly.
- Old URLs redirect to their new equivalents, so rankings carry over.
- The sitemap is submitted to Google Search Console and the Google Business Profile points to the right pages.
- Privacy policy, cookie consent and email consent checkboxes are in place.
Redirects deserve a special mention. Skipping them is the most common reason a new website loses traffic in its first month.
The first 90 days after launch
Launch is the start of the useful data, not the end of the project. For the first three months we watch where visitors enter, where they hesitate and which pages produce enquiries, then adjust copy, layout and calls to action.
This is also when the site starts to grow: new service pages, projects added as they finish, answers to questions the sales team keeps hearing. That rhythm is how our website projects turn into long-term sales tools rather than one-off launches.
