Website Platform Choice: Builder, WordPress or Custom

Three families of platform sit behind every website, and the one that suits you is settled by what happens after launch.

Your platform is chosen by whoever maintains the site, not by whoever compares them. A comparison describes launch day, when every option looks capable and nothing has gone wrong yet. The consequence arrives months later, when somebody has to add a page, change a price, or work out why the contact form stopped sending. Three families sit behind that moment, each handing that person a different job.

Three Families of Platform Exist, and Each Is the Right Answer Somewhere

Hosted site builders run the software for you. Wix, Squarespace and Shopify host the site, patch it, back it up and ship features on their own schedule, while you work inside an editor and a design system they maintain.

WordPress is software you install and run on hosting you choose. It carries more of the web than anything else, because it stretches from a brochure to a publication, a membership site or a store, and because the database and the code stay yours.

Bespoke and headless means the front end is written for your site and the content lives in a system chosen separately. An Astro front end reading structured content from Sanity is one common shape, sitting on the line between static and dynamic. Nothing is inherited, so nothing is in the way, and nothing exists until it is built.

All three ship sites that rank, convert and load quickly. What differs is who can change them, and how far a change can go before it stops being possible.

Any feature you can name today, all three satisfy in some form, which is why comparison grids come out looking so even. The ones that decide this arrive later and unannounced: a campaign landing page nobody planned, a second language, a booking calendar. What each costs the person who receives it is the real difference, and whether the answer can be yes at all.

Hosted Builders Take the Maintenance and Keep the Ceiling

Everything that keeps a website alive belongs to somebody else here. Hosting, updates, certificates, backups and payment security are the vendor’s job, on published plan tiers that make it a subscription rather than a project.

The editing experience is the real strength, and it gets undersold as a compromise. These editors were built for the owner of the business, and the template systems behind them are maintained as products in their own right, so whoever wants a price changed usually changes it that afternoon.

Shopify earns a separate mention. In a store, checkout, payments, sales tax, shipping and inventory are the product rather than the plumbing, and Shopify has already solved that machinery. Building it again elsewhere rebuilds solved work.

What you take on is the ceiling. It sits at the edge of the vendor’s features and app market, and reaching it produces a no rather than a quote, because there is no hiring your way past it. Leaving is a rebuild for the same reason, since content comes out in an export format and the design does not travel.

Four situations make this family the right call outright. Physical products where the store is the business. A portfolio with one editor. A local service business with nobody technical involved. Anything with an end date.

WordPress Covers the Widest Range and Hands You Every Open Decision

The same software runs a five page brochure, a daily publication and a catalogue of thousands. That range comes from being open source software you host yourself, with an ecosystem large enough that booking, membership, multilingual, ecommerce and CRM synchronisation each exist several times over.

Content portability is the quieter advantage. Pages and posts written in the core block editor stay readable when the theme changes, so a later redesign restyles content instead of recreating it.

The cost of that range is the decisions it leaves open. Which host. Which approach to the design layer. Which plugins, and who updates them. Who watches for security disclosures. A hosted builder answered every one of those for you, and the comparison between the two runs on that difference. Here they are yours, and getting them wrong is how a WordPress site ends up slow, brittle or dependent on one person. The design layer is the one you feel first, and it now includes how much of a theme a model can write for you and how much still needs a person.

WordPress is the right answer when publishing is the plan, when the site has to exchange data with software you already run, and when you expect the business to change shape.

Write down the sentence first

In one sentence, describe the site as it will be in eighteen months and name the person who will be editing it. That sentence decides this more reliably than any comparison, because it describes the site you will run rather than the one you picture.

Bespoke Stacks Give You Everything Except a Starting Point

A bespoke front end is code written for one site. Astro is a common choice because it renders components to plain HTML and CSS and loads JavaScript only for the parts you explicitly mark as interactive, which means you control every byte a browser and a crawler receive. That extends to the structured data your pages emit, which on the other two families arrives from a theme or a plugin and here gets written by you.

The content side is usually a headless CMS. Sanity stores content as structured documents behind an API, with an editing interface you configure rather than accept, and that is what lets one backend feed a website, an application and a partner feed without the same content being written three times.

Three advantages here are real. Performance has no ceiling except the one you build in. Structured content is reusable across surfaces. The whole site sits in version control, so every change is reviewable and revertible.

The precondition is equally real, and it is the part that gets skipped. There is no theme and there are no plugins. Navigation, forms, search, sitemaps, redirects and editing fields all get built, then maintained, because frameworks and dependencies keep moving and the person who wrote it may not be there in a year.

This family is right when content has to appear in more than one place, when page speed is a requirement somebody holds you to, when pages come from a data source, and when you employ developers.

Four Questions Separate the Three, and Feature Counts Are Not Among Them

Each question below describes something you will live with rather than something you will evaluate.

The question worth asking	Hosted site builders	WordPress	Bespoke or headless
Who changes a page on an ordinary Tuesday?	The business owner does, in an editor designed for that person.	Whoever edits works in the block editor, and how far they get alone depends on how the design was built.	An editor updates content in the CMS, and anything touching layout goes to a developer.
Who is responsible when something breaks?	The vendor is, and it patches, backs up and renews certificates without telling you.	You are, or whoever you pay to be, because core, themes and plugins update separately.	You are, and the work resembles software maintenance more than site administration.
What do you hold if you walk away?	Your content in whatever export the vendor offers, and none of the design, which was theirs.	The database, the media library and the code, which run on any qualifying host.	The repository and the content outright, useful only to somebody able to run them.
Where does the ceiling sit?	At the edge of the vendor’s features and app market, where reaching it produces a no rather than a quote.	Far enough out that the plugin ecosystem reaches it first, and a developer can extend past that.	Nowhere except time, because anything the web can do can be built, and all of it has to be.

