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

# Go-To-Market

Your commercial operation in Plenit at a glance: quotes, customer billing, rates, and the customization of your resources.

Here you manage your commercial operations with your customers: you create quotes, invoice them, define your rates, and customize how you present the resources to them.

Each section has a quick start, concepts, step-by-step guides, frequently asked questions, and details. Start with whatever you need.

{% hint style="info" %}
Is this your first time here? Go to Where to Start below and set up your commercial operations in minutes.
{% endhint %}

### Explore Go to Market

<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>Quotes</strong></td><td>Create, send, and manage the quotes you offer your customers.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/concepts/quotes.md">Quotes</a></td></tr><tr><td><strong>Customer billing</strong></td><td>Invoice your customers and track what you charge them for each service.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/concepts/customer-billing.md">Customer billing</a></td></tr><tr><td><strong>Rates</strong></td><td>Define the prices you apply to your services and to each customer.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md">Rates</a></td></tr><tr><td><strong>Resource customization</strong></td><td>Adjust how resources and services are presented to your customers.</td><td><a href="https://docs.plenit.com/docs-en/platform/organizations/detalles/customization.md">Customization</a></td></tr></tbody></table>

### Where to start

<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>Create your first quote</strong></td><td>Prepare and send a quote to a customer in four steps.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/how-to/how-to-generate-a-quote.md">How to Generate a Quote</a></td></tr><tr><td><strong>Set up your rates</strong></td><td>Define the prices you will apply to your services.</td><td><a href="https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md">Rates</a></td></tr><tr><td><strong>Issue your first invoice</strong></td><td>Invoice a customer and review the month's invoiced amount.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/concepts/how-we-bill-you.md">How We Bill You</a></td></tr></tbody></table>

### Support

{% hint style="success" %}
Need help with your commercial operations? Open a ticket or write to us on WhatsApp from the \[Support]\(../support) section.
{% endhint %}


---

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