Sales cadence

A sales cadence is the agreed order and timing of outreach to a prospect. It tells an SDR what to do next, gives each touch a purpose, and tells the team when to stop.

Without one, follow-up usually depends on memory and mood. An SDR sends an email on Monday, forgets the call on Wednesday, then notices the account three weeks later while cleaning up a task list. That isn't a strategy. It's admin debt.

What a sales cadence actually controls

A cadence can include email, calls, voicemail, LinkedIn, personalized video, or direct mail. The channels matter less than the reason for using them.

A useful cadence answers four things:

• Who is this for?
• Why are we contacting them now?
• What happens next, and when?
• What response or event removes them from the cadence?

Take a 200 to 1,000-person SaaS company that has just hired a VP of Security. A security vendor might send a note on day one about the first 90 days in the role, call on day two, send a short LinkedIn connection request on day four, then follow up with a specific observation about SOC 2 reporting on day six. A second call and a close-the-loop email might follow.

The sequence isn't useful because it has six touches. It's useful because the trigger gives the outreach a reason to exist.

That distinction gets lost all the time. Teams build a sequence first, then hunt around for a message to put in it. Start with the account and the event. The copy comes after.

Building a sales cadence around a real trigger

Your ideal customer profile tells you which companies are worth pursuing. It doesn't tell you why one of them might take a meeting this month.

Look for an event that changes the account's situation. A funding round, acquisition, new executive, audit finding, processor change, expansion into a new country, or sudden hiring spike can all work. The event needs to connect to a problem your buyer owns.

For example, imagine a payroll software company selling to businesses with 50 to 500 employees. A generic message about “simplifying payroll” won't give a finance leader much reason to reply. A better target is a company that has just acquired another business and now has people working across two payroll systems. The first email can ask how they're handling reconciliation after the acquisition. The call can test whether the problem is creating month-end work. A later touch can share how a similar company consolidated the process.

That is much stronger than sending six versions of “just following up.”

The contact matters, too. A new VP of Finance may care about reconciliation delays and reporting. An IT director may care about unfinished access reviews after an audit. A COO may care about the operational cost of keeping two systems running. Same account, different problem.

A practical build process

Pick one segment and one trigger before writing anything. Don't start with “all B2B companies” or “people who might need our product.” A small, specific segment gives you a chance to see patterns.

Then assign a job to each touch. The first email should establish relevance. The first call might check whether the issue exists. A later email could add a useful comparison or customer example. An executive message might make sense only for a high-value account where senior involvement is credible.

Six to eight touches across two or three channels is a reasonable starting point for cold outbound. Space them over roughly 10 to 15 business days, then adjust based on the buying motion. A simple sale with a clear trigger may need less. Enterprise software involving security, finance, and procurement may need more time.

Write the exit rules before the cadence goes live. A prospect who replies “send me details” shouldn't keep receiving automated cold emails. They need a human reply. Someone who says the issue belongs to another department should be routed or removed. A meeting booked, an opt-out, a disqualified account, or an active opportunity should all stop the sequence.

This sounds basic. It gets missed constantly.

One opinion, plainly: most teams don't have a follow-up problem. They have a targeting and judgment problem. Adding more steps to a weak cadence just helps them send irrelevant messages more consistently.

Sales cadence examples by situation

For a 100-person ecommerce company announcing international expansion, a short cadence could run like this in practice. On day one, send an email about cross-border tax and reporting exposure. On day three, call and leave a short voicemail tied to the expansion. On day five, send one LinkedIn message with a specific observation about the countries involved. On day seven, share a brief example from a retailer that handled the same change. On day ten, make a final call and close the loop.

The messages don't need to be long. They do need to move the conversation forward.

A data infrastructure company selling to 1,000-person businesses may need a longer cadence. The buying group could include engineering, security, finance, and procurement. In that case, touches might run over 30 to 45 days, with account research, calls, useful technical material, and carefully timed outreach to another stakeholder. The point isn't to keep nudging until somebody gives in. It's to stay relevant while the account works through a real project.

Inbound needs a different pace. Someone who downloads a migration guide has shown interest, but not necessarily intent to buy. A rep might call the same day, send a short question about the prospect's current setup, and follow up with an implementation note. That follow-up should be faster than cold outbound because the prospect initiated the interaction.

Don't copy a published cadence just because it has 12 steps or a neat day-by-day format. Those examples can give you a starting shape. They can't tell you whether your audience responds to calls, whether your trigger is credible, or whether the people entering the cadence are even qualified.

What to measure, and what to ignore

Activity counts are easy to report and easy to misuse. A rep can complete 80 calls and create no useful pipeline. More touches don't fix that.

Track positive reply rate, meetings held, qualified opportunity rate, and revenue by segment and trigger. Break the numbers down by cadence step when you have enough volume. If the first email gets replies but almost nobody attends the meeting, the problem may be qualification or expectation-setting. If nobody responds until the second call, the call timing or message may be doing the work.

Be careful with open rates. Privacy features and email security tools make them noisy. They can be a directional signal, but they shouldn't decide whether a cadence stays in place.

Test one meaningful change at a time. Compare a funding trigger with a hiring trigger for the same segment. Or compare a problem-led email with a customer example. Changing the subject line, sender, offer, call script, and timing together gives you a new cadence, not a useful test.

Keep the workflow short enough that reps will actually use it. A five-step cadence completed well beats a 14-step sequence that ends in sloppy personalization and overdue tasks.

When the cadence should stop

Silence isn't permission to contact someone forever. Every cadence needs an end date and a next path.

A 300-person fintech company might say, “Our compliance project starts after the next audit.” Remove it from outbound. Put it into a light nurture path and set a reminder for when the audit approaches. Contact them sooner only if something changes, such as a new compliance leader, a market launch, or a public incident that makes the problem more urgent.

The same applies to poor fit. If the company is too small, uses a different system, or has no plausible need, stop. Don't keep it in the sequence because the CRM still has untouched tasks.

A good cadence makes the next useful action obvious. It also makes stopping easy.