The challenge
Miro ships a major feature every month, but most customers never found them. Release notes went unread and in-app banners were ignored.
Enterprise rollouts were the bigger worry. A stalled rollout often went unnoticed until a renewal conversation, when it was too late.
How they use Path
- 1
Launches inside the product
Each release now ships with a short tour aimed only at the roles who'll use it, timed to the first time they open the relevant page.
- 2
The agent on every account
Each morning the agent reviews usage across Miro's customer base and suggests plays. The product team approves them in a few minutes.
- 3
Hand-offs with context
Accounts that need a person go to the account manager with a short brief: what changed, when, and what the agent recommends.
“The agent caught a stalled enterprise rollout two weeks before we would have. That one save paid for Path for the year.”
Results
- more users on new features in month one
- 0.0×
- more users on new features in month one
- earlier warning on stalled rollouts
- 0 days
- earlier warning on stalled rollouts
- gross revenue retention
- 0%
- gross revenue retention
Month-one usage of new features is up 3.1× compared with the year before.
The agent flagged a 400-seat rollout that had stalled after the pilot team. The account team stepped in two weeks before the customer's internal review, and the account renewed.
