Test finance-workflow adoption's retention impact
Strong adoption signals do not always reveal the customer outcome behind them.
Teams often have to choose between plausible explanations before the evidence is complete.
“We’re closing the books with spreadsheets around the system, and it’s getting harder every month.”
Hakon Bergstrom · Controller
Owns month-end close at a scaling subscription software company showing declining engagement with financial workflows.
What pulls against what
- correlation vs. causation
- feature adoption vs. realized value
- finance-user needs vs. technical readiness
- external benchmarks vs. customer-specific learning
What is at stake
The correlation may point to a meaningful customer need—or a misleading maturity signal. Focused learning prevents broad, low-value adoption efforts
Why Stripe
At Stripe, this can matter when recurring-revenue customers connect financial workflows to long-term payment volume.
Written for
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.