How to choose a cloud cost tool
Choose a tool using a reproducible billing and workflow pilot, with mandatory scope and permission checks before weighted scoring.
In this guide
Start with the decision your team cannot make
Write down one recurring decision that currently stalls. A finance owner might need to explain an invoice variance by subscription. An engineer might need enough evidence to accept a VM resize. An allocation lead might need to distribute shared platform charges without changing the provider total. These are different buying requirements, even when the teams describe their problem as cloud cost optimization.
Choose a primary outcome and name its owner. Record the current manual steps, the evidence those steps require, and the meeting or delivery deadline they support. A useful requirement says that finance can reproduce the selected month's actual charges. A requirement such as better visibility leaves vendors free to demonstrate unrelated screens.
Record mandatory provider and billing scope
List the providers you use today, then the agreement and hierarchy within each. For Azure, include the billing account type and the subscriptions that must appear. Microsoft's export documentation distinguishes EA, MCA and partner scopes, with specific limitations for management group exports. A vendor's Azure logo does not establish support for your billing arrangement. [1]
Treat an unsupported mandatory scope as a failed requirement. Separate present requirements from an anticipated migration next year. Costframe has generally available Azure support, an AWS private pilot and a Google Cloud private preview. Those maturity levels should remain separate rows in a purchasing worksheet; they do not establish equivalent production coverage.
Scroll the table sideways on smaller screens. Keyboard: focus the table and use the arrow keys.
| Requirement | Acceptance evidence | Decision |
|---|---|---|
| Billing scope | All selected subscriptions reconcile | Mandatory |
| Resource review | One recommendation has dated evidence | Mandatory if buying audits |
| Allocation | Shared charges and residual reconcile | Score if buying allocation |
| Future provider | Written maturity and supported scope | Separate roadmap item |
Test the financial basis with one closed period
Give each shortlisted vendor the same approved test scope and period. Compare actual cost with actual cost, preserving native currency. Ask where reservation purchases, unused commitments and Marketplace charges appear. Microsoft documents differences between actual and amortized datasets; combining their totals would count different treatments of the same spend together. [1]
Choose one resource with negotiated pricing. Ask the vendor to explain the recommendation's price basis and reproduce the estimate. Azure Advisor documents retail-rate VM savings and warns that existing reservations or savings plans can change the outcome. A larger headline estimate therefore needs investigation before it receives a higher score. Do not deduct a negotiated discount again from charges that already reflect it. [2]
Follow one recommendation through review
Use an authorized resource or a clearly labeled demonstration record. Ask the engineer to inspect its observation window, missing metrics and dependencies. Request a second example where the tool cannot make a confident recommendation. That example tests whether incomplete evidence remains visible instead of becoming a zero-utilization claim.
Follow the proposed change into the team's existing approval process. Establish who assigns it, who approves implementation, and which system records the completed change. Then inspect the evidence required to assess the next billing period. A completed ticket alone cannot prove savings, and a lower bill cannot attribute the difference to that ticket when demand or other resources also changed.
Review permissions and ongoing work
Ask for the exact integration instructions for your account type. Vantage documents separate Azure billing arrangements and additional permissions for commitment visibility. Finout documents export storage access, Advisor access and commitment roles. These are concrete onboarding dependencies you can assign to your identity and billing administrators. Neither integration should be judged from a generic read-only label. [3][4]
Estimate the work after onboarding: credential renewal, failed imports, new subscriptions and monthly reconciliation. Request commercial terms covering the required features and scopes, including support and exit arrangements. Keep purchase price separate from modeled savings. A recommendation estimate is neither guaranteed value nor proof that your team has capacity to implement it.
Agree pilot acceptance before connecting
Set a pilot scope with a named finance reviewer and engineering reviewer. Require one closed-period reconciliation, one investigated variance, and one recommendation accepted or rejected with a recorded reason. Preserve the selected scope, source version and currency in the evidence pack so another reviewer can repeat the checks.
Only score vendors that pass mandatory requirements. Weight the remaining criteria according to the decision identified at the start: allocation depth matters more for shared-cost reporting, while observation quality matters more for engineering review. Document an unresolved requirement as unresolved. Finish the pilot with a purchase recommendation, an owner for each operational dependency and a list of capabilities the team has actually tested.
Sources
Use this in your next review
Use your completed worksheet to decide which product differences need a live demonstration.
Compare specific vendorsCheck plans and current scope