Decision Pack: See it
Why the bill moved, by service.
Bill breakdown
- Each rise explained by service and cause. Anything not yet explained is marked.
- Spend with no clear owner, named.
- One 45-minute call with your engineer.
3 to 5 ranked cost decisions from an Azure expert, for growing companies.
Monthly bill
Previous level
8 months of changes
€750k+ a year off the bill
Proven by hand. The same method shapes every Pack.
Explained for finance. Prioritised for engineering.
Decision Pack
Monthly Close
Why the bill moved, by service.
Ranked changes, and what to leave alone.
An expert flags cost surprises within 1 working day.
Sample dashboard. Last month: €48.2K, up 10.6% on the month before. This month so far: €24.1K, halfway through. Projected month-end: €47.0K, 94% of a €50.0K budget. Chart: monthly cost by service category over six months, rising from €39.8K to €48.2K last month, with this month projected.
Sample monthly report: how last month's bill got from €43.6K the month before to €48.2K, up €4.6K. Increases: usage growth, more production traffic, €2.9K; new project, a new analytics workspace, €2.4K; unplanned cost, data copied to North Europe, €1.8K. Decreases: lower rate, a VM reservation, €1.6K; waste removed, oversized VMs downsized, €0.9K.
Sample network deep dive: last month, €6.4K of network cost flowed from three subscriptions, through six ways Azure bills it, to where the traffic goes. Cross-region traffic to North Europe, €2.3K, is the unplanned cost: up €1.8K on the month before.
Sample chat. Question: why did the bill rise last month? Answer: last month came to €48.2K, up €4.6K on the month before. Three causes: usage growth, more production traffic, €2.9K; a new project, a new analytics workspace, €2.4K; unplanned cost, data copied to North Europe, €1.8K. Two savings took €2.5K back off: a lower rate and waste removed.
November forecast: on budget
Sample
| Service | Cause | Type | Change |
|---|---|---|---|
| AKS | Customer growth | Growth | +1.5% |
| App Service | Acquired company joins | New scope | +1.4% |
| Azure OpenAI | More product usage | Growth | +0.7% |
| SQL Database | Auto-pause off, flagged in 1 working day | Surprise | +0.7% |
| Reservation | Saving landed | Saving | Down |
| Other services | Other | +0.5% | |
| Not yet explained | Not yet explained | +0.2% | |
| Net change | +3.1% |
Example: a standby server at 4% CPU looks idle. It is your recovery copy, and your contracts need fast recovery. Leave in place.
Every finding is read through all three lenses before it reaches you. Your team's capacity sets the order: this sprint, next or later.
The 45-minute call with your engineer gives us the architecture and business lenses.
Your Azure estate
Infralign
Scale back the load-test poolSample
Your team decides
Decision PackMost of last quarter's rise came from one load-test pool left at peak size. Waste and growth, told apart.
Monthly CloseThe month-end forecast moves up, and the Close names each driver. Finance approves the change.
Decision PackAzure cost mapped to each product with your team. Spend with no owner, named.
Monthly CloseCustomers grew faster than the bill, so cost per customer fell.
| Effort | Change risk | |
|---|---|---|
| Do now | Low | Low |
| Plan | Low | Medium |
| Leave in place | None | High |
Decision PackScale back the load-test pool first: low risk, easy to undo. The standby stays.
Monthly CloseA template change undid one saving. Flagged in 1 working day.
Decision PackServer reservations end on 31 January. Options sent 2 December: renew, change or wait.
Monthly CloseAn acquired company brings subscriptions with no owner. Owners proposed for you to confirm.
€2,500, one-off
Monthly Close only if you continue. Fixed fee, quoted in writing first.
The Pack. €2,500, credited in full against the first 3 months of a plan. The 7 days start once read-only access is in place.
The monthly fee. A fixed fee, never a share of savings. Fee and scope quoted in writing before you buy the Pack.
Term. A first term of 3 months. Then billing is monthly or quarterly, or you stop. Nothing renews until you say so.
Leaving. After the first term, remove access at any time. The service and fees stop that day.
Savings. Every saving is re-checked on the bill and counted once.
What to do firstSample
Two read-only roles in Azure: Reader and Cost Management Reader. An admin assigns them in about 15 minutes. Then one 45-minute call with an engineer about your constraints. Nothing is installed, and we cannot change your resources. Your team or your MSP makes every change.
A fixed monthly fee, never a share of savings. It depends on your estate. We quote the fee and scope in writing before you buy the Pack, so you know the full cost first.
You still get the bill explained by service and a clear list of what to leave alone. You owe nothing more.
We read billing data, resource settings and usage metrics, not your customer content. It is held in Microsoft Azure in the EU, and we delete it on request. Security details
Saving companies real money, with real data.
No sales deck. No obligation.

Dr Tahir RabbaniCTO. PhD, TU Delft. 20+ years in enterprise architecture.

Rakhi GuptaCEO. PhD researcher, Erasmus. New Frontiers alumna.
Two read-only roles. Nothing installed. Billing data, resource settings and usage metrics, held in Azure in the EU. Deleted on request.
Security details