Use fields that force a decision
A template should connect choices rather than collect descriptions. 'Midmarket SaaS' needs an operational condition explaining fit. 'Save time' needs a workflow and a buyer who can validate the effect. 'Outbound' needs contact coverage, a relevant opening question and a responsible reply owner.
For each field, include what you know, what remains hypothetical and the next validation action. Keep the template short enough to use during an operating review. Link detailed research and opportunity records instead of turning the plan into a document that nobody updates.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Customer condition | Problem + segment + disqualifiers + source | Choose a cohort a researcher can reproduce |
| Buying decision | Stakeholders + trigger + standard offer + adoption limits | Design discovery and an evaluation the buyer can act on |
| Learning loop | Channel + owner + experiment + economics + stop rule | Run, inspect and revise one assumption |
Work through the decision
Illustrative filled field: 'B2B platforms adding an enterprise pricing tier, with manually administered access and an engineering owner able to support an integration.' Evidence: public pricing documentation supports the tier; manual administration still needs validation. Disqualifier: no meaningful access complexity or no feasible standard integration.
The opening test asks how access changes are managed today. The decision rule is not 'send 1,000 messages'; it is to inspect whether the chosen operating condition corresponds to a buyer-confirmed problem and a feasible change project. Record the response distribution without pretending a small test establishes market-wide demand.
Blank fields are filled with confident assumptions
A template can make unsupported ideas look complete. Use explicit unknown labels and attach a validation owner. A field that says 'unknown; ask engineering in discovery' is more useful than a fictional budget estimate presented as research.
A concrete next step
Download the linked GTM worksheet and complete it for one cohort. Ask a colleague to select three accounts from the criteria; disagreement identifies fields that need sharpening.
Sources and research notes
- GitLab Command PlanCompany operating handbook
- Schematic product documentationCompany product description
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic