The Shape of Top-down FinOps
FinOps fails when it starts at the bottom. Top-down FinOps ties every optimisation to strategy: leadership sets intent, platform allocates time, managers put work in the backlog, and engineers deliver with recognition. …
Connections
Why clarity at the top creates action at the bottom
FinOps today is built almost entirely bottom-up.
Engineers get a dashboard. A bot posts a list of idle resources. Someone is told to resize a cluster “when you have time”. People assume that if a saving exists, it should magically matter to leadership.
But most bottom-up activity never connects to anything strategic.
Executives see noise. Engineers see chores.
And the company wonders why nothing changes at scale.
This month I am focusing on top-down FinOps because the industry has lost the chain of intent — the path from strategy to execution that ensures every action has meaning beyond the sprint.
A healthy organisation moves through seven layers when turning intent into work: strategy, translation, coordination, architecture, measurement, planning, execution.
Most organisations skip straight to execution and hope for the best.
Here is how the whole system should work.
<div class="kg-header-card-content">
<div class="kg-header-card-text kg-align-center">
<h2 id="all-the-topdown-finops-articles" class="kg-header-card-heading" style="color: #FFFFFF;" data-text-color="#FFFFFF"><span style="white-space: pre-wrap;">All the Top-down FinOps articles</span></h2>
<p id="for-you-to-enjoy-and-share" class="kg-header-card-subheading" style="color: #FFFFFF;" data-text-color="#FFFFFF"><span style="white-space: pre-wrap;">For you to enjoy and share</span></p>
</div>
</div>
</div><figure class="kg-card kg-bookmark-card"><a class="kg-bookmark-container" href="https://frankcontrepois.com/tag/topic-top-down-finops/"><div class="kg-bookmark-content"><div class="kg-bookmark-title">Topic - Top down FinOps - Context is everything</div><div class="kg-bookmark-description">Frank Contrepois on FinOps: insights, practical tools, and workshops that bring context to every cloud decision.</div><div class="kg-bookmark-metadata"><img class="kg-bookmark-icon" src="https://frankcontrepois.com/content/images/icon/Red-glasses-Monk-square-1.png" alt=""><span class="kg-bookmark-author">Context is everything</span><span class="kg-bookmark-publisher">Frank Contrepois</span></div></div><div class="kg-bookmark-thumbnail"><img src="https://frankcontrepois.com/content/images/thumbnail/41181479_s-1.jpg" alt="" onerror="this.style.display = 'none'"></div></a></figure><hr><h2 id="the-seven-layers-in-practice">The seven layers, in practice</h2><h3 id="ceo-%E2%80%94-strategy"><strong>CEO — Strategy</strong></h3><p>“We will reduce cloud waste and reinvest the savings into our 2026 AI roadmap.”<br>One sentence. Clear purpose. No technical noise.<br>This layer answers: <em>why does this matter?</em></p><h3 id="cto-%E2%80%94-translation"><strong>CTO — Translation</strong></h3><p>“Each team will reduce avoidable spend by fifteen per cent over the next two quarters.<br>No reliability impact. Cloud Efficiency Lead appointed. Monthly reporting.”<br>This layer defines what must happen and the constraints around it.</p><h3 id="vp-engineering-%E2%80%94-coordination"><strong>VP Engineering — Coordination</strong></h3><p>“Efficiency work will be part of quarterly planning.<br>Every group will deliver three high-impact optimisations.<br>Shared dashboard for progress.”<br>Now the organisation begins to move as one.<br>This layer aligns; it does not instruct.</p><h3 id="head-of-platform-%E2%80%94-architecture-and-resource-allocation"><strong>Head of Platform — Architecture and Resource Allocation</strong></h3><p>“We will focus on idle compute, over-provisioning, storage lifecycle and untagged assets.<br>Platform tooling will support the work; product teams own the fixes.<br>We are reserving sprint capacity across teams specifically for these optimisations.”<br>This is where the work becomes technical and funded.<br>Platform does not merely <em>suggest</em> improvements; it allocates time.</p><h3 id="finops-lead-%E2%80%94-measurement-and-opportunity"><strong>FinOps Lead — Measurement and Opportunity</strong></h3><p>“We will baseline waste, quantify savings, identify the most impactful actions, and publish weekly insights that make the right choices obvious.”<br>FinOps provides the truth. They surface leverage. They contextualise.<br>They give recommendations not tasks.</p><h3 id="engineering-manager-%E2%80%94-planning"><strong>Engineering Manager — Planning</strong></h3><p>Here is where your principle kicks in: <strong>if it’s not in the backlog, it doesn’t exist</strong>.<br>FinOps recommendations become backlog items like everything else.<br>Managers decide sequencing, sprint capacity and trade-offs.</p><p>During the optimisation window, feature delivery slows—deliberately and safely.<br>FinOps work becomes first-class engineering work, not something people squeeze into evenings or guilt.</p><h3 id="engineers-%E2%80%94-execution-and-recognition"><strong>Engineers — Execution and Recognition</strong></h3><p>Engineers deliver optimisation tasks the same way they deliver features:<br>resize, refactor, scale to zero, add lifecycle policies, fix tagging pipelines.</p><p>Because time was allocated and work was prioritised, engineers can succeed without heroics.<br>And because savings are measured, they are recognised.<br>Optimisation becomes part of engineering achievement, not invisible labour.</p><hr><h2 id="other-layers-that-quietly-shape-the-system">Other layers that quietly shape the system</h2><p><strong>CFO</strong> — validates reinvestment logic and confirms financial guardrails.<br><strong>Security</strong> — ensures optimisations do not violate controls or compliance.<br><strong>Product leadership</strong> — balances cost improvements with customer value and roadmap timing.</p><p>These layers influence what is possible even when they are not visible.</p><hr><h2 id="why-top-down-finops-matters">Why top-down FinOps matters</h2><p>Bottom-up FinOps asks engineers to fix things with no connection to strategy.<br>Top-down FinOps makes FinOps meaningful: leadership sponsors the work, platform allocates time, managers convert recommendations into backlog items, and engineers execute inside the normal workflow — with recognition.</p><p>This is the shift the industry needs:<br>from tactical resizing to strategic impact,<br>from “we saved money” to “we advanced the plan”,<br>from splashes to waves.</p><p>That is the shape of top-down FinOps.</p>