Why consultancies live with project-to-project revenue whiplash

Most consultancies know the cycle: heads-down delivering a big project, no time for business development, project ends, and suddenly the pipeline is empty. Feast, then famine, then feast.

The cause is timing, not demand

The whiplash isn't a demand problem — it's a *timing* problem. Business development stops during delivery because delivery is all-consuming. By the time the project wraps and the team looks up, there's a months-long gap before the next engagement can be sold, scoped, and started. The famine is structural.

What consultancies that smoothed it changed

1. Made business development continuous, not post-project. Even a small, protected weekly amount of pipeline activity *during* delivery prevents the cliff.
2. Separated selling from delivering where possible — so the people delivering aren't the only ones who can keep the pipeline warm.
3. Built a nurtured prospect list. Most consulting buyers aren't ready the moment you are; staying relevantly in front of them means the next project is closer to ready when you need it.
4. Added recurring or retainer revenue so not every dollar resets to zero at project end.

The protected-input discipline

The fix is unglamorous: a consistent, protected business-development habit that a busy delivery week cannot displace. A defined target-client profile, a steady volume of relevant outreach, follow-up that happens on schedule regardless of workload.

Whether that's a partner's discipline, a dedicated BD function, or tooling that keeps the cadence alive through delivery crunches, the principle is the one every services vertical repeats: predictable revenue needs a controllable input maintained continuously — not a burst of panic prospecting after the project ends.

The takeaway

Revenue whiplash is a BD-timing problem. Make pipeline activity continuous through delivery, separate selling from delivering, nurture a prospect list, and add recurring revenue — the famine is preventable.