RevOps playbook · AI Employee: Rev

Pipeline & Deal Lookup

Sellers get deal snapshot in one turn

The problem

Sales reps live in the CRM. Every deal question — status, size, next step, last activity — is a CRM lookup that interrupts flow. In Slack, in email, on a call, the answer is always "one sec, let me pull it up". The time cost per lookup is small; the aggregate over a rep's day is enormous. And the manager who asks "how's the Acme deal?" gets the same delay.

At a glance
Trigger
Chat
Approvals
None
What it does
Read-only
Systems
Salesforce · HubSpot
How it feels in production

An hour-by-hour walkthrough.

10:47am. Sales manager Alex DMs Rev: "where's the Acme deal?" 10:47am + 3 sec. Rev queries Salesforce, finds Acme's opportunity: stage=Negotiation, ARR=$120k, close date=Sep 30, owner=Priya, last activity=Gong call yesterday. Pulls the last call summary from Gong. Drafts a summary: "Acme, $120k, Negotiation, Priya. Last call yesterday — Priya reviewed pricing with CFO, they want to negotiate down 10%, waiting on her response by Thursday." 10:47am + 4 sec. Alex sees the summary. Continues the conversation without a tab switch. Rev works across every context: in Slack, in the widget, in the MCP endpoint for Cursor / Claude Desktop, via API for custom dashboards. Same lookup, same data, same summary style. When the deal doesn't exist, or exists but the requester doesn't own it, or is restricted (confidential opportunity), Rev handles cleanly: says so, offers to route to the right person, or explains the access boundary.
How it works

Step by step.

  1. 01

    Look up deal by name / ID / account

    Rev parses the request ("Acme deal", "opp #12345", "account 001abc"). Queries Salesforce / HubSpot with the parameter. Handles ambiguity ("there are 3 opportunities for Acme, which one?").

    Salesforce · HubSpot
  2. 02

    Return stage, owner, ARR, notes

    Fetches the standard opportunity fields plus recent activity (calls, emails, notes). Formats a compact summary that reads well in Slack or Teams.

    Salesforce · HubSpot · Gong · Chorus
  3. 03

    Enrich with recent context

    Pulls the last Gong / Chorus call summary; recent emails; last stage change. Reader sees not just current state but recent motion.

    Gong · Chorus · Outreach · Salesloft
Systems and wiring

What you connect to make this run.

Salesforce

read

OAuth credential with opportunity + account + activity read scopes. Respects field-level security — Rev never surfaces fields the requester can't see.

HubSpot

read

Same pattern for HubSpot deals + companies + activities.

Gong · Chorus

read

Call recording + summary read. Links back to the call playback for detailed review.

Context Graph

read

Deal-to-owner + deal-to-account edges. Enables cross-referencing like "all my deals" or "deals in my territory".

What changes

Before and after, honestly.

Time from question to answer
Before
30-90 seconds (CRM tab switch + navigation)
After
Under 5 seconds
Rep tab switches per day
Before
100+ context switches to CRM
After
10-20 (only for actual updates, not lookups)
Manager 'quick deal check' overhead
Before
3-5 min per check (login, search, review)
After
10 seconds in Slack
"Where's that deal?" Slack noise
Before
Constant interruption of the deal owner
After
Rev answers directly; owner not pulled in unless needed
Frequently asked

Answers about this playbook.

Can Rev handle 'my deals' queries?

Yes — "show me my open deals", "my deals closing this quarter", "my top 5 by ARR". Requester identity read from Slack SSO; queries filtered to their ownership.

What about access to deals I don't own?

Respects Salesforce sharing rules. Public deals visible to all sales; restricted / confidential deals only to their owner + management chain. Rev never surfaces what the requester can't see.

Does this work for HubSpot as well?

Yes — same lookup pattern for HubSpot deals + companies + engagements. If you use both, Rev queries both and returns unified results.

Can Rev update deals, not just look them up?

Yes — separate playbook (deal update / stage advance / note logging). Updates go through your approval matrix per field type — some low-risk updates auto-apply; stage changes and deal-value edits require confirmation.

How does this work from Claude Desktop / Cursor?

Via MCP endpoint. "What's the Acme deal status?" in Claude Desktop hits Rev via MCP; same lookup + summary; response streams back into the chat.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.