> 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/what-it-is.md).

# What is Go to Market

Go to Market is your sales area in Plenit: define prices, prepare quotes, review what you bill your customers, and use ready-to-sell materials.

Go to Market is your commercial area within Plenit: the space from which you turn Plenit services into your own business offering.

Here you decide what price you sell at, prepare the offers you send to your customers, review what you are going to bill them, and make use of ready-made sales materials.

Instead of building spreadsheets, quote templates, and sales documents on your own, you have it integrated into the dashboard.

> #### 📘 The underlying idea
>
> We sell you the services at a price (your cost as a partner) and you sell them to your customer at the price you decide. Go to Market is where you manage that difference: your margin, your prices, and your offers, under your brand.

### The four tools

Go to Market brings together four tools that cover the sales cycle from beginning to end.

#### Rates

This is the financial foundation. A rate defines the price at which you sell each service to your customers, applying your margins over Plenit’s price.

You can have several rates, set one as default, and start from the rate recommended by Plenit for your country. Everything else (quotes and invoicing) is based on the rate.

More in [Rates: PVD, PVP and margin.](https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md)

#### Quotes

This is where you prepare offers for your customers. You choose the services, size them, and the platform calculates the price according to your rate, showing you both your cost and the customer price.

You can preview, download the offer with sales documents and contracts, and duplicate quotes to reuse them.

More in [Quotes.](https://docs.plenit.com/docs-en/go-to-market/concepts/quotes.md)

#### Customer billing

This is the view of what you are going to charge each customer. It brings together the delivery notes generated from your customers' subscriptions, with their financial breakdown, and lets you view and download them.

This is a consultation tool, not an editing tool.

More in [Customer invoicing.](https://docs.plenit.com/docs-en/go-to-market/concepts/customer-billing.md)

#### Documentation

It is the repository of sales materials: presentations, sales documentation, contracts, email marketing templates, and more, many customizable with your brand.

It saves you from producing sales materials from scratch. More in [Documentation.](https://docs.plenit.com/docs-en/go-to-market/concepts/documentation.md)

### How they fit together

The four tools follow a natural order. First you define a [**rate**](https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md) with your margins.

With that rate you prepare a [**quote**](https://docs.plenit.com/docs-en/go-to-market/concepts/quotes.md) for a customer, which automatically calculates prices and can be accompanied by [**documentation**.](https://docs.plenit.com/docs-en/go-to-market/concepts/documentation.md)

When the customer accepts and the services are activated, their usage appears in [**customer billing**](https://docs.plenit.com/docs-en/go-to-market/concepts/customer-billing.md), where you can see what they owe.

The rate is the foundation: it determines the quotes, the amounts you see in the dashboard, and the associated billing.

> #### 👍 What you gain with Go to Market
>
> You sell under your brand, with your margins and with ready-made materials, without leaving the dashboard or setting up separate tools. Less sales friction, more time to sell.<br>

### What Go to Market is not

It is not a CRM or a billing system of its own: it does not replace your management tool or issue legal invoices to your customers. Customer billing is a consultation view of the delivery notes derived from usage, so you know what to charge; invoicing and tax management remain yours. It also does not include brand customization of the dashboard and portal, which is managed in its own area.

### Next steps

* Start selling with the [Go to Market Quick Start](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Go-To-Market/go-to-market-conceptos/go-to-market-inicio-rapido/README.md).
* Understand the pricing model in [Rates: PVD, PVP and margin](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Go-To-Market/go-to-market-conceptos/go-to-market-tarifas/README.md).
* Learn how to prepare offers in [Quotes](https://gitlab.com/plenit-group/plenit-docs-es-es/-/blob/v1.0/docs/Go-To-Market/go-to-market-conceptos/go-to-market-presupuestos/README.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/what-it-is.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.
