What a website should cost: the economics behind Website-as-a-Service

Ask five agencies what a website costs and you will get five numbers and no arithmetic. This article is the arithmetic. We sell websites on a monthly model, so we have an obvious interest here, and the honest way to handle that is to show the working, including the cases where our model is the wrong choice.

The £4,000 website is not a £4,000 website

The traditional deal looks clean: pay an agency £4,000 or more, get a website, own it outright. The problem is that a website is not a brochure. It is software running on a stack that moves underneath it: browsers update, frameworks patch security holes, plugins are abandoned, Google changes what it rewards, and design conventions age visibly.

A one-off build starts depreciating the day it launches. In our experience the pattern for a small business runs something like this: year one, the site is fresh and nobody touches it. Year two, small things break or drift (a form stops delivering, the opening hours are wrong, the plugin stack needs updates nobody applies). Year three, the site is visibly dated and quietly leaking enquiries, and the fix on offer is a rebuild, at which point the cycle restarts with a new invoice of the same size.

The rebuild cycle is the real bill. £4,000 every three years is £111 a month, except you get the value in one lump at the start and the decay for the remaining thirty-five months, with nobody on the hook for maintenance in between. Most small businesses never budget for that maintenance, not because they are careless but because the big-bang model never presents it as a line item. The invoice says "website", not "website, decaying".

What a monthly model actually buys

Website-as-a-Service inverts the deal. Instead of a large one-off invoice, you pay a small design and build fee up front and a monthly fee for as long as you run the site. Ours is public: plans from £99, £149, £199 and £399 per month depending on tier, plus a one-off bespoke design and build fee of £299 to £799 that can be spread over your first three months. You can inspect the full ladder at /website-as-a-service and the plain-English legal terms at /terms/website-as-a-service.

The monthly fee is not rent on a static artefact. Every month it covers managed hosting and SSL, security patching, platform maintenance, performance monitoring, an allowance of minor content updates (text, images, prices, opening hours, typically live within two working days) and ongoing search iteration. In other words, it converts the invisible maintenance debt of the one-off model into a visible, budgetable line, and it puts the ongoing risk (hosting outages, dependency vulnerabilities, breakage) on the party equipped to carry it.

The trade is ownership structure. Under our model the studio owns and maintains the codebase, hosting and infrastructure; the client holds an exclusive licence to their live site for the duration of the plan. Brand, content, images, customer data, domain and search rankings remain the client's at all times, exportable on request. There are longer minimum terms on bigger plans (12 months on Starter, 24 on Business and Growth, 36 on Ecommerce) because the engineering cost we absorb at the start scales with the tier, and a published buyout route exists if a client ever wants to own the code outright. None of that is small print to hide; it is the mechanism that makes £99 a month possible at all.

Where the margin honestly comes from

A fair question: if a bespoke build is worth thousands, how can anyone deliver it for £99 a month without cutting corners? The suspicious answer would be templates. Ours is platform reuse, which is a different thing, and the difference is worth spelling out.

Template reuse means selling the same design repeatedly with the logo swapped. It is cheap because the design work happens once, and it shows, because your site looks like your competitor's.

Platform reuse means every site is designed individually but runs on one shared, hardened engineering platform: the same rendering architecture, the same image pipeline, the same form-security patterns, the same consent, analytics and structured-data plumbing, the same deployment and monitoring setup. We built and battle-test that platform on our own site first. The expensive part of a small-business website was never the layout; it is the invisible engineering underneath it, and that cost, once paid, amortises across every site on the platform without any two sites sharing a design.

The economics compound in maintenance too. One platform means one set of security patches applied everywhere at once, not thirty snowflake codebases each needing an update visit at hourly rates. That operational leverage, not template cloning, is the margin.

Run the honest comparison over six years, using our Business tier and a like-for-like agency cycle:

// Six-year cost comparison, GBP. Adjust the inputs to your own quotes.
const years = 6

