How Routific Lifted Its SaaS Activation Rate by 70%

Routific raised its free-trial activation rate from roughly 40% to over 70%, and cut median activation time from 75 minutes to under 10 — with two customer success managers, zero sales reps, and no A/B tests that mattered. The person who led the effort came from sales, not product. Here is how the delivery route planning company did it, and where it nearly went wrong.

Why was activation stuck at 40%?

Routific sells route planning software to small delivery businesses. Its product-led growth model depended on a free trial converting itself. It didn't. Activation hovered around 40%.

The core problem was time-to-value. The median user needed 75 minutes to reach the first moment of value. The average was 12 hours, because many users quit and returned in later sessions. Busy owners would not commit that much time just to evaluate the software.

There was a second, uncomfortable cause. The product team followed modern UX conventions closely. Users who hadn't tried new software in years found the first interactions confusing and unfamiliar. The intended competitive differentiator — the user experience — required work to even understand.

What did investigating friction reveal?

The author, responsible for sales at Routific, started by watching session recordings of new users. Hundreds of customer conversations had not matched the motivating force of "horror footage" showing users spending an hour just to reach first value. Many frustrated users dropped off so early that no conversation with them was ever possible.

Findings went into an Airtable spreadsheet, flagging which problems hit critical mass. That data was cross-referenced with Mixpanel product analytics. The recommendation is emphatic: do this step, no matter how good you think your onboarding is.

How did they map the user journey?

Working with the senior customer success manager, the team mapped every step from signup to first value in a Miro board, one screenshot at a time. Under each step they listed the most common friction points, using a simple color system:

• Red sticky notes: critical problems
• Yellow sticky notes: potential hazards
• Green sticky notes: delightful experiences worth protecting

This made the problem space easy to communicate to a designer, verbally and visually. A developer and designer then joined, with conversations kept hyper-focused on problem understanding. Their solution-finding skills surfaced naturally once the problems were clear.

What did the product tour change?

The team set a one-quarter roadmap and an ambitious OKR: a 20% activation lift. Because most development would not land until quarter's end, they got leaner. For problems caused by lacking user education or confusing UX, they built a Product Tour to guide users through. Everyone chipped in.

The tour launched and immediately delivered a 20% lift from historical averages. Users wrote in raving, "it's so easy to use!"

So Routific doubled down. Over the following months it shipped multiple lean ease-of-use improvements, many leveraging users' familiarity with Google Maps. Mixpanel data projected each improvement's impact on activation rate and MRR, and an engineer scored work on an Impact/Effort matrix. The estimates proved accurate.

Activation rose past 70%. Average activation time dropped by over 60%. Hundreds of new users each month now activated within 10 minutes, with no help at all.

What was the business impact beyond activation?

With less need to support users through the trial, customer acquisition cost fell by roughly 25%. That proved critical when COVID-19 hit and the delivery industry boomed.

In April 2020 alone, Routific acquired almost 300 new paying subscribers with two customer success managers and zero sales reps. It also provided its software free to over 400 non-profits delivering mission-critical goods during the pandemic. Seventy percent of new subscribers upgraded before ever speaking to the company — a direct result of the self-onboarding engine.

What was the biggest regret?

The author wasted a couple of months A/B testing solutions, with small sample sizes, burning one engineer's bandwidth. The worst part: they already knew what to do. The problem understanding was complete, and confidence in the solutions was total. A/B testing is valuable under genuine uncertainty — not when you have complete confidence, and especially not when the uncertainty is really fear of failure.

What are the transferable lessons?

• Obsess about problems. Misunderstood problems produce underperforming solutions. Well-understood problems make solutions obvious.
• Map friction. Record where it occurs, how many users it affects, and its impact. A visual map keeps you lean, focused, and makes internal communication far easier.
• Don't over-analyze when you're certain. A/B test when you lack knowledge, not when you lack nerve.
• Build for them, not yourself. The weakest solutions catered to the team's own tech-native tastes; the best ones designed against those tastes for users catching up on modern UI.
• Cross-functional teams can be magic. Expect jargon friction and bad ideas from non-specialists, but a perspective that truly represents the user will move the metrics.

Routific's result points to where product practice is heading: activation work led by whoever holds the user's pain — sales, success, or product — with analytics and session recordings as the shared evidence base.