Nurture cadences — not-yet-ready contacts and the 30/60/90.

The premise

The reply categories defined in Chapter 01 produce a population that is neither positive intent nor negative intent. The soft-pass — "interesting, not now" — is the largest of the non-binary categories at production volume, typically accounting for 25 to 40% of total reply flow on a mid-market B2B campaign. The operator who routes this population to a "no" bucket loses the entire downstream pipeline contribution. The operator who routes it to an undifferentiated "follow up later" bucket loses most of it through inattention.

The empirical conversion rate from soft-pass to eventual qualified opportunity ranges from 15 to 25% over a twelve-month window for operators running disciplined nurture, and under 3% for operators running no nurture or undifferentiated time-based nurture only. The variance is not a function of the underlying contact quality. It is a function of the operational discipline of categorizing the soft-pass, scheduling the next touch against the stated condition, and detecting the external trigger that converts a paused conversation back into an active one.

The soft-pass categories

A soft-pass reply, on inspection, decomposes into three distinct sub-categories. The category determines the nurture cadence — not the other way around — and the operator who runs a single cadence over all three sub-populations is leaving the majority of the eventual conversion on the table.

Timing-based soft-pass

The reply names a specific future date or quarter: "follow up in Q3," "circle back after the launch in September," "we're heads-down on a migration until end of the year." The re-engagement condition is a calendar date. The cadence is driven by that date, not by an arbitrary interval.

Budget-based soft-pass

The reply names a budget cycle: "we'll look at this in next fiscal," "this would be a budget conversation for our annual planning," "we just locked our quarterly spend." The re-engagement condition is the company's fiscal calendar — for most US enterprises, the boundaries are January 1, April 1, July 1, and October 1, with named fiscal-year starts more variable.

Evaluation-based soft-pass

The reply names an in-flight evaluation of a competing or adjacent solution: "we're already piloting X," "we just signed a six-month trial with Y," "we're in implementation on something similar." The re-engagement condition is the eventual evaluation of that solution — typically 90 to 180 days from the reply date, longer for enterprise implementations.

The per-category nurture cadence

Each sub-category has a different cadence anchor. The operational pattern is to set the re-engagement date at categorization time, not to discover it at follow-up time.

• Timing-based: a single touch at the named date, plus a confirmation touch seven days prior. Multi-touch volume between the categorization date and the named date adds noise and increases unsubscribe risk.
• Budget-based: a touch six to eight weeks before the named fiscal-quarter boundary, timed to land while planning conversations are active but before budget is locked. A second touch immediately after the boundary, framed against the new fiscal context.
• Evaluation-based: 90-day-interval touches anchored to the reply date, each framed around how the evaluation is progressing rather than a re-pitch. The objective at each touch is information — is the pilot succeeding, is the implementation on track — rather than conversion.

The 30/60/90 default

For the soft-pass replies that do not name a category — "thanks, not now" with no further context — the default nurture cadence is 30/60/90: a touch at 30 days, a second at 60, a third at 90, and a quarterly cadence thereafter. This is the unstructured default. It is also, in operator practice, the cadence applied to the bulk of soft-pass volume because the categorization step is the operational discipline most often skipped.

The 30/60/90 default exists because, in the absence of a categorization signal, the empirical reply-to-meeting conversion curve from a soft-pass population peaks in the 30-to-60-day window after the original reply and decays predictably thereafter. The operator who waits 180 days before the first nurture touch is touching the population at a point in the curve where conversion is already below baseline cold outbound.

Per-cadence conversion-rate decay

The empirical conversion rate, per touch, on a soft-pass nurture cadence follows a steep decay curve. Across mid-market B2B campaigns the observed ranges are:

The implication is that a pure time-based nurture cadence converges on cold-outbound baseline at the 270-day mark. Any pipeline contribution beyond that point is either a function of trigger-based re-engagement or of the contact returning inbound through a separate channel.

Trigger-based re-engagement

The empirical conversion-rate lift from a trigger-based re-engagement, relative to the same-aged time-based touch, is 3 to 7x. A nurture contact who receives a re-engagement message anchored to a relevant external event — a funding announcement, a named-leader hiring, a regulatory change in their industry, a competitor's product launch, a public restructuring — converts at materially higher rates than the same contact would on a calendar-driven touch.

