Required
Read-only AWS access
Tightly constrained access is required to examine relevant cost and service evidence.
14-DAY AWS SAVINGS SPRINT
Find what is worth changing in 14 days.
A focused engineering and cost review that ranks the AWS opportunities worth acting on and produces a specific implementation roadmap.
14-Day AWS Savings Sprint
£5,000upfrontTightly constrained read-only access.
01 · Engagement sequence
A bounded review from access to a ranked plan.
Six explicit stages turn AWS cost evidence into decisions your engineering team can act on.
- 01
ACCESS
Customer provides tightly constrained read-only AWS access.
- 02
FIND
Identify economically meaningful opportunities across cost, waste, commitments and architecture.
- 03
VALIDATE
Assess value, confidence, engineering risk and relevant commitment exposure.
- 04
MAP
Connect opportunities to services, teams and IaC locations where identifiable.
- 05
REMEDIATE
Document the specific engineering changes required.
- 06
PRIORITISE
Return a ranked Savings Ledger and implementation roadmap.
02 · Review scope
The review follows cost through engineering consequence.
Each category is assessed as decision material, not as an isolated recommendation list.
- SAVINGS OPPORTUNITIES
- Ranked by monetary value, confidence and engineering risk.
- COMMITMENTS
- Savings Plan / commitment exposure.
- IDLE / WASTE
- Infrastructure with unnecessary ongoing cost.
- ARCHITECTURE
- Expensive architecture patterns.
- REMEDIATION
- Specific engineering steps.
- IAC
- Repository / infrastructure-as-code locations where identifiable.
03 · Primary deliverable
You leave with a ranked Savings Ledger.
A decision record that preserves value, confidence, risk, accountability and remediation state.
IllustrativeDecision-quality fields, not a customer result
| Priority | Opportunity | Expected saving | Confidence | Engineering risk | Owner | Remediation status |
|---|---|---|---|---|---|---|
| 01 | RDS rightsizing | £4,820 / mo | High | Low | Platform | Change mapped |
| 02 | NAT architecture | £2,140 / mo | Medium | Medium | Core infra | Architecture change mapped |
| 03 | Idle EC2 | £980 / mo | High | Low | Data | Awaiting approval |
Approved Ledger items become the implementation backlog. The example shows the structure used to support a decision; it is synthetic and illustrative, not a real report, live account or customer result.
04 · Inputs
What we need from your team.
Access is deliberately narrow. Context helps the review stay connected to operational reality.
Typically useful
A technical point of contact
Architecture and operational context are typically useful for validating risk, ownership and constraints.
05 · Control boundary
Discovery, not uncontrolled change.
The Sprint does not independently deploy. Any later engineering change remains within your repositories, review, approval and deployment controls.
06 · After the Sprint
When the Ledger is ready, choose how approved work gets implemented.
The first engagement identifies what is worth changing. Approved work can then follow one of two implementation routes.
Fixed implementation
Implementation Sprint
£15,000A fixed-price implementation engagement for the approved scope.
Outcome-based implementation
Outcome-based implementation
25%of verified savingsAn alternative commercial model linked to savings that meet the agreed verification definition.