> For the complete documentation index, see [llms.txt](https://help.usedotted.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usedotted.com/en/dotted-platform/finops-teams-time-spent.md).

# Finops Teams Time Spent

This criteria below is used to calculate the number of hours saved as a result of utilizing Dotted's services.

1. **Small Infrastructure (up to $40k/month in cloud spending)** 
   1. **Low ESR (<10%):** 25 hours/month, indicating the need for more work in identifying savings opportunities.&#x20;
   2. **Medium ESR (10%-30%):** 20 hours/month, reflecting moderately efficient cost management.
   3. **High ESR (>30%):** 15 hours/month, suggesting efficient use of discounts and less need for continuous optimization.
2. **Medium Infrastructure (or $40k to $400k/month in cloud spending)**&#x20;
   1. **Low ESR (<10%):** 90 hours/month, higher need for analysis and adjustment to improve savings.&#x20;
   2. **Medium ESR (10%-30%):** 70 hours/month, good cost management, but room for improvement.&#x20;
   3. **High ESR (>30%):** 50 hours/month, high efficiency in obtaining discounts and cost management.
3. **Large Infrastructure (more than $400k/month in cloud spending)**
   1. **Low ESR (<10%):** 225 hours/month, indicating significant potential for optimization and need for intensive efforts.&#x20;
   2. **Medium ESR (10%-30%):** 175 hours/month, active cost management with need for continuous optimization.&#x20;
   3. **High ESR (>30%):** 125 hours/month, demonstrates highly effective cost management, reducing the workload required for optimization.


---

# 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.usedotted.com/en/dotted-platform/finops-teams-time-spent.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.