Build and sell in one connected sequence
Early work establishes the account logic, systems, ownership and initial plays. Selling then tests those choices with actual buyers while infrastructure and message adjustments continue. Later work deepens opportunity progression and prepares internal operators to inherit the motion.
Do not separate a long build phase from a blind execution phase. If discovery disproves the original segment hypothesis, change the plan and record why. Training should begin during delivery rather than as a final presentation. Client product and approval support remain necessary across the period, especially for complex evaluations and procurement.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Establish the motion | Account criteria, ownership, systems and first experiments | Launch bounded plays with reviewable assumptions |
| Operate and learn | Replies, discovery, evaluations and rejection evidence | Adjust based on buyer decisions rather than activity alone |
| Transfer capability | Successors, playbooks, access and recovery practice | Demonstrate independent operation before closing handover |
Work through the decision
Illustrative plan: the first cohort targets finance-led reporting problems. Discovery reveals that engineering owns the actual integration constraint. The team revises contact coverage and the evaluation plan while keeping the original account evidence. This is a change in the buying hypothesis, not a reason to reset every tool.
An internal seller shadows the revised conversations, then leads one with review. The administrator practices the workflow recovery before the final month. Active deals retain named ownership throughout the transfer. The schedule provides structure, while the evidence determines which action is appropriate.
The calendar is mistaken for buyer progress
A month-three proposal is not evidence of a month-four close. Stage advancement should depend on buyer decisions and verified conditions. Keep the delivery timeline separate from opportunity forecasts and record the assumptions behind both.
A concrete next step
Ask for the proposed delivery sequence alongside the responsibility map. Mark client dependencies and successor participation so the calendar has real owners and capacity behind it.
Sources and research notes
- Ramp Year: delivery method and public offerOur public offer; final agreement controls
- GitLab commercial opportunity stagesCompany 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