How the best do it

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

Three things. The renewal tracking process, because it shows what a renewal looks like as an operational pipeline with stages and owners rather than a date in a spreadsheet. The health scoring model, where green explicitly means 'expand or renew flat', so the score maps to an action instead of a colour. And the playbooks, which are written per product stage with assets attached, which is what separates a play from a suggestion. Read it as an org design document. The specific DevOps content will not apply to you, but the shape of a CS function that scales to a public company will.

Go deeper

5 resources, 5 link-checked.

📄 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
📄 Article
✓ Link checked Free Intermediate

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).
Open gainsight.com
📄 Article
✓ Link checked Free Advanced

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.
Open gainsight.com

Browse all 796 resources →

The same ground, at another level

How customer success and retention reads from a different seat.

Terms in this answer

People also ask

Also in Starting Up

The same ground, over in Grow & market, our Starting Up track.

Also in D2C

The same ground, over in Grow organically & retain, our D2C track.

eChai Partner Brands The partnership →