Phone vs Email vs LinkedIn: Running the Expected-Value Maths on Your First Touch

Nobody argues about channels once the numbers are on the whiteboard

Every phone-versus-email argument I have sat through was two people trading anecdotes. One rep booked three meetings off a LinkedIn DM last month, so LinkedIn works. Another rep has a manager who came up dialling, so the phone works. Neither of them had written a single number down.

The argument is boring because it is answerable. Not with somebody's benchmark report — with your own logged activity, an hour of arithmetic, and the honesty to include the time you spend on things that are not the touch itself.

I am going to walk through the maths using letters rather than numbers. That is deliberate. Every benchmark figure you have ever read was measured on somebody else's list, somebody else's ICP, somebody else's data provider and somebody else's caller ID reputation. If I hand you a connect rate, you will anchor on it and then argue with your own dialler when it disagrees. Pull your own inputs. The whole point of this exercise is that the answer is different for a rep selling SOC tooling to hospital systems than it is for a rep selling to plant managers in the Midlands, and a shared benchmark hides that.

The only metric that settles it: meetings per hour of rep time

Not reply rate. Not connect rate. Not "engagement". Those are components, not answers. A channel with a beautiful reply rate that consumes your entire morning to send twelve touches can easily lose to an ugly channel you can run at volume, and it can also win — you cannot tell by staring at the rate.

The unit is meetings booked per hour of your time, because your time is the constraint you cannot buy more of.

Write the equation down

For the phone, in one focused hour:

Meetings = D × c × m

Where D is dials you actually complete in that hour, c is the share of dials that turn into a live human conversation, and m is the share of those conversations that end in a booked meeting.

For email, over the same hour of your effort:

Meetings = E × r × p × b

Where E is emails you can research, write and send in the hour, r is reply rate, p is the share of replies that are positive rather than "not interested" or an out-of-office, and b is the share of positive replies that convert into a meeting on the calendar. Note that E is not the number of emails your sequencer sends — it is the number you can produce at the level of personalisation you are claiming. If you are running fully templated sends, E for the hour is enormous and r is small. If you are researching each account properly, E collapses and r climbs. Both are legitimate strategies. They are different equations.

For LinkedIn:

Meetings = C × a × d × q × b

Connection requests sent, acceptance rate, share of accepts you actually message, reply rate on the message, conversion of that reply to a meeting. Five multiplications, each one a leak. That is the first honest thing the maths tells you about LinkedIn as a pitching channel: the chain is long, and long chains multiply small numbers into very small numbers.

Now add the costs nobody logs

This is where most people cheat themselves. Three costs get left out constantly.

List and research time. If you spend the first ninety minutes of the day building the list you will call, that time belongs in the denominator. Split it across the channels it serves.

Infrastructure tax. Domains, warm-up, deliverability babysitting, the day a mailbox gets flagged, the recurring cost of somebody senior worrying about whether the main domain is at risk. That is real time. It sits on the email side of the ledger and almost nobody prices it in.

Recovery time. After a run of dials, most reps need a few minutes before they can do it again. After a run of emails, they don't. This is not a moral failing, it is a real capacity constraint, and if you plan an eight-hour dial day you will get something considerably less than eight hours of dialling. Measure what you actually do, not what the plan says.

Where to get your inputs without lying to yourself

Your dialler has D and c. Your sequencer has E and r. Your CRM has m and b, assuming your reps log conversations honestly, which they mostly don't — so spot-check against calendar invites rather than against activity records.

Two rules on measurement.

First, one good morning is not evidence. A single connect that happened to be a buyer already in-market will distort a week of data. Measure across a full month, and measure the same rep on the same segment. Comparing your best dialler's phone numbers to your worst writer's email numbers tells you about people, not channels.

Second, segment before you average. If your territory contains both mid-market operations buyers and enterprise security executives, the blended number is meaningless and will point you the wrong way for both. Run the equation per segment. This is the single highest-value thing in this whole post and it takes an afternoon.

What the equation tends to show

Here is my read, from selling inside AWS and Dell and from building and selling four businesses where I did the prospecting myself before anyone else would.

Phone wins when the list is finite and the buyer is operational

If you own a named list — the kind you can print on one page — meetings per hour is not even the right frame. Coverage per account is. You are not trying to find the cheapest touch; you are trying to get into a specific building. And on a finite list, the constraint flips: you cannot email your way to more attempts, because the fourth email into an unresponsive account does more harm than the first. The phone lets you make more attempts per account without burning it, because a missed call costs the buyer nothing and a voicemail is not clutter in the same way an unread email is.

The phone also wins hard with buyers whose job keeps them off email. A plant manager is not in an inbox at 6am. He is walking the floor, he has a mobile in his pocket, and he answers it because production calls him on it. That is a connect rate advantage no amount of email cleverness closes, and it is why the manufacturing cold call script is built around earning a specific, short block of time rather than around a value proposition — the whole exchange happens in the ninety seconds before he goes back to the line.

Same logic, different building, for shift-based technical buyers. A SOC lead is at a console with a queue in front of them. Their email is a firehose of alerts and vendor noise. A call at the right hour of the shift gets a real conversation, which is the premise of the cybersecurity cold call script — you are not competing with other emails, you are competing with the queue, and you have to be worth looking up from it.

Email wins when the list is bigger than your hands

When your addressable market runs into the thousands and you cannot possibly dial it, the multiplication that matters is not conversion, it is E. Small conversion times large volume beats large conversion times a number capped by how fast you can talk.