The mechanical reason is that the trigger provides the message a non-pitched opening — the operator is responding to something the contact's organization actually did, rather than producing manufactured cadence. The reply rate is higher; the meeting-booking rate from the reply is higher; the overall conversion lift is multiplicative through both stages.

Per-trigger detection automation

The operational pattern of trigger detection is the monitoring of a named-account list against a defined trigger taxonomy. The triggers that materially predict re-engagement conversion, in order of observed lift:

• Named-account funding announcement — Series B and later
• Named-leader hiring at a relevant title — VP and C-level
• Regulatory change in the named-account industry that creates direct demand for the offering
• Public restructuring, layoff, or org-chart change at a named account
• Competitor product launch that creates a comparison frame
• Industry-wide event the named-account roster attended

A correctly built trigger-detection layer surfaces the named-account event into the nurture queue with the contact's prior reply, the original categorization, and the suggested re-engagement frame pre-attached. The operator's time per re-engagement is reduced from research-plus-write to review-plus-send, which is the difference between trigger-based re-engagement being a practiced discipline and being a quarterly aspiration.

CRM-stage discipline

Every nurture contact must have a CRM stage and an explicit re-engagement date attached at categorization time. A contact without a stage falls out of the operational system within 30 days. A contact without a date falls out within 60.

The minimum-viable stage taxonomy for nurture is three values: nurture-timing, nurture-budget, nurture-evaluation, plus a fallback nurture-default for the 30/60/90 population. The re-engagement date is a CRM field, not an inbox flag. The CRM is the source of truth; the inbox is a working surface.

The most common operator failure at this layer is the conversational soft-pass that never gets categorized at all — the operator reads the reply, mentally classifies it as "not now," archives the thread, and never writes a stage or a date anywhere. The contact does not re-surface. The pipeline contribution is zero. The upstream campaign cost is unchanged.

Multi-channel nurture

Nurture is not channel-locked. The operational decision is whether each touch is delivered through email, LinkedIn, or a mix. The per-channel observed response rates on a nurture population differ materially from the response rates on cold outbound to the same contact, and the channel mix shifts the population's tolerance for cadence.

• Email-only nurture: 1.5 to 3% reply rate per touch, low coordination overhead, scales linearly with list size. The channel of record for unstructured 30/60/90.
• LinkedIn-only nurture: 3 to 6% response rate per touch, higher coordination overhead, capped by per-account connection volume. The channel of record for trigger-based re-engagement on named accounts.
• Mixed-channel nurture: 4 to 8% response rate per touch when alternated, but only if the alternation pattern is structured rather than parallel. Sending both email and LinkedIn simultaneously to the same nurture contact reduces the combined response rate below either channel in isolation.

Content-asset distribution in nurture

The empirical conversion effect of nurture touches that deliver a content asset — a curated industry analysis, a customer case study, a relevant data point, a piece of original research — versus templated check-in touches ("just circling back") is roughly 2 to 3x on reply rate and somewhat smaller on downstream meeting-booking rate.

The mechanism is that the asset-delivery touch passes the recipient's mental "is this worth opening" filter on a different basis than the check-in touch. The check-in produces a binary continue/ignore decision against the recipient's current bandwidth. The asset-delivery produces a value judgment against the asset itself, which is decoupled from the recipient's current bandwidth.

The operational requirement is a steady supply of distribution-ready assets. Operators without a content production pipeline fall back to the templated check-in by default and absorb the conversion penalty silently.

Drip campaign vs manual touch

The operational tradeoff between automated drip-campaign nurture and manually written per-contact touches is the per-pattern conversion-rate differential against the per-pattern operator-time cost. Across the cadence ranges:

• Templated drip: 0.5 to 1.5% reply rate, scales to unlimited list size, near-zero per-touch operator time. The default for unsegmented 30/60/90.
• Lightly personalized drip: 1.5 to 3% reply rate, scales to several thousand contacts per operator, modest per-touch overhead in the variable-field preparation.
• Manual per-contact touch: 6 to 12% reply rate, scales to roughly 30 to 50 trigger-based re-engagements per operator per week, requires the trigger-detection layer to be operational upstream.

