What we ask for
Reader and Cost Management Reader at the agreed scope, recent cost export if available, and one short walkthrough with a person who understands the critical workloads.
Azure Cost & Reliability Audit
Know what is safe to change before you touch the Azure bill.
We audit your environment in five business days and tell you exactly what is safe to change, what to leave alone, and what it is worth. Fixed fee. If we cannot find savings worth at least three times the fee, you pay nothing.
For companies running EUR 10,000+ per month on Azure.
EUR 4,500, fixed. If we do not identify annualised savings worth at least three times the fee, you pay nothing.
The Audit covers the whole environment. Remediation is scoped to one approved finding, which is why it can start lower.
What you receive
A decision-ready report, written for the people who have to live with the change.
The final report includes a spend baseline, ranked opportunities, safe-change guidance, a risk register, dependencies, and a clear recommendation for the next step.
1. A sample Day 5 readout (PDF)
2. Ranked findings with owners and risk notes
3. The 88-check workbook
4. No email required
Case study
Azure cost reduction for Magrid, a LetzMath Sarl product.
Read the case studySecurity before access
We review first. We do not change production during the Audit.
We ask for Reader and Cost Management Reader roles only. If your security policy does not allow access, a Cost Management CSV export plus a 90-minute walkthrough gives us a workable evidence path.
- Read-only roles: Reader and Cost Management Reader
- Customer commitment: 90 minutes across the five days
- CSV route available when direct access is not possible
- Data is used only to deliver the agreed Audit
Access request
The smallest access request that lets us make a responsible call.
What we do not do
We do not change resources, deploy code, open broad admin access, bypass your change process, or claim a recommendation is safe without the evidence to support it.
Five business days
A short engagement with a defined rhythm.
- Day 1
Baseline and context
We agree the bill baseline, critical workloads, change constraints, and who will use the decision.
- Days 2-3
Evidence review
We inspect cost, architecture, reliability, security, and operational evidence against the workload.
- Day 4
Decision brief
We rank changes by annualised value, safety, dependencies, and the order in which to make them.
- Day 5
Readout and handover
We walk through the findings, answer questions, and hand over the report and next-step route.
Coverage
We inspect the bill and the engineering context around it.
Cost baseline
Three recent invoices, top cost drivers, usage shape, reservations, Savings Plans, and forecast.
Workload fit
Compute, App Service, SQL, storage, networking, and data workload choices against actual use.
Reliability and security
Monitoring, backups, identity, secrets, locks, and operating dependencies that affect safe change.
Operating ownership
Who approves, implements, observes, rolls back, and owns the baseline once the decision is made.
Data residency and GCC controls
Where GCC PDPL, NCA, data-residency, or customer contractual controls apply, we record those constraints before recommending a workload or access change.
Audit guarantee
How the three-times promise is assessed.
Identified saving
A saving counts when the report names the specific resource or commitment, the change that produces it, and the evidence behind the number. Findings that depend on assumptions we could not verify are listed separately and do not count toward the guarantee.
Annualised value and baseline
Before analysis starts we agree a spend baseline from your recent invoices. Each identified saving is annualised over twelve months against that baseline, with the assumptions stated next to the number in the report.
Verification
The figures are walked through line by line at the Day 5 readout and verified jointly against the evidence in the report before the engagement closes. If the identified annualised savings do not reach three times the fee at that readout, you pay nothing.
If implementation is declined
The guarantee is assessed on identified savings, not implemented ones. Whether you implement the changes with your own team, with us, or not at all is your call, and it does not change the assessment.
Commercial and working terms
Clear boundaries before work begins.
Price and payment
EUR 4,500, fixed. If we do not identify annualised savings worth at least three times the fee, you pay nothing. Payment timing and invoice details are set out in the engagement letter.
Baseline
We agree the current spend baseline before analysis starts. Annualised value is estimated from the evidence available and is stated with assumptions.
Contract and liability
The engagement letter defines scope, confidentiality, liability, escalation, and the applicable contracting entity: Accepire Techsol Pvt. Ltd. (India).
Exit and knowledge transfer
You keep the report, evidence summary, assumptions, and implementation notes. You may implement with your own team or ask us to scope Remediation.
Escalation
We name a delivery contact at kickoff and record the escalation path in the engagement letter. Production incidents are handled through the emergency channels, not the Audit queue.
Insurance and references
We do not hold professional indemnity insurance; liability is defined in the engagement letter. Reference-call availability is confirmed in writing on request, and we do not publish a client reference without approval.
Not a fit
This is not a free health check or an emergency response service.
The Audit works best where the Azure bill is material, the team can provide context, and the buyer wants a considered decision before changing production. For a live outage or blocked release, use a rescue route.
Start with the evidence
Bring the Azure bill and the constraints around it.
For companies running EUR 10,000+ per month on Azure.