The challenge
Retool's implementation plan lived in a spreadsheet that each implementation manager copied and edited. Customers couldn't see their own progress, and managers chased them by email.
Product and CS also measured account health differently, so every renewal review started with an argument about which numbers to trust.
How they use Path
- 1
The spreadsheet became a checklist
Each implementation step is now a checklist item that completes when the matching event arrives from Retool's API.
- 2
One health model
Product and CS agreed on five signals, backtested them against last year's renewals and switched over in a week.
- 3
Alerts instead of chasing
When a customer stalls on connecting a data source, the implementation manager gets a Slack alert with the account's history attached.
“The health score finally gave product and CS the same view of an account. Our Monday renewal meeting takes half the time.”
Results
- of implementations now self-serve
- 0%
- of implementations now self-serve
- shorter average go-live
- 0 days
- shorter average go-live
- shorter renewal reviews
- 0%
- shorter renewal reviews
63% of new customers now complete implementation without a scheduled call. Average go-live is nine days shorter.
Renewal reviews start from the same health score, and the weekly meeting has dropped from two hours to one.
