Everything from

The GitLab Handbook

2 resources from The GitLab Handbook we point people to, and the questions each answers.

📄 Article
✓ Link checked Free Advanced

A real public company's internal renewal process, published rather than described. You can copy the structure instead of inventing one from blog posts.

Customer Renewal Tracking

From The GitLab Handbook reference

  • The renewal task fires four months before the renewal date, with the internal account-team sync due inside 30 days.
  • That timing is deliberate: it leaves three months to actually change the outcome if risk surfaces.
  • The CSM opens with a soft question (how are you feeling about the renewal, any changes coming) rather than asking for the order.
  • Any hint of contraction sets CSM sentiment to red, which overrides the account's overall health to red.
Open handbook.gitlab.com
📄 Article
✓ Link checked 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.

Customer Success Playbooks

From The GitLab Handbook reference

  • 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.
Open handbook.gitlab.com
eChai Partner Brands The partnership →