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.
4 hand-picked resources, 4 link-checked. Pick how you want to dig in.
Why we picked it A real public company's internal renewal process, published rather than described. You can copy the structure instead of inventing one from blog posts.
From The GitLab Handbook reference
Open handbook.gitlab.com →Why we picked it 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.
From The GitLab Handbook reference
Open handbook.gitlab.com →Why we picked it 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).
From Gainsight 12 min read
Open gainsight.com →Why we picked it 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.
From Gainsight 16 min read
Open gainsight.com →How customer success and retention reads from a different seat.
The same ground, over in Grow & market, our Starting Up track.
The same ground, over in Grow organically & retain, our D2C track.
