Website builder limitations are a ceiling, not a bug.
Does it have a ceiling you’ll hit?
Every platform has a ceiling. The test is whether you will hit it.
Website builder limitations are why a working client site gets rebuilt from scratch. A ceiling is not a bug, and it is not a complaint to file. It is a decision about who the platform is for, and the question worth asking is whether your clients will still be under it in three years.
Scalability, in this test, is not about traffic first. Traffic is the easy ceiling to reason about. The harder ones are pages, languages, editors, environments, and the point at which the next thing the client wants is on a plan the client will not pay for. The test asks you to find the ceiling on purpose, before the client finds it by accident.
And the test cuts both ways. The owned stack has a ceiling too, and this page says exactly where it is, because a test that only fails other people is a sales pitch.
The plan comparison page is the ceiling, with prices.
Open the plan comparison page for the platform your clients are on and read it as a list of limits rather than a list of features. Page counts, storage, bandwidth, staff seats, languages, environments, the tier where the custom code box appears. Each column boundary is a ceiling. Each boundary with a price beside it is a ceiling you will be asked to explain to a client.
Then find the performance ceiling. Take the largest site you have on the platform and open it with the network panel visible. Count the requests the page makes that are not to the client’s own domain. That number is the share of the site’s speed that belongs to someone else’s uptime, and it does not go down as the site grows.
Then ask the exit question. If the client outgrows the plan, what is the next step: a higher tier on the same platform, or a rebuild? If it is a rebuild, the ceiling was the platform all along.
The comparison page
Read it for the limits, not the features. Note which ones come with a price beside them.
The network panel
Open the client’s largest site and count the requests to other domains. That is the part of the site’s speed you do not control.
The next step
Ask what happens when the client outgrows the plan. A tier is a ceiling. A rebuild is a wall.
A ceiling you pay to raise is still a ceiling.
Files on a CDN, and an honest line around them.
For a content or marketing site, the owned stack is a folder of static files on a CDN. There is no page count. There is no seat licence. There is no request to anyone but the client’s own domain, so speed does not degrade as the site grows and does not depend on anyone else’s outage. The traffic ceiling is the CDN’s, not yours, and the host’s free tier is documented on the host’s own page for anyone who wants to read it before believing it.
The way the stack grows is silos. The folder is the URL, an unregistered folder fails the build, and every page owns exactly one search query. Ten pages or a thousand, the structure is a rule the build enforces, not a diagram somebody drew once.
Here is the line, drawn plainly. The playbook is scoped to content and marketing sites. A store with a cart and payments, a site with logins, a multi-user application: those need a database, sessions and a different discipline, and the playbook does not claim them. If the client’s business is one of those, run the test again on a different stack. Scope is not a fail. Pretending the ceiling isn’t there would be.
Within scope, files on a CDN. Outside it, the playbook says so.
Scalability is the last test. The rule needs all five.
Extensibility
Add what isn’t there yet, without waiting on a roadmap.
Control
Can you change how the system behaves, or only what the settings panel exposes?
The full test runs all five, with the assembling word and the rule: pass all five, or don’t build on it.
Read the sharpest chapter first. It costs an email.
We’ll send the build-gate chapter in full: the checks, the code, and the reasoning. Read it. If it doesn’t change how you think about shipping client sites, you’ve lost ten minutes and kept a working release gate.
That did not send. Check the address and try again.