Key takeaways
- RevOps owns the CRM, the go-to-market stack and the data that runs through it.
- The function hides behind many titles: revenue, sales, marketing and GTM operations, plus CRM and systems roles.
- A CRM migration, a stack review or a renewal is when RevOps adds or removes tools.
- Expect detailed questions on what your product reads and writes, who approves changes and where data goes.
What does RevOps own
RevOps owns the systems, data and processes that sales, marketing and customer success share, with the CRM at the centre. That makes the team the gatekeeper for any tool that reads from or writes to the CRM. A head of sales may want your product, but RevOps decides whether it can connect, which fields it may touch and how its activity is reported.
In a buying group they are the technical evaluator and, in many companies, the budget owner for the go-to-market stack. They also live with the consequences of every tool long after the seller has moved on, which shapes how sceptically they listen.
Which titles cover revenue operations manager and sales ops contacts
Search the whole operations family, because the same job is labelled by function, by maturity and by fashion.
In small companies RevOps is often one person, or a sales manager who looks after the CRM as well as selling. Seniority filters separate the person who owns the stack from the analysts who maintain it.
- Revenue operations: VP or head of revenue operations, revenue operations manager.
- Sales operations: head of sales operations, sales operations manager or analyst.
- Marketing operations: often the owner of automation and lead routing.
- GTM operations and GTM engineering: newer titles for people who build workflows across the stack.
- Systems roles: CRM manager, CRM administrator or business systems manager.
Which triggers bring RevOps to the table
RevOps reviews tools when the stack is changing, so migrations, consolidation and renewals are the triggers to watch.
- A CRM migration, visible in job adverts asking for experience with the new system.
- A drive to consolidate the stack, often after a budget review or new finance leadership.
- The first RevOps hire, or a new head of RevOps reviewing what they inherited.
- Sales team growth that breaks routing, territories or reporting.
- Tool renewal dates, which RevOps usually manages.
How to reach RevOps with the right answers
Reach RevOps by leading with how your product connects to their CRM and what it will do to their data, because that is the first thing they check. Answer plainly, including what your product does not do. RevOps leaders have inherited tools that promised more than they delivered, and honesty about limits earns more trust than a long feature list.
- Which CRM objects and fields does it read, and which does it write?
- Is the connection native or through another protocol, and does it update automatically or only on request?
- Who approves changes, and can permissions be limited by role?
- How are duplicates and conflicting updates handled?
- Where is data stored, and is any of it used to train a model?
What GDPR means when RevOps owns the contact data
RevOps is often responsible for the lawful basis recorded against each contact in the CRM, so your outreach to them should model good practice. Emailing a RevOps leader at work under legitimate interest is usually possible: keep your assessment on file, explain where their details came from and give them an easy opt-out.
Expect them to ask how your own product records objections, consent and retention, because they will have to answer the same questions for every contact your product adds. In the UK, PECR governs the email as well. This is general guidance, not legal advice.
How to find RevOps contacts, step by step
Lead with the technical answers RevOps will ask for anyway.
- Search revenue, sales, marketing and GTM operations titles, plus CRM and business systems roles, with seniority filters.
- Look for CRM migrations, stack consolidation, a new RevOps leader, sales team growth or a renewal date.
- Write down exactly how your product connects to each CRM, what it reads and writes, and what needs approval.
- Open with the connection and data answers, then the problem your product solves for the teams they support.
- Offer a technical session and documentation instead of a sales demo.
Where Pebbles Ai fits
- FoundationIntegrationsThe assistants keep Attio or Pipedrive in step through their MCP connections, reading records and creating or updating them from chat. Each write is an approval action under the execution mode; there is no automatic or two-way sync, and HubSpot and Salesforce are not in the catalogue.
- CapabilityProspecting & customer recordsFind fresh leads takes revenue operations and sales operations as roles at up to ten named companies and lands the people found as contacts in a segment in the CRM (in Beta), with work emails where found and a confidence score.
Common questions
What is the difference between RevOps and sales ops?
Sales operations supports the sales team alone, while revenue operations covers sales, marketing and customer success together. Many companies renamed sales ops as RevOps as the remit widened.
Who owns the CRM in most companies?
RevOps or sales operations where they exist; otherwise a sales manager or a CRM administrator. Check who approves new connections before you sell a tool that uses the CRM.
Does Pebbles Ai sync with HubSpot or Salesforce?
No. HubSpot and Salesforce are not in the MCP catalogue. For Attio and Pipedrive, the assistants read and update records through MCP, with each write approved under the execution mode.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
