For years my client sites lived on WP Engine and I paid around $600 a month for the privilege. I passed a slightly bigger fee on to each client and called that my margin. It worked, but the margin was thin and it was never really mine, because the second the host raised prices my margin shrank and there was nothing I could do about it. Moving the same roster to Cloudflare, where it runs about $200 a month for unlimited sites, changed that math completely, so let me walk you through it.
Why static hosting changes the whole equation
Most agency sites do not need a server sitting there running around the clock waiting for requests. They are marketing sites. The pages do not change per visitor. When you build a site as static HTML, it is just files, and serving files is close to free at the scale a normal agency operates at.
Cloudflare Pages serves those static files from their edge network, and unlimited bandwidth for static assets is included on every tier, even the free one. Read that again. For a brochure site, a local business site, most of what an agency builds, serving one more site adds basically nothing, so my whole roster runs on one flat plan, around $200 a month, instead of the $600 I was handing WP Engine.
Once your whole roster runs on one flat plan, the hosting you have been reselling to clients at a markup costs you a few dollars a site to provide. That gap is not a problem. It is the business.
The setup, start to finish
Here is the shape of it, without pretending it is one button.
- Build the site as static output (that is what a modern static site builder produces by default)
- Connect the project to Cloudflare Pages, usually straight from a Git repo
- Point the client domain at it, which is a couple of DNS records
- Every update redeploys automatically, and the old version is still there if you need to roll back
The first one takes an afternoon while you learn the flow. The tenth one takes a few minutes, because by then you have done it enough that its muscle memory.
Join the Seedly owners community.
Owners trade setups, share add-ons, and swap playbooks. See what people are building before you commit.
The part that makes it an agency tool, not a hobby
Hosting one site is a hobby. Hosting your whole book of clients on one flat plan you control is a business. The reason this works at agency scale is that adding another client site does not add a meaningful cost. You are not buying another hosting plan every time you land a client. You are deploying another set of files to the same edge you already pay for.
That is the difference between renting hosting per site and owning the pipeline that hosts all of them. I built the Seedly Sites platform around exactly this, so I could run every client site from one place and keep the hosting margin instead of passing it to a host.
The honest catch
Static is not the right answer for everything. If a client needs a full application with logins and a database and per-user pages, that is a different tool and a different cost. But that is a small slice of what agencies actually build. The other 90%, the marketing sites, the local business sites, the landing pages, all of that is a perfect fit for static edge hosting, and you are almost certainly overpaying to host it right now.
Run the numbers on your own hosting
Go look at what you pay per client site per month, then look at what static edge hosting would cost you for the same site. The gap is margin you are currently handing to a hosting company for no reason. I get into how to price that in charging clients for hosting when your hosting is free, and the fuller case against the old stack is in why agencies are leaving WordPress.
Own the pipeline, keep the margin.
