By Kevin August·4 min read
This gets framed as a technology argument. It isn’t. Both WordPress and a custom-coded site can rank at the top of Spokane search results, and both can be catastrophically slow. We’ve fixed sites on each.
The real question is narrower and much more practical: who needs to be able to change this site, how often, and what happens if you want to leave?
Here’s how to answer it for your business.
What each one actually is
WordPress is a content management system. You get an admin dashboard, a theme controls how it looks, and plugins add features. Roughly 40% of the web runs on it. Anyone you hire will have heard of it.
Custom-coded — in our case usually Next.js — means the site is built as an application rather than assembled from a theme. There’s no dashboard unless one is built. Content lives in code or in a database you decide the shape of.
Webflow sits between them: a visual builder with cleaner output than most page builders, hosted on their platform.
Where WordPress wins
You edit constantly and don’t want to ask anyone. If you’re publishing weekly, running events, or changing prices often, an admin dashboard is genuinely worth a lot. This is the strongest argument for WordPress and it’s a good one.
You want a large hiring pool. Every Spokane agency and freelancer can work on WordPress. If we get hit by a bus, you have options on Monday.
You need a specific integration yesterday. Membership, events, complex booking, a particular CRM — there’s usually a mature plugin, and building the same thing from scratch is rarely worth it.
Budget is genuinely tight. A well-built WordPress site is typically the cheapest route to something that isn’t a template.
Where custom-coded wins
Speed you can guarantee. This is the real one. A custom build ships only the code the page needs. There’s no theme framework, no plugin stack, no page builder rendering nested divs sixteen levels deep. Sub-2.5s Largest Contentful Paint isn’t a stretch goal — it’s the default, and it stays that way because nothing can quietly add 400KB to it next Tuesday.
Nothing changes without you. No plugin auto-updates and breaks a layout. No theme update overwrites a customization. The site you launched is the site you have.
A much smaller attack surface. Most WordPress compromises come through outdated plugins. A site with no plugin layer doesn’t have that category of problem.
Exactly the structure search needs. No fighting a theme’s heading markup or a builder’s URL scheme. Schema, internal linking, and page architecture are all decided rather than inherited.
The honest trade-offs
Custom-coded: editing usually means a developer, unless a CMS is built in (we do build one when it’s warranted, and it costs more). The hiring pool is smaller. Cheap-and-fast isn’t on the menu.
WordPress: performance is an ongoing discipline, not a launch achievement. Plugins accumulate. Updates need doing. Left alone for two years, a WordPress site reliably gets slower and less secure — which is what a maintenance plan is actually for.
Webflow: good output, real speed, genuinely nice editor. But you’re on their platform at their pricing, and exporting is possible-but-awkward. That’s the trade, and it’s a reasonable one if you know you’re making it.
The Spokane-specific bit
Two things are true of this market in particular.
Most local WordPress sites aren’t slow because of WordPress. They’re slow because of a page builder — Elementor, Divi, WPBakery — stacked on a bloated multipurpose theme with fifteen plugins. WordPress with a lean custom theme is fast. That distinction gets lost, and it’s the one that matters. If somebody tells you WordPress is inherently slow, they’re overselling. If somebody tells you their Elementor build will hit Core Web Vitals, ask to see a live one.
Lock-in is more common here than it should be. Several local shops build on proprietary systems, or on WordPress configured so it only runs on their hosting. Ask directly: if I leave, what do I take with you? If the answer isn’t “everything,” that’s the answer to the whole question.
How to actually decide
Answer these four honestly:
- How often will content change? Weekly or more → WordPress, or budget for a CMS.
- Who’s making the change? Non-technical staff → you need a dashboard.
- Is speed a competitive advantage in your category? High-intent local service search, especially on phones → custom is worth the money.
- What’s the five-year plan? Selling the business, or expecting to switch agencies → prioritize portability above everything.
For most Spokane small businesses with a services site that changes a few times a year, either works, and the platform is not what determines whether you rank. How the site is structured matters more than what it’s built with — every time, without exception.
That’s why we’ll build on any of the three. We ask what you need to be able to do, and then recommend accordingly. If somebody leads with the platform before asking about your business, they’re telling you what they like building, not what you need.
Want a straight recommendation for your situation? Tell us what you’re working with — it’s a short form, and you’ll get an actual answer rather than a discovery call.
