​

FinOps Strategy

​

Command

arckit finops "<project ID or cloud provider>"

​

Description

​

Arguments

• Project ID or cloud provider: Project identifier or cloud description (e.g., ‘001’, ‘AWS multi-account’)

​

When to Use

• During planning phases
• For cost optimization initiatives
• Multi-cloud governance
• Budget forecasting and control
• Cloud financial accountability

​

Required Context

• Requirements (ARC--REQ-.md) - MANDATORY (for scale/budget)
• Architecture Principles (PRIN) - Recommended
• DevOps Strategy (DEVOPS) - Recommended
• Architecture Diagrams (DIAG) - Recommended

​

FinOps Maturity Levels

​

Document Sections

​

Section 1: FinOps Overview

• Strategic objectives
• FinOps maturity (current and target)
• Team structure (FinOps team, cloud teams, finance)
• Stakeholder responsibilities

​

Section 2: Cloud Estate Overview

• Cloud providers and accounts
• Major workloads and cost centers
• Current spend baseline
• Spend trends and projections

​

Section 3: Tagging Strategy

• cost-center
• environment (dev/staging/prod)
• owner
• project

• team
• application
• data-classification

• Policy-based enforcement
• Automated tagging
• Untagged resource handling

​

Section 4: Cost Visibility & Reporting

• By team / project / environment
• Shared cost distribution
• Proportional allocation methods

• Daily: Anomaly detection
• Weekly: Team review
• Monthly: Finance reconciliation
• Quarterly: Trend analysis

• Executive summary
• Team-specific views
• Cost center breakdowns

​

Section 5: Budgeting & Forecasting

• Fixed budgets
• Variable budgets
• Per-unit budgets

• Trend-based forecasting
• Growth projections
• Seasonal adjustments

• 50% threshold → Info email
• 80% threshold → Warning
• 100% threshold → Alert + escalation
• 120% threshold → Critical escalation

​

Section 6: Showback/Chargeback Model

• Cost reporting to teams
• No actual billing
• Awareness and optimization

• Internal invoicing
• Cost center allocation
• Budget accountability

• Direct allocation (tagged resources)
• Proportional allocation (shared resources)
• Fixed allocation (platform overhead)

• Cost per transaction
• Cost per user
• Cost per API call

​

Section 7: Cost Optimization Strategies

• Regular rightsizing recommendations
• Automated resize for non-prod
• Production resize with approval

• Reserved Instances (1-year, 3-year)
• Savings Plans coverage
• Commitment utilization targets (>80%)

• Non-prod workloads on Spot
• Fault-tolerant prod on Spot
• Hybrid on-demand + spot

• S3 Intelligent-Tiering
• Lifecycle policies
• Delete unused volumes

• Automated detection
• Auto-shutdown for dev/test
• Cleanup workflows

​

Section 8: Commitment Management

• Current RI coverage
• Utilization rates
• Expiration dates

• Coverage gap analysis
• ROI calculations
• Purchase approval workflow

• 80% utilization for RIs

• 90% for Savings Plans

​

Section 9: Anomaly Detection & Alerts

• ML-based anomaly detection
• Baseline establishment
• Sensitivity thresholds

• Email for amounts under £500
• Slack for £500-£2,000
• PagerDuty for over £2,000

1. Alert received
2. Cost Explorer analysis
3. Tag-based attribution
4. Root cause identification
5. Remediation

​

Section 10: Governance & Policies

• Service Control Policies (SCPs)
• Resource quotas
• Approved instance types

• £5,000/month: Manager approval

• £20,000/month: Director approval

• £100,000/month: CFO approval

• Tag compliance (block untagged)
• Instance type restrictions
• Region restrictions

• Exception request process
• Temporary exemptions
• Audit trail

​

Section 11: FinOps Tooling

• AWS Cost Explorer
• Azure Cost Management
• GCP Billing

• CloudHealth
• Cloudability
• Apptio

• Cost data exports
• Dashboard automation
• Report generation

​

Section 12: Sustainability & Carbon

• Carbon emissions visibility
• AWS Customer Carbon Footprint Tool
• Azure Sustainability Calculator

• Green region preferences
• Right-size for efficiency
• Auto-shutdown for dev/test

• Quarterly carbon reports
• Reduction targets

​

Section 13: UK Government Compliance (if applicable)

• Cabinet Office Digital Spend Controls
• Treasury Green Book alignment
• G-Cloud/Digital Marketplace tracking
• Annual technology spend reporting

​

Section 14: FinOps Operating Model

• Daily: Anomaly review
• Weekly: Team cost review
• Monthly: Finance reconciliation
• Quarterly: Strategy review

• Engineering: Cost awareness training
• Finance: Budget management
• Executive: Strategic reporting

• Team Lead → Engineering Manager → CTO → CFO

• Monthly optimization targets
• Quarterly retrospectives
• Annual strategy refresh

​

Section 15: Metrics & KPIs

• Cost per transaction trend
• Cost per user trend
• Infrastructure efficiency ratio

• Revenue per cloud dollar
• Gross margin impact

• Rightsizing coverage: >70%
• Commitment coverage: >70%
• Waste reduction: 10% YoY

• Tagging compliance: >95%
• Budget adherence: ±10%

​

Section 16: Traceability

• Requirements to FinOps element mapping
• NFR-P → Resource sizing
• NFR-S → Auto-scaling costs
• NFR-A → Multi-AZ costs
• BR → Budget constraints

​

Output

​

Example

arckit finops "AWS multi-account organization"

• FinOps Maturity: Walk (target: Run)
• Cloud Provider: AWS
• Monthly Spend: £45,000
• Tagging: 4 mandatory tags
• Reporting: Weekly dashboards
• Optimization: Rightsizing + RIs
• Governance: Approval for >£5k/month

​

Related Commands

• arckit devops - Infrastructure patterns
• arckit diagram - Resource topology
• arckit requirements - Budget constraints

​

Next Steps

1. Implement mandatory tagging policy
2. Set up cost dashboards and alerts
3. Conduct initial rightsizing analysis
4. Evaluate commitment purchases
5. Establish FinOps review cadence
6. Train teams on cost awareness

​

Key Principles

1. Cost Visibility First - Can’t optimize what you can’t see
2. Shared Accountability - Engineering owns spend
3. Real-Time Decisions - Timely, accessible cost data
4. Variable Cost Model - Spend scales with value
5. Continuous Optimization - Ongoing, not one-time
6. Tagging is Foundational - Basis for all allocation