Surface latent scope risks the surface mapping missed
Packaged know-how that tells an agent how to do a job well.
You might say…
“We're two weeks in and it turns out the client's data hasn't been cleaned since 2022 — something we would have caught in intake if we'd known what to look for.”
What it does
Reviews the intake picture for signals that could compromise delivery or client outcomes — data quality issues, political landmines, unrealistic expectations, or downstream scope expansion — and surfaces them as named risks.
Trigger: Use alongside the fit check to catch risks that don't show up in the formal criteria but could derail delivery if left unnamed.
I/O: Intake data and client context → named risk register for this engagement (risk, signal, potential impact, recommended mitigation)
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