Article · reference
Customer Success Playbooks
The GitLab Handbook Free Advanced
Shows what a productised CS play looks like when written down for a whole team: a named motion, tied to a product stage, with the assets attached. Rare to see this published.
- Sorts every play by trigger type: risk, lifecycle event, opportunity or expansion, objective, activity, digital journey.
- Risk plays are named off observable signals, for example low license utilisation, non-engaged customer, product risk.
- Each playbook has the same four parts: procedure, positioning, discovery questions, and an adoption map.
- Every play is marked automated or manual, so only some fire without a human deciding.