Most small businesses choose a platform the way they choose a van: by what the salesperson had on the lot. The agency builds in WordPress, so the site is WordPress. That is not a bad choice. It is just rarely a considered one. Here is a way to consider it in ten minutes.
Count what the site has to do
Write down what the site actually needs to do in the next two years. Not what it might need one day. For most small businesses the list is short:
- Say what you do, where, and for whom.
- Show a few examples of work, or a team, or a price list.
- Let people call, write or book.
- Change a sentence, a price or a photo a few times a year.
- Be found on Google for the right searches, and be quoted by AI assistants.
If that is the list, nothing on it needs a database, a plugin ecosystem or a theme engine. It needs five to twenty well-written pages and a way for the owner to edit them.
When the list is longer
Some lists go on. A shop with a cart and payments. Customer accounts. A blog with several authors and hundreds of posts. Comments. Membership content. Any of those, and a real CMS earns its place. WordPress with WooCommerce is a sound answer for a small shop, and there is no point fighting it.
What the short list costs on WordPress
A WordPress site for a short list still carries the full stack. On every visit the server queries the database, runs the theme and the plugins, and hands the browser a page with the plugins' scripts attached. It works, and with a caching plugin it is fast enough. But the owner now has a system to keep updated, a login page on their domain, and a dependence on whichever plugins the agency picked. Three years in, the site is slower than it was, and someone has to look after it.
What the short list costs on a hand-built site
Nothing, after the build. The pages are files. There is no database, no update schedule, no plugin that stops working. The site is as fast on day one thousand as on day one. The only real cost was that the owner could not edit it, and that is the part that has changed.
The editing question
cmsspot connects to a plain HTML or PHP site over SFTP and turns the pages into fields the owner can edit in a browser: text, images, links, the menu, titles and descriptions. Nothing is installed on the site, and only the changed field is written back. The owner gets the editing they wanted from WordPress, and the site stays as light as it was built.
A fair way to decide
Ask the agency to build the short-list site in plain HTML or PHP, and to connect it to cmsspot so you can edit it. If they say the site needs WordPress, ask which item on your list requires it. If the answer is "the blog", ask how many posts a year. Two or three posts a month do not need a CMS. If the answer is a shop or accounts, they are right, and you should build it on a system made for that.
Related: cmsspot vs WordPress · Why hand-built sites win
More articles: Why a plain HTML page is the easiest thing for Google and AI to read · Let Claude edit your website: what AI access in cmsspot allows, and what it never can