Fixed-scope offer
Single-Cloud Cost Decision Diagnostic
CAD 3,500 for one cloud environment. Three weeks from receipt of the agreed inputs. A decision-ready pack and leadership readout at the end.
Questions the work answers
- What changed in spend and what evidence supports the explanation?
- Which costs have a clear owner, and which remain unallocated?
- Which opportunities are actionable now?
- What engineering risk or dependency could change the order?
- Who should do what over the next 30, 60 and 90 days?
- Which assumptions need validation before implementation?
Scope and inputs
One environment
One Azure tenant or AWS organization with a defined account or subscription boundary. The fit call confirms the exact boundary.
Read-only evidence
Recent billing exports, cost categories or tags, architecture context and current reporting. Access method and data handling are agreed before work begins.
Named stakeholders
An engineering or platform owner and a finance or business stakeholder to validate findings and join the readout.
Implementation, production changes, tool procurement, and quantified savings commitments are outside this diagnostic. Additional environments or deep technical analysis require a separate scope.
Three-week path
- Week 1: Confirm the decision, data boundary and baseline; reconcile material spend changes.
- Week 2: Test allocation and candidate actions with engineering and finance; record uncertainty and dependencies.
- Week 3: Rank the action register, agree owners and sequence a 30/60/90-day roadmap; present the leadership readout.
What you receive
- Executive cost-change narrative
- Allocation and ownership assessment
- Prioritized optimization register
- Evidence and confidence notes
- Risk, effort and dependency view
- 30/60/90-day action roadmap
- Leadership readout and decision log