> 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/real-customers-real-success-stories.md).

# Real Customers, Real Success Stories

Here are some **PUMP**ed customers we have saved on their AWS bill:

* We saved [**Smartlead**](https://www.smartlead.ai/) **25% on AWS** in their first month with Pump!
* We saved [**Arc Boats**](https://arcboats.com/) **30%** **on AWS** in their first month with Pump!
* We saved [**Reality Defender**](https://www.realitydefender.com/) **28% on AWS** in their first month with Pump!
* We saved [**Terra**](https://tryterra.co/) **$3,200** using Pump!
* We saved [**Finsera**](https://finsera.com/) more than **$2,000/mo** with Pump!

<figure><img src="https://44033590-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9AjQj4Qn0NOuXDBL27jQ%2Fuploads%2F8QiLXjqNLWVriDPdcxXn%2FReal_customer.png?alt=media&amp;token=8ae4e451-c48c-417d-a3fe-d188ec282122" alt=""><figcaption><p>This is a real customer dashboard depicting that the customer was spending ~$6500, and ended up spending under $3,000!</p></figcaption></figure>

This is a real customer that was spending \~$6500 before they joined Pump. When they joined Pump, it took a few days, and then by their first full month with Pump, they spent under $3,000! (you read that right, all thanks to Pump)

Pump's goal is to help customers reduce their on-demand spend, and we do this by scanning their infrastructure with our autopilot model, and creating / executing recommendations on SPs/RIs with the focus of optimizing your AWS spend for free.

🎉 You could be the next success story, feel free to [**sign up today in minutes**](broken://pages/GMB7yXWUWPFpcQTl6Gyi)! 🎉


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pump.co/getting-started/real-customers-real-success-stories.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.