Stop Chasing an Onboarding Timeline That Isn't Yours

I was in a working session with a company recently, doing what I usually do: digging into their onboarding process. Somewhere in that conversation, a familiar number came up. Ninety days. That was the timeline they were pushing every customer toward, the number stamped on internal decks and used as the measuring stick for whether onboarding was "working."

So I asked the obvious question. What percentage of customers were actually hitting that 90-day mark?

Eighty percent were not.

Sit with that for a second. If eight out of ten customers are blowing past your target, that's not a customer problem. That's not a "we need better project management" problem. That's a sign the number itself was never real to begin with.

Then I asked where 90 days came from. Why that number, specifically. I didn't get a real answer. Not a data point, not a customer insight, not a benchmark tied to their product's actual complexity. It was just a number that sounded reasonable at some point, probably in a planning meeting where nobody wanted to be the one to say "I don't know."

The timeline is about you, not them

Here's what's actually happening when a company clings to a timeline most of its customers can't hit: the timeline was never designed around the customer. It was designed around internal goals. Maybe it's tied to a board metric. Maybe someone read it in a LinkedIn post or heard it on a podcast and decided it sounded like the industry standard. Maybe it just felt like a clean, round number that would look good in a QBR.

None of those are reasons. None of those have anything to do with what it actually takes for your specific customer, with your specific product, to get to value.

And that's the distinction that gets lost. Time to value matters. I'm not arguing against urgency or against giving customers a reason to move quickly. But your timeline and someone else's timeline are not the same thing, and pretending otherwise is how you end up designing an onboarding process that looks good on paper and fails in practice for the majority of the people going through it.

Why 90 days might genuinely be the wrong number

There are real reasons a timeline might be unrealistic, and none of them are about effort or willpower. Product complexity is one. If your platform requires real configuration, training, and behavior change, you cannot compress that into the same window as a plug-and-play tool. Data and integration requirements are another. If a customer needs to connect three systems and migrate historical data before they can even see the product working, that alone can eat weeks.

Then there's resourcing and bandwidth, both yours and theirs. Your team might be stretched thin trying to hit an artificial deadline, cutting corners in ways that create rework down the line. Your customer's team might have one person juggling this implementation alongside their actual day job. And priorities shift. What felt urgent to a customer in week one might get deprioritized by week four because something else caught fire internally.

Any one of those factors can blow up a 90-day plan. Most companies are dealing with several at once, and still holding onto the same arbitrary number like it's gospel.

Design backwards from the customer, not forwards from a deadline

If you're serious about fixing this, the fix isn't a new number. It's a new process for getting to the number, one that actually starts with the customer instead of starting with a goal you want to hit.

Start by mapping out what genuinely needs to be true in your product before a customer can build the workflow that gets them to value. Not what you wish were true. What's actually required, step by step, for this specific use case to function.

From there, look hard at the blockers. What tends to slow customers down or knock them off track during onboarding? Those blockers are usually predictable if you're honest about them, and most companies aren't, because acknowledging them means admitting the process has gaps.

Look at your actual data. Not the timeline you want, the timeline you're getting. What is the real average time to onboard today, and where specifically does it slow down? That's your starting point for optimization, not some external benchmark.

Consider who you're actually onboarding. Are these highly technical users who move fast, or are they people with a steeper learning curve who need more hand-holding? A 90-day plan built for a technical power user is going to crush a less technical team, and that mismatch shows up as frustration, disengagement, and eventually churn.

And finally, look at what you're actually asking customers to do. Is the scope too heavy? Could you break it down, sequence it differently, or cut steps that don't actually move the needle toward value? Sometimes the fastest way to hit a faster timeline is to ask for less, not to push harder.

The cost of chasing a made-up number

I could keep going, because there's no shortage of variables that go into designing implementation and onboarding well. But the point stands regardless of how deep you go. When you force customers to hit a timeline that was never built around them, you don't just risk missing the deadline. You throw the entire project off track, you create friction at the exact moment you're trying to build trust, and you leave your customer with a bad taste in their mouth before they've even gotten to see your product deliver real value.

That's an expensive way to start a relationship you're hoping will renew and expand for years.

The better path is slower to set up and faster to pay off. Design something realistic. Something built around where your customers actually are, not where you wish they were. Meet them there, and build the path that gets them to where they need to be, on a timeline that reflects reality instead of a number someone made up in a planning meeting.

Your customers will notice the difference. So will your retention numbers.