I spent years building WordPress sites. I know the platform inside out. I know when it's the right tool — and I've also watched plenty of clients struggle with it when it wasn't.
My honest take after all that: most small businesses on Vancouver Island don't need WordPress. And if I'd been more upfront about that ten years ago, I would have saved a lot of people a lot of headaches.
Let me break it down in plain English.
What WordPress actually is
WordPress is a content management system — software that runs on a server and builds your web pages on demand, from a database, every time someone visits. It started as a blogging platform and grew into a general-purpose tool that powers roughly 40% of the websites on the internet.
The big sell: you can log in, click around, and update your own website without knowing any code. That sounds great. And for the right use case, it is great.
The catch: all that flexibility comes with complexity. WordPress sites need to be kept up to date — the core software, your theme, every plugin, constantly. They need security monitoring because they're a common target for automated attacks. They can (and do) break when updates conflict. And they're slower by default, because every page load triggers a whole chain of software running in the background.
When WordPress is the right choice
WordPress makes real sense when:
- You're publishing new content constantly — a news site, a multi-author blog, a publication with daily posts
- You need a full online store with inventory management, product variations, and payment processing
- You have a team of people who all need to log in and edit the site independently
- You need a complex membership system, a learning platform, or user-generated content
For those things, WordPress does the job well. It's genuinely the right tool.
When it isn't
Here's the thing: most local small business websites aren't any of those things. They're what people in the industry call brochure sites — they say who you are, what you do, where you're located, and how to get in touch. Maybe a photo gallery. Maybe a pricing page. That's it.
For a site like that, you don't need a database. You don't need software running on demand. You don't need a CMS that has to be patched every two weeks. You need a clean, fast, well-designed site that loads quickly on mobile, looks professional, and sends the right signals to Google. That's a completely different problem.
What a static website is
A static website is just pre-built HTML files — no database, no server-side software, nothing running on demand. When someone visits, the server hands over the file. That's it.
The result is a site that:
- Loads much faster, because nothing needs to be "built" on the fly
- Is essentially unhackable, because there's no login, no database, nothing to exploit
- Doesn't break when software updates conflict
- Costs less to maintain, because there's less to maintain
The trade-off is that you can't log in and edit it yourself. Changes go through me. For the businesses I work with — a roofing company that updates its service list once a year, a café that changes its hours seasonally — that's completely fine. The contact me once or twice a year, I make the update, done.
- Frequent content publishing
- Online stores with inventory
- Multi-user editing teams
- Complex membership systems
- Clients who update daily
- Local service businesses
- Brochure & portfolio sites
- Restaurants, B&Bs, cafés
- Professionals & tradespeople
- Anyone who wants fast + simple
What this looks like in practice
I've built six demo sites that show exactly what a well-designed static site looks like for different types of businesses — a roofing company, a café, a wellness studio, a bed and breakfast, a professional services firm, and a restaurant. None of them look "static." They look like proper, modern business websites. Have a look — it's the fastest way to understand what I mean.
They also all load fast. If you open them on your phone you'll notice the difference compared to most small business sites you come across. That's not an accident — it's what you get when there's no WordPress in the way.
Six demo sites, six different businesses
The best way to understand what a static site actually looks like is to click through one. I've built demos for a café, a B&B, a roofing company, a wellness studio, a restaurant, and a professional services firm. Real designs, real layouts, real speed.
The one thing to ask yourself
Here's the simplest way to figure out which you need: how often do you genuinely need to update your website content yourself?
If the answer is "pretty much never" or "a few times a year" — static is almost certainly right for you. You'll get a faster, more secure site at a lower ongoing cost, and the fact that you can't log in yourself doesn't matter because you wouldn't have anyway.
If the answer is "every day" or "multiple times a week" — we should talk about whether WordPress or another CMS actually makes sense for your situation.
Either way, I'll tell you honestly which I think fits. I'd rather lose a sale than set someone up with the wrong tool. You can read more about how I think about this on the static sites explained page, or just send me a message and describe what you're trying to do — I'll give you a straight answer.
Or if you're ready to see what a new site would actually cost and include, the quote builder takes about three minutes.