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

# Frequently Asked Questions

Frequently asked questions about Go to Market: the pricing model, rates, quotes, customer billing, and sales documentation.

The most common questions when selling Plenit services with Go to Market, grouped by topic. Each answer links to the concept, guide, or reference where the details are.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Rates</strong></td><td>Recommended rate, default, margin levels, and periods.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md">Rates</a></td></tr><tr><td><strong>Quotes</strong></td><td>How they are created, the review screen, statuses, documents, and white label.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/details/billing-detail.md">Billing Details</a></td></tr><tr><td><strong>Invoicing and documentation</strong></td><td>Customer delivery notes, downloads, and sales materials.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/concepts/customer-billing.md">Customer billing</a></td></tr></tbody></table>

### Pricing model

<details>

<summary>What is the difference between PVD and PVP?</summary>

The **PVD** (selling price to distributor) is your cost as a partner: the price at which we bill you for each service. The **PVP** (retail price) is the price at which you sell to your end customer. The **margin** is the difference between the two: what you earn. More in [Rates](https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md): PVD, PVP and margin.

</details>

<details>

<summary>How is the sale price calculated from the margin?</summary>

It is not just cost plus the percentage, but cost divided by (1 minus the margin): `Price = Cost / (1 - margin)`. For example, with a cost of €100 and a 25% margin: 100 / (1 - 0.25) = €133.33. Calculating it this way ensures that the margin on the final price is exactly what you want.

</details>

<details>

<summary>Where can I see what I earn on each offer?</summary>

In the review screen of a quote and in the quote list you will always see the figures together: **your cost** (PVD), **what you are selling it for** (PVP) and the **margin** percentage margin. That way you can see your profit at a glance.

</details>

### Rates

<details>

<summary>Do I have to create a rate before making a quote?</summary>

It is not mandatory. If you generate a quote without having created your own rate, the recommended rate or your default rate is applied. Creating your rate first gives you more control over your margins, but you can start without it. [More in Rates](https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md): PVD, PVP and margin.

</details>

<details>

<summary>What is the recommended rate?</summary>

It is the rate we propose as a starting point, adjusted according to the partner's country. It is a good starting point if you do not want to build your own from scratch. If there is no recommended one for your case, the one marked as default is used.

</details>

<details>

<summary>Can I set different margins for each service?</summary>

Yes. The margin is defined at three levels: **global** (the whole rate), **by service** (for example, one margin for Servers and another for Remote Desktop) and **by item** (a specific line). The most specific overrides the more general. The fields are in [Rate parameters.](https://docs.plenit.com/docs-en/go-to-market/details/rate-card-parameters.md)

</details>

<details>

<summary>What billing periods does a rate have?</summary>

A rate is defined **Hourly** or **Monthly**. That period determines how prices are expressed and how it fits with the estimated hours per month of the [Quotes.](https://docs.plenit.com/docs-en/go-to-market/concepts/quotes.md)

</details>

### Quotes

<details>

<summary>How do you create a quote?</summary>

With a three-step wizard in one window: basic data (name, customer, and hours estimate), service selection, and configuration of each one. When saved, the review screen opens, where you adjust margins and close the offer. The step-by-step instructions are in How to generate a quote.

</details>

<details>

<summary>What is the monthly hours estimate?</summary>

These are the monthly hours used to calculate the cost, since we bill by the hour. You can choose 730 (annual average), 720 (30-day month), or 744 (31-day month). The recommended option is 730: your customer sees a fixed payment each month and the differences are balanced out at year-end.

</details>

<details>

<summary>What do I do on the review screen after saving?</summary>

It is the screen where you see your cost, selling price, and margin, adjust the margin (globally with Edit Margin or line by line), choose the status, and can preview, download, or finalize the quote. Finalizing saves it for reference, already closed.

</details>

<details>

<summary>What statuses can a quote have?</summary>

A quote is created in **Draft**, and there are the statuses **Approved** and **Rejected** to reflect the customer's decision. The automatic step to a "Sent" status is not operational for now: delivery to the customer is done by downloading or previewing.

</details>

<details>

<summary>What documents can I download with a quote?</summary>

When downloading, you can accompany the quote with **financial quote**, **contracts** customized (with tax ID and representatives for data protection purposes) and **sales presentations** for each service. If you choose several, they are delivered in a single compressed file. You can also include an acceptance section with remarks.

</details>

<details>

<summary>What does my customer see when I send them the quote?</summary>

The preview shows the quote exactly as your customer will see it: with your branding (your logo and details), their details, and the PVP. The PVD (your cost) does not appear in what the customer sees. It is white label.

</details>

<details>

<summary>Can I reuse a quote for another customer?</summary>

Yes, with the **Clone** action in each quote's menu. You duplicate an offer that already works and adapt it, instead of starting from scratch. The menu also includes Update rate, Edit, Download, Preview, and Delete.

</details>

### Invoicing and documentation

<details>

<summary>Does customer invoicing issue the invoices for me?</summary>

No. It is a reference view: it gathers the delivery notes derived from your customers' usage so you know what to charge them, but issuing the legal invoice and handling its tax management are still your responsibility. More in [Customer invoicing.](https://docs.plenit.com/docs-en/go-to-market/concepts/customer-billing.md)

</details>

<details>

<summary>In what formats can I download a delivery note?</summary>

You can preview each delivery note and download it in **PDF** (to send) and in **CSV** (to process it in a spreadsheet). The delivery note includes a summary and an itemized breakdown with quantity, unit price, VAT, and amount.

</details>

<details>

<summary>What happens to the delivery notes if I delete a customer?</summary>

They are kept. If you delete a customer, their delivery notes remain accessible (marked as deleted); if a customer migrates to another partner, the ones prior to the migration remain visible to you. That way you keep the history for audit and reference.

</details>

<details>

<summary>Can I use sales materials with my brand?</summary>

Yes. The Documentation center brings together presentations, sales documentation, contracts, and email marketing templates, and much of it is downloaded white-label, with your logo in the PDF. More in [Documentation.](https://docs.plenit.com/docs-en/go-to-market/concepts/documentation.md)

</details>

### Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quick Start</strong></td><td>Create your first rate and generate a quote step by step.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>The key ideas for selling with judgment.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides to understand go-to-market</td><td></td></tr><tr><td><strong>Details</strong></td><td>Reference for fields, columns, and options.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/details.md">Details</a></td></tr></tbody></table>


---

# 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/faq.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.
