Most "platform problems" are content, maintenance, or strategy problems wearing a disguise, and switching platforms moves the disguise, not the problem. The stale pages board the moving truck, and the invoice runs four figures. Yet the platform conversation arrives in nearly every small organization eventually, usually when a new board member, a new director, or a persuasive vendor decides the current site "looks dated" and names a different product as the cure.
Episode 6 of The Web Managers Podcast is about making that decision honestly, whether you are choosing a platform for the first time or living with one you inherited. This post is its companion: the five questions the episode uses instead of a feature list, the three-year math that puts the "free" option in perspective, the reason plugins belong in a Security Month discussion, the myth about custom builds, and a ninety-second quick win that shows you what any stranger can already see about your site.
Why this one is personal
Starting in 2008, I built and managed more than five hundred client websites on a platform called Business Catalyst. Adobe later acquired it and, in 2018, announced it would close. I still had a handful of client sites there when it finally shut down in 2021, and every one of them had a planned migration waiting. Not one suffered an outage. That experience is why the episode's central question is the one I now ask of every platform pitch: what does it cost to leave?
Five questions instead of a feature list
A content management system (CMS) is the software that lets people update a website through an editing screen instead of writing code. Every major platform is a CMS at heart, so the episode sets the marketing aside and uses five questions. What will it cost over three years, not this month? How much control do you have over design, data, and function? How much maintenance lands on you? How locked in do you become? And how ready is it for commerce, if selling is part of the mission?
The five platforms you are most likely to meet fall into two families. Self-hosted WordPress is open-source, owned by no vendor, and installed on hosting you control; it offers near-unlimited control and hands you the maintenance. Squarespace, Wix, Webflow, and Shopify are hosted platforms, where the software, the hosting, and the maintenance come bundled and the site lives in the vendor's building on the vendor's terms. For accidental web managers, the maintenance question is usually the quiet decider: a hosted platform's higher subscription is often cheaper than the hours responsible WordPress ownership requires.
The honest math
The episode works one example over three years for the same ten-page site with a blog and a contact form, rounded. A hosted platform's business tier, plus the domain, lands around nine hundred dollars. Self-hosted WordPress, with quality hosting, a premium theme, plugin licenses, and occasional professional help, lands around nineteen hundred, in exchange for more control and a much cheaper exit. The "free" platform cost twice as much in cash.
Neither column wins on its own. Total cost of ownership (TCO), everything a choice costs over its life, does not make the decision for you; it makes the decision honest. And the line people zero out is their own time. Five hours a month fighting an ill-fitting tool is sixty hours a year, and at any honest rate, that number can change which column wins.
Plugins are a debt, not a purchase
A plugin, called an app on hosted platforms, adds a capability your platform lacks. Each one is also an ongoing obligation: it must be updated, it must stay compatible, and it widens the site's attack surface. Outdated plugins are among the most common ways small sites are compromised, which makes this a Security Month topic too. Before any install, ask four questions. Is it actively maintained? Is it widely used? Can you replace it without losing its data? Does the organization actually need it? Once a year, remove, not merely deactivate, every plugin without a good answer. A deactivated plugin still sits on the server as unpatched code.
Myth busted: "We need a custom-built site to look professional"
Visitors do not experience your code. They experience your words, your speed, and whether the site answers their question, and a well-chosen template filled with clear, current content delivers all three at a fraction of the cost. A custom build full of features only one developer understands is also a continuity problem wearing a nice design. Most of the time, "looks dated" is a theme problem, and a new theme on the platform you already have solves it.
Also in this episode
The Question Line takes on a colleague who insists the Wix site must move to WordPress "because that's what real businesses use," and the episode's fix, extend, or migrate decision tree takes that argument apart branch by branch. The Tool Minute covers BuiltWith, a free lookup that shows what any website is built on.
Quick win: scan your own stack
Run your website through a free stack scanner, Wappalyzer or BuiltWith.
Write down everything it reveals: the platform, plugins, analytics, and connected services.
Compare that list against your inventory and add anything missing.
Notice that everything the scanner showed you is visible to any curious outsider in about ninety seconds, including the kind with bad intentions.
Done looks like the scan run, the findings written down, and your inventory updated.
Get the worksheet. The M5.1 Platform Decision Matrix and TCO Calculator scores your current platform against any proposal and runs the three-year math with your real numbers. Bring it to the next meeting where someone says the platform is the problem. It is at Episode 6, Choosing Your Platform Without Regret, free with a Web Managers account at https://webmanagers.com/register, and it arrives with the weekly Web Managers letter.