Find post-sale owners
Find customer success leaders by book size and stack
A customer success function appears the quarter after renewals start mattering. Before that, support answers tickets and the founder saves the shaky accounts personally.
Post-sale org shape is the qualifier almost nobody filters on. A company with twelve success managers and a large book has a ratio problem your product either fixes or does not. A company with two has a hiring problem instead, and that is a different message from a different angle.
Both numbers are readable from outside. Count everyone holding success, onboarding, and account management titles, store the count on the account, and put your floor where the product starts to matter. The contact chain then runs only against rows that cleared it.
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.
Book size as the filter
find saas companies with more than 8 people in customer success and get the leader
The count lives on the account, so you can raise the floor and re-run the filter without paying for the people work a second time.
Success against support
split these accounts by whether they have a success function or only a support team
They are different budgets and different buyers, and the split is visible from the titles long before anyone answers your email.
The first post-sale hire
which companies just added their first customer success title
A first hire in a function means the process is being invented right now, which is the only moment a new tool gets adopted without a fight.
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.
Ratio-qualified success list
Accounts whose post-sale team is big enough to feel the problem you solve.
- 1Count success, onboarding, and account management titles onto every account row.
- 2Cut below your floor, resolve the leader, and enroll from what remains.
oxygen people search runSeparate success from support
Two lists that never share an opening line, because they never share a budget.
- 1Promote the post-sale shape onto each company record: a success function, a support team, or both.
- 2Tag the records by that shape, then enroll one cadence per tag out of the same table.
oxygen crm tagEvery answer in one place
Replies across channels arrive together and land on the company record as history.
- 1Enroll the leader and let answers on any channel collect in a single inbox.
- 2Log the outcome against the company record so the next person sees what happened.
oxygen inbox list
Who you can reach
Roles you can find at customer success 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 Customer Success | VP | Work emailLinkedIn |
| Head of Customer Success | Director | Work emailLinkedIn |
| Director of Account Management | Director | Work emailLinkedIn |
| Customer Success Manager | Manager | Work email |
| Head of Support | Director | Work emailLinkedIn |
| Chief Customer Officer | C-level | Work emailLinkedInMobile |
Filters you can search on
- People holding customer success titles
- Support headcount counted separately
- Post-sale staff against total headcount
- Headcount band and funding stage
- Industry and contract model
- Country, region, or metro area
- Seniority: C-level, VP, or Director
Titles in this function drift more than in any other. Account management, customer success, and support cover overlapping work and companies relabel them constantly. Read the count across all three rather than trusting one string, and expect a founder to hold the job at anything under thirty people.
Data sources
What the data actually comes from
Every value lands with its provider and cost recorded on the cell.

People Data Labs
Person and company records, which is what makes counting a post-sale team possible from outside.

Apollo
Post-sale titles from your own Apollo account, for teams that tracked the function there before moving.
LinkedIn Scraper
Reads the profile text, which is what separates a success manager from a support lead when the titles overlap.

Blitz API
First attempt at the post-sale owner's work email, and the LinkedIn company read the headcount is counted from.
LeadMagic
The later lane, run only where the post-sale owner resolved but no usable address came back with them.
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
- Counting post-sale staff depends on people labeling themselves consistently, and this is the function where they least do. Treat the count as a band rather than a precise number.
- No success titles does not mean no renewals. Plenty of companies run them through sales, which is a different pitch rather than a reason to drop the account.
FAQ
Questions people ask first
Why count the team instead of filtering on ARR?
How do I tell success apart from support?
Why target the first post-sale hire?
Do these titles change often?
Where do replies end up?
Can I run this on my existing customers too?
Build your customer success 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.