We spent eight weeks listening, and what we heard surprised us in the kindest way.
The team ran twenty-eight long-form interviews, shadowed nine teams during their busiest week of the year, and sat with the support inbox for ten unbroken days.
The themes that emerged were not the ones we set out to find. The brief asked about onboarding; the answers we got were about trust. So we followed the thread.
This deck is the short version. Each insight is a door — open the ones that matter to your team this quarter, and let the others wait.
Twenty-eight long-form conversations with customers across four segments and three regions.
Nine on-site shadowing sessions during peak workflows. We took notes, not video.
Ten days inside the support inbox, tagging every message by intent and emotional tone.
Three rounds of thematic clustering with the design and policy teams, ending in eight themes.
Customers don't churn on day one because the product is hard. They churn because the first three emails feel like a stranger.
The people we asked to love new features the most quietly resent them. They want fewer surprises, not bigger ones.
Half of "feature requests" in the inbox are existing features that customers couldn't find. We have a discovery problem dressed as a roadmap problem.
The product can be perfect on day one, but if the welcome email reads like a contract, half of new accounts will never log in twice. The fix is small and writerly, not technical.
I did not need a better product. I needed it to behave like it remembered me.
Each one is small enough to ship inside a sprint, and structured so we can tell, six weeks from now, whether it moved the dial.
From templated to written. Owner: lifecycle. By: May 17.
Opt-in for power users; soft rollout for everyone else. Owner: product. By: June 1.
Surface in-product help when a request matches a feature. Owner: support × product. By: June 14.
Three behavioral signals in the first 72 hours predict 18-month retention better than any feature-usage metric we tracked.
The first three days are the only window where customers are both paying attention and willing to write back. Every interaction during this window does the work of roughly four interactions in week three.
The cost of getting this wrong is not refunds — it is the long, quiet churn of an account that never returns to the inbox.
Cohorts that received a written welcome and a human reply within 24 hours retain at roughly 2× the rate of the templated cohort, and the gap holds steady for the first ninety days.
Translate the insight into a single behavioural hypothesis we can falsify.
Sketch the smallest end-to-end change that lets the hypothesis be tested in one sprint.
Ship to a 50/50 holdout in a single segment. Hold the line for two full cycles.
Review the cohort against pre-registered metrics. Decide kill, scale, or extend.
Graduate the change to the default surface. Retire the legacy path inside the same release.