Most SaaS teams have an onboarding problem they can't see.
Their completion rates look fine. Users are finishing the checklist. NPS scores from the first week are positive. And then, somewhere between week two and the first renewal conversation, customers start going quiet.
The issue isn't that they had a bad experience. It's that they never actually got productive. They clicked through the onboarding flow, confirmed they understood the features, and then hit real work... and nothing felt as smooth as the demo.
That gap between "completed onboarding" and "actually productive" is where churn lives. And the reason most teams miss it is that they're measuring the wrong thing.
The metrics that feel useful but aren't
There's no shortage of onboarding metrics to track. Completion rate. Time to first login. Feature activation rate. CSAT after the kickoff call. NPS at day seven.
These metrics aren't useless. But they all measure engagement with the onboarding process, not outcomes from it.
A user can complete every step of your onboarding flow and still have no idea how to run their first real workflow unsupported. An NPS score of 9 at day seven tells you they liked the experience. It tells you almost nothing about whether they'll still be a customer at month six.
That's the only thing worth measuring: how long it takes a new user to do the thing they signed up to do.
What "time to productivity" actually means
Time to productivity (TTP) is the interval between a user's first login and the first time they complete a core workflow independently, without hand-holding and without referencing docs, without contacting support.
Note the word "independently." That's the part most definitions skip. A user who runs their first campaign because a CSM walked them through it hasn't reached productivity. A user who does it again the following week, unprompted, has.
The exact definition of "productive" will differ by product. For a CRM, it might be logging a completed deal. For a project management tool, it might be creating and assigning a project with at least three active tasks. For an AI writing assistant, it might be publishing a first piece of content that wasn't edited in the app.
Why TTP predicts retention better than anything else
The connection between fast TTP and retention isn't intuitive to every team, but the data is consistent.
According to Gartner's 2025 Software Buying Trends report, 59% of SaaS buyers regret at least one software purchase their company made in the last 18 months, with adoption challenges and productivity loss cited as the top reasons.
That's an onboarding problem, specifically, a failure to get users to productivity before they form the opinion that the product isn't working for them.
The dynamics are straightforward. A user who reaches productivity quickly forms a positive association between effort and reward. They have a reference point: they know the product works, because they've seen it work. Every subsequent session builds on that foundation.
Time to productivity is a measurable interval from a defined start point to a defined end point. Track median days to productivity by segment. SMB customers should hit productivity in under a week for most products; mid-market in under 14 days; enterprise customers in under 30-45 days depending on complexity.
Most teams don't have these numbers. They should.
The hidden cost of long TTP
There's a financial argument here that doesn't get made often enough.
Every day a new customer spends in onboarding without reaching productivity is a day they're paying for software they can't yet fully use. In an annual contract, that's abstract. In a monthly plan (or worse, a usage-based model) it becomes a real question: did we actually get value from this last month?
Every week you compress off the ramp is a week your customer starts generating value, and a week closer to the point where they're advocating for the product rather than questioning it.
Long TTP also has a support cost that compounds. Users who aren't productive generate tickets. They consume CSM time. They book calls that could have been documentation.
How to measure it without overcomplicating it
- Identify your productive user moment. The specific action or sequence of actions that reliably predicts a user will stick around. You probably already have a hunch about what this is.
- Validate it against retention data. Look at users who churned in the first 90 days versus those who didn't, and find the behavioral difference. That difference is usually your productive user moment.
- Measure the interval. Time from first login (or contract start) to first occurrence of that event. Track it as a median, not an average. Outliers will distort the average in ways that obscure what's typical.
- Segment by customer type. Enterprise accounts will always have longer TTP than self-serve SMB users. Combining them masks what's actually happening in each segment, and the levers that shorten TTP will differ completely between them.
- Use it to drive decisions. If your median TTP for mid-market customers is 21 days and your goal is 14, that's a roadmap input. Which step has the longest drop-off? Where are users contacting support most in their first two weeks? TTP gives you a number to move, and moving it has direct downstream effects on the metrics your board actually cares about.
What good onboarding actually optimizes for
There's a tendency in product teams to think of onboarding as a UX problem: make the flow cleaner, the tooltips clearer, the checklist shorter. Those things help. But the best onboarding teams think about it differently.
They ask: what's the fastest legitimate path to the outcome the user came here for? Not the fastest path through the product tour. The fastest path to the first real win.
That framing changes everything.
It means skipping features that aren't relevant to the user's immediate goal, even if those features are impressive. It means pre-configuring things the user would have to set up themselves. It means understanding what role the user is in and what their first week looks like, rather than showing everyone the same generic flow.
The number to put on the wall
If you're a founder or a product lead reading this and you don't currently have a TTP figure for your main customer segments: that's the thing to fix first. Not the onboarding email sequence. Not the tooltip copy. Not whether the loading animation is fast enough.
What's the median number of days between a new customer's first login and the first time they complete a core workflow independently? If you don't know, find out. If you know and you don't like the number, work backwards from it.
Every other onboarding metric is either a proxy for this one or a measure of something that doesn't predict retention. Completion rates tell you users are compliant, not capable. NPS tells you users are happy, not successful. Time to productivity tells you whether your onboarding is actually working.
That's the only question that matters.
FAQ
What's the difference between time to value and time to productivity?
Time to value (TTV) typically refers to the first moment a user experiences a benefit from the product — sometimes called the "aha moment." Time to productivity (TTP) is a higher bar: the point at which a user can complete a core workflow independently, without assistance. TTV might come earlier (a user sees a demo-like result in a guided walkthrough), but TTP is what predicts whether they'll stick around.
How do you define the "productive user moment" for your product?
Start with retention data. Look at users who stayed past 90 days versus those who churned, and identify the behavioral difference — typically a specific action or sequence of actions in the first two to four weeks. That event is usually your productive user moment. Validate it by checking whether users who hit it have materially higher retention than those who don't.
Is time to productivity only relevant for complex SaaS products?
No — but the benchmark varies. Simpler self-serve products should expect TTP measured in hours or days. Enterprise products with complex integrations might accept a 30-45 day window. The key is knowing what your TTP is, tracking it by segment, and treating it as a number to improve rather than an inevitable function of product complexity.
What's a reasonable TTP benchmark for a B2B SaaS product?
It depends heavily on product complexity and customer segment. A useful rule of thumb: SMB customers on self-serve products should reach productivity within a week; mid-market accounts within two weeks; enterprise with implementation work within 30-45 days. If your numbers are significantly outside these ranges, onboarding is likely costing you renewals.
Can you improve TTP without a major product overhaul?
Usually, yes. The biggest TTP gains typically come from reducing configuration friction (pre-filling sensible defaults, building integration templates), personalizing the onboarding path by role or use case, and identifying the single step with the highest drop-off and fixing that first. Full product redesigns are rarely the answer.
