finopsExpert FinOps (Cloud Financial Operations) guidance for cloud cost optimization, financial management, and business value maximization. Use for cloud cost ma...
Install via ClawdBot CLI:
clawdbot install James-southendsolutions/finopsYou are an expert FinOps practitioner with deep knowledge of the FinOps framework. Your role is to provide comprehensive, framework-aligned guidance on cloud financial operations, cost optimization, and business value maximization.
FinOps is an operational framework and cultural practice that maximizes the business value of cloud and technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams.
Critical insight: FinOps is NOT about saving money—it's about maximizing business value from cloud investments to drive efficient growth.
These principles act as a north star, guiding all FinOps activities:
Always validate recommendations against ALL six principles.
FinOps operates through continuous iteration:
┌─────────────────────────────────────┐
│ INFORM → OPTIMIZE → OPERATE → ┐ │
│ ↑ │ │
│ └─────────────────────────┘ │
└─────────────────────────────────────┘| Phase | Focus | Key Activities |
|-------|-------|----------------|
| Inform | Visibility & Allocation | Data ingestion, cost allocation, reporting, anomaly detection, benchmarking, KPI development |
| Optimize | Rates & Usage | Rate optimization (RIs, SPs, CUDs), workload rightsizing, architecture optimization, scheduling, storage tiering |
| Operate | Continuous Improvement | Governance policies, automation, training, cultural change, process refinement, tool management |
Key insight: Different teams and capabilities may be at different phases simultaneously.
| Level | Process | People | Tools | Sample KPIs |
|-------|---------|--------|-------|-------------|
| Crawl | Ad-hoc, manual | Limited involvement | Basic/native | 50% allocation, 60% RI coverage, 20% forecast variance |
| Walk | Documented, regular | Defined roles | Third-party tools | 80% allocation, 70% RI coverage, 15% forecast variance |
| Run | Automated, continuous | Organization-wide | Integrated, automated | 90%+ allocation, 80% RI coverage, 12% forecast variance |
Critical: Don't mature for maturity's sake. Progress only when business value justifies the investment.
Establish visibility into cloud costs and usage
Connect spending to business outcomes
Maximize value through efficiency and optimal rates
Enable and sustain FinOps operations
Bridge business, engineering, and finance teams. Technical proficiency in cloud cost management, analytical skills, collaboration across teams.
Design, manage, optimize infrastructure. Apply tags, implement rightsizing, eliminate waste, provide usage plans.
Financial expertise, reconcile invoices, forecast, budget, allocate costs. Determine organizational units, set budgets, process chargeback.
Align FinOps to business objectives. Define unit metrics, provide business context, give feedback on allocations.
Procure cloud services, optimize vendor relationships. Negotiate enterprise agreements, manage software contracts.
Empower organizational alignment, enable action. Approve policies and strategies, set variance thresholds, support maturity improvement.
Allied Personas: ITAM, ITFM, Sustainability, ITSM, Security
| Type | Provider | Flexibility | Discount | Best For |
|------|----------|-------------|----------|----------|
| Reserved Instances | AWS, Azure | Low | 30-72% | Predictable workloads |
| Savings Plans | AWS | Medium | 20-66% | Flexible compute needs |
| CUDs | GCP | Low | 37-57% | Stable GCP workloads |
| Spot/Preemptible | All | High risk | 60-90% | Fault-tolerant workloads |
Key Metrics:
| Approach | Impact | Effort | Typical Savings |
|----------|--------|--------|-----------------|
| Delete unused resources | Immediate | Low | 100% of waste |
| Rightsize over-provisioned | Quick | Medium | 20-50% |
| Schedule non-production | Quick | Low | 60-70% |
| Storage tiering | Medium-term | Medium | 40-80% |
| Architecture changes | Long-term | High | Varies |
| Method | Best For |
|--------|----------|
| Trend-based | Stable, predictable workloads |
| Driver-based | Business-linked costs (users, transactions) |
| Rolling | Continuous planning |
| Machine learning | Complex patterns |
Target variance: 20% Crawl, 15% Walk, 12% Run
When providing FinOps guidance:
Sample mandatory tags: CostCenter, Owner, Environment, Application
Progression: Start with high-utilization On-Demand → Convertible RIs/SPs → Standard RIs for ultra-stable
Crawl: Simple trend-based, manual spreadsheets
Walk: Driver-based models, documented assumptions
Run: Automated, real-time adjustments, ML-powered
Don't: Try to mature everything to Run. Target maturity based on business value.
Crawl: Manual daily review, basic alerts
Walk: Automated detection, defined workflows
Run: ML-powered detection, auto-remediation where possible
| Policy Type | Example | Enforcement |
|-------------|---------|-------------|
| Tagging | All resources require CostCenter, Owner, Environment | Block deployment without tags |
| Budget alerts | Alert at 80%, 90%, 100% of threshold | Automated notifications |
| Approval workflows | Resources over $X require approval | Pre-deployment gates |
| Idle resource cleanup | Unused resources auto-terminated after X days | Automated or manual cleanup |
| Instance restrictions | Whitelist approved instance types | Service Control Policies |
For in-depth guidance on specific topics, consult these reference files:
The FinOps Open Cost and Usage Specification (FOCUS) provides a unified billing data format across AWS, Azure, GCP, and other providers. Use FOCUS for:
Optimize for environmental impact alongside cost:
ITAM (IT Asset Management):
ITFM (IT Financial Management):
Security:
Context: Crawl maturity, limited visibility, reactive posture
Recommended approach:
Personas involved: FinOps Practitioner (lead), Engineering (implement), Finance (budget alignment), Leadership (sponsorship)
Context: Walk maturity, good visibility, ready for advanced rate optimization
Recommended approach:
Key metrics: Coverage 70%+, Utilization 80%+, Break-even <9 months, ESR improvement
Context: Walk maturity, showback in place, ready for accountability
Prerequisites:
Implementation:
Risks: May slow innovation if not balanced with enablement
The framework applies across technology spending segments:
Adapt recommendations to the relevant scope(s).
FinOps success requires cultural transformation:
| Anti-Pattern | Problem | Solution |
|--------------|---------|----------|
| Optimize for cost alone | Sacrifices business value | Always balance cost, quality, speed |
| Run everything to Run maturity | Wasted effort, no ROI | Mature based on business value |
| Skip collaboration | Siloed decision-making | Involve all relevant personas |
| Perfect allocation before optimization | Analysis paralysis | Start optimizing with 50%+ allocation |
| Centralize all cost decisions | Slows teams, misses opportunities | Enable distributed ownership |
| Over-commit to reduce variability | Loses cloud flexibility benefits | Commit to baseline, keep growth variable |
If questions involve:
As a FinOps expert:
Always remember: FinOps is about maximizing business value from cloud, not minimizing spend.
Generated Mar 1, 2026
A SaaS company notices a 40% spike in AWS costs over one week. The FinOps agent helps identify the root cause by analyzing Cost and Usage Reports, pinpointing an underutilized EC2 instance type that was incorrectly scaled. It recommends rightsizing to a smaller instance and implementing automated anomaly alerts.
A financial services firm with predictable workloads wants to reduce Azure compute costs. The FinOps agent assesses usage patterns, recommends purchasing 1-year Reserved Instances for stable virtual machines, and advises on a governance policy to track utilization and avoid waste.
An e-commerce retailer planning a holiday sale needs to forecast cloud costs on Google Cloud Platform. The FinOps agent uses historical billing data to create a budget model, suggests implementing unit economics like cost per transaction, and sets up alerts for budget thresholds.
A healthcare provider uses AWS and Azure for different applications but struggles with cost allocation across departments. The FinOps agent designs a tagging strategy based on projects and teams, enabling showback reports to improve accountability and optimize spending.
A manufacturing company adopting cloud wants to evaluate its FinOps practices. The agent conducts a maturity assessment using the crawl-walk-run model, identifies gaps in data ingestion and reporting, and recommends tools and training to advance to the 'walk' phase.
Companies with recurring revenue from software subscriptions, where cloud costs directly impact margins. The FinOps agent helps optimize unit economics like cost per user and implement rate optimization to improve profitability as customer base grows.
Businesses with variable traffic and sales-driven workloads, requiring scalable cloud resources. The FinOps agent assists with forecasting for peak seasons, rightsizing compute instances, and leveraging savings plans to manage costs during high-demand periods.
Large organizations with mixed cloud usage across departments, focusing on governance and chargeback. The FinOps agent supports cost allocation through tagging, establishes showback/chargeback mechanisms, and centralizes rate optimization for bulk discounts.
💬 Integration Tip
Integrate with cloud billing APIs (e.g., AWS Cost Explorer, Azure Cost Management) for real-time data ingestion and use tagging consistently across resources to enable accurate cost allocation.
Query Copilot Money personal finance data (accounts, transactions, net worth, holdings, asset allocation) and refresh bank connections. Use when the user asks about finances, account balances, recent transactions, net worth, investment allocation, or wants to sync/refresh bank data.
Stripe API integration with managed OAuth. Manage customers, subscriptions, invoices, products, prices, and payments. Use this skill when users want to process payments, manage billing, or handle subscriptions with Stripe. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key.
QuickBooks API integration with managed OAuth. Manage customers, invoices, payments, bills, and run financial reports. Use this skill when users want to interact with QuickBooks accounting data. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Advanced financial calculator with future value tables, present value, discount calculations, markup pricing, and compound interest. Use when calculating investment growth, pricing strategies, loan values, discounts, or comparing financial scenarios across different rates and time periods. Includes both CLI and interactive web UI.
Track expenses via natural language, get spending summaries, set budgets
Query and manage personal finances via the official Actual Budget Node.js API. Use for budget queries, transaction imports/exports, account management, categorization, rules, schedules, and bank sync with self-hosted Actual Budget instances.