> 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 A quote is the offer you prepare for a client: it gathers the services you propose to them, sized to fit their needs, and calculates the price according to your rate. It is the tool that takes you from "I have some services to sell" to "I have a specific proposal for this client", with your commercial documents ready to send. ### What a quote includes A quote is built in a three-step wizard: the **basic data** (name, client, and estimated hours per month), 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 tailored and valued offer. > #### 📘 The estimated hours per month > > 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 balanced out. ### Your cost and the price to the client 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're selling it for** (the price for your client) and the **margin** margin, in percentage. You can edit the margin centrally for the whole quote, or adjust it line by line whenever you want a different deal for 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**, goes to **Sent** when you send it to the client, and ends as **Approved** or **Rejected** according to their decision. Having the states clear helps you know where each open offer stands. ### The documents it generates A quote is not just a number. When you download it, you can accompany it with a package of commercial documents ready to send: the **financial quote**, **contracts** customized with the name and tax ID of your company and your client, and **commercial presentations** with your brand for each included service. If you choose several, the platform generates a ZIP with everything inside, with descriptive names so you can keep them organized. > #### 👍 Clone to go faster > > From the menu of each quote you have actions like 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 dummy clients to prepare simulations, later compare what was quoted with the actual invoicing, and in the more recent developments 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.](/docs-en/go-to-market/how-to/how-to-generate-a-quote.md) * Define your margins first in [Rates.](/docs-en/go-to-market/concepts/rate-cards.md) * See the fields and columns in [Quote details.](/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 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://docs.plenit.com/docs-en/go-to-market/concepts/quotes.md?ask=&goal= ``` `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.