How you currently explain cloud costs

• How does your team currently produce the bill breakdown the CFO asks for? Options: Manual spreadsheets, Cloud provider native tools, Homegrown scripts, Third-party cost tool, Combination, Other
• Tell me about the single report or spreadsheet you use most to allocate cloud spend, and who owns it.
• Which cloud account did you plan to connect first for evaluation? Options: Primary production account, Consolidated billing account, Dev/test account, Shared services account, Other
• On average, how many people touch that report each month? Options: 1-2, 3-5, 6-10, 11-20, 20+
• Describe the last time a quarterly bill surprised leadership, what was the first place you looked?
• Do you have a target accuracy or allocation confidence the finance team expects? Options: >95%, 90-95%, 80-90%, <80%, No formal target

Where surprises appear and who notices them

• If a single unexplained 40 percent increase showed up on a bill tomorrow, who would be asked to explain it first and why?
• When did you last trace a spike back to a misconfigured autoscaling policy or runaway test environment? Options: Within last week, Within last month, Within last quarter, Longer than a quarter, Never traced one
• Walk me through the tools and alerts you have in place to catch abnormal spending before it hits the CFO's desk.
• Which teams or services most often generate allocation disputes when you try to map costs? Options: Platform/infra, Data engineering, Product teams, Research/ML, Security, Other
• Estimate the number of dollars that are currently unallocated or disputed each month. Options: <0.5% of monthly spend, 0.5-2%, 2-5%, 5-10%, >10%, Not tracked
• Would a faster detection time, measured in hours not days, change who owns cloud cost accountability? Options: Yes, shift to engineering, Yes, shift to FinOps/Finance, No change, Unsure

Who signs off and who gets held accountable

• What single governance gap would trigger a CFO-mandated freeze on new cloud spend?
• Who is currently listed as the owner for cost allocation in your RACI or runbook? Options: Head of FinOps, VP of Cloud Engineering, Finance lead, No clear owner, Other
• Tell me about the approvals required to pause or scale down a workload that is driving costs.
• How many teams would need to agree before an optimization recommendation could be implemented? Options: 1, 2, 3-4, 5+, Varies by change
• List legal, procurement, or security reviews that could delay granting the platform access to billing data.
• If the pilot validates savings, what is the fastest path to executive signoff? Options: CFO approves directly, Committee approval, VP sponsor signs, Procurement cycle, Unsure

Tagging, exports, and the data that makes allocation possible

• To what extent does inconsistent tagging make your current allocations unreliable? Options: Severely, many tags missing, Moderate, some critical tags missing, Minor, mostly complete, Not an issue, Unknown
• List the billing exports and file locations currently available for the account you plan to connect.
• When was the last tagging audit, and what percentage of resources were missing required tags?
• Walk me through your common allocation rules, for example by team tag, cost center, or shared services split.
• Estimate how many resources or services you believe are currently untagged or mis-tagged. Options: <1%, 1-5%, 5-15%, 15-30%, >30%, Unknown
• Would missing access to billing export locations or invoices stop a pilot from proceeding? Options: Yes, No, Depends on which exports, Unsure

Constraints that determine whether configuration can start

• What single technical blocker could stop setup within 2 weeks?
• Who owns the cloud accounts and who will need to approve connector credentials?
• Identify the APIs, service accounts, or third-party systems that must be integrated for allocation to work.
• Describe your internal capacity to support setup, including named engineers or an estimated FTE allocation per week.
• Are there regulatory, compliance, or procurement approvals that could extend the timeline beyond one month? Options: Yes, regulatory, Yes, procurement, Yes, security/compliance, No, Unsure
• Name the smallest decision or resource that would clear the path to start within two weeks.

The other options you are weighing

• Name the external vendors and internal projects you are considering, and the single reason each stakeholder favors them.
• Are any of those alternatives already connected to your billing or monitoring data? Options: Yes, fully connected, Partially connected, No connections, Not sure
• To what extent would clearer cost-by-product transparency change procurement's choice? Options: A lot, it would sway them, Some, it would help, Little impact, No impact, Unsure
• Provide your rough estimate of the headcount and months required to build a comparable internal solution.
• Identify three conditions that would have to hold for you to stay with your current vendor this year.

Acceptance criteria that unlock a purchase

