Skip to content

Measurement

Time to first dial by rep: when “the leads are bad” is one rep

The short answer

Timestamp every stage change in the CRM — new, contacted, app out, docs in, submitted, funded — and two numbers fall out that most brokerage owners have never seen: each rep’s time from lead in to first dial, and cost per funded deal by lead source. Read over a month, six months and a year, they show where the pipeline actually stalls. If the time from new to contacted is an hour, that is the bottleneck, hands down.

On this page
  1. Stamp every stage
  2. Number one: time to first dial, by rep
  3. Number two: cost per funded deal, by source
  4. Setting it up
  5. Questions brokers ask

A floor-wide median time to first dial tells you there is a problem. It does not tell you whose. The per-rep split does, and so does the per-source cost per funded deal — and both come from the same thing: a timestamp every time a lead changes stage.

Each rep’s time to first dial, at 4:58. Chapters and transcript
Whiteboard. A pipeline of stages, each with a clock and a time: new 10:02, contacted 10:04, app out 10:31, docs in 1:15, submitted 2:40, funded next day, renewal date +6 months. Below, two panels. Time to first dial, by rep (median, lead-in to first call): rep A 3 min, rep B 11 min, rep C 14 hrs — “rep C is why ‘the leads are bad’”. Cost per funded deal, by source (spend on that tag ÷ deals funded off it): vendor A $1,140, aged sheet $870, own ads $1,400, vendor B 0 funded from 50 — “vendor B gets cut”. Marked: example numbers.
The board’s example numbers. Rep C is why “the leads are bad”, and vendor B gets cut.

Stamp every stage

Stage changeWhat the gap measures
New → contactedTime to first dial: the rep, the routing and the alerts
Contacted → app outHow fast a conversation becomes an application
App out → docs inThe bank statement step, usually the biggest leak
Docs in → submittedPackaging time on your side
Submitted → fundedThe funder, and how complete the file was
Funded → renewal dateWhen the next deal is due, computed rather than remembered

With every stage stamped, you can read the averages across a month, six months and a year, and fix the bottleneck the data points to rather than the one somebody complains about loudest. Alex’s view of which one it usually is: if your time to contacted is an hour, that is the biggest bottleneck, hands down. But you cannot know that without the timestamps.

Number one: time to first dial, by rep

The median from lead in to first call, per rep. In the board’s example, rep A is at three minutes, rep B at eleven and rep C at fourteen hours. The floor median hides that entirely, and so does every complaint about lead quality. Rep C is why the leads are bad — the same fourteen hours that turned up in one client’s export in speed to lead, except this time with a name on it.

Use the median rather than the average, for the reason the weekly metrics give: a handful of leads dialled days late drags an average somewhere no lead ever was. And pair it with the five-minute reassignment rule, so a slow rep costs you a coaching conversation rather than the lead.

Number two: cost per funded deal, by source

Spend on a source tag divided by the deals funded off it. The example on the board has vendor A at $1,140, an aged sheet at $870, the shop’s own ads at $1,400, and vendor B at nothing funded from fifty leads. Vendor B gets cut; the others get compared on what they produce, and the order goes to whichever sources deliver merchants that fund. It only works if every lead carries its source permanently, which has to start before the leads arrive.

Setting it up

In GoHighLevel: a “first contacted at” field set by the first outbound call or text, then a report by user from lead created to first contacted. The other stages work the same way — a date field written when the opportunity moves — and any CRM with workflow triggers on stage changes can do it. The CRM setup guide has the rest of the instrumentation.

Questions brokers ask

How do I measure each rep’s speed to lead?

Stamp the time the lead is created and the time of the first outbound call or text, then report the median gap per rep. In GoHighLevel, a “first contacted at” field and a report by user does it.

Which CRM stages should an MCA brokerage timestamp?

Every stage change: new, contacted, application out, documents in, submitted and funded, plus a computed renewal date. The gaps between them show where deals stall.

How do I know if my leads are bad or my reps are slow?

Split time to first dial by rep and cost per funded deal by source. If one rep is at hours while the others are at minutes, the leads are not the problem.

How do I calculate cost per funded deal by lead source?

Take the spend on each source tag and divide by the deals funded from leads carrying that tag. A source that funds nothing from fifty leads gets cut, whatever its cost per lead.

What is the biggest bottleneck in most MCA pipelines?

Time from new to contacted. If that gap is an hour, it is the bottleneck before anything later in the pipeline matters.

Reference

Watch: six things the top MCA brokerages have in their CRM

Time to first dial by rep is number four, with the stage timeline on the board.

AM

Alex Makowski

Founder, Infinite Bookings

Runs the lead generation operation behind Infinite Bookings — paid traffic, the funding application, and the delivery pipeline that puts records into brokers’ CRMs.

Reachable directly at alex@infinitebookings.com or 732-609-7182.

Get started

We will tell you straight up if we cannot help you. No commission deals, no free trials, no chasing you for three weeks.

Book a 15 min callRather not book? Text my number instead
Exclusive MCA leads
Book a 15 min call