FinOps & Analytics Lifecycle
As much as 70% of the development efforts of an AI-based solution are composed of wrangling and harmonizing data.
AI agents build governed. Humans ship trusted. 80% autonomy, 100% accountability.
Golden Path: From Raw Cost Data to Optimized Spend
Phase 1: Collect (3 min)
Who: gitops-cost-optimizer collects via READONLY profiles. HITL verifies account coverage.
What: Gather cost data from AWS + Azure with FOCUS 1.2+ normalization.
Why: Data quality at the source. Portal CSV is SSOT, not API alone — prevents FINOPS_API_SSOT_MISMATCH.
What-if skip: Incomplete data, RBAC-scoped undercounts, wrong numbers to leadership.
How
/finops:aws-monthly # AWS cost report with persona modes
/finops:azure-monthly # Azure cost report with 4-way validation
Output
- FOCUS 1.2+ cost reports per cloud provider
- Persona-mode views: CFO, CTO, CloudOps Engineer
- CSV + JSON export for downstream analysis
Quality Gate: All accounts visible. FOCUS 1.2+ tags present.
Phase 2: Validate (15 min)
Who: qa-engineer validates accuracy. HITL reviews deltas.
What: 4-way cross-validation: CLI vs Config Aggregator vs Cost Explorer vs Console.
Why: 99.5% accuracy gate. SELF_COMPARISON_VALIDATION prevented — must use 2+ independent sources.
What-if skip: Bad data in reports, false savings claims, eroded stakeholder trust.
How
/inventory:lz-cross-validate # Multi-source cross-validation
/devtools:validate # MCP server accuracy check
Output
- Cross-validation report with per-source accuracy deltas
- Independent source comparison (not same-process exports)
- Variance analysis with root cause
Quality Gate: Cross-validation accuracy >=99.5%. Independent sources used.
Phase 3: Analyze (30 min)
Who: gitops-cost-optimizer analyzes. product-owner validates business alignment.
What: Cost trends, anomaly detection, decommission candidate scoring.
Why: Analysis with measured data, not estimates. NO_ESTIMATED_COUNTS anti-pattern prevented.
What-if skip: Estimated numbers in reports, unvalidated savings claims.
How
/finops:analyze # Cost trends + anomaly detection
/finops:decommission-inventory # Scream-test scored candidates
Output
- MoM cost trend analysis with anomaly flags (>20% change)
- Decommission candidates with E1-E7 / S1-S7 signals
- Scream-test scores (0-100, >=70 flagged)
Quality Gate: Every number cites measurement method. No estimates.
Phase 4: Report (10 min)
Who: observability-engineer generates. HITL distributes to stakeholders.
What: Persona-mode reports for CFO, CTO, CloudOps. Executive FinOps report.
Why: Right data for right audience. CFO needs cost totals, CTO needs trends, CloudOps needs actions.
What-if skip: One-size-fits-all reports, executive disengagement.
How
/finops:report # Executive FinOps report with persona modes
Output
- 4 persona reports (CFO, CTO, CloudOps, FinOps)
- Stakeholder email template
- Evidence-backed claims (no unvalidated savings)
Quality Gate: Claims cite sources. Under 5 minute HITL review time.
Phase 5: Optimize (ongoing)
Who: gitops-cost-optimizer proposes. HITL approves decommission actions.
What: Rightsize, decommission unused resources, track savings attribution.
Why: Evidence-based decommission with READONLY profiles. AWS IAM prevents mutations.
What-if skip: Zombie resources persist, savings potential unrealized.
How
/finops:azure-rightsizing # Azure over-provisioned resource detection
# ec2-scream-test skill # AWS decommission feasibility scoring
Output
- Rightsizing recommendations with cost impact
- Decommission actions tracked with savings attribution
- Savings evidence for FinOps reporting
Quality Gate: READONLY only. HITL approves any changes. Savings measured, not estimated.
LEAN/5S Applied to FinOps
| Principle | Application | Evidence |
|---|---|---|
| Sort | FOCUS 1.2+ normalization across AWS + Azure | /finops:aws-monthly |
| Set in Order | Persona modes: CFO / CTO / CloudOps / FinOps | --persona flag |
| Shine | Cross-validation at 99.5% accuracy gate | /inventory:lz-cross-validate |
| Standardize | Portal CSV as SSOT, not API alone | FINOPS_API_SSOT_MISMATCH prevented |
| Sustain | Monthly reports with trend tracking | /finops:report |
By Persona
CFO / Finance
Path: /finops:aws-monthly → /finops:report → /finops:azure-monthly
Time to Value: Board-ready cost report in under 3 minutes.
CloudOps Engineer
Path: /inventory:discover → /finops:decommission-inventory → /finops:analyze
Time to Value: Cost optimization pipeline in 1 hour.
FinOps Practitioner
Path: /finops:aws-monthly --persona=all → /devtools:validate → /metrics:update-dora
Time to Value: FOCUS 1.2+ data product in 1 day.
Common Mistakes (Anti-Patterns)
| Mistake | Why It Fails | Fix |
|---|---|---|
| FINOPS_API_SSOT_MISMATCH | API-only data misses RBAC-inaccessible subs | Portal CSV is SSOT |
| SELF_COMPARISON_VALIDATION | Same-process JSON+CSV = trivial 0% delta | Use 2+ independent sources |
| NO_ESTIMATED_COUNTS | Estimated numbers in reports | Cite measurement method |
| ADJUSTED_METRIC_EXCLUSION | Shrinking denominator to inflate rates | Include all relevant items |
| HARDCODED_ENV_IN_PRODUCT_DOCS | AWS account IDs in product docs | Use env vars and generic terms |
| DRYRUN_OVER_READONLY | Using --dry-run when READONLY profiles exist | Real execution with READONLY |
Quick Reference: Command Cheat Sheet
# Collect
/finops:aws-monthly
/finops:azure-monthly
# Validate
/inventory:lz-cross-validate
/devtools:validate
# Analyze
/finops:analyze
/finops:decommission-inventory
# Report
/finops:report
# Optimize
/finops:azure-rightsizing
Last Updated: March 2026 | Status: Active | Maintenance: gitops-cost-optimizer