Two quarters of pipeline, modelled in three minutes.
Plug in your motion. See the meetings, SQLs, and sourced pipeline a coordinated outbound engine would produce — with sensitivity ranges and explicit assumptions.
Your motion
Two-quarter projection
Outputs are operator ranges, not contractual forecasts. Cycle: 4 months — pipeline lands in current quarter and the next.
What this model does and doesn't do.
We'd rather you trust the output than be impressed by it. Here's exactly what's underneath.
Multi-channel coordination
Numbers assume email + LinkedIn + calling against the same account list, with shared signal and routing.
Six-month ramp curve
Output ramps M1 → M6 (0.55× → 1.15×). Real engines compound modestly month-over-month as copy, data, and ops tighten.
Conversion benchmarks
Defaults sit inside operator-observed ranges across SaaS, fintech, services, and enterprise expansion engagements.
Pipeline = opps × ACV
Sourced pipeline is opportunity count × ACV. Win rate and cycle are out of scope — that's a different model.
Questions about the model.
A coordinated multi-channel outbound engine in steady state. Numbers are based on operator-observed ranges across our engagements. Treat outputs as a band, not a forecast.
Run the audit, get the live model.
A 30-minute audit. We replace the defaults with your actual data, and show you what shipping an engine on top would do.