Guide
How to build a sales cadence when you're the only one running it
Most cadence advice is written for teams running automated sequences through a dedicated tool. As a solo seller, you don't need the tool. You need a small number of touches you actually run, every time, without having to remember to.
TL;DR
A sales cadence is just a defined pattern of follow-up touches after first contact, timing and channel, repeated consistently instead of reinvented per lead. Teams with sales engagement platforms automate this. As a solo seller, you don't have the volume to justify that tooling, and you don't need to: a simple, fixed cadence (for example, call, then email at day 3, then a shorter check-in at day 7, then a "should I close this file" message at day 14) run consistently by hand outperforms a more sophisticated cadence that only gets followed some of the time. The part that actually needs infrastructure isn't the sequence logic, it's knowing when each next touch is due without holding it in your head.
Why cadence advice built for teams doesn't transfer directly
Most published cadence frameworks (8-touch, 12-touch sequences across email, call, and social) are designed for outbound teams running volume through a sequencing tool, where the marginal cost of an extra touch is close to zero because it's automated. None of that math applies to a solo seller doing every touch personally. Trying to run a 10-touch automated-style cadence by hand isn't a lighter version of the same thing, it's a different, much heavier task, and it tends to collapse within a couple of weeks under real workload.
The part of cadence discipline that's actually worth keeping isn't the touch count. It's the core idea: a defined, repeatable pattern beats improvising follow-up timing lead by lead, because improvising means the leads you're least excited about (often the ones that need the most nudging) are the ones that quietly stop getting followed up on.
A cadence built to survive being run by one person
Keep it to three or four touches, not eight or twelve. Something like: same-day or next-day first follow-up after the initial call, a check-in around day 3 if there's been no response, a shorter, lower-effort nudge around day 7, and a final "still worth pursuing, or should I close this out" message around day 14. The exact intervals matter less than having a fixed, small number you don't have to redecide for every lead.
Vary the channel, not just the message. A call, then an email, then a shorter message, reads as more natural persistence than the same channel four times in a row, and it costs nothing extra to plan since you're already deciding this once, not per lead.
The part that actually needs a system isn't the sequence, it's the due date. A cadence only works if you know when touch three is due without checking a spreadsheet or relying on memory. This is the specific gap the Bell's task system and AIDA-stage pipeline are built to close, log a call through Smart Input, set the next touch as a task with a due date in the same sentence, and it shows up when it's due instead of depending on you remembering to check.
What this doesn't solve
A cadence doesn't fix a weak first conversation, and it isn't a substitute for genuine relevance to the prospect. Following up four times on a lead that was never a real fit just produces four unwanted messages instead of one. Cadence discipline matters most after you've already qualified that the conversation is worth having again.
Who this is for
Founders and small teams running their own follow-up without a sales engagement platform, who need a cadence simple enough to actually run by hand, consistently, rather than a more sophisticated one that only gets followed sometimes.
More guides
- How to qualify a lead when there's no sales ops team to build the process for you
BANT, MEDDIC, and every other qualification framework were written for teams with a sales ops function to formalize them. You don't need the formalization to use the logic. You need a short, repeatable habit you actually do on every call.
- How to run a real B2B pipeline before you can justify a RevOps hire
RevOps exists to keep the revenue engine, pipeline data, forecasting, process discipline, consistent as a company scales. That's a real function. It's also not a function you need a dedicated hire for on day one, and treating it as one before you're ready just delays getting the underlying discipline in place.
- How to keep a CRM clean when there's no one whose job it is to keep it clean
Data hygiene at a bigger company is a role. At a founder-led company, it has to be a property of the system itself, because there's no one to assign it to.
- You've decided to move off the spreadsheet. Here's how to actually do it.
Not whether to move, that's a different question. This is the practical part: getting your existing pipeline out of a spreadsheet and into a CRM without losing anything or stalling out for a week.
Set the next touch once. Let it show up when it's due.
Tasks and follow-ups tied to the pipeline, not a separate list you have to remember to check.
Start Your Free Trial