Find ops owners
Find RevOps leaders by CRM stack and go-to-market size
RevOps exists at companies that outgrew a spreadsheet and admitted it. The tell is the tooling on the site plus a revenue team large enough to need someone keeping it honest.
RevOps is a young function and its title has not settled. At one company it is Revenue Operations, at the next it is Sales Ops, Business Operations, or an analyst reporting to the CRO who owns the whole stack anyway. Matching on the string alone misses most of them.
Two account facts fix that. What the company runs, read from the tooling BuiltWith detects on its domain, and how many people sit across sales, marketing, and success combined. Below roughly fifteen there is no ops owner. Above it somebody is doing the job under whatever name the org chart gave them.
Example searches
Ask for it the way you'd say it
Every search below runs on the same hosted Tables, with the cost previewed before anything is spent.
Stack first, title second
find companies whose site shows a crm and analytics stack, then get whoever owns revenue operations
Detection runs on the domain before any person work, so the contact chain only touches accounts that already showed a stack.
The unnamed ops owner
give me the person closest to sales operations even if their title does not say revops
Function and seniority are the filters, so a business operations manager comes back with the actual title recorded beside them.
Size the go-to-market team
which accounts here have more than 20 people across sales, marketing and customer success
The combined count is one column, so you can set the floor where your product starts paying for itself and re-sort the list.
Plays
Three motions you can run this week
Each one is a chain of Oxygen primitives — the same hosted objects your workspace already has, composed.
Stack plus team size
A list where every account runs real tooling and employs enough people to need it.
- 1Detect the go-to-market stack across the account table and keep each tool as a column.
- 2Add the combined revenue headcount, cut below your floor, then resolve the ops owner.
oxygen companies enrich runFind the owner without the title
The person doing the job surfaces even where the org chart calls it something else.
- 1Keep your definition of an ops owner as a page in the workspace wiki.
- 2Let the scoring column read that page for every row, then enroll what it marks.
oxygen knowledge page upsertKeep the ops contact on the record
Your own CRM stops holding a person who left two quarters ago.
- 1Re-resolve the ops owner on accounts whose contact was written more than a quarter ago.
- 2Assert the current person onto the record so the timeline keeps both.
oxygen crm assert
Who you can reach
Roles you can find at RevOps and sales ops leaders
Reachability is per channel: a role marked for mobile is one the phone waterfall usually resolves, not a guarantee for every record.
| Role | Seniority | Reachable by |
|---|---|---|
| VP of Revenue Operations | VP | Work emailLinkedIn |
| Head of Revenue Operations | Director | Work emailLinkedIn |
| Sales Operations Manager | Manager | Work email |
| Business Operations Lead | Manager | Work emailLinkedIn |
| Marketing Operations Manager | Manager | Work email |
| Chief Operating Officer | C-level | Work emailLinkedInMobile |
Filters you can search on
- Go-to-market tooling detected on the domain
- Analytics or BI tools in use
- Combined sales, marketing and success headcount
- Headcount band and funding stage
- Country and primary market
- Seniority: VP, Director, or Manager
- Title keywords across every ops variant
Detection sees tools that touch the public site and misses anything purely internal, which is most of a CRM. Read a positive result as strong evidence and a blank as no information. Title coverage also thins out under fifteen people in go-to-market, because the job exists there but nobody has been given the name yet.
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.

BuiltWith
Technology detected on the company domain, the outside view of what a revenue team actually runs.

People Data Labs
Person and company records for counting the revenue org and resolving who operates it.

Apollo
Ops titles from your own Apollo account, which is where most teams first tried to group this function by hand.
LinkedIn Scraper
Profile reads on a role that changes hands fast, so a message never assumes history the person does not have.

Blitz API
First attempt at the work email for an ops owner whose title you could not have predicted, plus the LinkedIn company read.
Run these on Oxygen's managed credits, or connect your own provider keys and pay the vendor directly — the same columns, the same runs, the same provenance either way. See every integration.
Limits
Where this stops
- A CRM lives behind a login, so detection infers it from forms, tracking scripts, and embedded widgets. Plenty of companies run one and show nothing at all from outside.
- Ops titles move fast. Someone who owned the stack two quarters ago may have been folded into a broader operations role, so check tenure before writing a personal opening.
FAQ
Questions people ask first
Why is RevOps hard to search for by title?
Does a company need a CRM for this to work?
What counts as the go-to-market team?
Can I reuse my own ICP definition here?
How do I keep the contact current?
What is free here and what draws credits?
Build your revops and sales ops leaders list
Start with a search, preview the cost before anything is spent, and keep the rows, sources, and runs in a workspace you own.