FinOps Opportunities

How to track FinOps opportunities across GitLab: lifecycle stages, owners, labels, and status notes

Overview

Every FinOps opportunity across GitLab should be visible in one place, with its status, no matter which team opened it. A FinOps opportunity is any change that reduces our cloud costs or gets more value from them; the name follows the FinOps::Opportunity labels. We track each opportunity in a GitLab issue, and labels on the issue show its stage.

When we talk about the outcome, we say run-rate reduction, not cost savings: see Run-rate reduction, savings, and cost avoidance.

Tracking is not the goal on its own. It shows where opportunities get stuck, so we can remove the roadblock and land the change.

Most of this page is in two parts:

This page holds no cost figures. Figures live only in internal notes on the issues; see Communication and Confidentiality.

What counts as an opportunity

We track value, not only run-rate reduction. A change that lets us serve more for the same spend counts, even when the bill does not go down.

An opportunity is one of:

  • Run-rate reduction: the cloud bill goes down, for example rightsizing, deleting idle resources, or a cheaper storage class.
  • Efficiency: we serve more for the same spend, for example higher utilization of an existing node pool.
  • Cost avoidance: a guardrail or automation that stops a cost from reaching the bill, for example a default lifecycle policy or a CI check.

Opportunities come from two sources, and both follow the same process:

  • The CCU team, from cost analysis and, later, automated findings (for example GCP Recommender).
  • Engineering teams, who find optimizations in the services they own.

Run-rate reduction, savings, and cost avoidance

We track opportunities by their run-rate reduction, not by savings. The terms measure different things:

  • Run-rate reduction is an engineering number: a validated cut in what a service costs per month, times 12. The owning team records it on the opportunity issue, and FinOps validates it from billing data. It is counted gross per change, and setbacks are shown beside it.
  • Savings is a finance number: the annual operating plan (AOP) minus actual costs, counted once at month close. Until then, it is estimated savings. Savings need a budget to compare with: we can cut the run rate and still end over the AOP.
  • Cost avoidance is a cost that never reached the bill, because we acted first. It has its own line and never counts toward the run-rate reduction target, because the bill has no “before” to compare with.

Every saving is a run-rate reduction, but not every run-rate reduction is a saving. When unsure, say run-rate reduction.

Roles

  • Author: whoever opens the opportunity issue, for example a CCU team member or an engineer in the owning team.
  • Owning team: the team that owns the infrastructure resources in scope of the opportunity (the service-owning team). Its engineering manager (EM) commits to delivery.
  • Cloud Cost Utilization (CCU) team: owns the framework, the process, and the automation that suggests opportunities. Helps the author engage the owning team.
  • FinOps TPM: oversees the FinOps program.

Track an opportunity

This walkthrough follows one opportunity from idea to closed issue. Each step names who acts. For the formal definitions, see Stages.

Open and label the issue

As the author:

  1. Open an issue in the project of the team that owns the change, with that project’s usual template.
  2. Describe the opportunity without cost figures. Cover the points in Issue description.
  3. Add the labels FinOps::Cost-Optimization and FinOps::Opportunity::Proposed.
  4. Add the owning team’s group::<group> label, and a Service::<service> label for the affected service where one applies. See Labels. If you do not know the owning group yet, find it out while the opportunity is Proposed: it must be set before the opportunity is Confirmed.
  5. Add the owning team’s other usual labels, for example category labels, so the issue also appears on their boards.
  6. Post a status note as an internal note, with the estimate if you have one.

While the opportunity is Proposed, the author works out three things: the owning group, the affected service where one applies, and the estimated run-rate reduction.

Move the opportunity through its stages

Whoever moves the issue to a new stage changes its stage label and posts a new status note.

  1. Proposed ⟶ Confirmed: the author and the CCU team engage the owning team. When the owning team confirms the opportunity and the estimated run-rate reduction, make sure the issue has the owning team’s group::<group> label (and a Service::<service> label where one applies), then change the label to FinOps::Opportunity::Confirmed.
  2. Confirmed ⟶ Committed: the owning team’s EM commits to deliver the change by a due date. Set the due date on the issue and change the label to FinOps::Opportunity::Committed.
  3. Committed ⟶ Implemented: the owning team ships the change. When it is fully live, change the label to FinOps::Opportunity::Implemented.
  4. Implemented ⟶ Realized: within 14 days, the owning team measures and documents the run-rate reduction, with support from the CCU team and the FinOps TPM. Change the label to FinOps::Opportunity::Realized, post the final status note, and close the issue.

If you decide not to pursue the opportunity before it reaches Implemented, for any reason (for example, it is not feasible or does not reduce cost): change the label to FinOps::Opportunity::Discarded, explain why in the issue, and close it.

Committed and Implemented have a service level objective for how long an opportunity stays in them. The SLOs for Proposed and Confirmed are still to be defined.

Process reference

Stages

An opportunity is in exactly one stage at a time. The regular path runs from Proposed to Realized. Each arrow names who owns that transition.

