GTM Dual Sprint
“Not two Quick Starts run back to back — one phased build across exactly two workstreams.”
The Problem This Solves
Some gaps are real but genuinely confined to two workstreams — say, ICP validation and the messaging built on top of it. Running those as two separate Quick Starts risks building the second artifact before the first is actually validated, then reworking it. GTM Dual Sprint sequences both inside one engagement instead: Diagnosis, Build, Handoff.
Who It's For
Two confirmed workstream gaps, real urgency
Companies with exactly two workstream gaps — typically where one depends on the other, such as ICP before messaging, or process before pipeline development — and real urgency behind fixing both.
Not the right engagement if:
Only one workstream is actually in play — that's a Quick Start.
Three or four workstreams are interdependent and urgent — the two-workstream ceiling here is a boundary, not a soft limit; that's a GTM Full Sprint.
What Malcolm Does
A phased build across the two named workstreams: a Diagnosis Review at the end of week 1 confirms scope and direction, a Build Midpoint Review near the end of week 3 checks the work in progress, and Delivery lands in week 5.
Engagement Structure
Duration: 4–5 weeks.
Fee: scoped and fixed at intake once the Scope Lock is signed.
Scope: exactly two workstreams. A third is a GTM Full Sprint, scoped and quoted as its own engagement — never an informal addition to this one.
How It Connects
GTM Dual Sprint sits between Quick Start and the full GTM Full Sprint — built for the gap that's bigger than one workstream but doesn't need the full four-workstream rebuild.