Delays: this month's revenue was decided in March

This month's revenue is the output of decisions made months ago — the campaigns started, the conversations opened, the follow-up done or skipped back in March. Business systems respond on a delay, so by the time a result appears on the P&L, the cause is long past editing. Managing by current results is therefore steering by the rear-view mirror; the correction is to manage the inputs whose effects have not arrived yet.

Why do delays matter so much?

Because they break the feedback that learning depends on. When cause and effect sit side by side, people adjust naturally. When they are separated by a quarter, people connect the effect to whatever happened recently instead — and draw the wrong lesson with complete confidence. Donella Meadows put delays near the top of her list of leverage points in Thinking in Systems for exactly this reason: a delay in a feedback loop changes how the whole system behaves, usually by making it oscillate.

The oscillation is recognisable in any service firm. Busy quarter, so business development stops; two quarters later, a revenue trough; panic selling; a glut; another busy period; business development stops again. The feast-and-famine cycle is not a market condition. It is a delay in a feedback loop, expressed as a P&L. It is one of the structures I walk through in A Systems-Thinking Guide for Founders, and it is among the most common findings when we audit a firm's growth system.

How long are the delays in a B2B pipeline?

Longer than intuition says, and stacked in series. A typical outbound motion: a database takes days to build and verify; a new sending domain typically needs two to four weeks of warm-up before it can carry real volume; sequences run 4 emails over 14 days; positive replies turn into meetings over one to three weeks; UK B2B sales cycles then commonly run one to six months depending on deal size. Even the infrastructure has memory — sender reputation moves on a lag measured in weeks, which is why the groundwork in Cold Email Deliverability: The Practical Guide has to be laid well before the month you want the results.

Sum the chain and the conclusion is unavoidable: the decision to start generating pipeline must be taken roughly a quarter before the revenue is needed. March decides July. If July looks thin, July is too late.

What goes wrong when founders ignore the delay?

Three predictable errors:

• Stopping too early. The campaign has run three weeks, replies are thin, so it gets killed — often just before the responses arrive. Judging a delayed system on immediate output guarantees you abandon working systems.
• Overcorrecting. Results dip, so the founder changes the list, the copy, and the offer in the same week. When you change three variables inside one delay period, then you cannot attribute the eventual movement to any of them, so the next change is equally blind.
• Cutting the invisible. In a tight month, the first spend cut is the one with no visible short-term consequence — which is precisely the long-delay, high-compounding work. The damage arrives two quarters later, unattributed.

How do you manage a system with delays?

The mechanism is to manage leading inputs against known lags:

1. Map the chain from first activity to cash and write an honest estimate of each stage's delay. Even rough numbers beat none.
2. Pick input metrics you can read weekly: verified contacts added, emails sent, positive replies, meetings booked. These respond in days, while revenue responds in months.
3. Set the input budget from the delay. When you need revenue in month four, then the sends must happen in month one — so the weekly send volume is a hard commitment, not a mood.
4. Hold changes for one full delay cycle. When you alter copy or targeting, then freeze the rest until enough of the sequence has played out to read — as a rule of thumb we treat roughly 4% positive replies as on-target and below 3% as the trigger to fix the campaign, measured over a full cycle rather than a nervous fortnight.
5. Review causes against their proper effects. When you review July revenue, then pull March's activity numbers next to it, so the lesson attaches to the right decision.

Where else do delays hide?

Everywhere the feedback is slow: hiring (the mis-hire surfaces at month six), pricing (the underpriced book of clients hurts next year), reputation, and referrals — where the delay is so long that the loop feels like luck rather than structure, a dynamic worth its own treatment in the referral loop: reinforcing until it isn't. Delays also interact badly with local fixes: speeding up one stage while the constraint sits elsewhere just moves the queue, which is the territory of optimising the part vs the whole.

What does this change on Monday?

Write down your pipeline's total delay, first touch to cash, in weeks. Then check whether this week's diary contains any work whose payoff sits that far out. If everything in the diary pays off this month, the current quarter may be fine — and the one after it was just quietly cancelled.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.