Oversized instances
Servers picked during a launch panic, still running at 6% CPU three years later.
[ AWS & Cloud / AWS Cost Optimization ]
Stop paying for cloud you don't use.
I audit your AWS account, ship the fixes myself, and prove the savings on your next invoice. No dashboards to learn. No account managers. If the bill doesn't drop, you don't pay.
Read-only access · Report in 5 days · No sales call required
30-60%typical bill reduction
5 daysto a written report
Read-onlyaccess to start
No savingsno fee
[ What I fix ]
Six places your money leaks.
Most accounts show at least four of these. None of them need a re-architecture.
No commitment coverage
Running 100% On-Demand is a standing 30-40% premium on compute you already know you need.
Storage nobody cleans
Old snapshots, unattached disks and buckets with no lifecycle rule, billing quietly forever.
Invisible data transfer
NAT Gateway and cross-AZ charges hide under EC2-Other and routinely hit four figures a month.
Environments that never sleep
Staging and QA billing through nights and weekends for exactly zero users.
No guardrails
Nothing tells you a spike happened until the invoice lands on the 3rd of next month.
[ How it works ]
Three steps. Six weeks to proof.
01 — Day 1-5
Audit
You give me a read-only role. I go through every service and send back a prioritized list: the saving, the effort and the risk for each item.
02 — Day 6-15
Implement
I ship the changes myself. Terraform pull requests where you use IaC, console changes where you don't. Canary first, always reversible.
03 — Day 30
Verify
We compare invoices. Budgets, anomaly alerts and a runbook go to your team. My fee follows the measured saving, nothing else.
[ What actually changes ]
The specific work, listed.
No black box. This is the checklist I run, and the same one your team gets in the handover runbook.
Compute
- EC2 rightsizing — 14 days of CPU, memory and network data per instance, not a 7-day guess.
- Graviton migration — ARM instances, typically 15-20% cheaper and often faster.
- Savings Plans & Reserved Instances — modeled against your usage trough, not your average.
- Spot for the right workloads — CI runners, batch jobs and stateless workers only.
- Kubernetes & ECS — requests versus limits, node consolidation, Fargate economics.
Storage, network & control
- S3 lifecycle & Intelligent-Tiering — plus the incomplete multipart uploads nobody can see.
- EBS gp2 to gp3 — around 20% cheaper per GB, live migration, no downtime.
- Orphaned volumes, snapshots and AMIs — the quiet few hundred a month.
- NAT Gateway & cross-AZ transfer — replaced with free VPC endpoints where possible.
- Tagging, budgets and anomaly alerts — so the savings survive the next two quarters.
[ Example engagement ]
SaaS platform, four-figure monthly saving.
A container platform across three availability zones with zero commitments and a data-transfer bill nobody had ever opened. Two weeks of work, no downtime, no product code touched.
Illustrative example of a typical engagement. Figures vary with the state of your systems and are not a guarantee of a specific outcome.
44%bill reduction
11 daysto full rollout
0incidents caused
6 weeksto payback
[ Free · 5 days · no obligation ]
Find out what you're wasting first.
A full written report on your account: every finding, priced and prioritized. Yours to keep and implement in-house, whether or not you hire me.
[ Pricing ]
Pricing that fits your budget.
Tell me the number you have to work with. I'll tell you honestly what's achievable within it — and if it isn't enough, I'll say so before we start rather than halfway through.
Fixed project price
Scope agreed in writing, price agreed in writing, before any work starts. No hourly creep and no invoice you haven't already approved.
Monthly retainer
For ongoing work — maintenance, monitoring, updates and small changes. Month to month, cancel whenever, no minimum term.
Hourly for small jobs
For a single bug or a short task where writing a full scope would cost more than simply doing the work.
Budget too tight for the whole thing? I'll often suggest doing the highest-value part first and the rest later, rather than doing all of it badly.
[ Questions ]
The things people ask.
How much can I actually save?
It depends on how long the account has been running untouched. Accounts that have never been rightsized and have no commitments in place see the largest reductions; teams already running a FinOps practice see less. The free audit gives you your specific number before you commit to anything.
What access do you need?
A read-only IAM role scoped to my account with an external ID. No write permissions during the audit. If we go ahead with implementation, we agree the scope together and you revoke it when the work is done.
Will this break anything?
Changes go out in risk order. Zero-risk first — deleting unattached disks, buying Savings Plans, adding VPC endpoints — none of which touch running workloads. Rightsizing rolls out as a canary with an explicit rollback, inside your change window.
What does it cost?
The audit is free. If I implement, it is a percentage of the first twelve months of verified savings, billed once — not a slice of your bill forever. Fixed-price is available if procurement needs a purchase order.
I already use a cost tool. Why do I need you?
Cost tools tell you where the money goes. They do not rewrite your Terraform, migrate you to ARM instances, or restructure a VPC to remove NAT charges. What is left after a tool has reported needs engineering, not more reporting.
Can you keep managing things afterwards?
Yes. Most clients continue with a monthly retainer covering patching, monitoring and cost review. Optional, month-to-month, cancel any time.
[ Related services ]
Same engineer, other problems.
AWS EC2 ManagementProvisioning, scaling, patching and rightsizing for EC2 fleets.AWS S3 OptimizationLifecycle rules, storage classes, CDN and egress cost control.DevOps ConsultingDeployment, reliability and process for teams without a DevOps hire.AWS Server SetupProduction-ready VPC, compute, database and CI/CD from scratch.Server Security HardeningLock down SSH, firewall, patching and access before it costs you.CI/CD & GitHub ActionsAutomated build, test and deploy pipelines with real rollbacks.
[ Let's talk ]
Tell me what's broken.
Describe the problem in a few lines and you'll get a real reply from the person who'd do the work — same working day, no discovery call required.