Four metrics predict outbound pipeline: speed to lead, connect rate, conversation-to-meeting rate, and cost per booked meeting. Dials and sends only measure activity. Calculate each of the four the same way every time. Use the median for time-based metrics, and compare yourself with your own trend instead of borrowed benchmarks.
Open an outbound dashboard and you'll see dials, emails sent, and touchpoints logged, all trending up and to the right. It looks like progress. Usually it isn't, because activity is easy to count and easy to inflate.
Activity metrics only measure effort
An activity metric counts something your team does: dials placed, emails sent, LinkedIn touchpoints logged, sequences started. They're popular because you can always pull them, they always look good, and they make an easy leaderboard. None of them is an outcome, though. They tell you how hard people are working without saying whether the work produces revenue.
They also push people the wrong way. A rep measured on dials will make dials. Some of those are short, low-effort calls to bad numbers that inflate the count without touching pipeline. Counts hide the funnel, too. A thousand dials that produce two meetings look the same on an activity dashboard as a thousand that produce forty. And when you celebrate volume you get volume, even when what's holding your pipeline back is quality or timing.
Keep tracking activity, since you need it as the denominator in the ratios below. Just treat it as an input and manage against outcomes.
The four metrics that predict pipeline
Tracked together, four outcome metrics tell you almost everything about the health of an outbound motion. Each one covers a different stage of the funnel. As a set they show whether pipeline is growing and, when it stalls, where it broke.
| Metric | What it measures | Formula | Why it matters |
|---|---|---|---|
| Speed to lead | Time from intent signal to first real contact | median(first contact time − intent signal time) | Response time moves conversion more than anything else in outbound, and intent fades by the minute |
| Connect rate | Share of outreach attempts that reach a live human | live conversations ÷ contact attempts | Isolates data quality, timing, and channel fit before any pitch happens |
| Conversation-to-meeting rate | Share of live conversations that turn into a booked meeting | meetings booked ÷ live conversations | Isolates messaging, qualification, and rep skill from top-of-funnel volume |
| Cost per booked meeting | Fully loaded spend required to produce one qualified meeting | total channel cost ÷ meetings booked | The one metric that ties the whole motion back to efficiency and lets you compare channels |
All four are ratios or durations, so adding volume doesn't move them on its own. If you double your dials and your connect rate holds, your data and timing are stable. If the connect rate falls as you scale, you've found your constraint. A dial count would never have shown you that.
Calculating each one
These numbers are only useful if you calculate them the same way every time. Pick a definition, write it down, and don't change it mid-quarter.
Speed to lead
Measure the time from the intent signal (a form fill, a pricing-page visit, a reply) to your first real contact attempt. Then take the median across all leads in the period. One lead you reached three days late will drag an average into meaninglessness. The median tells you what a typical lead experienced. We went through the research behind this number in our post on the first 60 seconds.
Connect rate
Divide live conversations by contact attempts over the same window. Be strict about what counts as live: a human answered and you exchanged more than a hello. Voicemails, gatekeeper deflections, and wrong numbers count only as attempts. Since nobody hears your pitch until someone picks up, a low connect rate almost always points to your list, your call times, or your channel.
Conversation-to-meeting rate
Divide meetings booked by live conversations. Messaging and qualification move this number. It starts from conversations instead of attempts, so it separates two questions: can you reach people, and do the people you reach agree to meet? If it's healthy and pipeline is still thin, look upstream at volume or connect rate. Leave the talk track alone for now.
Cost per booked meeting
Divide the fully loaded cost of the channel over a period by the qualified meetings it produced in that period. Fully loaded means the subscription plus everything else the channel costs. That includes tooling, telephony or sending costs, data, and the loaded cost of any human time. We wrote about the economics at volume in the real cost of outbound calling at scale.
A worked example
Some made-up numbers show the arithmetic. Suppose you make 1,000 dials in a week and reach 180 live people, an 18% connect rate. If 27 of those conversations turn into booked meetings, your conversation-to-meeting rate is 15%. If the channel cost $5,400 fully loaded that week, you paid $200 per booked meeting. We invented these figures to illustrate the formulas. Don't treat them as measured results or as benchmarks.
The example also shows where your effort pays off. Moving the connect rate from 18% to 22% adds forty conversations before you touch messaging at all. Measure each stage on its own and put your next hour of work into whichever metric is furthest from healthy.
Speed to lead belongs at the top
Speed to lead gets extra weight because the effect is so large. The studies agree with each other and measure the lift in multiples.
Calling within the first minute has been tied to a 391% conversion lift. Companies that respond first win about 78% of deals. Prospects contacted within the first hour are roughly seven times more likely to qualify. Yet Drift found the average B2B first response time sits around 42 hours. With that much upside and that big a gap, we'd put speed to lead at the top of your dashboard.
Benchmark against your own trend
You'll see benchmark numbers thrown around constantly. Most of them are worth ignoring. A connect rate from someone else's industry, list quality, and calling hours tells you nothing reliable about yours. Your own trend line is the benchmark to watch.
Start with a baseline by calculating all four metrics over a recent, stable period and writing the numbers down. After that, compare yourself with yourself, week over week and cohort over cohort. Your data can tell you whether speed to lead dropped after you automated the first touchpoint. It can also tell you whether connect rate held as you scaled, and whether cost per meeting fell as the motion matured.
Segment before you compare. Warm inbound and cold outbound behave nothing alike, so a blended connect rate across both is noise. Split by source, channel, and list, and compare like with like. A cohort view groups leads by the week they came in, so one good month can't hide a trend that's getting worse underneath.
Last, read the four together. If your connect rate is falling while conversation-to-meeting holds steady, the list and timing need work and the script is fine. Plenty of conversations with few meetings points at messaging and qualification. If everything else looks fine while cost per meeting keeps climbing, the funnel is healthy but each meeting is costing you more.
Know your own numbers cold. Find the one that's the current constraint and spend your effort there. Judge automation the same way, ours included. An AI SDR only earns its keep if you can measure the connect rate, speed to lead, and cost per meeting it delivers against your own baseline.
Measure what moves pipeline
RevDesk places an AI call within seconds of an intent signal, so speed to lead stops being the metric holding your pipeline back. Book a 30-minute walkthrough.
Book a demo
