The plan in one page
Six things to know
The stack
The architecture
Four parts, and only the first is new. It is how the author's own sites are built.
How it runs
The workflow
Setup once, in about three days. Then the change loop, for as long as the customer has a website.
| When | Step | What happens |
|---|
The change loop
Three things, priced three ways
What you sell
Setup once, for the expert's time. Maintenance monthly, for keeping it working. Bigger changes priced when they happen. Every number is a starting hypothesis for a UK operator in 2026.
| Setup · once | Price | What is in it |
|---|
| Maintenance · monthly | Price | What is in it |
|---|
| On demand | Price |
|---|
The money
The business model
The cost side is nearly empty, so the business is entirely about how many customers one operator can keep genuinely happy. Move the sliders.
| Cost | Per customer, per month | Notes |
|---|
One operator, your numbers
| Scenario | Customers | Setups / month | Changes / month | Revenue / month | Contribution / month | Annual |
|---|
Finding the first fifty
Go-to-market
The offer that converts: ship it, give it away briefly, take it away
| Against | Their position | Ours |
|---|
Execution
The first ninety days
One operator, no money raised, a laptop and an agent seat.
For an investor
Why invest in a business that does not need it
Stated plainly
The risks
| Risk | What to do |
|---|
What the sites look like
Mock-ups
Three invented customers and the operator's own sales site, each a standalone page in this vault. Every customer site carries a "changed by the webmaster" strip near the top, because a site that gets changed is the product.
The plan as documents
Read it in full
The same plan in prose, one document per section, plus the prototypes that are enough to run the first customer.