The correct architecture is tiered: templated drip for the default 30/60/90 population, lightly personalized drip for the categorized soft-pass populations at their anchor dates, manual per-contact touches reserved for trigger-based re-engagement on named accounts. Operators who run a single tier across the entire nurture population are either underinvesting at the top of the conversion curve or overinvesting at the bottom of it.

Nurture-to-active reactivation

When a nurture contact replies with positive intent, the operational pattern is to move them out of the nurture stage and back into the active campaign workflow within the same business day. The reactivation handoff has the same four-hour-window discipline as a fresh positive reply on an active campaign (Chapter 03), because the contact's signal is functionally identical to a fresh positive intent.

The CRM stage change is the trigger. A contact who moves from nurture-budget to active-positive-intent exits the nurture cadence in the same transaction. Failing to remove the contact from the nurture cadence at reactivation produces the failure mode of an in-flight active conversation receiving a templated nurture touch a week later, which is the most common single cause of preventable mid-funnel drop-off.

The nurture-fatigue threshold

The empirical limit on nurture-touch volume before a contact unsubscribes or marks the sender as spam is 6 to 10 touches over a 12-month window. The variance is largely a function of channel mix and content quality: a contact receiving 10 asset-delivery touches over 12 months unsubscribes at materially lower rates than a contact receiving 6 templated check-ins.

The operational implication is that nurture is a finite resource per contact. The 30/60/90 default plus a quarterly cadence thereafter produces 5 touches in the first year, leaving headroom for trigger-based re-engagement without breaching the fatigue threshold. Operators who layer a monthly cadence on top of a quarterly cadence on top of trigger-based touches exhaust the threshold inside 8 months and surface a wave of unsubscribes that they typically attribute to upstream campaign quality rather than nurture-layer overcadence.

Common operator failures observed in production

• No CRM-stage discipline. The soft-pass reply is read, archived, and never categorized. The contact does not re-surface. The most frequent stable failure state at the nurture layer.
• Time-based-only cadences. The operator runs 30/60/90 over the entire soft-pass population and never anchors timing-based or budget-based contacts to their stated dates. Conversion converges on the unstructured baseline.
• No trigger detection. The 3-to-7x conversion lift from trigger-based re-engagement is left on the table because the named-account trigger taxonomy is not monitored.
• No content-asset variety. Every touch is a templated check-in. Reply rate sits at the 0.5 to 1.5% drip baseline. The operator concludes that nurture does not work.
• No fatigue threshold. Cadences are layered without ceiling. Unsubscribe volume spikes between months 6 and 10. The operator concludes that the list quality is degrading.
• No reactivation pattern. A positive reply lands inside the nurture inbox, sits for days, and is then handled with a templated nurture touch rather than the active-campaign workflow. The contact's positive intent decays before the operator engages.

Pre-deployment nurture checklist

• CRM stage taxonomy defined and the four nurture stages provisioned
• Re-engagement date field present on the contact record and required at stage transition
• The categorization step embedded into the reply-triage workflow from Chapter 03
• A trigger-detection layer operational over the named-account list, with at least the funding, hiring, and regulatory categories monitored
• A content-asset library with at least one distribution-ready piece per 30-day window
• A drip-vs-manual routing rule at the stage level — templated drip for default, manual for trigger-based
• A fatigue-threshold ceiling enforced at the contact level, with the count surfaced in the operator's nurture view
• A reactivation handoff that exits the contact from the nurture cadence on positive-intent stage change

Where nurture fits in the broader reply-handling layer

Nurture is the operational answer to the population that the four-hour window of Chapter 03 routes neither to the active calendar of Chapter 05 nor to the closed bucket of negative intent. It is the longest-running stage of the reply-handling stack in calendar terms and the lightest in per-touch operator time, which is precisely why it produces the largest variance in eventual revenue outcome across operators with otherwise identical upstream campaigns.

The pipeline-conversion math of Chapter 07 takes the nurture-stage conversion rate as an input. A reply-handling stack that converts 15 to 25% of soft-pass into eventual pipeline carries a materially different upstream investment ceiling than a stack that converts under 3%, even when the per-touch reply rate at the top of the funnel is identical. The nurture layer is the longest single lever on that ratio.