TL;DR Summary
Define first value for your SaaS, calculate median and P75 time to value, and spot the setup step that makes new users wait.
A workspace can be fully set up and still have done nothing useful. Time to value is the time from a defined start to the first result the customer came for. I’d pick that result before I put a timer on anything.
Choose the start and the finish
For self-serve, start at the first eligible account signup. For a sales-led implementation, start at kickoff if you’re measuring the implementation team. If you want to measure the customer’s whole wait, start when the contract is signed. Report those two clocks separately.
A CRM integration being authorized can be a setup milestone. The first lead arriving with its fields intact is closer to value. For a receipt tool, use an exported receipt if the customer came to send or download one.
Report the wait and the reach
Say 60 of 100 new accounts reach value within seven days. Among those 60, the median time is 20 hours and the 75th percentile is 48 hours. Report all three numbers together. If you only show the median, you leave out 40 accounts. If you cut the reach from 60% to 40% while improving the median, the story may be getting worse.
Find the part of the wait you can change
Break the journey into signup, start setup, send test data, and see the result. Look at elapsed time and completion between each pair. If the longest wait is for admin approval, rewrite the permission handoff. If a queue takes two hours to process a file, fix the queue or set a clear expectation. A new welcome screen won’t shorten either wait.
Growth mechanics, zero fluff.
Join SaaS founders and operators getting weekly notes and tear-downs on organic acquisition and churn reduction.
Pick one customer path, set a window that fits its normal usage, and compare new cohorts after the change. Keep the event definitions fixed while you test.
For the broader testing process, see my SaaS growth experiment framework.






