Every nurture program is two designs in one: what you send, and when you send it. Teams spend weeks on the first and settle the second with a shrug — "wait 3 days" between every step, because three felt reasonable in the planning meeting. Then the program underperforms and everyone blames the copy.
Wait steps are the strategy. They encode your assumption about how long a buyer needs to read, think, and act — and when that assumption is wrong, no subject line fixes it. The examples here use Pardot (MCAE) Engagement Studio, where the wait step is an explicit building block, but the logic applies to any platform's nurture builder.
What a wait step is actually deciding
A wait between two emails is answering three questions at once: how long does a busy person need before a follow-up feels like persistence rather than pestering; how long does your evaluation window stay open before the moment passes; and how does this delay interact with everything else the person receives from you that week. "Wait 3 days" is a specific answer to all three — it's just usually an accidental one.
The most useful reframe: stop thinking of waits as pauses between your sends, and start thinking of them as response windows for the recipient. That immediately suggests different durations for different steps, which is where most flat-paced programs go wrong.
Duration guidelines that survive contact with reality
For B2B nurtures, patterns that hold up:
Early steps: shorter waits (2–4 business days). Someone who just downloaded an asset or joined a trial has you in working memory. A follow-up inside the same week lands in context; a follow-up two weeks later is a cold email with extra steps.
Middle steps: standard cadence (5–7 business days). Once the program settles into education mode, roughly weekly is the pace that reads as "helpful vendor" rather than "sales countdown." One touch per week also plays nicely with communication limits and whatever else your calendar throws at the same audience.
Late steps and re-engagement: longer waits (10–15+ business days). By the tail of a nurture, the people still unengaged aren't going to be argued into action by frequency. Stretch the pacing, change the angle, and let the exit criteria do their job.
After a hand-raise: no wait at all. If someone requests a demo or hits pricing, the nurture's job is to get out of the way — trigger the alert, pause or exit the program, and let a human respond within hours, not after the next scheduled step.
These are starting points, not laws. The point is that a well-designed program has deliberately uneven pacing — and if yours is a uniform "wait 5" all the way down, that's the tell that pacing was never actually designed.
Rule-based waits: pace on behavior, not just the calendar
Engagement Studio's underrated feature is that a wait step can carry rules — "wait up to 7 days, but proceed early if the prospect clicks the pricing link" or "opens the email." This converts fixed pacing into responsive pacing: engaged prospects accelerate, quiet ones get the full window.
Used well, this solves nurturing's core tension — fast enough for the ready, patient enough for the rest — without building parallel program branches for every speed. Used lazily ("proceed on any open," in a world where Apple's privacy features inflate opens), it accelerates everyone and collapses back into a fast flat cadence. Trigger early exits and accelerations on meaningful actions — clicks on high-intent links, form fills, page visits — not on vanity signals.
The mechanics that quietly ruin good pacing
Three operational details cause most wait-related incidents:
Business days versus calendar days. A "wait 2 days" that lands sends on Saturday isn't a pacing strategy, it's a scheduling accident. Use business-day waits and sending windows where the platform offers them (Engagement Studio supports both), and check what happens to steps that would fire on holidays.
Waits interact with everything outside the program. A perfectly paced nurture still collides with the webinar invite and the newsletter. Communication limits are the safety net here; the nurture's waits should be designed assuming other sends exist, which is another argument for weekly-ish middle cadence rather than aggressive multi-touch weeks.
Editing waits in a live program doesn't reschedule people already inside a wait step — behavior varies by platform and by edit type, and Engagement Studio has real constraints on what you can change mid-flight. Before editing pacing on a running program, check the platform's rules and, when in doubt, test with a copy. "We shortened the wait and a thousand people got two emails in one day" is a genre of incident we see more often than anyone admits.
Diagnosing a pacing problem
The signal that waits — not content — are the issue: engagement that decays step over step faster than list fatigue explains. Pull per-step metrics and look at the shape. Strong step 1, cliff at step 2 with a short wait: you're crowding people — lengthen the early gap. Slow bleed across steps with long waits: you're being forgotten between touches — tighten the middle. Unsubscribes clustering right after multi-send weeks: the collision problem — fix it at the calendar and communication-limit level, not inside the program.
Then treat pacing as testable. Clone the program, change only the wait durations, split the audience, and compare completed-step engagement after a full cycle. It's a slower test than a subject line A/B — and it routinely moves numbers a subject line never will.
Nurture architecture and pacing are part of what we build in marketing operations engagements — and part of what we review in a stack audit: 45 minutes, free, and the findings are yours whether or not we ever touch the program.