> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# RevOps and Sales Ops

> Set up a RevOps desk in Ravenna: a deal desk with fast approvals and CRM context on the ticket, plus go-to-market tooling requests that stop being DMs to the ops lead.

RevOps is the department most likely to already have a request process and least likely to have one anyone follows. Reps ask in a DM because it is faster, which means the ops team has no visibility into what it spends its week on.

There is one constraint that shapes every decision here: a deal desk that is slower than a DM will be routed around. Response speed is not a nice-to-have on this desk, it is the adoption strategy.

## What RevOps owns in Ravenna

<CardGroup cols={2}>
  <Card title="Deal desk" icon="handshake" href="/guides/playbooks/revops/deal-desk" horizontal>
    Pricing and terms approvals fast enough that reps use them.
  </Card>

  <Card title="Tooling requests" icon="wrench" href="/guides/playbooks/revops/tooling-requests" horizontal>
    CRM changes and seat requests as tracked work, not interruptions.
  </Card>
</CardGroup>

## Suggested shape

One workspace called **RevOps** or **Sales Ops**, and one public channel where the sales team already lives, `#deal-desk` or `#ask-revops`. Public matters more here than in most departments: reps learn from each other's approved exceptions, and a public channel means the same discount question is not asked four times.

Categories that map to how you would report: Pricing approval, Contract terms, CRM change, Data request, Tooling and seats, Reporting request.

## Connect the CRM

[HubSpot](/integrations/hubspot/overview) is available natively, with agent tools for searching contacts, companies, and deals, and for listing deals by stage, owner, or date. Reference them in agent rules with an `@` mention.

That turns "which deal is this about" from a question into context. A rep says "I need approval on the Acme renewal" and the agent can find the deal, its amount, its stage, and its owner without the rep pasting a link.

For any other CRM, [Foundry](/guides/how-to/foundry/overview) generates a typed action against its API. The [Foundry examples](/guides/how-to/foundry/examples) page has a CRM contact lookup as a worked example.

## The agent's role

Two jobs, both high volume:

* **Answer the documented questions.** Approval thresholds, standard payment terms, what needs Legal, which discount tiers exist, how to handle a multi-year deal. These are policy lookups.
* **Gather the deal context.** Pull the deal record so the approver is not asking the rep for the amount.

What it should not do is approve anything or state a price that is not in the pricing sheet.

## Where RevOps desks stall

<AccordionGroup>
  <Accordion title="Slower than a DM">
    If the desk adds a day, reps go around it. Aggressive SLAs on pricing approvals are the price of adoption.
  </Accordion>

  <Accordion title="A private channel">
    Reps learn from precedent. Keep it public.
  </Accordion>

  <Accordion title="Approving everything">
    Standard-terms deals should not need a deal desk. Only exceptions should.
  </Accordion>

  <Accordion title="No CRM context">
    An approver who has to ask for the deal amount is the reason the process feels slow.
  </Accordion>
</AccordionGroup>

## Next

<CardGroup cols={2}>
  <Card title="Deal desk" icon="handshake" href="/guides/playbooks/revops/deal-desk" horizontal>
    Fast approvals on pricing and terms.
  </Card>

  <Card title="Tooling requests" icon="wrench" href="/guides/playbooks/revops/tooling-requests" horizontal>
    CRM changes and seats.
  </Card>
</CardGroup>


## Related topics

- [Playbooks](/guides/playbooks/overview.md)
- [Tooling requests](/guides/playbooks/revops/tooling-requests.md)
- [Deal desk](/guides/playbooks/revops/deal-desk.md)
- [Workspaces](/documentation/platform/workspaces/overview.md)
- [Product Updates](/changelog/2025.md)