Staying present through a nine-month buying cycle

You stay present through a nine-month buying cycle by scheduling a useful touch every three to five weeks, running that schedule from your CRM rather than from memory, and making each touch worth reading on its own merits. You cannot compress a buyer's timeline; you can only make sure you are the obvious first call when it turns. That takes a system, because no salesperson's attention survives nine months of "not yet".

Why do long cycles lose more deals than rejection does?

A nine-month cycle is normal for considered B2B purchases — new systems, retainers of any size, anything that touches procurement. The failure mode is rarely a prospect saying no. It is the seller going quiet around month two. Most firms stop at two follow-up touches, while deals of this kind typically need five or more meaningful contacts before they close. If your touches stop in month two and the decision happens in month eight, you have spent six months being forgotten while a competitor stayed visible.

The 90-Day Follow-Up Framework covers the first quarter after an enquiry, where the cadence is tightest. This article covers the stretch beyond it — the part where discipline matters more because motivation is lower.

What does a nine-month presence plan look like?

The cadence should decay slowly, not collapse. A shape that works for most UK B2B service firms:

Across nine months that is roughly ten to twelve touches. Spread out and useful, that reads as professional persistence. Compressed into the first six weeks and followed by silence, the same effort reads as desperation followed by indifference.

How does the system run without anyone remembering?

The mechanism matters more than the calendar. When a prospect says "not now", then you record two fields in the CRM: the reason ("budget opens in Q1", "mid-contract until March") and a review date. When the review date arrives, then the CRM creates a task with the full context attached, so whoever picks it up knows exactly why they are calling. When a trigger event fires — a new senior hire, an office move, a funding announcement — then it overrides the schedule, because a relevant touch today beats a scheduled touch next month.

Nothing in that chain depends on memory or mood. The capture side — how the enquiry gets into the CRM with clean fields in the first place — is covered in Anatomy of an inbound engine.

What counts as a touch worth sending?

"Just checking in" is not a touch; it is an admission that you had nothing to say. Touches that hold attention over nine months share one property: the recipient would find them mildly useful even if they never bought from you. A short note on a regulation change in their sector. A one-paragraph teardown of a problem you solved for a similar firm, anonymised. A considered answer to a question they asked three months ago.

A regular newsletter carries much of this load at near-zero marginal cost — one asset reaches every long-cycle lead at once, on schedule, without per-lead effort. We cover the design of that in the newsletter as a nurture system.

Where do nine-month leads actually leak?

Three places, most commonly. Handovers: the person who took the enquiry leaves or changes role, and the lead is left with no owner. Hygiene: the review date was never set, so the CRM never prompts anyone and the record quietly fossilises. Classification: the lead was marked "lost" in month two because the pipeline report looked tidier that way, when the honest status was "not yet". Walking your pipeline against these failure points is the substance of the lead leakage audit.

Does nurture email need the same infrastructure as cold email?

Mostly, yes. Nine months of monthly emails still ends up in spam if the technical layer is neglected. The volumes are lower than cold outbound, but the deliverability fundamentals — authentication, list hygiene, a monitored sending domain — are identical, and a nurture email that lands in junk is a touch that never happened. The unglamorous sending infrastructure is the condition for everything above working.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.