> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/plans-and-contact/talk-to-sales.md). # Talk to Sales What a sales conversation covers, and how to start one. A sales conversation is the right route when you want to match Revenium to a specific workload rather than read about the platform. Typical ground it covers: * Which package fits your expected ingestion volume and the number of teams or environments you need. * How your AI providers, agents, and coding assistants would be connected, and what data each one reports. * Monetization requirements if you bill your own customers through Revenium. * Security, deployment, and data residency questions. See [Deployment Options](/plans-and-contact/deployment-options.md) for what is available, and the [Security and Trust Center](/plans-and-contact/security-and-trust-center.md) for where current security and compliance information lives. * Onboarding and what a first phase of rollout looks like. ## How to start one Email , or use the contact form at . Current packages are listed at . If you are an existing customer with a technical question rather than a commercial one, [Get Support](/plans-and-contact/get-support.md) is the faster path. --- # 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.revenium.io/plans-and-contact/talk-to-sales.md?ask=&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.