Sequence cadence that respects the recipient

How many steps, what delays between them, when Smart Send helps, and where InMail fits.

A cadence is the rhythm of your outreach: how many steps, how long between them, and what runs on which channel. It is the difference between a sequence that feels like a conversation and one that feels like a bot.

Step 01 · Foundation

What "cadence" actually means

Cadence is not just delays. It is the full pattern a lead experiences:

  • Number of steps in the sequence
  • Which channel each step uses (connection, DM, InMail, view)
  • Delay between steps
  • What triggers the next step (accepted, ignored, replied)
  • When you stop if nothing lands

A good cadence stays under the mental radar of the recipient. If they feel touched too many times, they mute you. If they feel touched too rarely, they forget you. The right rhythm sits in between.

Step 02 · Shape

The shape of a good sequence

3-6
steps. Longer sequences do not perform better. They just annoy people who were never going to reply.

Every good sequence has three moments:

  1. The touch: connection request or first message. Introduces you.
  2. The value drop: a message with a specific piece of value tied to the recipient.
  3. The soft close: one final nudge with an out ("wrong time, let me know").

Between those you can add view-profile steps as light signals. Anything beyond six steps starts to feel like harassment, not persistence.

❌
Long sequences do not fix a bad first message If steps 1 and 2 do not land, adding steps 6 and 7 will not save the reply. Fix the top of the sequence first.
Step 03 · Timing

Delays that feel human

The delay between steps is the single biggest control you have over how automated the sequence feels.

  • Between connection request and first message: 1 to 2 days after acceptance. Immediately messaging someone the moment they accept feels robotic.
  • Between the first message and the first follow-up: 3 to 4 business days. This is enough time to have been seen and to have felt "next".
  • Between follow-ups: 5 to 7 business days. Longer gaps at each step, not shorter.
  • After a "not now" reply: 30 to 90 days minimum before touching them again, and only with genuinely new information.
⚠️
Nights and weekends Sending at 3am on the recipient's local time reads as automation. A message that arrives Tuesday at 10am always beats the same message at 2am Sunday. Keep an eye on when your sequence is actually landing across timezones.
Step 04 · Smart Send

When Smart Send saves you three campaigns

Smart Send is a single step that decides the channel per lead. It checks connection status, then picks:

  • Already connected: sends a DM.
  • Not connected, reachable on Premium: sends an InMail (if the sender is Premium and has credits).
  • Otherwise: sends a connection request.

Use it when you have a mixed list where some prospects are already connected to your sender and some are not. Instead of running three parallel campaigns (one for connections, one for InMails, one for messages), one Smart Send step handles them all.

💡
When Smart Send does not help If every lead in the list is guaranteed to be first-degree already, use a plain DM step. Smart Send does an extra connection check that costs nothing but is not needed. When the list is 100% cold, a plain connection request is simpler.
Step 05 · InMail

Where InMail earns its keep

InMail is a paid Premium channel. It bypasses the connection requirement. It also costs credits.

Use InMail:

  • On high-value leads where a connection request has stalled for two weeks.
  • On second-degree prospects who are almost certain to be reachable (senior roles at target accounts).
  • As the last resort in a Smart Send branch (built in already).

Do not use InMail:

  • As the first touch on cold, low-value leads. It burns credits with no better result than a connection request.
  • To send generic pitches. InMail's "you paid to reach me" perception means the message has to earn the interruption.
Step 06 · Branching

Build for what happens next

A sequence that runs the same steps whether the lead replies or not is a mailing list, not a conversation. Use conditional branches to react.

The branches that matter most:

  • Has replied? If yes, stop the sequence. Never keep pushing after a reply, positive or negative.
  • Is connected? After a connection request, wait a few days, then branch based on whether the acceptance came through.
  • Is pending? If the invitation is still hanging after a week, do not send a second one. Move to another step or stop.
Step 1: Send connection.
Wait 3 days.
Branch on Is Connected?
  → Yes → Step 2: DM (first message). Wait 4 days. Branch on Has Replied? → Yes: stop. → No: Step 3: DM (follow-up).
  → Still pending → wait 7 more days, then stop.
Step 07 · Pre-flight

Cadence checklist before launch

  1. Step count. Between 3 and 6? If longer, cut the middle steps that add no new value.
  2. Delays. First follow-up at least 3 business days after the first message? Follow-ups spaced 5+ days after that?
  3. Reply branch. Every step past the first has a Has Replied? branch that stops the sequence when the lead engages?
  4. Cap on total touches. Nobody gets more than 5 messages from you across a single cycle. Past that, the lead goes on a slower follow-up loop or to DNC.

If all four check out, launch. If any of them do not, tighten the sequence before the first lead sees it.


Still stuck? Email contact@salesnext.io.

Didn't find what you needed?

Reach out and we'll help you out.

Contact support