Website strategy: get every decision right before you build anything.
We see far too many websites that were designed and built before they were planned: every website that works starts with a strategy, not a design brief.
What we mean by website strategy.
A website isn’t a deliverable. It’s a decision you’ll live with for years.
Most website projects go wrong long before a designer opens a laptop. The site looks fine, but nobody agreed what it actually needed to achieve, who it needed to convince, or how anyone would ever find it. By the time that becomes obvious, the budget’s spent and the site’s already live.
Strategy is simply doing that thinking properly, and doing it first. Before you brief anyone on design, you should have clear answers on your goals, your audience, your content, your competitors, your budget, your timeline, and what happens after launch.
Get those right and the design decisions become straightforward. Skip them, and no amount of visual polish will fix the site underneath.
Start with the one thing your website actually needs to do.
Most sites try to be everything to everyone: a shop window, a sales tool, a recruitment page and an authority piece, all competing for the same homepage. Pick a primary goal and the rest falls into place around it.
- Generate enquiries – the site’s job is to get the phone ringing or the form filled in, and every page should be judged against whether it moves someone closer to that.
- Sell directly – ecommerce needs a completely different structure, checkout flow and product content to a services site, so don’t bolt one onto the other.
- Support bookings or applications – if people need to book a slot, apply for something or register, that process needs to be the easiest thing on the site, not an afterthought.
- Build authority and trust – some sites exist to reassure rather than convert immediately, and that changes what “good” looks like and how you measure it.
- Recruit – if hiring good people matters as much as winning clients, your site needs a genuine case for working there, not a token careers page.
Secondary goals can still be served, but only once the primary one is settled. Trying to optimise for all of them at once is usually how sites end up serving none of them well.
Know exactly who you’re building for.
Generic messaging gets generic results. Specific messaging gets remembered.
“Small businesses and larger organisations” isn’t an audience, it’s a shrug. You need to know who actually lands on your site: how much they already know, what they’re worried about, and what would make them trust you over the next tab open in their browser.
Different audiences need different proof. A first-time visitor with no context needs the basics explained plainly. A visitor who’s been referred by someone they trust needs almost none of that, and just needs a fast route to contact you. Build for both, and don’t force everyone through the same journey.
This also decides your tone of voice. A website for a technical, expert audience can be direct and skip the reassurance. A website aimed at people making an emotional or high-stakes decision needs warmth and patience built into the copy, not just the design.
Key questions to answer before you brief anyone
What’s your realistic budget?
A website isn’t a fixed-price commodity, it’s an investment that scales with complexity. Decide this honestly before you get quotes, or you’ll end up comparing wildly different products against each other.
What’s your actual timeline?
Properly built websites take anything from a few weeks to several months. If you need something live in two weeks for a launch that’s already been announced, say so early, because it changes what’s achievable.
Who are your real competitors?
Not just the businesses you compete with for clients, but the businesses you’ll be compared to online. Look at what they’ve done well, and more usefully, what they’ve done badly.
Who owns your content?
Someone needs to actually write it, someone needs to approve it, and someone needs to be responsible when it goes out of date. Decide this before the project starts, not halfway through it.
How will AI and search actually find you?
Search engines and AI tools both need to read your site to recommend it. That means clean code, genuine content and proper structured data, not just a nice-looking homepage.
What happens after the site goes live?
Launch is the start, not the finish. Decide upfront who’s responsible for updates, security, ongoing SEO, and making changes as the business moves on.
Plan your content before you plan your design.
The words on your website matter more than the layout around them.
Wireframes and visual design are far easier once you know what each page needs to say. Map the site’s structure first: how many pages, what job each one does, and how someone moves between them, before anyone starts designing screens.
Decide who’s writing the content and build in time for it. Copy is consistently the thing that delays projects, because it gets left until the design is finished and then rushed.
- A sitemap and page hierarchy agreed before wireframes
- A clear owner for writing and approving content
- One call to action per page, not five competing for attention
- A tone of voice that matches how your actual customers talk, not how the industry talks
Get the technical foundations right from day one.
None of the content strategy matters if the technology behind it holds you back.
A beautifully written site on slow, bloated technology won’t rank well, won’t get crawled properly by AI tools, and won’t convert as well as it should. The technical build isn’t a separate concern from the strategy, it’s part of it.
- Hosting built for your traffic and growth, not a shared box that falls over the day you get busy
- Genuine page speed, not just a good score on one test
- Structured data so search engines and AI tools can understand what your pages actually are
- A security and update plan, so the site doesn’t quietly become a liability
- Accessibility considered from the start, not patched in afterwards
Be realistic about budget, timeline and what comes next.
A new website is the start of a relationship with your business, not the end of a project.
Underestimating any of your goals, audience, content or technical foundations tends to show up later as a budget or timeline problem, not a strategy one. Build in contingency for content, for review rounds, and for the inevitable “actually, can we also…” conversations partway through.
The site that goes live on day one is rarely the site that performs best a year later. Plan for iteration: what you’ll measure, how often you’ll revisit the content, and who owns making changes as the business, the market, and AI search all keep moving.
If a previous developer told you something wasn’t possible in WordPress, what they almost certainly meant is that it wasn’t possible with the theme they were using. There is very little you can’t plan for properly from the outset.