const agency = {
  build: 4000,           // one-off build, rebuilt every 3 years
  rebuilds: 2,           // year 0 and year 3
  maintenancePerYear: 0, // the number most small businesses actually budget
}

const waas = {
  setupFee: 399,         // Business tier build fee
  monthly: 149,          // Business tier monthly
}

const agencyTotal = agency.build * agency.rebuilds + agency.maintenancePerYear * years
const waasTotal = waas.setupFee + waas.monthly * 12 * years

console.log({ agencyTotal, waasTotal }) // { agencyTotal: 8000, waasTotal: 11127 }

Read that result carefully, because it does not flatter us. Over six years the monthly model can cost more in cash terms than two neglected rebuilds. What the extra buys is the difference between owning a depreciating artefact and running a maintained asset: seventy-two months of hosting, patching, edits and iteration, versus seventy-two months in which the agency-built site is touched twice. If a business genuinely needs none of that upkeep, the one-off build is cheaper and they should take it. Most businesses that believe they need none of it are describing the year-three leak from the section above.

When WaaS is the wrong choice

A pricing model is only credible if its seller can name its limits, so here are ours.

Heavy custom scope does not belong on a monthly plan. If the project is a SaaS product, a marketplace, a booking engine with bespoke logic, deep API integrations or an application with its own database model, the engineering is dominated by work that cannot amortise across a platform. Squeezing that into a subscription either bankrupts the provider or quietly starves the project. That work should be a properly scoped bespoke build with its own budget, and when a brief like that reaches us through /contact, a bespoke quote is what it gets.

The same applies to businesses with in-house developers who want direct control of the code, and to anyone for whom outright code ownership on day one is non-negotiable. The licence model is the engine of the economics; if it does not fit, the model does not fit, and no discount changes that.

WaaS earns its keep in the wide middle: clinics, trades, hospitality, salons, shops, professional services and early-stage companies that need a fast, secure, well-maintained site and would rather fund it as a running cost than a capital project followed by three years of neglect.

Key takeaways

• A one-off website quote hides its true cost: depreciation plus an unfunded maintenance gap plus a rebuild roughly every three years.
• A monthly model converts that hidden decay into a visible line item covering hosting, security patching, edits and iteration.
• Our ladder is public: £99 to £399 per month by tier, plus a £299 to £799 build fee spreadable over three months, with minimum terms scaled to the engineering absorbed up front.
• The margin comes from platform reuse (shared engineering, individual design), not template reuse, and from patching one platform instead of thirty snowflakes.
• Heavy custom scope belongs in a bespoke build with its own budget; a subscription that claims otherwise is underpricing your project or overcharging everyone else's.

Frequently asked

Is Website-as-a-Service just a template subscription?

No, and the distinction matters. Every site on our platform is designed individually from the client's brand and content; what is shared is the engineering underneath (rendering, security, hosting, monitoring). Template subscriptions share the design and skip the engineering, which is the opposite trade.

Who owns the website on a monthly plan?

The studio owns and maintains the codebase, hosting and infrastructure, and the client holds an exclusive licence to their live site for the duration of the plan. Brand, content, images, customer data, domain and rankings stay with the client at all times and are exportable on request. A published buyout route exists for clients who later want the code outright.

Why is there a minimum term?

Because the design and build cost we absorb at the start far exceeds the first months of fees. Starter carries a 12-month minimum, Business and Growth 24 months, and Ecommerce 36 months, reflecting how much engineering each tier front-loads. After the minimum, plans run month-to-month with 30 days' notice.

When is a one-off build genuinely the better deal?

When the project is engineering-heavy and unique (SaaS, marketplaces, custom integrations), when you have in-house developers who will maintain the code, or when day-one code ownership is a hard requirement. In cash terms a one-off build can also win if you truly need no upkeep for years, though in practice that assumption is where most three-year rebuild cycles begin.