In today’s fast-moving cloud landscape, cost visibility, governance and automation are essential for teams that want to scale effectively. As organizations shift from reactive cost tracking to proactive FinOps+ practices, new frameworks and technologies (especially AI) are enabling teams to drive better value and operational efficiency.

Here, we explore key lessons and practical steps you can apply in your FinOps+ journey.

Why FinOps+ is Essential today

• Traditional FinOps practices (spend reporting, forecasting, cost allocation) remain important, but practitioners report new priorities: governance at scale, managing cost beyond public cloud, and the rising impact of AI.
  
• The FinOps+ framework helps you bridge those priorities across three pillars: Automated Governance, AI-Driven FinOps, and Beyond Public Cloud.
  
• These pillars aren’t about more work. They’re about doing FinOps better and at scale: preventing waste before it begins, reducing manual effort, expanding visibility into all tech spend (not just AWS/Azure/GCP/OCI), and enabling safe, efficient use of AI.
  

Pillar 1: Automated Governance

• Start with policy: define what you consider waste (e.g., unattached volumes, idle dev environments), what tagging standard you enforce, what budget guardrails you set.
  
• Layer in automation:
  
  • Auto-tagging resources based on your policy
    
  • Scheduled shutdown of dev/test sandboxes outside business hours
    
  • Automatic cleanup: e.g., detect unattached EBS volumes older than 7 days → snapshot → delete
    
• Why this works: It prevents waste before it accumulates, reduces manual tickets, and builds processes that scale with your footprint.
  

Pillar 2: AI-Driven FinOps

• Guidance: For users who aren’t FinOps experts, natural-language AI assistants help them ask simple questions like “Show me spend by service” or “What’s my forecasted cloud cost for 2026?” and get useful answers quickly.
  
• Efficiency: AI can go beyond insights and actually execute tasks with approval—e.g., update budgets across dozens of projects in a few prompts rather than manual Excel exports and emails.
  
• Governance: AI can help you build and deploy policy templates (for example, “detect unattached volume >7 days → snapshot → delete”) without wrangling code or writing Cloud Custodian from scratch.
  
• Important note: Always include approval/guardrails so automation doesn’t become a risk.
  

Pillar 3: Beyond Public Cloud

• Ask: How many of your services live outside the “big three” cloud providers (SaaS, data-platforms, on-prem, AI/ML infrastructure)?
  
• FinOps+ encourages you to bring all technology spend into view, not just the public cloud bill.
  
• When you unify this data: you can compare cost across units, allocate shared services, see true product margins, and make better business decisions.
  

FinOps+ In Practice: A Real-World Example

Insulet, a company delivering cloud-connected insulin patch pumps and managing large volumes of real-time data, faced challenges like siloed visibility, inconsistent stakeholder awareness, disconnected data sources, and manual spreadsheets. By unifying cloud and third-party spend and empowering collaboration, they improved governance and enabled broader stakeholder engagement with cost data. Pairing automation with communication (for example, alerting teams before shutting down resources) helped drive adoption and trust.

• What Insulet did:
  
  • Created transparency across cloud + third-party platforms
    
  • Enhanced collaboration with stakeholders (rather than guessing at spend)
    
  • Leaned into governance automation (turning off idle environments, enforcing lifecycle policies)
    
  • Framed AI and self-service as a way for non-FinOps users to engage with cost without fear
    
• Tips from Insulet’s FinOps+ Journey:
  
  • Use data to have productive conversations (“Here’s how much you spent; here’s what we see; what do you want to do next?”).
    
  • Pair automation with communication (e.g., warnings to teams before turning off resources).
    
  • Ask vendors for standardized cost/billing exports (e.g., FOCUS) and include non-cloud spend early.
    

What you can do next

• Choose one pillar and pick a small, high-impact starting point:
  
  • Governance: Write down 1-2 key policies (e.g., tagging standard + idle environment shutdown) and automate them.
    
  • AI-Driven: Identify one manual task (budget updates, spend Q&A) and explore whether an AI assistant or scripted process could reduce hours.
    
  • Beyond Public Cloud: List 2-3 non-cloud-provider services you spend significantly on, then ask: How are we tracking this spend today? Can we bring it into our cost view?
    
• Communicate early wins. Even a simple automation or transparent cost dashboard is a win your stakeholders will notice.
  
• Make feedback a loop. As Insulet and we at Kion have learned: It’s okay to iterate. Let your users engage, make suggestions, and refine your FinOps+ workflows.
  

What’s New & Next at Kion

• Release Kion v3.15 will include the in-app AI assistant (Lux) and support for financial scopes (a more granular way to allocate spend across orgs).
  
• After that: major governance-policy engine overhaul, expanded out-of-the-box policies, improved shared cost allocation.
  
• If you’re curious how this works with your environment—or want to see Lux in action—book a demo with our team.
  

Bottom line:
FinOps+ isn’t a replacement of core FinOps, it’s the next step in the evolution. By introducing automation, AI-assisted workflows, and extending your cost view beyond traditional clouds, you’re better positioned to prevent waste, empower more stakeholders, and make smarter decisions across your technology investments.

Get Started with Your FinOps+ Journey Today:
Whether you’re just starting with FinOps+ or looking to expand your current practices, focus on high-impact opportunities like automated governance rules, AI-assisted workflows, and extending cost visibility across all technology spend. Small wins here build momentum and demonstrate value to stakeholders.

Want to learn more?