• Assuming the pilot proves the savings you expect, what remains between you and signing a production contract?
• Provide the concrete KPIs the pilot must demonstrate, for example allocation accuracy, detection time, or monthly savings percentage. Options: Allocation accuracy target (specify), Anomaly detection within hours, Monthly cost reduction % (specify), Clear ownership mapping across teams, No production impact from data collection, Other
• From which role will approval come, and what evidence will satisfy that role?
• On a scale, how confident are you that the necessary account access and billing exports can be provided within your target timeline? Options: Very confident, Somewhat confident, Not confident, Need help to achieve
• Specify the top three risks that would cause you to pause the pilot, and for each, who on your team would escalate it.
• Realistically, if the pilot hits the KPIs, how soon could you contract for production roll out? Options: Immediately, Within 2 weeks, Within 1 month, 2-3 months, Longer than 3 months, Unsure

Next practical steps and the decision cadence

• Pinpoint the single decision or approval that, if granted today, would remove most startup delays and name who would make it.
• Select the stakeholders who should be present during the initial setup call to remove blockers quickly. Options: Cloud account owner, FinOps lead, Security/IT, Legal/Procurement, Engineering lead, Other
• Please indicate whether you can provide a sample billing export or temporary read-only credentials to shorten the evaluation. Options: Yes, sample export available, Yes, temporary read-only credentials available, No, approvals required, Unsure
• Choose the earliest window you could schedule a 60-minute configuration workshop. Options: Within 1 week, 1-2 weeks, 2-4 weeks, More than 4 weeks, Unsure
• Finally, who on your side is enabled to sign a pilot order if the results meet the criteria? Options: CFO, VP Cloud/Engineering, Head of FinOps, Procurement, Multiple signers, Unsure

• Solution Walkthrough — Mapping, Detection, Prioritization

• Confirm the current state and its cost to your team
• You confirm the demonstrated allocation maps cost to the teams and services you care about and replaces the key manual spreadsheet outputs.
• Seller to run a one-week sample ingest of the provided billing export and deliver an allocation comparison report against the customer's spreadsheet before the follow-up session.
• You confirm the anomaly detection shown would have flagged recent cost spikes within hours rather than days.
• Prove how spend maps to teams and services using your billing and tags
• Seller to prepare an evidence pack showing how anomaly baselines would have flagged the most recent spike, including timestamps and expected alert thresholds.
• Prove anomaly detection against recent incidents
• You agree that the prioritized optimization recommendations align with your risk tolerance and reporting needs.
• Buyer to provide access to one representative billing account export and the current tag dictionary or allocation rules for that account.
• Walk through prioritized optimization opportunities in your context
• Buyer to identify the top three teams or services to use as validation targets for rightsizing and anomaly checks.
• You identify any gaps that must be closed before a full evaluation (missing billing exports, tagging gaps, or access constraints).
• Validation check — confirm this matches what you need

• Solution Walkthrough — Mapping, Detection, Prioritization
• Solution Experience Deck
• Solution Walkthrough Brief

• meeting
• slides
• document

• Connect and Ingest Cloud Billing Data
• Normalize Multi-Cloud Costs into Unified Model
• Map Costs to Teams, Services, and Features
• Activate Workload-Aware Baseline and Anomaly Detection
• Deliver Rightsizing Recommendations with Savings Estimates
• Generate Reserved Commitment and Purchase Recommendations
• Identify Idle, Orphaned, and Low-Utilization Resources
• Normalize Tags and Apply Automatic Tag Mapping Rules
• Deploy CFO-Facing Cost Allocation Reports
• Provision Cost Allocation API and BI Exports
• Create Optimization Runbooks with Performance Risk Notes
• Enable Role-Based Dashboards and Access Controls

Connect and Ingest Cloud Billing Data

• Which cloud provider billing export types do you need us to ingest (for example: linked account bills, consolidated billing CSV, or detailed usage export)? Options: Billing CSV export to object storage, Provider native cost API, Provider billing dataset export (warehouse), Consolidated/linked account export
• How many distinct cloud billing accounts or linked account IDs must be connected for this engagement? Options: 1, 2-5, 6-20, More than 20
• Provide the minimum historical months of billing and usage data we must ingest for baselining and reporting (for example: 3, 6, 12 months). Options: 3 months, 6 months, 12 months, No historical data required
• List the concrete delivery points for billing exports you will provide (for example: S3 bucket path, storage container URL, BigQuery dataset name).
• Specify the IAM or permission artifacts we will need to set up connectors (for example: service account email, role ARN, storage read policy).

