Which platform your small business website should be built on

Three recommendations, three different platforms, and no way to choose

Three people recommended three different things. A cousin who does marketing swore by one builder. A friend's nephew, self-taught, pushed WordPress. A local agency quoted a fixed number for something proprietary. None gave a reason strong enough to settle it.

That's the ordinary version of this decision. Nobody chooses a platform to be difficult. A recommendation just arrives already decided, from whoever you asked first, and it rarely gets questioned past that point.

A platform decides more than how the site looks. It sets what you can do to the site later, who can touch it, and how hard it would be to leave — practical facts, not preferences, and a handful of direct questions settle most of them in a single conversation.

Who will actually be making edits, and what that rules out immediately

Ask who is going to log in and make changes six months from now: you, an employee, or nobody at all, because every change would route through whoever built the site.

That single answer eliminates most of the field on its own. If nobody in the business will ever touch the backend, a hand-coded site built for speed and polish is a reasonable choice. Editing the site yourself once it's live covers what that actually looks like day to day, and it's worth reading before this decision gets made, not after.

If you or someone on staff plans to swap photos, add a page, or post updates, the platform needs a dashboard built for a non-technical person to use without breaking anything. Not every platform offers one. Ask for a demo of the actual editing screen, not a sales page describing it.

Hosted platforms against software you install and run yourself

Two broad families exist. A hosted platform runs on the provider's own servers, bundled with hosting, and you log in through a browser with nothing to install. A self-hosted platform is software you or a developer install on hosting you choose separately, with more control and more responsibility that comes with it.

Hosted platforms tend to be simpler to start with, because fewer decisions sit in your hands at all. Self-hosted platforms tend to offer more room to customize later, at the cost of needing someone who actually knows the software to maintain it.

Neither family is automatically the right one. A simple service business with a handful of pages seldom needs the flexibility a self-hosted platform offers. A business planning heavy customization down the line can find a hosted platform's limits frustrating fast.

Ask who is responsible for keeping a self-hosted platform updated and secure once it's running. Software installed on your own hosting needs someone watching for updates, the same way a building needs someone checking the locks. A hosted platform folds that responsibility into the account itself, for better or worse.

What the platform decides about extending the site later

A platform is also a ceiling on what gets added next. Online booking, a members' area, a store, multiple staff logins — some platforms support all of it natively. Others need a separate tool bolted on, with its own login and its own account, sitting next to the site instead of inside it.

That gap rarely shows up on day one. It shows up much later, when the business wants to add a feature and discovers the platform can't hold it cleanly. What platform lock-in actually looks like covers the hardest version of this problem, where the site can't be moved somewhere else at all.

Ask what a given platform can and can't be extended to do before you commit. A business that has already grown into a wall it didn't know was there has a much harder conversation ahead of it.

Staff logins are worth asking about directly if more than one person will ever touch the site. Some platforms allow separate accounts with different permissions for different people. Others hand out one shared login for everyone, which turns into its own problem the day a business grows past a single person managing it.

Matching the platform to what the site has to do

A five-page site for a local service business and a site selling products online have almost nothing in common as builds, even though both get called "a website" in casual conversation. The platform that fits one well fits the other badly, and the reverse holds just as often.

List what the site actually has to do before you look at platforms at all: show information, take bookings, sell a handful of products, host a blog people actually read. Compare that list against what each option genuinely supports, not against what a salesperson claims it supports.

A short list, written down first, keeps the whole comparison honest. It also gives you something concrete to hand to anyone giving you a recommendation, instead of a vague description of "a nice website."

A platform chosen by the builder for their own convenience

A builder recommending the platform they personally know best isn't automatically a red flag. Most people work faster in tools they already understand, and that speed can genuinely benefit you.

It becomes worth questioning only when that convenience gets presented as the only option, without ever naming an alternative or explaining the tradeoff. Ask plainly: why this platform, over the others, for a business like mine specifically.

A builder with a good answer will name the tradeoffs, including the ones that don't favor their own preference. What the platform choice decides about who actually owns the finished site sits underneath this whole decision, and it's worth raising in the same conversation, before any contract gets signed.

A licensed theme layered on top of whichever platform you choose adds one more thing worth checking — licensing on a theme installed on top of the platform covers what that changes. And before any of this gets decided, it helps to settle choosing the platform versus choosing the person building it, because the two decisions tend to get made together whether you plan for that or not.

More from the blog

All posts