We were paying for hosting our clients weren't being billed for.

How hosting pricing goes wrong in a growing agency

When you onboard your first ten clients, hosting is simple. You know exactly what each one costs to run because you set it all up yourself. €15/month here, a dedicated environment there. Easy.

By the time you're at 35 clients — with different server configurations, mixed reseller accounts, a couple of cloud environments from legacy projects, and billing set up by three different people over four years — it's anything but simple.

Our hosting pricing hadn't been audited since we'd set most of it up. We'd upgraded infrastructure as needed. We hadn't upgraded what we charged clients to reflect that.

What we thought we knew

I thought we were roughly margin-neutral on hosting. It was never a big profit centre — we viewed it as a service that kept clients sticky. Cover costs, charge a small management fee, move on.

The problem was I had no way to see hosting costs and billing side by side, per client, in real time. Hosting invoices went to the ops email. Client billing went through our invoicing tool. Nobody was reconciling the two in any structured way.

The moment everything became visible

When I was building Insighty, I used our own agency as the test dataset. I imported every client, every service, every hosting contract — cost, provider, environment size, and what the client was being billed for it.

The "Services Overview" view laid it out clearly: for each hosting service, the monthly cost on the left, the monthly revenue on the right. Green where we had margin. Red where the math didn't work.

There were seven red rows.

A client on a managed WordPress plan — we'd moved them to a faster environment 18 months prior after a performance issue, but never updated their billing. A client whose site now ran alongside three others on a shared server that cost more per seat than the individual amount we were charging. Two clients on "legacy" pricing we'd offered during a promotional period three years earlier, never expecting them to still be on it.

Combined across the seven: we were delivering €1,250/month more in hosting infrastructure than we were billing for. €15,000 a year. Straight loss.

The fix — and what it took

First, we consolidated. Three hosting providers down to one managed provider with cleaner per-client pricing. That alone removed a chunk of the gap through better infrastructure unit economics.

Second, we updated client pricing. Most clients were on contracts with annual review clauses — we'd just never used them. We had honest conversations. Every client stayed. A few pushed back on the increase; we explained the infrastructure change and that was enough.

One client was on hosting so old it predated our current contract template. We migrated them to our standard hosting tier and absorbed a one-time credit on their account. Still came out ahead by more than €2,000/year on that client alone.

What's different now

Every hosting service in Insighty has a cost field and a billing field. The moment those two numbers diverge beyond our threshold — 15% margin minimum — it surfaces as a flag on the dashboard.

We review it quarterly now instead of never. When we upgrade a client's infrastructure, the billing update is part of the workflow, not an afterthought six months later.

The €15,000 wasn't new money. It was money we were already spending effort to earn. We just weren't collecting it.