How Clinic to Cloud reduced Azure spend by 46% in 12 months.

Clinic to Cloud is a clinical practice management platform serving thousands of clinicians across Australia and South-East Asia. The product runs entirely on Azure — App Service, SQL Database, Service Bus, Functions — multi-tenant, per-practice cost-pooled.

By late 2022, two things were going badly. Azure spend was growing faster than ARR. And SaaS gross margin — a number every healthcare SaaS investor cares about — was under pressure.

The challenge

Like most multi-tenant SaaS providers, Clinic to Cloud didn't have a clean view of cost-per-customer. Engineering knew aggregate spend was high. Finance knew gross margin was eroding. Neither team could pinpoint which customers were driving the over-consumption.

The CloudMonitor deployment

The team installed CloudMonitor in a sandbox tenant on a Thursday, validated the data over the weekend, and pointed it at production on the following Monday. By mid-week the cost-group view was populated and the first recommendations were in the queue.

Two things changed the curve.

1. Per-customer cost mapping. The team tagged every resource with a customer ID. CloudMonitor's tag-based cost groups surfaced 12% of customers whose cost-to-serve exceeded their plan revenue. The Starter plan was redesigned within a quarter, with a usage cap.

2. Real-time anomaly detection. Three weeks after CloudMonitor was live, the Teams bot flagged a $3k/day anomaly on an ADF pipeline. The engineer on call killed it within the hour. Pre-CloudMonitor, that would have shown up on the next monthly bill.

Outcomes

Twelve months on, Azure spend is 46% lower than the pre-CloudMonitor run-rate. Gross margin is up 15 points. There has not been a single bill-shock incident since the Teams bot went live.

Just as importantly, finance and engineering now share a single reporting fabric. CloudMonitor reports are reviewed every Friday in the joint cost review meeting — a meeting that didn't exist 18 months ago.