Find out what your cloud bill should actually be.
A two-week, fixed-fee review of your AWS or Google Cloud spend and architecture. You get written findings, a savings model costed in SGD, and a remediation plan ordered by payback. No tooling to buy, no retainer, no implementation commitment.
If we do not think the savings will cover the fee, we will say so on the call and you will not be invoiced.
Singapore is two and a half hours ahead of our engineering team, so calls land inside both working days. An engineer replies within one business day.
This is worth your time if
- You spend more than SGD 20,000 a month on cloud and nobody owns that number full time
- The bill has grown faster than your traffic and no one can say exactly why
- You have no dedicated FinOps function, and your platform team is busy shipping
- A migration or re-architecture is on the table and you want the numbers first
It is not for you if
You spend under SGD 5,000 a month. At that size the savings will not cover the fee and we will tell you so on the call rather than take the work.
What you actually receive
The review is a written document, so here is a page of one. Every finding carries a costed monthly saving, the engineering effort to achieve it, and the risk of doing it, ordered so you can stop reading where the effort stops being worth it.
1 · Where the spend goes
- Compute
- Storage
- Data transfer
- Idle and orphaned
2 · Findings, ordered by payback
| Finding | Monthly | Effort | Risk |
|---|---|---|---|
| No savings plan on steady-state compute | 3,090 | Low | Low |
| Over-provisioned managed database tier | 2,180 | Medium | Medium |
| Cross-zone service calls billed as inter-AZ transfer | 1,510 | Medium | Low |
| Idle NAT gateways in two availability zones | 1,240 | Low | Low |
| Unattached volumes and orphaned snapshots | 760 | Low | Low |
| Modelled monthly saving | 8,780 | SGD, before implementation effort | |
Sample layout with illustrative figures, not a client engagement. Findings are the categories this review covers; yours will differ in both substance and size.
Google Cloud
Azure
Four deliverables, all written down
Everything is handed over as something you own and can act on without us. That is deliberate: if it only works with us in the room, it is not a deliverable.
-
01
Spend breakdown by cause
Where the money goes across accounts and services, including the lines teams usually miss: inter-AZ and egress transfer, orphaned volumes and snapshots, idle load balancers, over-provisioned managed databases, and logging retention.
-
02
Savings model in SGD
Each recommendation carries an estimated monthly saving, the engineering effort to achieve it, and the risk of doing it. Ordered by payback, so you can stop reading at the point the effort stops being worth it.
-
03
Architecture risk register
Single points of failure, backup and restore gaps, publicly reachable data stores, and missing failover. Cost work surfaces these whether you asked for them or not, so you get them written down.
-
04
Walkthrough with your team
Ninety minutes with the engineers who did the work, not an account manager. Your platform team can argue with the findings, which is the fastest way to establish whether they are right.
How the 2 weeks run
Stated day by day so you can see exactly what you are committing to, and what we need from you.
-
Days 1 - 3
Access and inventory
A read-only IAM role, billing and Cost Explorer access, and one 60-minute session on how the platform is put together.
-
Days 4 - 8
Analysis
Usage and billing data, rightsizing, commitment coverage, transfer paths, and a Well-Architected pass on cost, reliability and security.
-
Days 9 - 10
Findings written up
Draft shared with your platform owner first, so factual corrections happen before anyone presents it upward.
-
Day 11
Walkthrough and handover
You keep the documents whether or not we do any further work together.
What this engagement does not include
Implementation of the recommendations, vendor or reseller negotiation, and purchase of FinOps tooling. Those are decisions you should make after you have the findings, not before. If you want us to carry on, the fee for this engagement is credited in full against that work when it starts within 60 days.
Judge us before you pay us
We are a new name to you, so here is evidence you can check yourself rather than claims you would have to take on trust.
Read our work on this exact problem
Part of 143 technical articles published under our own bylines since April 2024.
We run this ourselves
Our own products run on AWS with S3, CloudFront, RDS on a private subnet and nightly verified backups. The practices in the review are the ones we apply to our own bill.
Verify the company exists
Chadura Tech Private Limited, incorporated 8 May 2018. Our CIN and GSTINs are published and can be checked against the Indian government registers.
Company record and teamTell us about your setup
A couple of answers is enough to start. We will tell you on the first call whether this is worth doing, including when the answer is no.