I'd heard time and time again that customers choose Karbon for its solution to work management, only then to discover what our email integration feature can do for their collaboration and communication—our stickiest feature. But I didn't have a definitive answer to what the golden moment is in a free trial that convinces a firm that Karbon is right for them. I observed and spoke to users in their 14 day free trial to better understand their motivations and objectives.
For example, to experience work visibility and reporting—a critical "aha!" moment—an operational leader would need to:
Build efficient workflows: Setup automated workflows in bulk, assign things like budgets, team roles, and deadlines, before inviting the wider team to experience workflow in Karbon.
Import client contact data: Client workflows are connected to hundreds if not thousands of client contacts. So detailed contact data needs to be imported in bulk before workflows can even be created.
Make individual contributors love Karbon: Only once client work and contacts are set up can individual contributors in the team use Karbon and find value in completing daily tasks and keeping their assigned projects up-to-date—this is required in order for the manager to benefit from that visibility and know work is being delivered on time.
Historically, these things all required hands-on assistance from Karbon’s Sales and Implementation teams. We needed a better way.
The key to successfully converting a new trial user into a paid customer would be for the product to effectively guide them toward realising the value of Karbon during their initial session. My goals were to:
Clarify that Karbon enhances workflow and team visibility.
Visualise the team's real projects on a Kanban board.
Invite the first team (3–5 members).
Guide them to reporting features to drill down on team progress.
To achieve a populated dashboard of client projects, users need to jump through a series of steps that happen in different areas across the app. So I chose to isolate these steps in a guided wizard to keep users focussed on only the actions they need to take, and let Karbon to do the heavy lifting in the background.
Conscious of the user’s mental load and mindset this early on in their buying journey, my focus was on crafting and iterating the perfect story that would compel users to continue, by boosting their psych and helping them feel a sense of progress and achievement. Karbon won't be the only tool they're evaluating, so if this is as far as they get, first impressions need to count for a lot.
Working closely with the Project Manager, I set up an Amplitude funnel to monitor results. It’s still early days, but 88% conversion is looking pretty promising given the amount of friction we introduced to accessing the free trial. Most importantly, users are making it through the flow and now I have a baseline to improve upon.
The primary reason for customer churn at Karbon is failure to launch. To truly engage and retain users, users need to develop rewarding habits in the product that align with Karbon's core value propositions, so they have more and more reasons to come back.
Weekly inspecting work progress (Manager)
Daily completing tasks (Individual Contributor)
Daily team communication (Everyone)
Karbon currently lacks the necessary infrastructure to measure product-led growth. So before leveraging opportunities to draw users back into the product, I'm working with senior product and customer leaders to define and implement a health score to measure user and team activation—that is—actions users can take that align to these retention loops. Then I'll be better equiped to guide users towards this behaviour and understand the impact of future onboarding experiments.
Before firms can set up more client work for their team, they need to import their client contact list. We know from past research that users who engage Karbon’s support team to manually import their client contact data convert at greater than 70%, and this is one of the stickiest activation activities a new user can take.
In a 3 week sprint, I worked with one product manager and two engineers to build a wizard aimed at delivering the shortest route for a new user to achieve a populated client list on their own. By reducing the required contact data fields down to the minimum, we were able to cut the import time of hundreds of contacts from 48 hours (via support) to mere minutes.
Onboarding occurs to varying degrees throughout the entire customer lifecycle but is especially impactful in the evaluate, implement, and adopt stages, to drive acquisition and help users establish positive habits. In a start-up environment, I need to juggle limited engineering resources and competing priorities, so future onboarding experiments must be scalable.
Evaluate: I think of evaluating a bit like dating. The first session is a user’s first date where they will consider; ‘Is this product interesting to me?’—We have minutes, if not seconds, to convince them that we are worth a second, and third, and fourth date and so on.
Implement: I think of implementation more like moving in together. The user wants to know; ‘I am doing this right so it will work for the long term’. We need to pave the shortest path to onboard users onto features they can get immediate value from.
Adopt: Adoption requires a combination of dating and moving in together. The user is drawn into increasingly complex and deep aspects of the product to become power users. Deep learning is required and additional feature areas begin the dating and implement phase all over again.