What Should Your Website Actually Do?
Most businesses can't answer this. That unanswered question is the root cause of most website problems.
Here is a question most business owners can't answer cleanly: what is your website supposed to do? Not “showcase what we offer.” Not “tell people about us.” What specific action should a specific person take after arriving at your site — and is everything on the site built around making that happen?
Most websites exist to explain. They describe services, show credentials, list prices, and tell the story of how the business started. Explanation is not a job. A website that exists to explain will have traffic and no conversions, because it was never built to convert — it was built to inform.
“If you can't say in one sentence what your website is supposed to do, it's probably not doing it.”
The one-sentence test
A website has one primary job. That job should be expressible in one sentence:
“This website exists to generate phone enquiries from commercial property owners in Brisbane.”
“This website exists to drive booking requests from women aged 30–50 who want a consistent, senior colourist.”
“This website exists to sell the starter package directly, without a sales conversation.”
If your sentence looks like “this website exists to show people what we do,” you don't have a job — you have an explanation. And the site probably reflects that.
Leads and traffic vs. taking purchases online
For most service businesses, the site's job is to generate qualified enquiries — people who understand what you do and are ready to have a conversation. The sale happens after the site has done its job. This means the site's single most important element is the call to action: what do you want them to do, and have you made it easy enough to do it?
For businesses that can package a service for direct purchase — or that sell products — the job is different. E-commerce requires a different structure, a different platform consideration, and a different content strategy. The site needs to handle objections, build confidence, and close a transaction without a person in the room. That's a harder brief, and it demands more from the site.
Trying to do both — generate leads and sell online — without a clear primary job usually means doing neither well. Decide what the site is primarily for before anything else gets decided.
The platform question
Platform is not a starting point. It's a consequence of the brief. The right platform is the one that lets the site do its job without requiring technical expertise to maintain and without limiting what you need to do in the future. Here's the honest picture:
WordPress
Flexible and powerful. The right choice when the site has complex requirements — custom post types, integrations, large content libraries. Requires ongoing maintenance and at least some technical confidence. In the wrong hands, it becomes a security liability and an update backlog.
Squarespace / Wix
Good for simple brochure sites where the job is straightforward and the content won't change much. Easy to manage without a developer. The limitations become a problem when you outgrow them — and they're hard to migrate off cleanly.
Shopify
Purpose-built for e-commerce. If you're selling products or packaging services for direct online purchase at volume, Shopify is the right infrastructure. If you're a service business with no online store, it's the wrong tool.
Custom build
Right when the site has a specific job that template platforms can't do cleanly — a booking-heavy workflow, a complex integration, a performance requirement that off-the-shelf themes can't meet. More expensive upfront. No dependency on a platform's decisions about what features to support.
The platform decision should only be made after the brief is defined. Choosing a platform first — because someone recommended it, or because it looks familiar — is choosing a constraint before you know what the site needs to do. Sometimes that constraint is fine. Sometimes it's the reason the site fails.
Your options once the diagnosis is clear
Once you know what the site is supposed to do, who it's for, and what they need to see before they'll act — the options become clear:
Fix what you have
If the platform is right and the structure is workable but the copy and calls to action are wrong — fix those first. It's the cheapest path and often produces the fastest result.
Rebuild on the same platform
If the structure is wrong but the platform isn't limiting you — a rebuild with a proper brief, right content, and right hierarchy. Same technology, different architecture.
Migrate platforms
If the platform is limiting the site's job — slowing it down, making it hard to manage, or unable to support what you need — migration is a structural fix worth the disruption.
Full rebuild from brief
Strategy, structure, content, and platform all reconsidered together. The right starting point when the current site has too many problems to patch — or when the business has changed enough that a clean start is faster than fixing everything.
None of these decisions should be made without first answering the brief. And the brief starts with one question: what is this website supposed to do?
Define the brief first
Design cannot start without it.
My Pixel Strategy starts every website engagement with a structured discovery — audience, job, content, platform, and scope — before any design decisions are made. The brief determines the result.