Key takeaways
- WordPress is software we respect and still work on. Keep it when the site is stable and someone owns Tuesday's updates.
- The expensive part is rarely the host. It is plugins, neglected updates, and an offer nobody wrote.
- CLICK.BLUE may repair, rebuild, or replace the install — the CMS is not the product, the working site is.
It is Tuesday. WordPress wants five plugin updates, a theme update, and a core bump you have been postponing since March. The site still loads. The contact form still arrives — you think. Nobody on the team wants to be the person who clicks Update and breaks the header.
That is the real WordPress vs custom website argument for most owners. Not a religion about open source. Not a lecture about "leaving WordPress for small business." The CMS is fine. We respect it. We still work on it. The cost is the plugin list, the update Tuesday, and the fact that nobody owns the offer the pages are supposed to make.
Tuesday is when the stack gets expensive
WordPress gives you a CMS, a theme, a plugin directory, and a publish button. Developers have shipped marketing sites, stores, and editorial systems on it for twenty years. If you want to log in, change a page, and hit publish, it is a strong admin. Keep a stable install. We will not move you for sport.
The cheap line on the invoice is hosting. The expensive line is everything that accretes around a site with no owner.
Plugins solve a morning and create a year. One for forms, one for SEO, one for backups, one for a popup, one for a slider the last freelancer loved. Each has a setting screen. Each has an update. Two of them will conflict after a core bump. The site that was "free" becomes the most expensive afternoon on the calendar.
Updates are a job. They are not a weekend. A neglected plugin list is how a working page becomes a hostage. If nobody is paid to own Tuesday, Tuesday owns you.
A WordPress agency alternative that only sells a rebuild is often skipping the cheaper question: is the install still honest, and does someone own it?
The CMS is furniture
WordPress is furniture. It holds the rooms. It is not the shop, the offer, or the person who greets the buyer.
A theme does not write what you sell. A page builder does not decide the homepage job. An SEO plugin does not create a page that is actually about one thing. Those jobs stay with whoever is producing the site — you, a freelancer who left in 2024, or a team that is still around.
"WordPress vs custom" is usually the wrong fork. A WordPress site can look considered. A custom stack can be overkill for five pages and a form. The useful question is whether the furniture still holds, and whether anyone is writing the offer the furniture is supposed to display.
We treat Webflow the same way. Software we like. Software we build on. Software that does not replace production. The CMS is not the product. The finished site is.
Repair, rebuild, or replace
When a WordPress site is hurting, there are three honest jobs. Pick one in writing. Do not do all three by accident.
Repair when the structure still holds. Pages load. Forms work. The theme can take a new section without a fight. The offer is still true. What you need is updates, a cleanup of dead plugins, a form that actually emails, titles that match the pages, maybe SEO on the URLs you already have. That is website care, not a new company.
Rebuild when the install is the job. The theme cannot be restyled without breaking. The page builder has five ways to make a heading and none of them match. Speed work never ends. You are paying for plugins that fight each other. The content is worth keeping. The system is not. A rebuild on WordPress can be the right call if the admin is still the admin you want.
Replace when WordPress is the bottleneck and you are honest about why. Nobody will own updates. The offer needs a structure the theme family cannot hold. You want a stack your next hire can actually run. Replacement is a full website on whatever fits — sometimes still WordPress, sometimes not. The reason has to be the work, not a mood about the logo in the admin bar.
| Signal | Repair | Rebuild | Replace |
|---|---|---|---|
| Forms and pages work | Yes | Mostly | Often not, or only inside a maze |
| Theme takes a new section | Yes | No — every edit fights | The theme is the ceiling |
| Someone owns updates | Yes, or you will hire that | You will, after cleanup | You will not, on this install |
| Offer is still true | Yes | Yes, trapped in a bad system | The pages no longer match what you sell |
| Content is worth keeping | Yes | Yes | Only the writing — not the templates |
If two columns feel true, choose the cheaper one that still solves Tuesday. Ambition is how a repair becomes a six-month rebuild with the same unread offer.
Who owns the updates
Write a name next to the install. Not a company. A person.
That person updates core, themes, and plugins on a schedule. They keep a backup from before the bump. They know which form plugin is load-bearing. They have a half day after updates to click the money paths: homepage, service page, contact, checkout if you have one.
If that name is you, and you will actually do it, keep WordPress. If that name is empty, you do not have a CMS problem. You have an ownership problem. A WordPress maintenance vs rebuild search is often this sentence in disguise: nobody owns Tuesday, and the site is starting to show it.
Managed website care is one way to put a name on that job. A capable person in-house is another. A freelancer you remember to email is a third, until they disappear. What does not work is hoping the host "handles it" while twenty plugins drift.
Maintain a plugin and dependency risk register
For every plugin, theme, integration, and custom module, record:
| Field | Question |
|---|---|
| Job | What user or business function does it perform? |
| Owner | Who understands and maintains it? |
| Criticality | What breaks if it fails? |
| Data | What information does it read or write? |
| Update path | How is it tested before production? |
| Alternative | Can the job be removed or consolidated? |
| Last review | Is the component still supported and needed? |
The register exposes duplicate form plugins, abandoned page builders, analytics scripts installed three ways, and “temporary” tools that became infrastructure. Remove before replacing. Many rebuilds are justified by complexity the team could first reduce.
WordPress.org’s hardening guidance is explicit that security includes the host, network, server, database, themes, plugins, and operational practices—not only the core CMS. Keeping core and extensions current, limiting privileges, protecting credentials, and maintaining recoverable backups are ownership tasks.
Stay on WordPress when the content model fits, the stack is governed, updates are testable, and the team values its ecosystem and portability. Rebuild the theme or plugin architecture when the CMS still fits but implementation does not. Replatform when the application, editor, performance, or governance requirements are fundamentally mismatched.
Do not migrate because another tool has a cleaner marketing page. Migrate because the risk register shows a recurring constraint the new architecture will actually remove.
Read WordPress.org — Security hardening and WordPress.org — Technical requirements.
The offer still has to be written
Even a clean install can fail for a boring reason: the pages do not say what you sell.
WordPress will publish whatever you paste. It will not interview the customer. It will not tell you the homepage is a paragraph about "solutions." It will not notice that the service you actually close lives under a blog post from 2021. Leaving WordPress will not write that offer. A new theme will not write it. A custom website will not write it.
Monday, before you shop a stack: open the homepage and the two pages that should produce inquiries. Write one sentence for each — who it is for, what they get, what to do next. If you cannot, the next project is copy and structure, not a CMS. If you can, and the theme cannot hold those sentences without a fight, then the furniture is the problem.
CLICK.BLUE will work on WordPress when the install earns it — a repair, a rebuild, a wrap around a site that still takes inquiries. We have launched more than a hundred websites; some of them still live here. The full website is designed, written, and launched. SEO is how the pages stay understandable. We will replace the stack when the system is the bottleneck. A CMS is not a strategy.
If you want a second pair of eyes on repair versus rebuild versus replace, start a scoped proposal. Bring the plugin list and the two pages that should be making the phone ring.