Normalize Multi-Cloud Costs into Unified Model

• Confirm whether you require cost normalization across AWS, Azure, and GCP in a single allocation model or only a subset of providers. Options: AWS only, Azure only, GCP only, Any combination of AWS/Azure/GCP
• Describe the currency and tagging conventions we must normalize to (for example: USD, EUR; tag keys for cost center and environment).
• Identify any billing line-item transforms you require (for example: amortize committed discounts, map marketplace fees to product lines).
• Do you require hourly-granularity normalization for anomaly detection and chargeback, or is daily aggregation acceptable? Options: Hourly, Daily, Weekly
• Specify the acceptable data accuracy threshold for normalized cost allocation (for example: 95% matching to provider invoice), and note any reconciliation process you will use. Options: >= 99%, 95-98%, 90-94%, Custom threshold

Map Costs to Teams, Services, and Features

• Provide the canonical list of teams, services, and feature names we should map costs to (attach a CSV or list of identifiers if available).
• Which allocation rules should we apply when resources are shared across multiple services (for example: usage-weighted, reserved-split, fixed percentage)? Options: Usage-weighted, Fixed percentage, Equal split, Custom rule per resource type
• How many allocation rules do you expect to start with (estimate a count to size rule configuration effort)? Options: 1-5, 6-15, 16-50, 50+
• Provide the acceptance criteria for allocation accuracy that will define done for the mapping module (for example: allocation accuracy >= X% against controller reports, sample reconciliation of N resources).
• Who on your team will own final decisions for conflicting tag-to-team mappings and who will approve mapping exceptions?

Activate Workload-Aware Baseline and Anomaly Detection

• Which workloads or services should have workload-aware baselines first (for example: production web tier, batch ETL, data warehouse)?
• How many days of historical usage should we use to build initial baselines for each workload? Options: 7 days, 14 days, 30 days, 90 days
• Identify the alert thresholds you want for anomalies (for example: 20% above baseline within 24 hours, or $X delta).
• Do you want anomaly notifications sent by email, webhook to your incident platform, or both? Options: Email, Webhook/API, Both, None
• Specify the maximum acceptable time-to-detect for cost anomalies (for example: 2 hours, 24 hours) and any business-hours constraints. Options: < 2 hours, < 6 hours, < 24 hours, Daily only

Deliver Rightsizing Recommendations with Savings Estimates

• Which instance families, database tiers, or resource types should we prioritize for rightsizing analysis (for example: compute instances, managed DB instances, Kubernetes node pools)?
• Estimate the monthly spend coverage you want analyzed for rightsizing (for example: top 10 spend services, all compute spend). Options: Top 5 services by spend, Top 10 services by spend, All compute and DB spend, Full environment
• Provide the performance risk tolerance for recommended rightsizes (for example: no CPU contention risk, allow up to 10% performance risk) and any SLA constraints. Options: Zero risk (manual review required), Low risk (allow up to 5%), Medium risk (allow up to 10%)
• List any environments where automated rightsizing suggestions are disallowed (for example: production database clusters, PCI-scoped environments).
• Do you want estimated monthly savings and expected impact on utilization included in each rightsizing recommendation export? Options: Yes - savings and utilization, Yes - savings only, No

Generate Reserved Commitment and Purchase Recommendations

• Which commitment products should we analyze for reserve recommendations (for example: 1-year compute savings plan, 3-year reserved instances, committed use discounts)? Options: 1-year commitment, 3-year commitment, Savings plan style, All applicable commitment products
• How far back should we analyze usage patterns to suggest commitment sizes (for example: 30, 90, 180 days)? Options: 30 days, 90 days, 180 days, 365 days
• Specify your acceptable trade-offs between coverage and flexibility (for example: prefer higher savings vs prefer shorter commitment). Options: Maximize savings, Balance savings and flexibility, Prefer flexibility
• Are there existing reserved purchases or committed use discounts we should import and honor when computing net recommendation? Options: Yes - provide manifest, No
• Which approval workflow should be used for purchase recommendations (for example: auto-generate proposal, require finance sign-off, require engineering review)? Options: Auto-propose, Finance sign-off required, Engineering review required, Custom workflow

