> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/go-to-market/concepts/quotes.md).

# Quotes

What a quote is in Plenit: how it gathers sized services, shows your cost and the customer price, its statuses, and the documents it generates.

A quote is the offer you prepare for a client: it lists the services you propose, sized to fit their needs, and calculates the price according to your rate.

It’s the tool that takes you from "I have some services to sell" to "I have a concrete proposal for this client", with the sales documents ready to send.

### What a quote includes

A quote is built in a three-step wizard: the **basic details** (name, client and monthly hours estimate), the **services** services you include (Remote Desktop, Servers, Disaster Recovery, storage, licenses, or a custom service) and the **configuration** of each one (region, resources, networks, etc.). The result is a sized and priced offer.

> #### 📘 The monthly hours estimate
>
> At Plenit we bill by the hour, so the quote needs to know how many hours per month to estimate.
>
> You have three options: 730 hours (annual average), 720 (30-day month) and 744 (31-day month). The recommended option is the annual average (730): the client sees a fixed payment every month and, at the end of the year, the small differences between 30- and 31-day months are offset.

### Your cost and the client price

When you save the quote, the platform shows a summary with the three figures that really matter: **your cost** (what you pay Plenit), **what you are selling it for** (the price for your client) and the **margin** margin percentage. You can edit the margin centrally for the whole quote, or adjust it line by line whenever you want a different deal on a service. If something is missing, you can add services without leaving the summary.

### Quote statuses

A quote goes through several states throughout its life: it starts as **Draft**, then moves to **Sent** when you send it to the client, and ends as **Approved** or **Rejected** depending on their decision. Having the states clear helps you know where each open quote stands.

### The documents it generates

A quote is not just a number. When you download it, you can accompany it with a package of sales documents ready to send: the **financial quote**, **contracts** customized with the name and tax ID of your company and your client, and **sales presentations** with your branding for each included service. If you choose several, the platform generates a ZIP with everything inside, with descriptive names so you can keep it organized.

> #### 👍 Clone to go faster
>
> From each quote's menu, you have actions such as edit, preview, download, delete, and clone.
>
> Cloning is especially useful: you duplicate an offer that already works and adapt it to another client, instead of starting from scratch each time.

### Beyond the offer

The quote connects with the rest of your operations. You can work with real clients or with fictional clients to prepare simulations, compare later what was quoted with the actual billing, and in the most recent versions even deploy the services directly from an approved quote, so the accepted offer becomes active infrastructure without redoing the work.

### Next steps

* Prepare your first offer with [How to generate a quote.](https://docs.plenit.com/docs-en/go-to-market/how-to/how-to-generate-a-quote.md)
* Define your margins in [Rates.](https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md)
* See the fields and columns in [Quote details.](https://docs.plenit.com/docs-en/go-to-market/details/quote-fields.md)


---

# 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://docs.plenit.com/docs-en/go-to-market/concepts/quotes.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.