One trade runs through those rows, between what is handled for you and what stays available.

Locate Your Own Situation Before You Compare Anything

Three brochures produce three convincing cases, so this table runs the other way.

The situation you are actually in	Where it points	What you take on by going there
Physical products are the business, and checkout, shipping and stock are the daily work.	A hosted commerce platform, which is where Shopify is strongest.	Your storefront is assembled from that platform’s components, so a later move is a rebuild.
The site is a portfolio, one person edits it, and it will not grow into a library.	A hosted site builder such as Squarespace or Wix.	You accept the vendor’s ceiling in exchange for never patching anything yourself.
Publishing is the plan, and a growing library of articles is the asset being built.	WordPress, where content stays in portable core blocks.	You take on hosting, updates, and how the design layer gets built and maintained.
The site has to exchange data with software you already run, such as a booking system or a CRM.	WordPress, where an integration usually exists already or can be written.	You take on keeping those integrations working when either side updates.
One set of content has to appear on the site and somewhere else, such as an application or a partner feed.	A headless CMS such as Sanity, with a front end built against it.	You take on building and maintaining that whole front end, because none of it arrives with the CMS.
Page speed is a requirement someone will hold you to, and pages are generated from a data source.	A bespoke front end such as Astro, which ships static HTML by default.	You take on a codebase whose dependencies move, needing a developer next year.

Two rows often match at once, and the conflict is the useful part. A studio selling a dozen products while publishing a weekly journal matches the first row and the third, so the question becomes which is the daily work. If orders are, the commerce platform wins and the journal lives inside it. If the journal is, WordPress wins and the products sit in a plugin.

Building for the Site You Picture Instead of the One You Will Run

The common error runs in both directions. Somebody picks a bespoke stack for a five page site because it is what a serious company would have, then finds that a serious company also has the developer who keeps it running. Somebody else picks a builder because the site is small today, then stays on it through three years of growth it cannot carry, at which point the question has quietly become a rebuild rather than a redesign.

Both choices were made against an imagined site, which is what the sentence in the callout above is for. A quieter version is choosing whichever family your developer prefers. That is a fair tiebreak between two options that both fit, and a poor primary reason, because that person may not be maintaining it. Ask them who will, alongside the other questions worth putting to a vendor before you sign.

Book a free diagnosis

If you cannot tell which of the three families your situation points at, I will look at your current site, your plans for it and who edits it, then tell you which one fits and why.

Book your free diagnosis

A Good Choice Looks Boring Eighteen Months Later

Nobody talks about the platform. Requests take roughly the time they should, no single person is a bottleneck, and when the site gets faster or slower you can name the reason.

Wrong answers announce themselves just as clearly. Small changes turn into conversations. The phrase about the platform not letting you do something comes up more than once a quarter. You are paying for range you never reach, or reaching for range you never bought. Once the platform is settled the decisions inside it begin, and the first of them is WordPress Site Design: Builder, Parent Theme or Code. The structure of the site itself follows straight after, because the family you picked has already made part of that choice on your behalf.

Frequently Asked Questions

What is the best platform to build a website on?

No platform is best in the abstract. Hosted builders such as Wix, Squarespace and Shopify suit sites where nobody wants to run software. WordPress suits the widest range, particularly growing content libraries. Bespoke stacks suit sites needing full control of the front end and a developer to maintain it.

Is WordPress better than Wix or Squarespace?

WordPress covers more ground, which is not the same as being better. Wix and Squarespace handle hosting, updates, security and backups for you, and their editors are built for business owners. WordPress gives you range, portable content and ownership of the code, in exchange for every maintenance decision.

When should you use a headless CMS instead of WordPress?

Use a headless CMS such as Sanity when one set of content has to appear in more than one place, such as a website plus an application or a partner feed. Content stored once and queried by several front ends is the advantage. The cost is building each front end yourself.

What is Astro used for?

Astro builds websites that render to static HTML and send no JavaScript unless a component specifically needs it. It suits content-heavy sites where page speed is a firm requirement, and sites generated from a data source. Every component is written from scratch, so it needs a developer to build and maintain.

Can you move a website from Squarespace or Wix to WordPress?

Your content can move and your design cannot. Hosted builders provide content exports of varying completeness, so pages, posts and images generally transfer. The layout was assembled from the vendor’s own components, so it gets rebuilt rather than carried across, and old URLs need redirecting.

Do you need a developer to build a website on WordPress?

Not to start, because themes and plugins let a non-technical owner launch a working site. You do need somebody accountable for updates, backups and security afterwards, whether that is you, a maintenance arrangement or a developer. Sites that go wrong usually do so through neglect rather than software.

Continue Reading:

Next in this series

• WordPress Site Design: Builder, Parent Theme or Code, where your design layer is stored, because that is what changing direction later will cost.

From the library

• WordPress vs Shopify vs Wix vs Squarespace, Compared, those four set directly against each other.
• Technical SEO for Founders: What to Fix First, what the served page must get right on any platform.
• Core Web Vitals Explained for Non-Engineers, reading the performance numbers your choice produces.
• SEO for Startups: What to Do in the First 90 Days, what comes after the build question.
• Answer Engine Optimization: What AEO Actually Is, the standard your pages are judged against.

Explore TDM Insights Categories

• SEO
• AEO
• Content
• Case Notes