flowchart TD
  P["<b>Proposed</b><br/>Not yet confirmed by the owning team"]
  C["<b>Confirmed</b><br/>Opportunity and estimate confirmed"]
  CM["<b>Committed</b><br/>Delivery committed with a due date"]
  IM["<b>Implemented</b><br/>Change shipped and fully live"]
  R["<b>Realized</b><br/>Run-rate reduction measured and documented<br/><i>Final, issue closed</i>"]
  DS["<b>Discarded</b><br/>Not pursued, reason in the issue<br/><i>Final, issue closed</i>"]
  subgraph main[" "]
    direction LR
    subgraph pre[" "]
      direction LR
      P
      C
      CM
    end
    IM
    R
  end
  P -->|"<b>Author and CCU team</b><br/>get the owning team to confirm"| C
  C -->|"<b>Owning team EM</b><br/>commits to deliver"| CM
  CM -->|"<b>Owning team</b><br/>ships the change"| IM
  IM -->|"<b>Owning team</b>, CCU and FinOps TPM support<br/>measure the run-rate reduction within 14 days"| R
  pre -.->|"discarded, from any stage in the dashed box"| DS
  classDef state fill:#f3f4f6,stroke:#4b5563,color:#1f1f1f
  classDef final fill:#d1d5db,stroke:#374151,color:#1f1f1f
  class P,C,CM,IM state
  class R,DS final
  style main fill:none,stroke:none
  style pre fill:none,stroke:#9ca3af,stroke-dasharray:5 5
Stage Meaning Moves on when Owner of the next transition SLO
Proposed Proposed, but not yet reviewed or confirmed by the owning team. The owning team confirms the opportunity, and the issue has the owning team’s group:: label. Author and CCU team, who engage the owning team To be defined
Confirmed The owning team confirmed the opportunity and the estimated run-rate reduction. The issue has the owning team’s group:: label. The owning team commits to deliver. Owning team’s EM To be defined
Committed The owning team committed to deliver the change by a due date. The change ships. Owning team The committed due date
Implemented The change has shipped and is fully live. The run-rate reduction is measured. Owning team, supported by the CCU team and the FinOps TPM 14 days
Realized The run-rate reduction has been measured and documented. Final stage: close the issue. Not applicable Not applicable
Discarded Not pursued, for any reason, for example not feasible or no cost reduction. The issue says why. Final stage: close the issue. Not applicable Not applicable

Service level objectives

The service level objective (SLO) for a stage is the maximum time an opportunity should stay in it before it moves to the next stage. The due date on the issue shows when the current stage’s SLO runs out:

  • Committed: the owning team’s EM sets the due date when committing to deliver the change.
  • Implemented: when an opportunity moves to Implemented, automation will set the due date to 14 days later and send the owning team a reminder to measure the run-rate reduction.

Labels

We use FinOps issue labels in both the gitlab-com and gitlab-org groups. Every opportunity issue has:

  • FinOps::Cost-Optimization, which marks it as a FinOps opportunity, whatever its stage.
  • Exactly one FinOps::Opportunity::<Stage> scoped label for its current stage, for example FinOps::Opportunity::Confirmed. Because the label is scoped, adding a new stage label removes the previous one.
  • The owning team’s group::<group> label, for example group::gitaly, which names the owning team. It is required from Confirmed on, and best added when the issue is opened.
  • Where the opportunity affects a specific service, a Service::<service> label, for example Service::Gitaly. It is optional: some opportunities, such as a billing model change, affect no single service. Service:: labels exist in the gitlab-com group only.
  • The owning team’s other usual labels, for example category labels.

Status note format

A status note records the current status and estimate of an opportunity. Post one as an internal note whenever the stage or the estimate changes. Start the comment with /internal_note:

/internal_note

## FinOps status

Status: <Where does this stand at the moment?>

```yaml
estimated_annual_run_rate_reduction: 120000
```

Estimation basis: <How can we estimate (and later measure) the run-rate reduction in billing data?>
Part Format Content
Status: Text after the label Where the opportunity stands at the moment.
estimated_annual_run_rate_reduction Whole US dollars per year, digits only, for example 120000 The run-rate reduction from this opportunity: the monthly cost cut, times 12. Only for run-rate reduction opportunities.
Estimation basis: Text after the label How the run-rate reduction is estimated, and how it can later be measured in billing data. Say whether the figure is measured or estimated. For efficiency or cost avoidance opportunities, describe the value gained here instead.

Follow these rules, so that tools can read the notes:

  • Keep the ## FinOps status heading, the Status: and Estimation basis: labels and the field name estimated_annual_run_rate_reduction exactly as shown.
  • Keep the figure in the yaml block, with digits only.
  • If the estimate is not known yet, leave out the yaml block. Never write 0 for an unknown value.
  • For efficiency and cost avoidance opportunities, leave out the yaml block: they do not reduce the run rate, so a figure there would count toward the run-rate reduction.
  • Post a new note rather than editing an old one. The latest note is the current status, and earlier notes are its history.

Issue description

The issue description explains the opportunity, without figures:

  • What and where: the service (gl_service, also as a Service:: label where one applies), the cloud provider and project or account, and the resources affected.
  • Baseline: how the current cost or usage was measured, for example a query or a dashboard link. The baseline figure itself is not recorded.
  • Estimate: how the run-rate reduction is estimated, and its assumptions. The figure goes in the status note.
  • Owner: the DRI in the owning team.
  • Confidentiality: keep the issue public, and put figures only in the internal status note. If a description in a public project already holds figures, mark the issue confidential.

Where to see opportunities

In FY27 Q4, we are working on making FinOps opportunities more visible to leadership and teams, for example on service and team pages in the Engineering Portal. See the FinOps opportunities in Backstage epic.