> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/pump-save/savings-estimate.md).

# Savings Estimate

## Savings Estimate

A savings estimate shows you how much Pump can save on your cloud spend before you make any billing commitment. It runs using either read-only API access or a CSV upload, so nothing changes in your cloud account.

### How to run a savings estimate

You can generate an estimate during onboarding or at any time afterward. The process differs slightly by cloud provider.

#### AWS

You have two options:

**Option A: CSV upload (no permissions required)**

1. Sign in to the AWS Console.
2. Navigate to **Cost Explorer**.
3. Export two CSV files:
   * Your cost and usage data for the time range requested
   * Your existing Reserved Instance and Savings Plan inventory
4. In Pump, select **AWS** as your provider and choose **Upload CSV**.
5. Upload both files.
6. Pump generates your estimate within a few minutes.

**Option B: Read-only API access**

1. In Pump, select **AWS** as your provider and choose **Connect account**.
2. Follow the prompts to deploy a CloudFormation stack that creates a read-only IAM role in your account.
3. Once the role is active, Pump pulls your Cost Explorer data directly and generates the estimate.

The read-only approach provides a more detailed estimate because Pump can access granular usage data beyond what the CSV exports contain.

#### GCP

1. In Pump, select **GCP** as your provider.
2. Upload your billing history CSV (exported from the GCP Console billing page).
3. Pump generates your estimate based on your historical usage patterns.

#### Azure

1. In Pump, select **Azure** as your provider.
2. Upload your Azure usage file for the last 3 months (downloaded from the Azure portal).
3. Pump generates your estimate based on your usage data.

### What the estimate shows

Your savings estimate includes:

| Data point                     | What it means                                                                                    |
| ------------------------------ | ------------------------------------------------------------------------------------------------ |
| **Projected monthly savings**  | The estimated dollar amount Pump can save you per month based on your current usage              |
| **Savings percentage**         | Projected savings as a percentage of your current on-demand spend                                |
| **Commitment recommendations** | The specific RIs, Savings Plans, or CUDs that Pump would purchase to achieve these savings       |
| **Coverage analysis**          | How much of your eligible spend would be covered by commitments vs. remaining at on-demand rates |

The estimate is based on your historical usage. Actual savings may vary as your usage patterns change.

### What happens after the estimate

The estimate is informational. To start saving, you need to:

1. Agree to have Pump act as your billing partner (solutions provider relationship).
2. Accept the Terms of Service and Privacy Policy.
3. Grant billing-level permissions (this is the step that enables Pump to purchase commitments).
4. Enter your company details and payment method.

None of these steps happen automatically. The estimate does not commit you to anything.

### How long estimates take

| Provider | CSV upload    | API-based                                          |
| -------- | ------------- | -------------------------------------------------- |
| AWS      | A few minutes | A few minutes after CloudFormation stack completes |
| GCP      | A few minutes | N/A (CSV only for estimate)                        |
| Azure    | A few minutes | N/A (CSV only for estimate)                        |

### Troubleshooting

**Q: Why does my estimate show $0 in savings?** \
A: This typically means your current spend is already well-committed or your usage volume is below the threshold where commitment discounts are meaningful. Pump Save has the most impact at $5,000/month or more in cloud spend.

**Q: Why was my CSV rejected?**\
A: Ensure you are uploading the correct file format. For AWS, you need two specific Cost Explorer exports (Pump provides instructions during the upload flow). For GCP and Azure, you need the billing/usage file from the respective portal, not a custom export. 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.pump.co/pump-save/savings-estimate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.