Translate pipeline into a short-horizon capacity forecast
Takes confirmed and likely-to-close engagements and reasons out a 4–8 week load-versus-headcount picture, surfacing squeeze points before any staffing decision is made.
In / outConfirmed and likely-to-close deal list with estimated start dates and effort → 4–8 week load-vs-headcount picture with squeeze-point flags
You might say…
“I can see four engagements on the horizon but I have no idea if my two analysts can actually absorb them — I need a real read before I say yes to anything.”
What it does
Takes the current list of confirmed and likely-to-close engagements plus their estimated start dates and effort, and reasons out a 4–8 week load-versus-headcount picture — judging probability-weighted timing, likely concurrency, and where the squeeze points fall. Used when a principal needs a read on whether the next two months are over- or under-subscribed before any staffing decision.
Trigger: Use when a principal needs to judge whether the next two months are over- or under-subscribed before committing capacity or agreeing a start date.
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