> 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/getting-started/joining-pump/when-can-i-expect-to-see-savings.md).

# When can I expect to see Savings?

Cloud savings don’t have to take months to show up. With Pump, you’ll see some reductions *immediately* and even more within your first week. Here’s how it works:

💨 **Immediate Savings**

As soon as you join, you’ll benefit from **volume discounts** through our group buying model. These apply instantly, lowering your costs right out of the gate once you join Pump.

🤖 **AI-Driven Savings**

Our **AI-driven optimizations** will start within the first week:

* We only receive your cost data from AWS, GCP, and Azure 48-72 hours after you join.
* Our model needs a couple days of data to analyze your usage patterns and find the best savings opportunities for you!

Once we have enough data (usually within the first week) we start applying deeper optimizations, ensuring you get **the maximum possible savings** while keeping your infrastructure flexible.


---

# 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/getting-started/joining-pump/when-can-i-expect-to-see-savings.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.