Skip to content
The gap How it works Results Pricing About FAQ
Sign up

Scoped Implementation Project

3 min read

Most engagements start the same way. Not with a transformation program, and not with an assessment that takes a quarter. With one scoped project: a specific set of changes, each with the savings named before we begin.

The first call

We start with a short call with one or two of your engineers. We walk through your cloud architecture, and through whatever your own tooling has already surfaced. If you have a FinOps practice, its dashboards and its backlog are the starting point rather than something to redo.

We look at the billing console and your main cost drivers together, then at the resources behind them. Anything harmless that can be fixed on the spot usually gets mentioned right there.

What you get back

A list of specific changes, each with an estimated saving, the effort to implement it, and any caveats worth knowing about. That much is what most vendors call a report and stop at.

The difference is what the list is for. It is a work plan, scoped so that I can implement it with zero or close to zero involvement from your engineers. It isn’t a set of recommendations for somebody else to schedule.

Alongside it comes a proposal: which of those changes the first project covers, what it costs, and how we would work together after that.

Then the work happens

Once we agree and the prerequisites are in place, I implement the changes. Config-level work, instance and volume migrations, resource cleanup, and small pull requests that are trivial to review. The savings live in your infrastructure rather than in a subscription, so they stay once the engagement ends. On a flat fee or a retainer that means you keep all of it from day one; on the savings-share model the agreed share applies for each change’s first 12 months, and after that you keep all of it too.

Nothing stops you from taking the list and implementing it with your own engineers instead. Some teams do. Most of the teams we work with have already tried that, and found that cost work loses to the roadmap every sprint, which is the whole reason this service exists.

What it costs

Three ways, and we’ll tell you which one fits:

  • Scoped project. A flat fee for an agreed set of implementations.
  • Monthly retainer. An agreed block of engineering hours each month, working through your queue in your priority order. Priced case by case, against your scope and what you need.
  • Share of savings. A percentage of what each change measurably saves, billed for its first 12 months and measured from your real before-and-after billing data. A change that saves nothing isn’t charged for.

All three can be billed through AWS Marketplace, so the money comes out of the cloud budget you already have rather than needing a new line item and its own procurement cycle.

Please contact us if this sounds interesting or you have any questions.