What to Include in a Savings Assessment Request

A savings assessmentgives you a clear picture of where your cloud discount coverage stands and what closing the gaps would save. To produce an accurate assessment, we need a few pieces of information from your environment. Here's exactly what to prepare.

The essentials

1. Latest monthly invoice (all clouds)

The most recent full-month invoice from each cloud provider you use. This is the foundation of the assessment — it shows your current spend by service, region, and account.

• AWS:Go to Billing Dashboard > Bills. Download the PDF or CSV for the most recent complete month.
• Azure:Go to Cost Management + Billing > Invoices. Download the invoice for the latest billing period.
• GCP:Go to Billing > Transactions. Export the most recent monthly statement.

If you have multiple billing accounts or payer accounts, include invoices for each one. Consolidated billing invoices that cover all linked accounts are ideal.

2. Current RI and savings plan inventory

A list of your active reserved instances, savings plans, and committed use discounts. This tells us what coverage you already have and when it expires.

• AWS:Go to Cost Explorer > Reservations > Inventory. Export the active reservation list. For savings plans, go to Savings Plans > Inventory.
• Azure: Go to Reservations in the Azure portal. Export the list of active reservations with expiration dates.
• GCP:Go to Billing > Committed Use Discounts. Export your active commitments.

3. Existing pricing agreements

If you have an Enterprise Discount Program (EDP) with AWS, an Enterprise Agreement (EA) with Azure, or a negotiated pricing agreement with GCP, include the relevant terms. Specifically:

• The discount percentage or committed spend amount.
• The term (start and end dates).
• Any volume-based tier thresholds.

These agreements affect the baseline against which savings are calculated. Without them, the assessment may overstate the opportunity in areas where you already have negotiated pricing.

Nice to have (but not required)

Cost and Usage Reports (CUR/detailed billing)

If you have AWS Cost and Usage Reports enabled or Azure detailed billing exports, including a recent month's data allows for more granular analysis. This is helpful but not necessary for the initial assessment — invoices alone provide enough information for an 85% picture.

Planned infrastructure changes

If you know of upcoming migrations, decommissions, or significant scaling events in the next 6–12 months, note them. This helps us avoid recommending coverage for workloads that are about to change significantly.

What we do not need

• No platform access. The offline savings assessment works entirely from invoices and exports. No API connections, no IAM roles, no credentials.
• No architecture diagrams. The assessment focuses on billing and procurement, not infrastructure design.
• No code or application details. We analyze spend patterns, not workload architectures.

How to submit

Once you've gathered the materials, submit them through the savings assessment request process. You'll have results within 2–3 business days, showing exactly where coverage gaps exist and what closing them would save.

Ready to get started? Visit the how it works page to submit your savings assessment request.