Put the successor into the delivery process
An agency can deliver good short-term execution and still leave behind an unusable system. Avoid an end-of-contract document dump by naming who will inherit research, development, closing and administration before the workflows are built. Those people should see the decisions made during delivery, including errors and rejected opportunities.
Use a progression from observation to reviewed attempts to independent operation. The agency can explain and coach; the client must allocate time and make staffing decisions. If a role remains vacant, record that dependency openly rather than calling the handover complete because files were delivered.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Research successor | Can explain fit, source and disqualifier for a new account | Approves a fresh account cohort without agency correction |
| Commercial successor | Can run discovery and maintain an owned next step | Accepts or rejects an unfamiliar opportunity with reasons |
| System successor | Has access, export and recovery instructions | Resolves a controlled workflow failure independently |
Work through the decision
Illustrative example: a client hires an SDR midway through delivery and expects an existing AE to inherit closing. The training plan gives the SDR a rejected account as well as a strong one. The AE reviews an active evaluation with a missing stakeholder. The administrator practices restoring an export and routing a failed reply.
Each exercise produces an artifact: corrected account rationale, opportunity review or recovery log. Those artifacts make skill gaps visible while there is time to coach. If an exercise fails, extend the practice plan; do not hide the failure under a 'handover completed' checkbox.
Documentation is mistaken for capability
A comprehensive folder is not proof that someone can operate it. Ask an internal person to use the playbook on an unfamiliar account without live help. If they cannot decide what happens next, the material needs clearer reasoning, examples or recovery instructions.
A concrete next step
Name the future owner of each workflow and schedule one demonstration before the final delivery month. Leave enough time to repair the system or coach the person when the test reveals a gap.
Sources and research notes
- GitLab commercial sales enablementCompany operating handbook
- GitLab customer-ready shadow programCompany operating handbook
- Attio: Back up workspace dataProduct 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