The quote is not the cost
When businesses compare a Jamstack build with a WordPress build, they usually compare quotes. That is the least useful number available. A website's real cost unfolds over years of hosting bills, maintenance, security work and, the item almost everyone forgets, the cost of making every routine edit. This article models all five across three years for a typical UK small-business site, using illustrative figures you should adapt to your own quotes.
Quick definitions: "Jamstack" here means a site generated as static files by a tool such as Astro, Next.js, Hugo or Eleventy, served from a CDN, and optionally edited through a headless CMS. WordPress means the familiar self-hosted, theme-and-plugins platform that still powers a large share of the web.
Year zero: build costs
For a standard brochure site, WordPress usually wins the build quote. The theme ecosystem, page builders and an enormous developer pool make it quick to assemble, and many UK agencies quote lower for WordPress simply because more of the work is configuration rather than code.
Jamstack builds are custom by nature, so a comparable site typically costs the same or somewhat more to build, and adding a headless CMS so that non-technical staff can edit adds integration work on top. The gap narrows sharply if your design is bespoke anyway: at that point both stacks are hand-built and the traditional WordPress head start largely disappears.
Need a hand with this?
Our team delivers WordPress Development for UK businesses — with a free initial consultation, transparent fixed quotes and no lock-in contracts. Tell us what you're working on →
Hosting: 36 months of invoices
This is Jamstack's strongest column. Static files served from Cloudflare Pages, Netlify or Vercel cost nothing or nearly nothing at small-business traffic levels, and GitHub Pages is entirely free. Over three years, realistic spend runs from zero to a few hundred pounds, and then usually only if you outgrow a free tier.
WordPress needs a server. Budget shared hosting starts at a few pounds a month but performs accordingly; a decent managed WordPress host typically runs somewhere between £15 and £40 a month for a single site. Call it roughly £550 to £1,450 over three years, before premium plugin licences, which commonly add £100 to £300 a year for forms, SEO tools, backups and page builders.
Maintenance and security: the recurring tax
WordPress's flexibility comes from plugins, and plugins are where the vast majority of reported WordPress vulnerabilities live. Keeping core, theme and plugins updated is genuinely non-optional, which is why care plans exist. A typical UK care plan runs from around £30 to £100 or more a month; across three years that is £1,100 to £3,600. It is usually money well spent, because a hacked-site cleanup plus the reputational mess costs far more.
A static Jamstack site has almost no attack surface: no database, no admin login, no PHP to exploit. But low maintenance is not no maintenance. JavaScript frameworks move quickly, dependencies need periodic updates, and a site left untouched for two years may need developer time before it can be safely changed. Budget an occasional half-day of development per year rather than a monthly plan.
The edit problem: the line item everyone forgets
Here is where WordPress claws everything back. Once built, editing a page, publishing a post or swapping an image costs a staff member a few minutes and no money. Over three years of weekly changes, that is hundreds of free edits made without raising a ticket.
On Jamstack, the same edits either go through a headless CMS, where Decap is free and Sanity, Storyblok and Contentful offer free tiers that growing sites eventually outgrow, or through a developer. If every "quick text change" needs an hour of developer time at typical UK rates of £50 to £90, twenty edits a year quietly becomes £1,000 to £1,800 a year. That single behaviour pattern decides most three-year comparisons.
Key Takeaway
Compare stacks on three-year totals, not build quotes. Jamstack usually wins for brochure sites that change rarely: hosting is close to free and there is nothing to patch. WordPress usually wins when non-technical staff publish weekly, because editing is free at the point of use and a care plan costs less than developer-assisted edits. Price your own editing volume honestly before choosing; that single number decides most breakevens.
Breakeven scenarios and how to choose
Where Jamstack wins
A brochure site edited a handful of times a year: near-zero hosting, no care plan, and excellent speed and security by default. Over three years it is usually the cheaper and calmer choice, even when the build quote was higher.
Where WordPress wins
A content-led site where non-technical staff publish weekly: editing is free at the point of use, and the care plan costs less than the developer-assisted edits Jamstack would need. The blog-and-lead-generation model that suits many UK service businesses sits squarely here.
Where it is a draw
Ecommerce and complex functionality shift the debate to platform capability rather than hosting invoices; a WooCommerce versus headless-commerce decision deserves its own analysis.
Before choosing, estimate one number honestly: edits per month by non-developers. It predicts your breakeven better than any hosting price list. If you would like this comparison run against your actual requirements and quotes, our team is happy to model it with you.