Identify Idle, Orphaned, and Low-Utilization Resources

• Which resource types should be scanned for idle or orphaned state (for example: compute instances, unattached block storage, unused IPs, idle databases)? Options: Compute instances, Block storage volumes, Static IPs, Databases, All of the above
• How do you define 'idle' for compute resources in your environment (for example: CPU < 5% for 7 days, network < X MB)? Options: CPU < 5% for 7 days, CPU < 10% for 14 days, Custom definition
• Provide the remediation options you allow for identified idle resources (for example: notify owner, schedule stop, auto-terminate after approval). Options: Notify owner, Schedule stop, Auto-terminate after approval, No automatic remediation
• List the owners or owner groups that should be assigned to orphaned resources discovered during the scan.
• Are there compliance or regulatory scopes where orphan remediation is restricted (for example: PCI, HIPAA, regulated workloads)? Options: Yes, No

Normalize Tags and Apply Automatic Tag Mapping Rules

• Which tag keys are authoritative for cost allocation in your environment (for example: cost_center, product, environment)?
• Specify the minimum tag coverage you require before automated mapping is applied (for example: 80% of resources must have cost_center). Options: >= 95%, 90-94%, 80-89%, No minimum
• Identify any tag naming variations we should normalize (for example: costcenter vs cost_center) and provide examples.
• Do you want automatic tag-mapping rules to create derived tags (for example: map project ID to service name) or only normalize existing keys? Options: Derive and create tags, Only normalize existing keys, Hybrid approach
• Will you provide a canonical tag dictionary or should we propose one based on discovery? Options: You will provide dictionary, We should propose based on discovery

Deploy CFO-Facing Cost Allocation Reports

• Which CFO-facing artifacts do you need delivered (for example: monthly executive cost summary, cost-by-product P&L, chargeback CSV)? Options: Monthly executive summary, Cost-by-product P&L, Chargeback CSV, Ad hoc financial reconciliation
• Specify the cadence and recipients for CFO reports (for example: monthly to CFO and finance team, weekly to FinOps). Options: Weekly, Bi-weekly, Monthly, Ad hoc
• Provide the acceptance criteria that will validate the CFO-facing reports (for example: allocation accuracy >= X% on sampled P&L lines, sign-off by finance lead).
• Which export formats do you require for the CFO report (for example: PDF executive deck, CSV for GL ingestion, BI dashboard link)? Options: PDF deck, CSV export, BI dashboard link, All of the above
• Are there regulatory or audit artifacts to include with reports (for example: reconciliation log, raw billing extract attachment)? Options: Include reconciliation log, Attach raw billing extracts, No audit attachments required

Provision Cost Allocation API and BI Exports

• Which BI destinations or data warehouses should receive allocation exports (for example: your data warehouse dataset name or BI workspace)?
• Specify the API endpoints and payload formats you require for programmatic cost allocation access (for example: REST endpoint for per-team daily totals).
• Indicate the export cadence you require for BI and API outputs (for example: hourly, daily, monthly). Options: Hourly, Daily, Weekly, Monthly
• Do you require schema templates or sample payloads to be approved before exports are enabled? Options: Yes - approve schema, No - use standard schema
• Are there network or security requirements for export endpoints (for example: IP allowlist, VPC peering, private endpoint)? Options: IP allowlist, VPC/private endpoint, None

Create Optimization Runbooks with Performance Risk Notes

• Which optimization types require runbooks with step-by-step remediation (for example: rightsizing, idle resource reclamation, reserved purchase execution)? Options: Rightsizing, Idle reclamation, Reserved purchase, All of the above
• Provide the performance metrics and SLAs to include in runbook risk notes (for example: expected CPU utilization change, acceptable latency delta).
• Outline the approval and rollback steps that must appear in each runbook (for example: validation queries, monitoring window, rollback command).
• Do you want runbooks exported as documents, integrated playbooks in your incident tool, or both? Options: Exported documents, Integrated into incident tool, Both
• Will you require training or handoff sessions for operational teams on runbook execution? Options: Yes - training required, No - documentation only

