Judge whether the pipeline is adequately full
Reviews the current prospective-engagement set and forms a view on whether BD effort needs to increase, hold, or ease — and whether there is a shape problem like too many early-stage and too few near-proposal conversations.
In / outPipeline records (stage, conversion likelihood, timing, expected value) + stage-distribution view → adequacy verdict and shape diagnosis
You might say…
“My pipeline had lots of names in it but I could never tell if it was actually healthy or just busy-looking.”
What it does
Reviews the current set of prospective engagements (stage, conversion likelihood, timing, expected value) and forms a view on whether get-on-radar effort needs to increase, hold, or ease, noting any shape problem such as too many early-stage conversations and too few near proposal. Used as the meta-assessment of pipeline health. Single human-in-loop judgement; consumes the stage-distribution view.
Trigger: Use as the meta-assessment after viewing the stage-distribution — to form the single judgement that determines whether to increase or ease BD activity.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation