Skip to content

FinOps consulting that does the work.

Most FinOps products stop at a dashboard. We are hands-on across your stack: we find the waste and fix it, in your repositories, following your process, and you pay out of what we save.

Run by Cristian Magherusan-Stanciu, a former AWS Specialist Solutions Architect and the creator of AutoSpotting. We work with teams spending $100k+/month on AWS.

A tool finds things. We fix them.

Most FinOps products are dashboards. They surface where your money goes and hand you a list, and then the list sits in a backlog because acting on it still means an engineer researching, implementing and verifying each item. The FinOps Foundation's own surveys show most companies have barely started optimizing, and of those that have, few are far along. The gap is not visibility. It is the work.

We do the work. We come in hands-on, produce the prioritised list ourselves, then implement it as pull requests in your repositories through your own review and rollout. If you already run a FinOps tool, keep it: it can feed our backlog, and you still only pay us for what actually lands on your bill.

A lower bill is the visible outcome, but the real one is efficiency: more capacity, performance and reliability out of each dollar. For fast-growing teams the absolute bill often keeps rising because the business is growing; what drops is the cost per customer or per transaction.

The money is in the long tail of small wins

A commitment or a single big line item is the easy part. Most of the savings sit in a long tail of small changes, a few hundred dollars a month each, no migration project, no architecture change. Individually none of them are worth a half day of your engineer's time, which is precisely why they never get done.

The arithmetic works for us, because we automated it.

Over many engagements we built and battle-tested tooling that covers most common optimization scenarios end to end, from detection and safety checks to execution and measurement. What costs your engineer half a day costs us half an hour. This is still a service, productized by tooling, not replaced by it: we never let the tooling act unassisted, and every change ships through your own review.

We work with your engineers, not around them

The engagements that go worst are the ones where an outside consultant does the work in a corner and hands the savings to executives. Engineers end up defending a system they did not change, and the savings decay the moment the consultant leaves.

So we do the opposite. We work closely with your engineers, give them the same tooling we use, and let them own and take credit for the savings. You choose how hands-on that is:

  • Done with you: we work side by side with your team, they participate in the decisions and keep the knowledge behind each change.
  • Done for you: we offload as much of the hands-on work as possible. Your engineers review changes instead of researching them, and a weekly sync shows what landed, what it saved and what is next.

The engagement model

We charge on results, not on effort. You grant read-only access first, so we can produce the prioritised list, then scoped, per-change write access with minimal IAM and no standing admin. Every change goes through your review and rollout, and everyone who touches your account is under NDA.

We take a share of the savings, typically 10% to 30%, sized to the footprint under our optimization scope, with larger footprints paying a lower share. Each change is billed at that share for its first 12 months and then retires, after which you keep 100% of what it saves. Savings are measured automatically from your real before-and-after billing data, per change, so nothing about the number is hand-wavy. If a change saves nothing, it is not billed.

It typically costs less than a FinOps SaaS subscription, and we will agree a cap if you want one.

Related

See the full scope of our AWS cost optimization work and one of its biggest levers, Graviton migration. Or start with a free audit and read the case studies.

FinOps consulting questions

How is this different from a FinOps tool or dashboard?

A tool finds things; we fix them. Most products stop at surfacing spend and leave the implementation to you. We produce the list and then do the work, as pull requests in your repos. Keep your tool if you have one, it can feed our backlog.

How is this different from hiring a consultant?

A consultant on a day rate advises while your engineers implement, and you pay for the hours whether or not anything lands on your bill. We do the work ourselves, through your process, and are paid on results, so we keep finding savings, including the small ones an hourly engagement would skip.

What does FinOps as a service cost?

We take a share of the savings, typically 10% to 30%, sized to the footprint under our optimization scope. Each change is billed at that share for its first year, then retires. It usually costs less than a FinOps SaaS subscription, and if a change saves nothing it is not billed.

What happens when the engagement ends?

The savings are already in your infrastructure and the self-hosted tooling stays yours, so you do not need an ongoing subscription to keep the benefits. If you want continued coverage, a continuity program keeps watching for drift and new opportunities for a fraction of a full-time hire.

Want FinOps that actually ships?

Book a discovery call. We take read-only access and give you a prioritised list of what we found and what it is worth.

FinOps that fixes, not just charts

We find and fix the long tail of AWS waste, in your repos, paid out of what we save you.