Enable Role-Based Dashboards and Access Controls

• Name the user roles and access groups that should receive pre-built dashboards (for example: CFO, FinOps lead, engineering manager).
• Select which data domains each role can see (for example: finance sees cost-by-GL, engineering sees resource-level telemetry). Options: Finance - aggregated P&L, Engineering - resource-level, Ops - anomaly alerts, Custom per role
• Specify your single sign-on or identity provider details we must integrate with (for example: SAML provider name, SCIM provisioning requirement).
• Confirm the maximum number of seats or dashboards covered by the engagement or whether we should plan for unlimited viewer seats. Options: Up to 10 seats, 11-50 seats, 51-200 seats, Unlimited viewers
• Are there audit or access logging requirements for dashboard access that we must enable (for example: exportable access logs, retention period)? Options: Enable exportable logs, Retention period required, No special logging

• Subscription Order Form
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Data Processing Agreement (DPA)
• Access & Connector Authorization
• Roles & Responsibilities Matrix
• Go/No-Go Acceptance Certificate
• Change Order Agreement
• Regulatory Compliance Addendum (conditional)

• Go-live Health Check
• First Measurement Review
• Acceptance Gate and Outcome Verification
• Operational Monthly Sync
• Quarterly Business Review - Realization and Roadmap

• Execute prioritized configuration tuning changes and record the change log
• Apply agreed allocation-rule and tagging corrections in the platform configuration
• Schedule follow-up validation run and deliver the revised allocation accuracy report before the Acceptance Gate meeting
• Restate numeric acceptance criteria from Solution Scope
• Record a formal acceptance decision with the named signatory and publish the acceptance record to the shared workspace.
• If any criteria failed, have a time-bound remediation plan recorded with verification steps and target close dates.
• Publish the formal acceptance decision and capture the named signatory in the shared workspace
• Archive legacy billing spreadsheets or document retained-read-only status and archive locations
• Publish the remediation plan for any failed criteria with verification dates
• Short metrics review
• Reduce the count of critical open issues affecting allocation accuracy and confirm next-step dates for remaining items.
• Prioritize the enhancement request list for the upcoming quarter and commit to which items will enter the implementation backlog.
• Reconfirm acceptance criteria and owners
• Update the open-issue tracker with target resolution dates
• Publish a one-page metrics snapshot showing allocation accuracy, weekly anomalies triaged, and realized savings before the next monthly sync
• Quarterly metrics detailed review
• Confirm realized savings versus the Solution Scope targets and select the optimizations to execute next quarter.
• Agree a measurable plan to further reduce manual reporting hours and improve allocation accuracy over the coming quarter.
• Publish the prioritized quarterly optimization plan with milestones and target impact estimates
• Schedule implementation windows for approved optimizations and record expected verification dates
• Deliver before/after cost and time-savings comparison for each approved optimization within 30 days of implementation
• Confirm connectors are ingesting billing data and allocation rules are present for the accounts in scope.
• Document any high-priority blockers preventing measurement and agree remediation tasks with target completion windows.
• Publish the deployment validation checklist and ingestion health logs to the shared workspace
• Record the list of high-priority blockers and target dates for remediation
• Enable any missing permissions or connector settings required for allocation calculations
• Present measurement results
• Determine whether allocation accuracy rate and realized savings are trending toward the numeric targets in Solution Scope and document shortfalls.
• Agree a prioritized list of corrective actions with target completion dates to reach the acceptance gate.
• Publish the measurement workbook and raw allocation evidence for async review
• Deployment and ingestion validation
• Present outcome data per acceptance criterion
• Diagnose allocation mismatches
• Review optimization impacts and risks
• Open issue burn-down
• Document pass or fail per criterion and capture signatory
• Prioritize enhancement and integration requests
• Investigate unexpected cost drivers
• Early adoption signals and access checks
• Enhancement request triage
• Agree corrective actions and timeline
• Incumbent wind-down confirmation
• Blockers and open issues triage
• Configuration tuning and short fixes
• Integration and data-quality posture
• Confirm next steps and deliverables
• Confirm readiness timeline to Acceptance Gate
• Agree quarterly action plan and success metrics
• Remediation plan for any failed criteria
• Immediate remediation plan