The challenge
Asana's customers need to build a real project before they see any value. The first project took most teams three to four weeks, and the CS team could only walk the largest accounts through it.
Smaller customers were left with a help centre and a welcome email. Many never finished their first project, and they made up most of the churn at renewal.
How they use Path
- 1
A checklist built from their best customers
Path's activation report showed that teams who imported a project plan in week one renewed at almost twice the rate. That became step one.
- 2
Guides at the hard parts
Three short tours now cover the steps where users used to open a ticket: mapping custom fields, setting a timeline and sharing a project.
- 3
Health scores in every QBR
CSMs review their book sorted by health score each Monday and use the agent's suggestions to decide who gets a call.
“We used to onboard our top fifty accounts by hand and hope the rest figured it out. Now every customer gets a guided start, and my team spends its time on the accounts Path tells us are slipping.”
Results
- faster time to first value
- 0%
- faster time to first value
- adoption of new features
- 0.0×
- adoption of new features
- fewer accounts churned
- 0%
- fewer accounts churned
Median time to a first shared project fell from 24 days to 14. Feature adoption roughly doubled for the two releases Asana shipped after rollout.
Logo churn fell by 18% over the following four quarters, with the largest drop among accounts that never had a dedicated CSM.
