Use a quality funnel, not one headline number
Track selected accounts and why they fit, contacts attempted, delivery issues and response meaning. Then follow held conversations into accepted, returned and rejected handoffs. Keep the reason and receiving owner.
Review opportunities over an appropriate maturity window and distinguish commercial progression from signed value or cash. A development team influences results but may not own every later decision. Report its contribution accurately rather than attributing all revenue or all losses to the SDR function.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Coverage and relevance | Cohort criteria, roles and meaningful responses | Are we working the right accounts and questions? |
| Handoff quality | Accepted/returned/rejected records with reasons | Can AEs use the conversations without reconstruction? |
| Progression | Buyer evidence and elapsed cohort time | Are accepted conversations moving through real decisions? |
Work through the decision
Illustrative review: the team booked twelve calls, eight were held and four handoffs were accepted. Two returned records lacked role coverage; two rejections revealed product mismatch. The counts are examples, not performance targets.
Correct coverage and disqualifiers, then inspect the four accepted cases. If AEs did not act, solve the receiving capacity problem. If buyers rejected the problem, revisit qualification. A useful report maps each loss of progress to a decision and owner.
The report hides quality in an aggregate meeting rate
A meeting rate can rise while the product fit worsens. Add rejection reasons and inspect records. Keep account and contact denominators distinct so the same cohort does not produce misleading conversion comparisons.
A concrete next step
Build one cohort report from account selection through acceptance and progression. Use the rejected cases to choose the next targeting or coaching change.
Sources and research notes
- GitLab sales development handbookCompany 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