Website builder or self-hosted WordPress? Start with who will maintain it
Compare ownership, routine maintenance and exit options before choosing the platform for a small-business website.
Start here
Choose the setup your team can maintain reliably. A hosted builder can simplify day-to-day operation; self-hosted WordPress offers a different balance of control and responsibility. Test the work you must do every month, not just the first homepage.
Write down the job the website has to do
A five-page service website and a shop with hundreds of products are different projects. Before looking at designs, write a short brief: the main visitor action, the pages needed, the information that changes each month and the person responsible for changing it. A contact form, appointment booking, multilingual content or a members area should each have a named owner.
Separate requirements from preferences. Being able to update opening hours is a requirement; having twenty homepage animations is usually a preference. Ask a colleague to complete the three most important visitor tasks on a trial site. Record missing steps and confusing screens. This gives you evidence about usability before a polished demonstration influences the decision.
Compare the maintenance arrangement
Self-hosted WordPress is software installed with a hosting provider. WordPress.org describes a platform that can be extended with themes and plugins. WordPress.com is a hosted service with its own plans and boundaries. Other hosted builders have different terms, so do not assume one comparison describes the entire category.
For each actual shortlist, ask who handles software updates, security fixes, backups, restoring a failed update and support outside office hours. The answer may be the provider, a developer or someone on your own team. A service described as managed still needs a precise scope. Request a plain-English explanation of what happens if a plugin breaks the booking form on a busy morning.
Run a small maintenance rehearsal
Use the same test content on each trial: one service page, a form, a news item and several appropriately sized photographs. Have the future editor change a price, replace an image, correct a menu and publish a draft. Count the steps that require a developer. Then check the result on a phone.
Also rehearse recovery and handover. Can a second authorised colleague access the account? Where are the domain and renewal notices managed? Can you export the written content and original media? Keep domain registration, hosting and website editing as separate entries in your handover notes even when one provider supplies all three.
Make the decision with a one-year workload
Our practical comparison is a workload sheet, not a universal winner. List initial setup, monthly editing, updates, backup checks, form testing and annual renewals. Assign an owner and a realistic time allowance to each. Add developer support where the team cannot cover a task.
A useful final test is whether the business can keep the site accurate during a staff holiday. Choose the arrangement that makes the essential tasks manageable, then document a route out. More control is valuable when you will use it; fewer maintenance decisions are valuable when they let a small team keep the website current.
| Question | Evidence to request | Why it matters |
|---|---|---|
| Routine updates | Named responsible party and scope | Prevents maintenance gaps |
| Recovery | Restore process and backup access | Makes outages actionable |
| Editing | Trial completed by future editor | Tests the real workload |
| Leaving | Export and domain transfer procedure | Exposes switching friction |
Sources and further reading
Source details checked 2026-11-18. Product terms and availability can change; check the relevant seller or provider before ordering.
Editorial guidance, not a claim of hands-on testing. See our editorial policy for how we research guides. Our approach