Name a decision owner, not just a task owner
Responsibility means more than completing an activity. A researcher owns the reasoning behind an account; a seller owns the decision to accept an opportunity; an administrator owns recovery when an integration fails. Writing those responsibilities makes handoffs reviewable.
Define who is accountable, who provides expertise and who approves exceptions. For example, a partner can lead an evaluation while the client's engineer confirms technical feasibility. An outsourced AE can negotiate inside agreed terms without being authorized to promise new product features. These boundaries protect both buyer experience and delivery credibility.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Account and conversation | Partner creates evidence, handles replies and proposes next action | Client supplies product context and suppression requirements |
| Evaluation and terms | Commercial lead manages plan and approved negotiation | Client approves product, legal and exceptional price commitments |
| Hiring and ownership | Partner supports assessment, coaching and transfer | Client makes employment decisions and retains administration |
Work through the decision
Illustrative operating agreement: the external team can qualify accounts, schedule discovery and negotiate within an approved price range. A discount outside the range goes to a named client approver. Security questions go to the client expert, with a deadline and owner recorded in the opportunity.
If an approver is unavailable, the fallback is a truthful buyer update and revised next step—not an unauthorized promise. Review the map whenever a new stage or tool is introduced. A responsibility model that cannot handle absence is incomplete.
Everyone collaborates; nobody is accountable
Collaborative language often masks an unowned task. For each important buyer action, ask who notices a missed deadline and who fixes it. If both teams expect the other to respond, the agreement needs a single accountable person and an escalation route.
A concrete next step
Write a responsibility map for one active deal and one system failure. Test it with the people named in it; an owner who does not recognize the responsibility has not actually accepted it.
Sources and research notes
- GitLab sales operating proceduresCompany operating handbook
- Attio: Sharing and permissionsProduct documentation
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