Consulting
AWS FinOps consulting that starts with your bill, not a retainer
I help teams cut their AWS spend and keep it cut. Engagements are short and scoped: a cost review of your current bill, fixes implemented with your team, and the process left behind so the savings hold.
Delivered remotely from Cape Town (GMT+2) by a cloud architect with 15 years in AWS and FinOps, currently running technology operations inside a SaaS company, so the advice reflects what ships, not what sounds good in a deck.
Last updated
Engagement scopes
Three shapes. Most clients start with the first.
-
Cloud cost review
Where most clients start
A read-only pass over your recent bill, commitments, storage and data transfer. You get the findings ranked by dollar impact, with the quick wins separated from the structural changes.
-
FinOps process setup
Make the savings hold
The review is the start, not the win. Tagging and allocation, commitment strategy, a monthly cost ritual your team actually runs, and dashboards that make drift visible before the invoice does.
-
AI enablement for teams
Beyond the demo
Hands-on workshops that move your team from demo-ware to daily workflows: where AI fits your stack, where it does not, and the guardrails that keep it useful and safe.
How an engagement runs
-
Call
A short call, then a written scope
You describe your AWS footprint and what you want out of the engagement. You get a fixed scope and quote in writing before any work starts.
-
Review
The review, read-only
I work from your recent bill and cost data. No changes to your account during the review, and everything found lands in a ranked findings document.
-
Implement
Implementation with your team
We action the findings together, in your console and your repos, so the knowledge stays with your team when the engagement ends.
Frequently asked questions
What does AWS FinOps consulting cost for an enterprise?
It depends on scope. Every engagement is scoped before any work starts: after a short call covering your AWS footprint and goals, you get a written fixed-scope quote. Enterprises typically start with a cost review of the current bill, then decide on implementation support from there.
How much can AWS cost optimisation actually save?
It varies by workload. In one documented case, an e-commerce technology company was shown savings of $175K per year, actioned within 60 days. Typical wins come from commitment coverage, right-sizing, storage lifecycle and data transfer paths rather than from any single lever.
Do you work remotely and in which time zone?
Yes, engagements run remotely. Hermann is based in Cape Town, South Africa (GMT+2), which overlaps comfortably with both European and US East Coast working hours.
How do we get started?
Start with a short conversation covering your AWS footprint and what you want to achieve. If a cost review makes sense, the first practical step is a read-only look at your recent bill and cost data, with findings and a scoped quote before any paid work begins.
Your next bill is the easiest place to find budget.
Tell me about your AWS footprint and what you are trying to fix. You get a scoped quote before any work begins. The longer writing on AWS cost optimisation, including the full case study, lives on savings.easyentropy.com.