Most agencies reselling hosting are running a loss and calling it a revenue line. The markup on a hosting plan is small, fixed, and visible; the labor of babysitting what runs on that hosting is unbounded, unbilled, and invisible. One afternoon of “the site is acting weird” erases a year of margin on that client’s hosting — and afternoons like that arrive monthly. Here’s the math the hosting line item never shows.
How did agencies end up in the hosting business?
By accident, almost universally. The client asked “can you just handle the hosting too?” and the agency said yes — because saying yes was easy, the markup looked like free money, and handing a client to a hosting company’s support queue felt like bad service.
Reasonable at the time. But the yes came with an invisible clause: and everything that goes wrong on top of that server is now your problem, at no additional charge. Nobody priced the clause. Most agencies still haven’t.
Where does the money actually go?
Run the honest numbers on a typical arrangement — client pays the agency $50/month for hosting that costs the agency $25:
| Monthly | Annual | |
|---|---|---|
| Hosting revenue | $50 | $600 |
| Hosting cost | –$25 | –$300 |
| Gross margin | $25 | $300 |
| One plugin conflict investigated (2 hrs @ $75) | –$150 | |
| One “site is slow” rabbit hole (1.5 hrs) | –$112 | |
| Updates applied ad hoc through the year (4 hrs) | –$300 | |
| One after-hours outage scramble (2 hrs) | –$150 | |
| Actual annual result | –$412 |
Nine and a half hours of unbilled attention — a quiet year for a WordPress site — turns a $300 margin into a $412 loss. Multiply by forty clients and the agency is funding a five-figure subsidy for the privilege of appearing to have a hosting revenue line. (Swap in your own rate and hours; the shape survives any reasonable inputs.)
Why does nobody notice the loss?
Because the two sides of the ledger never meet. The hosting margin appears on an invoice — concrete, recurring, satisfying. The labor disappears into the workweek — a Slack interruption here, a lunch-hour fix there, an evening scramble no timesheet captures. The revenue is counted; the cost is absorbed as vibe.
There’s an emotional entry too: server babysitting is reactive work. It interrupts the projects that actually bill, breaks focus, and burns out exactly the senior people who get pulled in when something’s really broken. The –$412 undercounts it.
Isn’t the answer just better hosting?
No — and this is the trap within the trap. Premium managed hosting reduces server-side problems, but as we drew out in Managed Hosting vs. Website Operations, the server was never where the labor goes. The updates, the plugin conflicts, the monitoring, the security response, the “can you check on something” — all of it lives above the server line, and it follows the agency to any host. Upgrading the hosting upgrades the part that was already fine.
What’s the actual fix?
Stop selling the commodity and start selling the babysitting — named, scoped, and priced. The work was always real; it was just bundled invisibly into a $25 markup. Unbundle it:
- Name it. “Website Operations” (or Care, or Protection) — monitoring, updates, security, backups, response, and a monthly report.
- Price it like the service it is. Operations runs $99–$299+/month per site depending on scope — because it’s skilled recurring labor with an outcome, not a server invoice with a tip.
- Prove it monthly. The report is what converts “nothing broke” from silence into visible value — the same discipline of showing the work that runs through everything we’ve written about selling outcomes.
- Let a platform do the repetitive layer. Monitoring, update management, scanning, and reporting across every client from one place — so the service scales without the labor scaling with it. That’s precisely the layer Centry Host exists to carry, under your brand.
Same clients, same work — but now the work has a price, the price recurs, and the afternoon that used to erase a year of margin is what the client is happily paying for.
The hosting line was never the business; it was a loss leader nobody meant to run. The babysitting was the business all along — unnamed, unpriced, and given away. Name it and price it. If you want the full anatomy of the layer above the server, start with Managed Hosting vs. Website Operations: What’s the Difference?
Was this article helpful?
Thanks for your feedback.
Have a question about this topic?
