What sixteen interviews found
Across 16 interviews with marketing ops, sales ops, and RevOps leaders at B2B SaaS companies, routing infrastructure ranges from fully manual inbox checks to native CRM automation with domain-based deduping, largely tracking company size and maturity. The most consistent pain points are duplicate records and stale data (raised in some form by nearly every respondent with meaningful volume), thin or absent context on qualified leads when reps open them, unmatched leads sitting in queues for a day or more with manual triage, and qualification definitions that predate the current owner and are rarely revisited even as disagreement between marketing and sales persists. Where formal alignment or a rebuild has happened, respondents report the friction is markedly lower, but most organizations describe routing and hygiene as something one person maintains reactively rather than a governed, monitored process.
Five findings
Duplicate and stale record cleanup is almost universally manual and owned by a single person, even at companies with otherwise automated routing; this is the most frequently raised and least systematically solved pain point across interviews.
Unmatched leads consistently fall into catch-all queues with day-plus turnaround; teams that check these queues daily report tighter outcomes than those checking weekly.
Thin lead context at handoff was directly linked to wasted rep effort (re-contacting people already engaged); richer context at the point of qualification appears to reduce this friction where it exists.
Qualification definitions that are jointly negotiated and periodically revisited (as in cases of formal rebuilds or alignment projects) correspond with reports of less friction between marketing and sales than definitions that are inherited or undocumented.
Most organizations track routing speed but not record quality, and even speed metrics are often reviewed without follow-up action, suggesting measurement alone is not translating into process change.
Issue frequency across the set
Every issue raised by more than one respondent, counted once per person. Bars are out of 16.
- Duplicate records accumulating with manual, inconsistent cleanup10
- Unmatched or unassigned leads sitting in a manual queue for a day or more8
- Stale records with no owner or scheduled cleanup6
- Qualification definition inherited, undocumented, or not revisited in years6
- Thin or missing context on qualified leads when a rep opens the record5
- Record quality metrics not tracked at all, only speed metrics5
- Required fields not enforced or easily entered as free text/garbage data4
- Routing logic ownership fragmented across teams causing stalls when rules conflict2
Five themes, with evidence
Unmatched leads default to manual, delay-prone queues
Nearly every respondent with an automated routing layer described a catch-all or unassigned queue for leads that do not cleanly match segment, territory, or size rules. The volume in that queue varies from a handful a week to twenty or thirty, and turnaround ranges from same-day to a full day or two, with weekend or Friday submissions cited repeatedly as the worst case. In several organizations this queue is cleared by one specific person as a manual, recurring task rather than by any automated fallback.
- One sales ops owner described manually clearing an unassigned queue herself every morning before standup.
- An ops leader at a company with segment and territory rules that sometimes both fire said conflicting leads simply stall until someone notices in Slack.
- A RevOps contact estimated twenty to thirty leads a week landing in a general queue reviewed only once a week.
Duplicate and stale records are a near-universal, largely manual burden
Deduplication quality varies widely, from native automatic matching on email and domain that rarely needs intervention, to free-text company name fields producing thousands of uncounted duplicates. Cleanup cadence ranges from none at all, to reactive whenever someone notices, to scheduled monthly or quarterly passes, but in most cases the work falls to one person or team doing manual merges rather than a systemic fix. Stale record cleanup is even less consistently owned than duplicate cleanup, with several respondents saying it simply accumulates with no assigned owner.
- One respondent estimated duplicate records in the thousands and said cleanup was where the real friction sits for their role.
- A sales ops lead described losing a full Thursday afternoon every couple of weeks to fuzzy-matching and manually merging company name variants.
- Multiple respondents said stale record cleanup has no schedule and no clear owner, distinct from duplicate cleanup which at least sometimes runs on a cadence.
Reps often work qualified leads with minimal context
Several respondents described records that arrive to reps with little more than a name, email, and the page or form the person converted on, with no narrative about why the lead was flagged or what they are interested in. This thin handoff was linked directly by one respondent to reps repeatedly recalling the same problem: contacting people who were already spoken to months earlier because context was not visible or retained.
- One respondent said a rep opening a new record sees basically the form fill: name, email, and whatever page they were on.
- Another noted leads arrive thin at the lead stage even though opportunity-stage fields are enforced.
- A marketing ops lead named handoff context as the single most overdue fix, citing reps calling people already talked to months back.
Qualification definitions are frequently inherited, undocumented, or stale
A recurring pattern is that the definition of a qualified lead predates the current process owner, was set informally, or has not been revisited in one to two years even as the underlying business changed. This produces ongoing but low-intensity friction: reps grumbling in Slack, occasional kickbacks, or reps simply overriding marketing's tiering by re-sorting their own queue by company size. In the small number of cases where teams did a deliberate joint rebuild or alignment project, respondents reported the friction as mostly resolved.
- One respondent said the qualification definition predates them and is essentially inherited and untouched, with reps grumbling but nothing formally raised.
- A sales ops contact said reps mostly ignore the three-year-old qualification tier and instead sort their own queue by company size.
- A contact whose team ran a formal rebuild eighteen months earlier said reps rarely push back now, calling it a joint process from that rebuild.
Measurement is common but mostly passive
Time-to-first-touch or time-to-assignment is the metric most commonly tracked, usually by the same person who owns routing, reviewed monthly (sometimes weekly). However, most respondents said the number is watched rather than acted on, with few examples of it triggering a fix, and record-quality metrics like duplicate rate or percent-complete records are rarely tracked at all. A few noted the report goes to an exec or VP but gets little scrutiny or follow-up.
- One respondent said the report is mostly just for personal tracking and nobody above has asked to see it.
- Another described a weekly speed-to-first-touch number that goes to a VP and is mostly noted with not much action.
- One respondent's monthly time-to-first-touch number averages around two days despite acknowledged stalls, thin records, and regular kickbacks.
In their words
Thousands, easily. Honestly haven't counted in a while, it's a lot.
Honestly, the handoff context. Reps calling people already talked to months back, wastes everyone's time.
No picklist enforcement on company name, that's basically the whole problem.
Reps mostly ignore it. They sort their own queue by company size.
Only real worry is being the single point of failure.
CRO's asking for a recommendation now. That's the trigger, basically.
How this study was run
Based on 16 in-depth interviews on lead routing, CRM data quality, and handoff between marketing and sales at mid-market B2B SaaS companies.
Each conversation was a one-on-one interview run by Birdsong. Counts are distinct respondents; an issue is counted once per person however often they returned to it. Respondent names, emails and companies are not published.
- Published
- Interviews
- 16
- Sponsored by
- Meridian Ops