Make the founder's decisions teachable
Founders often adjust a pitch using product history, buyer context and instinct that never enters the CRM. A new AE cannot reproduce that judgment from a slide deck. Observe several live decisions, record the evidence and compare a won case with a rejected one.
Separate legitimate founder responsibilities from avoidable dependence. Product strategy and exceptional commitments should remain with leadership. Routine reply handling, qualification and agreed follow-up can move to another owner once the rules and escalation path are explicit. The transition should reduce dependence gradually while keeping important buyer conversations supported.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Account selection | Founder explains why a specific operating condition matters | Seller applies the same rule to unfamiliar accounts |
| Discovery judgment | Founder explains what would disprove the pain hypothesis | Seller asks neutral questions and records corrections |
| Commercial escalation | Pricing and product boundaries are documented | Seller negotiates inside authority and escalates exceptions |
Work through the decision
Illustrative example: a founder knows that integration requests from a certain buyer role usually reveal a compliance project. Instead of writing 'sell to compliance teams,' record the observable signal, the validation question and the circumstances where the inference fails.
Have a seller lead the next discovery call while the founder observes. Compare the seller's opportunity assessment with the founder's independently written assessment. Discuss discrepancies using buyer evidence. Repeat on a different account. The goal is consistent reasoning, not a seller imitating the founder's wording.
The founder approves every routine step forever
If a new seller needs founder approval for every message, qualification and follow-up, the bottleneck has moved rather than disappeared. Define the small set of decisions requiring approval, then let the seller operate within documented boundaries and review outcomes at a predictable cadence.
A concrete next step
Choose one recurring founder decision and write its trigger, evidence, action and stop condition. Ask another seller to apply it to three accounts, then review where the rule was incomplete.
Sources and research notes
- GitLab customer-ready shadow programCompany operating handbook
- GitLab sales operating proceduresCompany 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