Short answer
A strong sales follow-up cadence changes the reason for each touch. The first follow-up should confirm the next step, the second should add useful context, and later touches should either move the deal forward or close the loop.
Use templates only after you know the stage. Start with sales follow-up email templates, then use sales call follow-up email templates, post-demo follow-up templates, or pricing follow-up templates for the specific moment.
Use thread context and approval
A cadence only works when each touch reflects what the buyer already said. Anchor the draft on one real detail from the conversation: a metric they shared, a stakeholder they named, or an objection they raised.
Offer a concrete next step like [Thursday at 11] rather than asking when they're free. dreamif.ai drafts from the Gmail thread and any notes you keep against the contact. It doesn't push to your CRM or advance a sequence on its own.
Cadence principle
Salesforce's 2026 State of Sales report finds the average seller spends about 40% of their time actually selling. Every extra touch competes for that 40%, so on a sales cadence the reason behind each touch matters more than the raw touch count.
Make each step answer one question: what changed since the last touch, and what's the next concrete thing you're asking for? When nothing has changed, the next move is a call, a smaller ask, or a pause instead of another scheduled email.
Cadence map
Use the sales stage to choose the next touch.
| Touch | Include | Avoid | |
|---|---|---|---|
| After first conversation | Same day recap. | Decisions, open questions, owners, and next meeting time. | A generic thank-you with no action. |
| After demo | Recap within 24 hours. | Business problem, agreed value, open concerns, and next step. | A product feature list. |
| After proposal | Follow up on the decision process. | Ask about stakeholders, timing, and one specific blocker. | A discount nudge with no context. |
| No response | One new reason to reply. | A useful detail, deadline, recap, or close-the-loop question. | The same check-in again. |
Touch
- After first conversation
- Same day recap.
- After demo
- Recap within 24 hours.
- After proposal
- Follow up on the decision process.
- No response
- One new reason to reply.
Include
- After first conversation
- Decisions, open questions, owners, and next meeting time.
- After demo
- Business problem, agreed value, open concerns, and next step.
- After proposal
- Ask about stakeholders, timing, and one specific blocker.
- No response
- A useful detail, deadline, recap, or close-the-loop question.
Avoid
- After first conversation
- A generic thank-you with no action.
- After demo
- A product feature list.
- After proposal
- A discount nudge with no context.
- No response
- The same check-in again.
Example 6-touch cadence
Searchers usually expect a day-by-day starting point. HubSpot's sales cadence examples use explicit day offsets such as Day 1, Day 3, Day 7, and Day 10. Treat the sequence below as a default for a warm or active sales opportunity, then tighten or pause based on stage.
| Touch | Channel | Goal | |
|---|---|---|---|
| Day 0 | Same-day recap | Confirm decisions, owners, open questions, and the next meeting time. | |
| Day 2 | Specific follow-up | Email or call | Answer the likely next question or send the artifact you promised. |
| Day 5 | New context | Add one useful detail: stakeholder recap, comparison point, security note, or timing reminder. | |
| Day 10 | Channel switch | Call or voicemail | Check whether the decision moved, stalled, or needs a different owner. |
| Day 17 | Smaller ask | Ask for one answer instead of asking for the whole decision. | |
| Day 28 | Close the loop | Name the pause, log the restart trigger, and stop the active cadence. |
Touch
- Day 0
- Same-day recap
- Day 2
- Specific follow-up
- Day 5
- New context
- Day 10
- Channel switch
- Day 17
- Smaller ask
- Day 28
- Close the loop
Channel
- Day 0
- Day 2
- Email or call
- Day 5
- Day 10
- Call or voicemail
- Day 17
- Day 28
Goal
- Day 0
- Confirm decisions, owners, open questions, and the next meeting time.
- Day 2
- Answer the likely next question or send the artifact you promised.
- Day 5
- Add one useful detail: stakeholder recap, comparison point, security note, or timing reminder.
- Day 10
- Check whether the decision moved, stalled, or needs a different owner.
- Day 17
- Ask for one answer instead of asking for the whole decision.
- Day 28
- Name the pause, log the restart trigger, and stop the active cadence.
When to switch channels
Switch channels when the next email would repeat the same ask. A call or short voicemail does work the buyer won't do for you in another email, and it gives the deal a real read on whether the timing or the decision has actually moved.
- Use email for recaps, proposals, and forwardable context a champion can share.
- Use a call when a decision is stuck or the buyer has gone quiet after a meaningful meeting.
- Use calendar holds when the next step is already agreed and only timing is missing.
- Use a close-the-loop note when there is no business reason left to keep nudging.
- Stop the cadence when the buyer says the timing changed, then re-enter at the new trigger.
Cadence by deal stage
Generic cadences treat a discovery-stage opportunity the same as a procurement-stage one. They shouldn't be. The cadence shortens as the deal moves through stages, since the cost of silence rises and the buyer's internal calendar gets specific.
Keep the cadence denser inside an active deal and lighter at the top of the funnel. Below is a working starting point for B2B sales.
- Top of funnel (pre-discovery): Three to five touches over two to three weeks. One value-anchored email, one short follow-up, one breakup. Switch channels once between touches. Avoid daily nudges.
- Discovery and demo: Same-day recap, then a four-to-seven day follow-up if no reply, with one new piece of context. Bring a stakeholder into the next thread instead of repeating the ask.
- Pricing and proposal: Tighter: 24 to 48 hours after the proposal goes out, then every three to five days while the deal is open. Each touch names the decision process or the next stakeholder, not the proposal itself.
- Procurement and security review: Set the cadence with the procurement contact, not the champion. Weekly check-ins on document review status are appropriate; don't send marketing-style follow-ups during this stage.
- Verbal yes to signature: Move to daily check-ins on the signature path. The risk is no longer rejection; it's drift. Every email confirms what's blocking and what unblocks today.
Buyer signals to read
Cadence quality comes from reading the buyer's signals. The list below is what to watch in the reply, the silence, and the calendar.
- Reply length collapse: Two-line replies after multi-paragraph ones usually mean the deal is fading or the buyer has handed it off. Pivot to the stakeholder who is actually deciding.
- Calendar drift: Rescheduling twice on the same meeting is the cleanest signal that priority dropped. Acknowledge it, ask whether timing has changed, and stop pushing the original agenda.
- Stakeholder rotation: A new person on the CC line is information. Send the next message addressed to the new person and ask the original contact what role to play next.
- Question type shift: When discovery questions stop and procurement or legal questions start, the cadence has to match. Stop selling, start enabling.
- Pure silence after a soft yes: A verbal yes followed by two weeks of silence usually means an internal blocker the buyer doesn't want to name. A call beats a fourth email.
Pause and restart rules
The right pause is more useful than the next nudge. Pauses keep the relationship intact and give the rep a real trigger to come back to.
HubSpot's analysis of breakup emails reports one enterprise sales team seeing a 33% response rate to their breakup emails. Use them when the deal is late-stage and the buyer has gone quiet after multiple touches, not as the default fourth touch.
- Pause when the buyer tells you timing changed, then write down the trigger that should bring them back (renewal date, hire, fiscal year reset).
- Pause when the cadence has produced two identical no-reply emails. The third would be a tic, not a touch.
- Restart at a real event: a public hire, a funding round, a press release, a competitor change, or the calendar trigger you logged when you paused.
- Restart with one line of context tied to the event, not a 'wanted to check in' email.
- Close the loop explicitly when there is no plausible restart. A clean close earns referral surface area; a slow fade earns nothing.
How dreamif.ai fits
dreamif.ai plans each next touch on your sales cadence and has the draft ready on the timing you set, rather than firing messages off as an unattended drip. As a sales AI email assistant, it works from your Gmail thread and the notes you keep against the contact, using connected sources only when your settings allow. Nothing goes out until you approve it.
- Queues the next sales touch on your cadence for review
- Weighs whether that touch is a specific time, new evidence, a document, or a pause
- Reads the Gmail thread and saved contact notes to anchor each draft
- Supports voice review and note capture between meetings
- Keeps every send behind your approval