Wix, WordPress or custom built: what's right for a small business?
Compare editing, maintenance, ownership and ongoing costs before choosing how your business website will be built.
Choosing a platform is easier when you start with how the website will be used and who will look after it. A builder, WordPress and a custom build can each be suitable, but they leave you with different editing tools, costs and responsibilities.
Start with your requirements
Write down the pages and features you need, how often you expect to update them, and who will make those updates. A small service website has different requirements from a shop with changing stock or a publication with several authors.
Where you already expect the business to grow in a particular direction, it is worth checking whether the chosen approach could support that change. This does not mean paying for every possible feature now, just avoiding a limitation you can already see coming.
A hosted website builder
A hosted builder gives you a page editor and a managed platform. It can suit an owner who wants to create and maintain the site themselves, especially when the required features are already available within the service.
Before choosing one, check the plan that includes the features you actually need, rather than comparing introductory prices alone. Ask how forms, payments, domain connection and extra users are handled.
It is also worth checking what you can export if you leave. Being able to download your content is not necessarily the same as being able to move the finished website to another host.
WordPress
WordPress offers a content-management system that can be extended with themes and plugins. It can be a useful option when frequent publishing and an established editing workflow are important.
The maintenance arrangement matters as much as the initial design. Establish who is responsible for updates, backups, plugin licences and resolving compatibility problems. A managed service may handle some of this, but it should be clear in the quote.
If a developer proposes WordPress, ask to see the editing experience as well as the public-facing design. You should understand which changes you will be able to make comfortably.
A custom build
A custom website lets the design and functionality follow a specific brief. It can suit a business with a distinctive presentation, an unusual workflow or integrations that need individual development.
Custom does not automatically mean faster, cheaper or maintenance-free. Those outcomes depend on the implementation and hosting. Ask how content changes are made, whether an editor is included, and what support will cost after launch.
The handover should explain ownership, access and how another developer could take over. These details are especially important if the original developer will be your main point of contact.
Compare the complete cost
For each proposal, add together:
- The initial design and build.
- Hosting, domain renewal and platform subscriptions.
- Paid extensions or third-party services.
- Routine maintenance and the changes you expect to request.
- Any likely migration work if you later change platform.
These totals only make a fair comparison when they cover the same period and requirements. An inexpensive starting plan may become the more costly option once you add a feature your business relies on.
Test the editor with your own tasks
During a demonstration, ordinary tasks such as changing a service price, replacing a photograph or correcting opening hours will tell you more about day-to-day use than watching a developer build an impressive sample page. Choosing the tasks yourself helps you see how the system would fit the way you work.
Check the result on a phone as well as the editing screen. Can you change a heading without breaking the layout? Can you save a draft before publishing? Is it obvious where an enquiry goes? If several people will use the editor, ask what each person will be allowed to change.
If you would rather send changes to your developer than edit the website yourself, that is a perfectly workable arrangement too. The important details are how long changes usually take, what they cost and who can help when your usual contact is unavailable.
Compare responsibilities, not just features
Use this as a conversation guide rather than a scorecard. The details of an individual service can differ substantially.
| Decision | Hosted builder | Self-hosted WordPress | Custom build |
|---|---|---|---|
| Editing | Use the provider's editor | Depends on the theme and editor setup | Ask whether a content editor is included |
| Hosting | Usually part of the platform | Choose a host or managed service | Depends on the agreed deployment |
| Maintenance | Provider maintains the platform | Clarify core, theme and plugin responsibilities | Define responsibility for code and services |
| Moving later | Check export and rebuild requirements | Plan transfer of files, database and configuration | Confirm source access and setup documentation |
WordPress.com and a self-hosted WordPress.org installation are not the same arrangement. If a proposal simply says “WordPress,” ask which service and plan are involved. Do not assume that everything is included because the underlying software is available without a licence fee.
What leaving the platform would involve
Wix states that its sites need to run on Wix's infrastructure; you cannot simply take the complete working site to another host. That does not mean your domain must be registered there, or that you do not own your content. It means that owning content and being able to relocate the finished system are different things. Read Wix's hosting and export explanation.
For any platform, ask what you would receive if you left tomorrow. The answer might include content exports, original image files, a domain transfer, source code or a database backup. Ask which parts would still need rebuilding.
With a custom build, “you own the code” is only part of a useful handover. Another developer also needs to know how to run it, which external services it uses and which accounts control the live site. Request that information before the relationship ends, not during an urgent outage.
Plan maintenance around the actual setup
For self-hosted WordPress, establish who takes backups and applies updates. WordPress's own update instructions advise making a backup before updating. A backup should also have a known recovery process; a file somewhere in an account is less useful if nobody knows how to restore it.
A hosted builder reduces some platform administration, but you still need to maintain your content, account access and any business processes connected to it. A custom site also needs an agreed support arrangement, even if it has no traditional plugin dashboard.
Ask what happens when a form stops working or a connected booking service changes. Is fault investigation included, and are third-party charges separate? These questions are often more important than a long list of features you will rarely use.
Choose for the next realistic stage
Avoid selecting a complicated system solely because you might need it one day. Equally, mention a concrete plan to start selling products or introduce customer accounts, because that could affect the recommendation now.
A shortlist of current requirements, likely near-term changes and who will maintain the site is enough to compare options. The website cost guide helps compare the complete proposal, while the preparation guide explains what to bring to the first conversation.
Make the choice around the business
Look at working examples, try the editor where possible and ask how your particular requirements will be handled. The platform name alone will not tell you whether customers can understand your services, use the site on a phone or complete an enquiry.
If your current platform already supports those tasks, improving the content or layout may be more useful than rebuilding on a different system.
