Write a record that survives a change of owner
Capture enough context to support a decision, not a transcript dump. Quote or paraphrase the buyer accurately, with the conversation date and appropriate recording consent where relevant. Link research facts and note when discovery corrected them.
Document the next mutual action with an owner and timing, plus the most important unknown. For a technical product, include evaluation criteria and implementation constraints. For a commercial decision, include approval roles and scope. Do not fill missing facts with assumptions copied from similar accounts.
| Decision | Evidence to use | What changes next |
|---|---|---|
| What is established | Fit, buyer-confirmed problem and source or conversation evidence | Supports acceptance without redoing all discovery |
| What remains unresolved | Stakeholders, impact, scope, approval or adoption risk | Directs the next questions |
| Who acts next | Accepted owner, mutual action and review date | Prevents a useful conversation from being abandoned |
Work through the decision
Illustrative note: 'Engineering manager confirmed three teams request manual access changes. Impact is described as release friction, not yet quantified. Product lead joins evaluation on Tuesday. Finance approval role unknown. AE accepts ownership and will confirm evaluation success criteria.'
That record is more usable than 'great call; $40k; close next month.' It preserves the actual progress and gaps. If the owner changes, the successor can ask the right question rather than confidently repeat an invented business case.
The record is complete in length but empty of decisions
Long AI summaries can obscure what the buyer confirmed and what the seller inferred. Use short labeled fields and direct next actions. Review a sample by asking another seller what they would do next and why.
A concrete next step
Rewrite one active opportunity using the example structure. Have a colleague identify the next decision without a verbal briefing; repair any missing context they need.
Sources and research notes
- GitLab Command PlanCompany operating handbook
- GitLab sales development handbookCompany 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