Renewal risk is split between account history and the usage signals that should explain it.
CSMs need earlier priorities, while account owners need evidence strong enough to stand behind in a customer conversation.
Who you’d be doing this for
“Our renewal meeting is next month, and I’m still being asked why some teams never moved their pipelines over.”
Ebo Gbadamosi · DevOps Engineering Manager
Runs CI/CD for a self-managed customer whose renewal discussion depends on whether platform adoption is delivering operational value.
What is at stake
CSMs are preparing renewal conversations from conflicting usage and support evidence. You must weigh earlier risk detection against ranks that a CSM can verify and defend.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- earlier renewal risk vs. defensible evidence
- AI ranking vs. CSM judgment
- usage signals vs. support context
- pilot speed vs. durable handover
Why Gitlab
GitLab usage, Customer Success Plans, and Zendesk history sit close enough to connect CI/CD adoption with renewal risk.
Written with these in mind
Not your kind of problem? 26 more at Gitlab, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.