Growth audit
Funnel analysis, cohort retention curves and a prioritized backlog of 40 ranked experiments.
We act as your growth team: a weekly test cadence across acquisition, onboarding and retention, with a written record of what worked and what did not.
We start where the leak is largest, which is rarely the top of the funnel.
Funnel analysis, cohort retention curves and a prioritized backlog of 40 ranked experiments.
A strategist, an analyst and a designer running a weekly test cycle against your backlog.
Eight weeks focused only on getting new users to their first real outcome faster.
Willingness to pay research and plan structure modeling, tested with live cohorts where possible.
Event tracking and cohort reporting so experiments can be read without argument.
Compound was built by growth leads from three subscription companies who were tired of agencies reporting only their wins. Every client gets a running experiment log with the hypothesis, the result and the call we made. Roughly a quarter of tests win, which is normal, and pretending otherwise makes teams stop testing.
“Trial to paid went from 14 percent to 23 percent over two quarters, almost entirely from onboarding changes rather than more traffic.”
Hana Y., VP Growth, SaaS
“They talked us out of a pricing change we were sure about. The willingness to pay study showed we would have lost our best segment.”
Doug E., Founder, subscription box
Typically two to four meaningful tests per week depending on your traffic. Low traffic products need bigger swings and longer read windows, and we will tell you upfront if your volume cannot support standard significance testing.
Most will. A healthy program wins on roughly one in four tests, and the wins compound while the losses cost only the time to run them. If we ever report a run of tests where nearly everything won, something is wrong with the measurement.
Some. We can ship many tests through a testing tool and existing settings, but the highest impact experiments usually touch the product. We size engineering effort in the backlog so you can prioritize against your roadmap.
Six months. A shorter run does not give enough completed test cycles to see compounding, and you would be paying for setup without the payoff.
Share read access to your analytics and billing data. The audit will show you where users are actually falling out.