> 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/savings-survey.md).

# Savings Survey

Cloud usage changes over time. To make sure your savings fit your actual needs, we include a **Savings Survey** in our onboarding process. The survey helps us understand how your infrastructure might change over the next year so we can:

* **Optimize your savings** by aligning commitments with your expected usage.
* **Avoid overcommitting** and getting stuck with resources you don’t need.<br>

📋 **What We Ask**

A few quick questions about your plans:

* Do you expect your infrastructure to **grow** in the next 6-12 months?
* Are there any **services you plan to scale down** or stop using?
* Do you anticipate **any major architecture changes** that could affect your cloud spend?<br>

We use your answers to tailor your savings strategy so you get the best cost benefits without locking into commitments that won’t fit down the line.&#x20;


---

# 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/savings-survey.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.