Claim and evidence
Cadence calls drive week-to-week progress; business reviews assess strategy and surface new objectives.GitLab · handbook.gitlab.com · 2026-10-30
Primary
The company or founder describes the tactic and its result themselves: own blog, talk, filing.
Working · 2026-10 GitLab's handbook pages were updated in September and October 2026; they describe process, not measured outcomes.
What the numbers show
No published number for this tactic has passed our word-for-word check yet, so there is no chart.
Why it works
A written plan tied to the customer's own goals makes delivered value visible to the executives who approve spend. New objectives surfaced in the review become the natural next workstreams, which is where expansion comes from, while keeping the review itself free of renewal talk protects trust.
How to run it
- Document customer objectives in one shared success plan
- Run cadence calls on the plan's workstreams
- Prepare executive reviews months ahead with customer contacts
- In the review, show progress on past objectives and ask about upcoming initiatives
- Send follow-ups within a day and add new objectives to the plan
Ways to run it
Design options to test, not promised results.
- Option ASingle shared success plan
Keep one plan per account as the source of truth for objectives and workstreams, as GitLab CSMs do.
- Option BReview without renewal talk
Keep executive business reviews about the customer's goals, not the renewal, to protect trust.
- Option CFast follow-up
Send follow-ups soon after each review and add newly surfaced objectives to the plan.
Dated examples
- —
GitLab
GitLab customer success managers keep a success plan as the single source of truth per account and hold executive business reviews, planned about three months ahead and roughly 90 minutes long, after which the plan is updated.
“Cadence calls drive week-to-week progress; business reviews assess strategy and surface new objectives.”
✓ quote checked word-for-word on the pagehandbook.gitlab.com · 2026-10-30
Does it still work?
GitLab's handbook pages were updated in September and October 2026; they describe process, not measured outcomes. source
Risks
- Reviews that turn into sales pitches lose executive attendance
- Heavy preparation only pays off for large accounts
- A plan nobody updates becomes stale
Sources
- handbook.gitlab.com
“The EBR is a strategic touchpoint focused on aligning GitLab with the customer’s organizational objectives, not a renewal conversation.”
✓ quote checked word-for-word on the page - handbook.gitlab.com
“A success plan is the roadmap for achieving a customer’s business objectives using GitLab.”
✓ quote checked word-for-word on the page
Change log
- 2026-11-20 — harvest v0.1 (pass2-expansion-ops)