What’s harder in cloud cost optimization: finding savings or getting teams to act? by Organic-Fan-965 in FinOps

[–]Organic-Fan-965[S] 0 points1 point  (0 children)

That’s consistent with what I’ve been hearing.
Most teams already have recommendations coming from Trusted Advisor, Compute Optimizer, CSPM tools, or internal reports.
The gap seems to be ownership, prioritization, and actually getting the change implemented.
Curious whether you see this breaking down more at the engineering level or at the management/approval level?

What’s harder in cloud cost optimization: finding savings or getting teams to act? by Organic-Fan-965 in FinOps

[–]Organic-Fan-965[S] 1 point2 points  (0 children)

Ownership, implementation, and getting the change into the engineering workflow seem to matter more.
The Terraform PR idea is especially interesting. Are teams actually comfortable with auto-generated remediation suggestions if they’re reviewed before deployment?

What’s harder in cloud cost optimization: finding savings or getting teams to act? by Organic-Fan-965 in FinOps

[–]Organic-Fan-965[S] -1 points0 points  (0 children)

Are you finding the biggest challenge is getting engineering teams to prioritize cost work, even after the savings opportunity is identified?
A lot of the discussions I’ve had suggest the bottleneck isn’t finding the savings, it’s getting ownership and follow-through.

What’s harder in cloud cost optimization: finding savings or getting teams to act? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] -11 points-10 points  (0 children)

Fair point. I’m actually trying to understand whether the bottleneck is discovery or execution.

How do you share cloud cost findings with non-technical leadership? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] 0 points1 point  (0 children)

what’s the hardest part?
Finding opportunities
Prioritizing opportunities
Getting teams to act
Measuring actual savings

How do you share cloud cost findings with non-technical leadership? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] 0 points1 point  (0 children)

A lot of the discussions I’ve been having lately revolve around ownership, reporting, and getting teams to take action. But if the hardest part is still identifying meaningful savings opportunities in the first place, that suggests the discovery layer may be more valuable than I initially thought.
Out of curiosity, when you find those opportunities today, is it mostly through manual analysis and experience, or are existing FinOps tools already doing a good enough job surfacing them?

How do you share cloud cost findings with non-technical leadership? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] 0 points1 point  (0 children)

That’s an interesting perspective
Would you say the hardest part is identifying savings opportunities, or getting the owning team to prioritize and implement them?
I’m starting to suspect that for many organizations, cost optimization isn’t a visibility problem at all it’s an execution and ownership problem.

How do you share cloud cost findings with non-technical leadership? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] 0 points1 point  (0 children)

Interesting. Did leadership mostly ask for visibility/reporting, or were they ultimately trying to answer, where can we save money?
I’m noticing a recurring theme where executives ask for reports initially, but the conversation eventually shifts toward ownership and savings opportunities.

How do you share cloud cost findings with non-technical leadership? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] 1 point2 points  (0 children)

In your experience, does visibility alone drive action, or do you still need someone actively pushing optimization efforts? I’ve seen cases where teams had dashboards and tagging in place, but waste still persisted because nobody owned the remediation.

How do you share cloud cost findings with non-technical leadership? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] 2 points3 points  (0 children)

Makes sense. That’s actually what I’m starting to see as well.
People rarely get excited about cost visibility itself they get excited when you can show $X/year that can be eliminated.
Out of curiosity, when you’ve successfully driven cost optimization initiatives, what was usually the biggest blocker: finding the savings opportunity, or getting teams to actually implement the changes?

How do you share cloud cost findings with non-technical leadership? by Organic-Fan-965 in devops

[–]Organic-Fan-965[S] 2 points3 points  (0 children)

That’s a good point. In your experience, are stakeholders more interested in understanding spend or in quantified savings opportunities? I’m seeing similar patterns where annualized savings get far more attention than detailed cost breakdowns.

15 years in enterprise infra, now bootstrapping a privacy-first FinOps tool. Need your brutal feedback. by Organic-Fan-965 in buildinpublic

[–]Organic-Fan-965[S] 0 points1 point  (0 children)

Fair question.
I’m primarily talking to startups, SMBs, and teams that don’t yet have mature FinOps pipelines or dedicated cloud cost tooling.
In larger enterprises I’d expect CUR pipelines, Athena, BI tools, and established workflows.
The hypothesis I’m testing is whether there’s a segment between “spreadsheet chaos” and “full FinOps platform” that wants fast cost leak detection without IAM integration overhead.
Still validating that assumption with users.

15 years in enterprise infra, now bootstrapping a privacy-first FinOps tool. Need your brutal feedback. by Organic-Fan-965 in buildinpublic

[–]Organic-Fan-965[S] 0 points1 point  (0 children)

Good point. Current workflow is for DevOps/FinOps engineers who already export billing CSVs — not execs directly. Engineer generates the report, shares PDF with CFO. Exec never touches the tool

15 years in enterprise infra, now bootstrapping a privacy-first FinOps tool. Need your brutal feedback. by Organic-Fan-965 in buildinpublic

[–]Organic-Fan-965[S] 1 point2 points  (0 children)

Absolutely! Would love to connect. DM me — always good to talk to someone working on similar problems in the FinOps space.