Custom CMS vs WordPress, Wix and generic page builders

Most CMS comparisons begin with a list of features. That is backwards. The useful first question is: what does your team actually manage?

If the answer is six service pages and a monthly article, WordPress, Wix or another established builder may be exactly right. If the answer is vehicles, prices, locations, approvals, bookings and customer records, a generic page editor may turn into a maze of plugins and workarounds.

A custom CMS earns its cost when the shape of the business matters more than the shape of a page.

The comparison in one table

What ownership really looks like on Wix

Wix's terms say users own their User Content. That is important and should not be misstated. Wix also owns the platform and its underlying intellectual property. Its own help centre says a Wix site must run on Wix's servers because the SaaS architecture relies on proprietary technology and does not support external hosting. Wix terms and Wix export guidance

That is not theft and it is not a hidden defect. It is the hosted-service bargain: Wix handles infrastructure, security monitoring and updates; you accept platform dependence. A business should choose that bargain knowingly.

Wix is often a good fit when:

• the site is mostly standard pages;
• one or two people edit it;
• integrations are available in its ecosystem;
• speed of setup matters more than architectural freedom;
• rebuilding elsewhere would be inconvenient, not existential.

What WordPress actually gives you

WordPress core is released under GPLv2 or later, and WordPress provides an XML export for posts, pages, comments, custom fields, categories and tags. That makes it fundamentally more portable than a closed hosted builder. WordPress licence and WordPress export documentation

But open source does not mean maintenance-free. WordPress documentation tells administrators to keep core, plugins and themes current, choose actively maintained extensions and keep backups before automatic updates. It also notes that plugins and themes are important points of weakness around the core platform. WordPress security guidance and auto-update guidance

WordPress is usually strong when:

• publishing is the main job;
• editors understand posts, pages, categories and media;
• a proven plugin cleanly handles the special requirement;
• the business has somebody responsible for updates, backups and testing;
• the site should be movable between competent WordPress hosts.

The common failure is not "WordPress is bad." It is installing a plugin for every unresolved business decision until no one understands which extension owns the form, schema, cache, redirect or customer record.

What a custom CMS changes

A custom CMS starts with records and actions, not blank pages.

For a dealership, the primary record might be a vehicle with price, mileage, status, photos and sale history. For a clinic, it might be a location, practitioner, service and booking rule. For a multi-location service business, it might be a location with hours, service area, staff, reviews and local landing pages.

The interface can then say:

• Publish vehicle, not "add custom post type."
• Approve price change, not "edit field group."
• Open a new location, not "duplicate page and replace tokens."
• Mark lead as qualified, not "update a spreadsheet and send an email."

That clarity is the benefit. The cost is that discovery, data modelling, permissions, migration, testing and documentation all have to be done properly.

When a custom CMS is overkill

You probably do not need one if:

• fewer than 20 standard pages change occasionally;
• one trusted person manages all content;
• there is no approval flow;
• the website does not share data with operational systems;
• a proven hosted tool already matches the workflow;
• the business process itself is still changing every week.

Building custom software around an unstable process does not stabilize it. It makes the uncertainty more expensive.

When generic tools begin to cost more than custom

Watch for operational symptoms rather than aesthetic frustration:

• staff enter the same information in the CMS, CRM and spreadsheet;
• an update requires remembering five pages and two plugins;
• permissions are all-or-nothing;
• nobody can tell who changed a price or policy;
• a plugin conflict blocks routine updates;
• the public site and the internal record regularly disagree;
• reporting requires manual exports and spreadsheet joins;
• a platform limitation prevents a revenue-producing feature.

One awkward workaround is normal. A stack of recurring workarounds is an architecture.

The hybrid answer is often best

"Custom CMS versus WordPress" is not always a binary choice. A team can keep WordPress for editorial content and build a separate operational service. A custom front end can read from a hosted headless CMS. A custom admin can send approved marketing content into several channels. The right boundary follows the data.

The United States digital-service group 18F recommends leaving room to decide which pieces to buy and which to build, using product-agnostic architecture and open data formats to reduce future switching costs. Its guidance is written for government, but the principle travels well to small business: buy the commodity; build the differentiator; integrate at a boundary you control. 18F technology budgeting handbook

Questions to ask before choosing

1. What are the ten most common things an editor needs to do?
2. Which records have fields and rules beyond title, image and body copy?
3. Which system is authoritative for each record?
4. Who may view, draft, approve, publish, delete and export?
5. Can the content and data be exported in a documented format?
6. Can another qualified developer operate the site?
7. Who owns the repository, database, hosting and vendor accounts?
8. What is the three-year cost, including maintenance and replacement risk? For our own work, the published pricing ranges are the honest starting point.

Choose the least complicated system that answers those questions cleanly. Sometimes that is Wix. Often it is WordPress. Occasionally it is a custom CMS. The honest recommendation depends on the work, not on which platform the agency prefers to sell.

Source check

Platform ownership, export and update statements were checked against the vendors' own documentation on August 22, 2026. Vendor documentation establishes capabilities and terms, not comparative superiority. The decision framework is editorial analysis based on those verified constraints and on our own stated ownership standard: code, data and infrastructure delivered under client control.

Sources

• Wix: Terms of Use
• Wix: exporting or hosting a site elsewhere
• WordPress: GPL licence
• WordPress: content export
• WordPress: security administration
• WordPress: plugin and theme auto-updates
• 18F: technology budgeting handbook