LeadHaste
IntermediateNo variables to fill — paste & go

Optimize the timing and cadence of your follow-up sequence

Diagnoses where your sequence timing crowds, gaps, or quits too early, then rebuilds the cadence with day offsets, day-of-week guidance, and reasoning per touch. It refuses to invent statistics — where your data is thin, it designs the cadence test instead, so changes rest on your numbers, not folklore.

The prompt
You are a sequence-cadence analyst who has studied send-timing data across sequencing platforms, and your core finding is that most teams get the copy right and the clock wrong: touches bunched too tight at the start, dead air in the middle, sequences that end just as prospects start to recognize the sender. Cadence is a lever most teams never pull deliberately.

Analyze my current cadence and rebuild it. Deliverables:

1. A diagnosis of my current timing: where touches crowd, where gaps kill momentum, where the sequence ends relative to when my replies actually arrive.
2. A rebuilt cadence: for each touch, the day offset, day-of-week guidance, and one sentence of reasoning. Use widening-gap logic as the default but adapt to my data and deal motion.
3. Rules of thumb calibrated to my situation: when to pause for opens without replies, how weekends and holidays shift sends, and when a prospect's engagement should pull them out of the standard cadence entirely.

Constraints: don't invent statistics — reason from the data I give you, and where my data is thin, say so and give a testing plan instead of a fake certainty. No cargo-cult rules ('never email on Mondays') without reasoning tied to my list. If my sequence has a structural problem bigger than timing (too few touches, no angle variation), flag it before optimizing the clock.

Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. List your current touches and the delays between them (channel included if multi-channel).
2. What does your reply data show — which touches get replies, and roughly when after sending?
3. Who's the audience — role, seniority, timezone spread?
4. What's your sending volume and tool (Smartlead, Instantly, other)?
5. Any constraints — deliverability warm-up limits, compliance windows, seasonal cycles in your market?

Once you have my answers, deliver the diagnosis, the rebuilt cadence, and the calibrated rules. If my reply data is too thin to justify changes, design the A/B cadence test that will generate it in 2 to 3 weeks.

How to use it

  1. 1

    Copy the prompt into Claude, ChatGPT, or any LLM.

  2. 2

    Pull your per-touch reply stats from your sequencer before starting — even rough numbers change the quality of the rebuild.

  3. 3

    Describe your audience's rhythm in question 3; executives, practitioners, and seasonal industries reward different clocks.

  4. 4

    Apply the rebuilt cadence to one campaign as a test before rolling it across all sequences.

  5. 5

    Rerun the prompt quarterly with fresh data — cadence drifts as lists, seasons, and inbox behavior change.

Best practices

  • Fix structure before timing — if every touch says the same thing, no cadence will save it, and the prompt will tell you so.

  • Watch reply latency, not just reply rate: if replies to touch 2 arrive on day 3 after sending, a day-2 touch 3 steps on them.

  • Respect deliverability constraints as hard limits; a cadence that ignores warm-up schedules optimizes its way into the spam folder.

  • Change one cadence variable per test cycle — gap widths or send days, not both — or you won't know what moved the number.

Example: what this looks like in practice

A RevOps manager at a 70-person fintech-services firm runs a 5-touch sequence at uniform 2-day gaps and wonders why touches 4 and 5 pull almost nothing. She feeds the interview her Smartlead stats: replies cluster on touches 1 and 2, arriving 1 to 3 days after send; audience is CFOs across four US timezones. The diagnosis: touches crowd the first week, the sequence is over by day 8, and touch 3 lands before touch 2's reply window closes. The rebuild spreads five touches across 19 days with widening gaps, shifts sends to Tuesday-through-Thursday mornings per timezone, and adds a pause rule for multi-open non-repliers. Reply rate climbs from 2.1% to 3.4% over the next month with identical copy.

Best fit

Roles
RevOpsSales LeaderSDR / BDRFounder / CEO
Company size
Startup (1–10)SMB (11–50)Mid-market (51–500)
Audience
B2B
Industries
Any industry
Works with
Any LLM
Difficulty
Intermediate

This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.

Apply for a Pilot Spot →
Prompt FAQ

Frequently asked questions

Widening gaps is the most reliable default: 2 to 3 days between touches one and two, then 4 to 5, then 6 to 8, with the full sequence spanning 2 to 3 weeks. But 'best' depends on your reply latency — if your replies arrive 3 days after a send, tighter gaps step on your own touches. That's why this prompt builds from your data rather than a universal template.