Shiftmove cut commitment risk by two-thirds without rewriting a workload.

What Shiftmove asked of Cloud Capital

Wouter Hendricks knew the AWS bill was going to be a problem before he opened it. Shiftmove had been built through the merger of Avrios and Vimcar, then expanded with Telematics. What looked like one company on the cap table was, inside AWS, a 36-account organization with overlapping environments, four primary cost centers, and legacy accounts that mixed production and non-production workloads under a single roof. Every quarter, Wouter walked into board reviews with Battery Ventures carrying a number he couldn't fully defend. Cloud spend was one of Shiftmove's largest operating expenses and its most volatile. It moved with the business in ways finance couldn't model and engineering couldn't predict in advance.

The annual budget made the gap visible. Engineering would build a forecast in Google Sheets, applying growth rates to historical spend across the four primary accounts. Finance would receive it, accept it, and have no independent way to challenge it. When the actuals came in differently — and they always came in differently — there was no shared model to point to. Just two teams trying to explain the same number from different directions.

The instinct on the engineering side was to optimize harder. Tighter Reserved Instance coverage. More aggressive Savings Plans. But every move toward higher commitment coverage moved Shiftmove further out on a risk curve they were holding alone. The optimization Wouter needed required absorbing variance the company didn't want on its balance sheet.

What changed for Shiftmove

Shiftmove's requirements were governance-first, and they were not negotiable. IAM roles were provisioned through Terraform. SCPs were applied across the org. Compliance posture had been hardened over years. The AWS environment was working. Engineering wasn't looking for someone to come in and improve it. What Shiftmove needed was someone to take the financial risk of optimization off the company's balance sheet, give finance a defensible forecast, and do both without touching a workload, moving an account, or changing the security model.

Shiftmove would capture the savings from aggressive AWS commitment coverage. Cloud Capital would absorb the downside if actual usage fell short of forecast.

Implementation was limited to billing and account setup, IAM configuration, and data alignment. Cloud Capital became the underwriter of Shiftmove's commitment portfolio. Read-only cost and usage access plus a scoped purchase role, both provisioned through Shiftmove's existing Terraform pipeline. No re-architecting, no re-tagging, no account moves, no SCP changes. Within 90 days, commitment coverage moved from 34% to 75%. Shiftmove's share of commitment utilization risk dropped from 100% to 34%, and continued declining. Today it sits at 12%, with Cloud Capital absorbing 88% of the downside.

Six-figure annualized savings flowed directly into operating margins. The annual budgeting cycle stopped starting in a Google Sheet. Engineering's monthly time on cost management fell by more than 80%. The recurring escalations between finance and engineering stopped. The two teams now work from the same forecast, refreshed monthly, with both sides able to read it.

What it changed for the business

Wouter walks into board reviews with Battery Ventures carrying a different number now. AWS isn't the line item finance has to apologize for anymore. It's governed, it's forecastable, and it scales with the business in a way both finance and engineering can stand behind. The four subsidiaries each have a clean view of their own spend. New accounts inherit coverage automatically.

Cloud is one of the largest line items on Shiftmove's P&L. Now it's managed like one, with finance and engineering working from the same forecast, and the financial risk of optimization sitting where it belongs.

Achieved within 90 days. No account moves, no re-architecture, no re-tagging, no SCP changes.