I keep seeing the same pattern in growth-stage companies.
Cloud spend rises.
Delivery slows.
Complexity increases.
And the instinct is:
“Should we rebuild?”
Usually, that’s the wrong first move.
Before rewriting anything, I ask a simple question:
When was the last time someone actually opened AWS Cost Explorer (or any otherr cloud) and reviewed the last 6 months of spend?
When was the last time you checked on all the company subscriptions to endless tools?
Not yesterday.
Six months.
In most companies I see:
- Storage is heavily over-provisioned
- Databases have 200GB allocated for 10GB of real data
- Idle environments sit untouched
- “Temporary” services never get turned off
And here’s the part most teams miss:
Those costs often don’t show under “EC2 instances.”
They hide under EC2-Other.
Which means they don’t get questioned.
I’ve seen meaningful cost reductions without touching core architecture — just by introducing ownership and review cadence.
The problem usually isn’t tooling.
It’s that infrastructure cost has no clear owner.
Rebuilds feel strategic.
Cost discipline feels operational.
Only one improves margin immediately.
Most of the time, the real leverage isn’t building something new.
It’s subtracting what shouldn’t be there.
If your platform is live and things feel heavier, slower, or more expensive than they should, I’m happy to do a short sanity-check call.