Quality needs a shared definition
Define who should attend and what the conversation is meant to establish. A plausible job title alone is not enough if the person has no relevant workflow or role in the decision. Include accurate expectations so the buyer does not arrive thinking the meeting is a different kind of call.
Have the receiving AE record specific acceptance or rejection reasons. Review a sample together to distinguish poor targeting, insufficient preparation, inaccurate qualification and seller-side follow-up problems. This makes accountability actionable instead of a recurring argument over whether a call felt good.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Before booking | Account fit, relevant role and truthful meeting purpose | Prevent unsuitable or misleading appointments |
| After the call | Buyer evidence and AE accept/return/reject decision | Assess commercial usefulness |
| During review | Reasons, denominators and corrective action | Improve the cohort and preparation |
Work through the decision
Illustrative review: a meeting is with a relevant manager but the buyer expected a free technical consultation unrelated to the offer. The problem is expectation setting, not merely role fit. Another meeting has correct expectations but an incompatible deployment requirement; targeting needs repair.
Give each a distinct reason and corrective action. Do not combine both into 'bad meeting' and request replacements without learning. Conversely, if an AE failed to attend a suitable meeting, that should not be disguised as provider quality failure.
The provider is rewarded for a number without a purpose
A fixed meeting count can encourage booking unsuitable conversations if quality is vague. Make acceptance evidence visible and inspect a sample regularly. Do not inflate pipeline to make the count appear commercially valuable.
A concrete next step
Write a quality rubric with three example calls: accepted, returned and rejected. Use it with the setter and AE before applying it to invoicing or performance reviews.
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