New Savings Proposals: approve, test and roll back cost changesLearn more Sign in|Talk to a cloud engineer
Product tourGet a demo

Low-risk savings you can finish before lunch

High-confidence fixes grouped by the action they need: release, delete, stop or resize. Each group comes with the command ready to copy. Run it, mark it done, and the next scan confirms it.

Get a demoSee all recommendations
What you're watching
  1. 1
    Open Apply Fix on unattached volumes

    Delete 22 unattached EBS volumes: detached over 7 days, 97% confidence, $516/mo. The delete commands are already written.

  2. 2
    Copy the command and run it

    You run it with your own credentials. CloudLens stays read-only.

  3. 3
    Click “I did it”

    The row shows Marked done. The next scan verifies the change before anything is counted.

  4. 4
    Route the sandbox VMs to Teams

    Idle sandbox VMs belong to another team, so Route posts them to Cloud Ops › Alerts with owner and saving.

Who does thisCloud engineer, between two meetingsWhat you get$516/mo of unattached volumes cleared, and a $1,380/mo item in front of its owner.
Ready now47quick wins in the sample estate
Worth$3,390/mowith confidence of 90% or more
Grouped byActionnot by detector
Actions6release, delete, terminate, stop, resize, review

Sample data from a fictional company.

Easy savings sit in the backlog for months

Unattached volumes and old snapshots are low risk, but someone still has to check and remove them.

Waste

Leftovers nobody prioritizes

What usually happens: Unattached volumes and unused Elastic IPs cost a little each, so they never make a sprint and keep billing month after month.

How CloudLens resolves it: They are grouped into one decision per action, with the total saving and the command, so one engineer can clear them in a sitting.

Resolved
Ops

Remediation commands typed by hand

What usually happens: Someone looks up the CLI syntax for each resource type and hopes the flags are right.

How CloudLens resolves it: Apply Fix shows the remediation command for the group, ready to copy and run with your own credentials.

Resolved
Ownership

Fixes that belong to another team

What usually happens: A cleanup request in a general channel gets a thumbs-up and no owner.

How CloudLens resolves it: Send it to Jira with the resources filled in, or post it to the owning team’s Slack or Teams channel.

Resolved

How Jonas cleared a batch of leftovers in 20 minutes

A gap between two meetings, used on waste that had been billing for months.

JWJonas WeberCloud engineer, Lumora Retail

Lumora Retail is a fictional company. The people, names and numbers are sample data.

    1
    Wed 13:00

    Opens Quick Wins

    The Delete group lists 22 unattached volumes left behind by the retired batch fleet, all above 90% confidence.
    2
    Wed 13:05

    Reviews the list

    Every volume has been detached for more than 30 days and none are tagged as backups.
    3
    Wed 13:08

    Copies the command

    Apply Fix shows the delete command for the group. Jonas runs it from his own terminal with his usual credentials.
    4
    Wed 13:15Awaiting next scan

    Clicks “I did it”

    The group shows as done, but the saving is not counted yet.
    5
    Wed 13:20

    Routes the NAT gateway to its owner

    The idle NAT gateway in staging belongs to Shared Services, so he posts it to their Teams channel instead of deleting it himself.
    6
    Thu 06:00Confirmed

    The next scan confirms it

    The volumes are gone. The saving moves into the realized savings ledger once the bill reflects the change.
Unattached volumes still billing every hour?

Find your quick wins in one scan

Get a demo

Grouped by the action, not by the detector

Twenty-two unattached volumes are one decision, not twenty-two. Quick Wins bundles them so one engineer can clear a whole class of waste.

One action per group, six in total

Every quick win maps to one action: Release, Delete, Terminate, Stop (deallocate), Migrate/Resize or Review. Each group shows how many resources it covers, what it saves and how confident the detector is. Review is for the ones that deserve a human look first, like old snapshots.
  • Release, Delete or Terminate
  • Stop (deallocate) for idle VMs
  • Migrate or resize, like gp2 to gp3
  • Review first for old snapshots
What you're watching
  1. 1
    One card per action

    Release, Delete, Terminate, Stop (deallocate), Migrate / Resize and Review, each with its resource count and monthly saving.

  2. 2
    See the command for each

    aws ec2 release-address for 6 Elastic IPs, az vm deallocate for 9 Azure VMs, aws ec2 modify-volume for 41 gp2 volumes.

  3. 3
    Review the risky ones first

    64 snapshots older than 90 days open as a list for a person to check before anything is deleted.

Who does thisCloud engineerWhat you getSix decisions instead of 144 separate line items.

Send it to the team that owns it

Slack & Teams integration
Create a Jira issue with the saving and resources filled in, or post the quick win to a Slack or Microsoft Teams channel so the owning team sees it where they already work. Jira status syncs back to CloudLens.
  • Create Jira issue
  • Post to Slack
  • Post to Teams
  • Status synced from Jira
What you're watching
  1. 1
    Create a Jira issue

    Stop 9 idle sandbox VMs in analytics-rg, $1,380/mo, becomes FINOPS-231, assigned to Data Platform and labeled quick-win.

  2. 2
    Status syncs back

    When the issue moves to In Progress in Jira, CloudLens shows the same status.

  3. 3
    Post it to Slack

    #cloud-cost-alerts gets “Quick win ready” with the saving, 95% confidence and an Open in CloudLens button.

Who does thisFinOps lead handing work to the owning teamWhat you getThe fix sits on Data Platform's board, and its Jira status shows up in CloudLens.

Marking it done starts verification

Clicking “I did it” tells the team it is handled. The saving only shows as realized after the next scan sees the change and the bill reflects it. In the example, the gp2 to gp3 migration on mobile-api-asg counts as $516/mo only once billing shows it.
  • Mark done
  • Checked on the next scan
  • Realized savings ledger
What you're watching
  1. 1
    Move gp2 to gp3 through the statuses

    The mobile-api-asg migration goes from Not Started to In Progress, then Addressed.

  2. 2
    Nothing is counted yet

    Addressed only means someone says it is done. Realized savings still reads $38,210 for the quarter.

  3. 3
    Billing confirms $516/mo

    Once the bill shows the drop, the ledger adds it. Resources that simply vanished are never counted.

Who does thisCloud engineer, then the FinOps lead who reports the numberWhat you getOnly savings the bill confirms reach the ledger.

The command, ready to copy

Apply Fix shows the remediation command for the group. You run it with your own credentials, and CloudLens stays read-only.

High confidence only

Quick Wins only includes low-risk findings the detector is sure about. Anything riskier belongs in a Savings Proposal.

Minutes, not sprints

Grouping by action turns dozens of line items into a few decisions an engineer can clear between meetings.

When a change needs approval, use a proposal

01 · Find

Recommendations

Priced per resource, owned and tracked.

You are here

Quick Wins

Safe fixes with the command ready.

03 · Change safely

Savings Proposals

Approve, dry-run, apply, roll back.

04 · Automate

Scheduler

Stop non-prod when nobody's using it.

Quick Wins questions

Not from Quick Wins. You copy the command and run it yourself. If you want CloudLens to apply changes with approvals, dry runs and rollback, use Savings Proposals.

Low risk, high detector confidence and a clear action, for example an unattached volume or an unused Elastic IP.

The next scan still sees the resource, so the saving is not counted as realized.

Yes, for example stopping and deallocating idle virtual machines.

Ready to see CloudLens in action?

Connect a read-only AWS role or Azure service principal. We'll walk you through your bill, your security graph and the first things worth fixing.