Map decisions, not just titles
Ask which decisions must happen before a purchase and who can make or block each one. The same person may hold several roles in a smaller company, while a larger account may distribute them across teams. Keep influence, approval and operational ownership separate.
For each role, record the evidence, current concern and next action. Do not assume a contact can introduce every stakeholder immediately. Help the champion explain why another participant matters to the evaluation, and let the buyer define the internal process.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Problem and adoption | Who experiences the issue and operates the solution? | Validate the workflow and implementation criteria |
| Technical and risk | Who evaluates integration, security or legal constraints? | Prepare accurate materials and named answers |
| Commercial decision | Who authorizes spend and procurement steps? | Confirm approval process and mutual timing |
Work through the decision
Illustrative deal: an engineering manager supports the product, product leadership owns the roadmap, finance approves spend and security reviews access. The engineering manager is a strong champion but cannot alone settle scope or price.
Build a mutual plan that identifies each decision and the owner's concern. If finance is unknown, the next action is to clarify commercial approval, not to claim the deal is ready for a proposal. A committee map should expose missing coverage rather than decorate the opportunity with unverified executive names.
The champion is treated as the entire buying process
An enthusiastic user can advocate for the product and still lack budget, risk approval or implementation capacity. Ask how similar purchases are made and what the champion needs to involve others. Do not pressure them to promise authority they do not have.
A concrete next step
Draw a decision map for one active account. Mark confirmed roles, hypotheses and missing coverage with plain labels, then choose the next conversation that resolves the most important gap.
Sources and research notes
- GitLab Command PlanCompany operating handbook
- GitLab commercial opportunity stagesCompany 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