GitLab publishes its entire customer success handbook. What is worth copying?

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.

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.

The most complete breakdown of what goes into a health score: which four to six categories to weight, how to segment scores by journey stage, and the failure modes (too many metrics, too much subjective input).

Customer Health Score Explained: Metrics, Models and Tools

From Gainsight 12 min read

• Sample health score weighting: usage 40 percent, support trends 25 percent, sentiment 20 percent, executive engagement 15 percent.
• Score bands used to triage accounts: 71 to 100 healthy, 31 to 70 at risk, 0 to 30 critical.
• 78 percent of customers say personalisation makes them more likely to buy again (McKinsey, 2021).

Lays out the three real ways to organise a CS team (by segment, by lifecycle stage, by engagement model) and what each one costs you, which is the actual decision a first-time CS leader faces.

Customer Success Team Structure: The Ultimate Guide

From Gainsight 16 min read

• Names three scalable structures: embedded digital experience team, centralised content with distributed strategy, and community hub with program satellites.
• Forrester's read is that most CS organisations struggle for lack of a clear charter and a segmentation framework.
• Tie each program to NRR, gross retention, time to value, renewal forecast accuracy, and health score accuracy.

Someone from inside GitLab explaining the health score the handbook only documents, including why each colour has to map to an action. Hearing the reasoning is what tells you which parts of the handbook to copy and which are GitLab specific.

Building Effective Customer Health Scores with Jeff Beaumont of GitLab - Ep. 4 | Digital CS Podcast

On The Digital CX Podcast by Jeff Beaumont 52 min