The situation
The database looked healthy. Seven hundred contacts, growing, plenty of activity.
The question nobody could answer was which of them were worth a conversation. “More leads” was the plan. Nobody had checked whether the existing ones were any good.
What RevOps XL did
1. Six personas, drawn from the deals that closed
Not a workshop. The personas came from reading what had actually been bought, by whom, and what they had in common - then classifying every contact against that, one at a time, with a written rationale for each.
Each persona got a success-likelihood score, an entry motion, and the specific thing that stalls it. One persona’s deals always stall on commercial structure. Another needs the CEO in the room on call one or the board gates it later. Knowing that turns each persona into a play sales can run.
2. The number that changed the conversation
392 of 708 - 55.4 per cent - landed in “needs qualification,” missing a title or a company, with nothing that pointed to a use case. They weren’t bad leads so much as unknowable ones.
Twenty were disqualified outright: spam, vendor pitches, records with neither a name nor a company.
Which left roughly three hundred real, classifiable people. On success likelihood: 36 scored 5/5 and 94 scored 4/5. So about a hundred and thirty contacts were worth active effort - out of seven hundred.
The team didn’t have a lead-generation problem. It had a hundred and thirty good leads it wasn’t working, hidden behind five hundred and seventy it couldn’t see past.
3. Sequences per persona, not per campaign
Each persona got its own sequence, built around the thing that motivates that buyer and the objection that stalls them.
The largest persona was also the fastest to close. It was not the one the team had been prioritising.
4. Enrichment as triage, not decoration
The 55 per cent weren’t deleted. They were routed - enrich what can be enriched, and the rest stop being counted as pipeline.
A database of seven hundred where three hundred are unqualifiable isn’t a database of seven hundred. Calling it one is how a team ends up believing it has more coverage than it has.
Where it landed
The classification went back into the CRM as properties - persona, score, rationale, recommended sequence - so it drives routing and reporting rather than sitting in a spreadsheet.
That’s the difference between a segmentation exercise and a segmentation you can route on - the second one changes what the team does on Monday.
What we’d tell you before you start
Every team we’ve done this for expected the answer to be “here are your best segments.” The answer is almost always “most of your list isn’t a list.”
That’s the better finding - segments you can act on this week, and a number you can stop lying to yourself about.