Email also wins with buyers who structurally do not answer phones — anyone with a gatekeeper who is good at their job, anyone at a company where the switchboard is a web form, anyone whose mobile number is genuinely not obtainable. You can be right about the phone in principle and still have c be effectively nil for that segment. When c is nil, everything downstream of it is nil, and no amount of belief in cold calling fixes multiplication by zero.

And email wins on latency in one specific way: it works while you sleep, in a timezone you are not awake for, on a Sunday night when a VP is clearing their inbox. That is not a conversion advantage, it is a coverage advantage, and it belongs in the model.

LinkedIn is a research and warm-path channel that occasionally converts

Five multiplications is a long chain, and the volume ceiling is set by a platform that will restrict you if you push it. As a pitching channel at scale, the arithmetic rarely wins.

Where it does win is as a discovery layer. You are not looking for a meeting, you are looking for a path: who moved into the account from a customer of yours, who used to work with the person you already know, who commented on the post about the migration project you can now reference by name in a call. That intelligence raises m on the phone and r on email. It is an input to other channels' conversion rates, and if you only credit LinkedIn with the meetings it books directly you will underrate it and switch it off.

The exception is the buyer who is genuinely native to the platform. Sales leaders live there. So do a lot of CROs, marketing executives and founders. For those people the DM is not a side door, it is a channel they check personally, unfiltered by an EA. A short DM that asks for a direction rather than a meeting does well:

"Working with a few teams on the same problem your ops lead posted about last week. Is that yours or does it sit with RevOps? Happy to just point you at what we've seen if it's not you."

No pitch, no calendar link, one question, easy to answer in four words. That is what a DM should be doing.

Latency is a cost the model usually ignores

A dial resolves in seconds. You know within a minute whether you have a conversation. An email resolves in days, if at all. A connection request might resolve in a week, and then the DM adds another few days.

If you are running a quarter and you are behind, latency is not a footnote — it is the whole thing. A channel that produces meetings three weeks from now cannot save a month that closes on Friday. This is the honest reason a lot of good managers push the phone in week ten of a quarter and it is not irrational, even if the meetings-per-hour maths slightly favours email in that segment. Speed to resolution has value that the simple equation does not price.

Capacity ceilings change the answer more than conversion rates do

Every channel has a hard ceiling. Dials per hour are capped by how fast humans talk and how long ring cycles take. Emails are capped by deliverability, not by your typing speed — you can send more, you just cannot send more that arrive. LinkedIn is capped by the platform, and the cap is not negotiable.

Once you have your per-channel meetings-per-hour figures, do a second calculation: how many hours can each channel absorb before it hits its ceiling? A channel that produces more meetings per hour but saturates in ninety minutes a day cannot fill a whole rep's calendar. That is why the winning answer is almost never one channel. It is an allocation.

Why the sequence beats any single channel

The reason to run all three is not diversification and it is not "multi-threading" as a buzzword. It is that the channels change each other's variables.

A voicemail raises the open rate on the email you send in the next four minutes, because the name is now familiar. An email sent before you dial gives you an opener that is not cold: "I sent you a note this morning about the second-shift changeover, that's why I'm calling." A LinkedIn profile view before a call means your name is not a stranger's name when it appears on their screen.

The practical version I would run on a named account: dial first, and if no answer, leave a voicemail that names one specific thing and says an email is coming. Send that email within the next few minutes, subject line referencing the voicemail. Wait, dial again at a different hour of the day — a different hour, not a different day, because the biggest driver of c on most lists is time of day and reps almost never test it properly. Then LinkedIn, and make it a question about routing rather than a pitch. Then let it rest and come back.

That sequence is not more work than picking a favourite channel and hammering it. It is roughly the same number of touches, arranged so each touch makes the next one land better.

Segment-by-segment exceptions worth writing on the wall

A plant manager is not on LinkedIn at 6am, and probably not at 6pm either. Do not build a manufacturing motion around social selling.

A CRO reads DMs personally and might never see an email that went to an address a data provider guessed. But they also get pitched relentlessly, so the bar on the message is brutal — which is why the SaaS cold call script for CROs and RevOps leaders leads with a specific operational problem rather than an outcome claim.

A VP of Sales whose own team cold calls for a living will respect a good call and hold you in contempt for a bad one. There is no neutral outcome. That segment has the widest spread between a rep who has practised and a rep who hasn't, which is exactly the ground the cold call script for VPs of Sales and SDR managers covers.

A security leader in the middle of an incident will not answer anything. The channel question is secondary to the timing question in that segment.

The channel changes the arithmetic. It does not change the opener

Here is the thing that keeps the channel argument alive long past its usefulness: people think switching channels lets them skip the hard part. It doesn't.

Whatever channel you pick, the first ten seconds have to do the same three jobs. Say who you are without waffle. Name a specific problem the person on the other end recognises as theirs, in their language, not yours. Ask for a small, defined amount of time rather than a vague conversation.

A cold email that fails those three jobs fails for the same reason the call did. A DM that opens with "I'd love to learn about your priorities for next year" gets deleted for the same reason the voicemail did. The medium changes the length and the etiquette. It does not change the burden of being immediately relevant to someone who did not ask to hear from you.

So do the maths, allocate your hours accordingly, and then go and work on the twenty words at the front. That is where the variance actually lives.

What I'd do next

If I were picking this up on a Monday, I would spend the first hour pulling my own inputs per segment, the second hour writing the three equations out properly, and the rest of the week practising the opener until it stopped sounding like a script — because the moment the maths tells you to dial more, the quality of the first ten seconds becomes the only variable that matters. That is what we built DrillCall for: rehearsing openers and objection handling against a realistic buyer, out loud, before you spend those hours on live accounts. Run the numbers first, then go and earn the connects you've now decided are worth having.