How do I build a renewal and expansion process that runs without me in every deal?

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.

A three-step forecasting framework plus the honest list of what breaks it (cross-team data gaps, non-recurring revenue, scale). Useful when your renewal forecast keeps missing.

A data-driven framework for customer success renewals forecasting

From ChurnZero by Chris Pilbeam 10 min read

• Lists five forecasting approaches: linear regression, cohort analysis, time series, machine learning, and top-down or bottom-up.
• Anchors the forecast on six tracked numbers: MRR, ARR, customer lifetime value, CAC, churn rate, expansion revenue.
• Without enough clean historical data you will read random fluctuation as a trend.

The single most common cause of a surprise churn, handled step by step, including the 48 hour window for reaching the new contact and the 'you, we, me' meeting structure.

Did your customer champion leave? Use this five-step playbook to reduce churn risk

From ChurnZero by Emily Nesterick 9 min read

• When a customer champion leaves, there is a 51 percent chance the account churns within 12 months.
• 65 percent of accounts that see an executive change do not renew their SaaS contract.
• Acting inside the first 48 hours makes that customer 33 percent more likely to renew.
• Only about half of customer success teams have a play for a key contact leaving.

Two Indian SaaS founders on how they structured customer success, made the first hire and defined the handoffs, which is how a renewal stops depending on you being in the deal. Chapter marked, so you can jump to the structure and ownership sections.

SaaS Talks #32: Customer Success feat. Manan Shah, Recruiterflow & Varun Sharma, Enterpret

On Stellaris Venture Partners by Manan Shah and Varun Sharma 54 min