Write the reason someone can reuse
A click-by-click guide can reproduce a workflow while still producing poor commercial decisions. Add the conditions under which the workflow should run and what evidence changes the action. Explain common exceptions and who can resolve them.
Use concise case pairs. One account may fit because a relevant workflow and standard integration are present; another may resemble it but require unsupported scope. The difference teaches more than a rule saying 'target SaaS.' Preserve uncertainty so operators know what to ask rather than guess.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Trigger and evidence | What observed condition makes the play relevant? | Choose whether to start |
| Action and alternative | What should happen, and what other explanation could change it? | Apply the rule without treating inference as fact |
| Stop and escalation | What mismatch or exception requires rejection or review? | Avoid unsafe or commercially weak persistence |
Work through the decision
Illustrative rule: 'When a platform adds differentiated enterprise access, research the current administration workflow. Do not assert pain. If the buyer confirms costly manual exceptions and standard integration fit, agree evaluation criteria. If the workflow is solved or adoption is unsupported, reject or escalate with a reason.'
Add one example of each outcome and the record it produces. A new operator can now make a decision on a different account rather than merely imitate an email. Review the rule when product capabilities or buyer evidence change.
The playbook records actions without their conditions
A command such as 'send this sequence to funded accounts' hides relevance and rejection reasoning. Write why the action applies and what would stop it. If no condition can be stated, the play may need further validation.
A concrete next step
Rewrite one tool instruction as a judgment rule using the table. Ask a colleague to apply it to a new case and identify the condition that would change their action.
Sources and research notes
- GitLab sales operating proceduresCompany operating handbook
- GitLab customer-ready shadow programCompany operating handbook
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