The 25-minute prospect research problem

Ask any sales leader where their team's time goes and you'll get the same shrug: "They're researching." Pull the actual numbers and the picture sharpens fast.

The average SDR spends 25 minutes on each prospect before they write a single line of outreach. Multiply that across a list of 200 leads a week and you've burned 83 hours — more than two full work weeks per rep, every month, just on prep.

That's the bill. Here's why it stays unpaid for so long.

Research isn't one task — it's six#

When an SDR "researches" a prospect, they're actually running through a chain:

1. Find the right person (LinkedIn Sales Nav, Apollo, ZoomInfo)
2. Confirm role, seniority, and decision power
3. Read recent posts, reactions, and shared content
4. Pull company news and funding signals
5. Identify a hook — something specific they'd care about
6. Synthesize all of it into a first line

Each step takes 3–5 minutes. The fast SDRs sometimes shave step 1, but they pay for it later when their messages land flat. The slow ones do every step every time, which is what gets you to 25.

The hidden multiplier: context decays#

Here's what makes this worse than it looks. The research an SDR did on Monday is stale by Wednesday. If your cadence sends a follow-up four days after the first touch, the LinkedIn post your hook referenced is buried; the news angle is yesterday's news.

The honest version of the math is closer to 35–40 minutes per active prospect when you account for re-research before each touchpoint in a 5-step cadence. Most teams just don't measure it.

Why the obvious fix doesn't work#

The cleanest answer is "hire researchers" — and we tried that for years. The problem isn't that researchers are expensive (they are). It's that the work doesn't compose.

A junior researcher can't reliably spot the angle that matters. A senior one is bored within a quarter. You end up with high churn on a role that needs context-sensitive judgement, which is exactly the wrong shape for a learning curve.

The shape of the fix#

Whatever tool you use, the criteria are the same:

• Reads the same sources a good SDR would. LinkedIn activity, recent posts, company news, funding rounds, role tenure. If it just pulls a job title from a database, it's not research, it's enrichment.
• Surfaces the hook, not the data. A wall of company facts isn't useful. The output that matters is "this person reposted a take on AI hiring two days ago — open with that."
• Re-researches on cadence. Touch 1 and Touch 4 should look at fresh signal, not the same snapshot.
• Fails loud. If there's no good hook, the system should say "no good hook" and let the SDR move on, not invent something generic.

What it costs to get wrong#

Three numbers we use internally to argue for fixing this:

• 3% — the average reply rate on cold outreach when research is generic.
• 12% — the average when research is specific and recent.
• £85K — the average fully-loaded cost of an SDR doing the manual version.

You can do that arithmetic. The interesting bit isn't the cost of bad research; it's the cost of spending the same amount on bad research and good research and ending up with a 4× difference in pipeline.

Where to start tomorrow#

If you're not ready to swap tools yet, try this for one week:

1. Have one rep track time-on-research, accurately, in 5-minute increments.
2. Tag every reply you get with whether the hook was specific or generic.
3. At the end of the week, compute reply rate by hook quality.

You won't need a second week.

We built OREE because the agency taught us this is the actual bottleneck — and that almost nobody is solving it well. The time numbers above aren't aspirational; they're what the product does in production for our pilot teams. If you want to see your own list run through it, start a free trial.