WordPress, Webflow or a custom website: How should an SME choose?

WordPress, Webflow or a custom website? For an SME, the decision starts with the next edit rather than a list of technical advantages. Who publishes a new service, corrects a telephone number and updates four language versions? If only the original developer can do those things, even an inexpensive website may be awkward to operate.

All three approaches can produce a useful site. The right choice depends on editorial work, features, responsibilities and handover. Ask to see more than the finished homepage. Have the person who will maintain content make a real change. That exposes requirements which a polished demonstration with prepared examples often misses.

Begin with three everyday tasks

The first task is small: update opening hours and a telephone number. The second is a new service page with an image, form and internal links. The third is a multilingual change that also preserves search previews and language switching. Record who performs each task, who reviews it and how publication happens.

Measure more than clicks. Can the editor save a draft and request review? Can they identify missing languages? Can they reverse an error? An interface with many options is not automatically bad, but unexplained options increase training needs. A very simple editor may lack the control required over metadata or relationships between pages.

WordPress: How much layout control should editors have?

The WordPress block editor provides a way to edit content through individual blocks. What matters in your project is which blocks and templates are configured. Adding a paragraph should not let an editor accidentally change navigation, spacing or booking logic.

Ask about roles, essential extensions and responsibility for updates. Which functions come from a plugin, a theme or custom development? Documenting that allocation helps another maintainer take over. A long plugin list does not, by itself, describe a maintainable operation.

The official WordPress backup guide distinguishes files from the database. Full restoration must account for both. Ask for a practical demonstration. A daily backup that nobody can restore meets the operational need only on paper.

Webflow: Ask precisely about export

Webflow may suit visual editing and structured content. Check the actual workflow and plan scope. Its official code-export documentation states eligibility conditions and explains that CMS functionality, form processing and localised content do not simply accompany an export as a complete working site.

Do not equate a ZIP containing HTML with a transferable editing system. How will content stay editable when hosted elsewhere? Which features need replacement? Which languages need separate migration? An honest answer may still lead to Webflow. It prevents the decision from relying on a mistaken understanding of handover.

Custom websites: Who owns the publishing route?

A custom or static site can be tailored closely to your needs. Static does not automatically mean awkward editing. A project can use an editor or clearly governed content files. Check which route is actually supplied and whether the responsible person can operate it.

Review the repository, hosting account, documentation and release process. Who has access? Who can reverse a failed update? Which pages share a template and which are built separately? Without that map, a minor edit can affect unexpected places. A tidy codebase does not replace an understandable guide for the content team.

Compare work your business actually performs

Need	Project evidence	Open question
Regular content	An editor creates a genuine draft.	Which training and review are included?
Several languages	Changes remain connected across locales.	Who checks missing translations?
Forms	A test request reaches its destination.	Who handles failures?
Handover	A new maintainer restores a test instance.	Which dependencies remain?

Score these tasks against the actual proposal rather than the platform name. Poorly configured WordPress and a documented custom site are different candidates from managed WordPress and an obscure custom project. Maintenance and recovery responsibilities therefore belong in the comparison.

Include the ongoing work in costs

Add hosting, necessary plans, extensions, maintenance, content work and support. Avoid generic prices unrelated to the project. Ask the supplier for understandable assumptions: how many edits, which functions, what response arrangements and what your own staff will handle?

A one-off project price says little about a multilingual blog with frequent publication. A monthly platform fee says little about additional integration maintenance. Separate recurring required services from optional work. That lets you compare proposals without pretending that different support models have identical scope.

Also consider the cost of a normal staff change. If the editor leaves, how does the replacement learn the workflow? If the agency changes, how does the new team identify custom components? A short usable handbook and a recorded editing exercise may reduce uncertainty. They should be defined deliverables, not something requested after the relationship ends.

Acceptance includes operating the site

Check a real editorial change, a test enquiry and restoration. Add narrow screens, browser zoom and both themes if the site provides them. Long headings and translations must not overlap the next section. Choosing a CMS does not automatically prevent these problems; the implementation and acceptance process must address them.

Ask the editor to repeat the task without the developer directing every click. Record where they hesitate and whether the documentation resolves it. A successful guided demonstration can conceal missing permissions or unclear publishing steps. The repeat exercise gives both teams a practical final list of corrections.

Check an edit involving two people

Try one more editorial task: two people working on the same draft. One corrects the English text while the other adds an image. Check how the supplied setup handles this. Does it merge changes visibly, report a conflict or replace the earlier work with the last save? Assign a simple editing owner if collaborative editing is unavailable.

Also examine the boundary between a draft and publication. Changing a reusable template can affect several live pages. The preview needs to reveal the actual scope. With four languages, editors should know whether a shared component changes every version or whether each locale needs a separate update. Demonstrate that relationship using the sample task and a test instance.

Finally, let another person take over the saved draft. Can they find the outstanding corrections and identify the approval still needed? This exercise represents an ordinary holiday handover or staff change. Put the agreed procedure in the editorial handbook so it remains usable when the interface changes.

After acceptance, hand over access and responsibilities in writing. Domain and hosting details should not exist only inside the former maintainer’s personal account. Our article on transparent website costs adds context. For web design and branding, bring the three editing tasks. They let the choice follow the work your business really needs to do.

Test the same journey without a mouse and with magnification. The guide to accessible enquiries and bookings provides acceptance checks for zoom, keyboard, form errors and contrast.