Karbon is a feature-rich global operating platform for accounting firms that needed better solutions to onboard new users.

mission

At the time, Karbon was a 200 person start-up that had historically relied on sales, implementation and customer success teams to drive growth. In 2023, the team shifted to a product-led approach where I was tasked with designing onboarding features to better engage, activate and convert customers in a free 14-day trial.

Impact

I implemented a new home page and multi-step wizards which streamlines setup activities and reduced time-to-value for customers. We didn't yet have the tooling or infrastructure to correlate experiments to retention metrics, so I strategised new metrics and used my experiments to influence our executive team to implement a more data-driven framework for measuring user acquisition and retention.

My Contribution

User Research
Product Management
UX & UI Design
Prototyping
User Testing
Measurement

CUSTOMER INSIGHT

An accounting firm manager who lacks adequate visibility over their team’s work has a hindered ability to ensure they will meet client expectations. Above all else, they're desperate for visibility and rightfully look to Karbon to address this.

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. Does that even exist? I observed and spoke to users in their 14 day free trial to better understand their motivations and expectations.

USER jobs-to-be-done

It became clear that Karbon's first-use experience poses challenges as it is a complex product that requires a lot of set up before a firm fully realises its value

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 and use 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 implementation teams. We needed a better way.

How might we simplify the setup process so managers can experience visibility and reporting, with their team's real work, from the moment they land in the app?

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. While simplifying some non-negotiable set up activities. 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.

I chose to isolate the set up steps in a guided wizard so I could craft the right story and keep users hyper-focussed on their jobs to be done

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 the tech to do the heavy lifting in the background.

This early on in their buying journey, I was very conscious of the user’s mental load and eagerness to get into the app. My focus was on crafting and iterating the right copy and story that would demonstrate value and boost their psych to helping them feel a sense of progress and remain compelled to continue. Every included detail had to count.

results

After a couple of weeks, 87% of users had made it through the new onboarding steps—69% returned for a second session.

At the time we didn't have a reliable metric or mechanism for AB testing to compare conversion impact against. Our team was okay with this trade-off given the majority of users (and likely higher quality leads) successfully completed the set up steps and we had a new baseline to improve upon.

ITERATION

Regarding iteration, there's so much I would have loved to explore here! Like the impact more personalisation might have on conversion for our different personas. But given the feature-rich nature of Karbon, our small team size and our general lack of onboarding solutions, we had bigger fish to fry...

next steps

Auditing existing journeys to identify high-impact opportunities

Up until this point, we had the signup and some basic getting started implemented. I needed to level this up. I decided mapping what the user journey looks like for our target persona (Managers/Admin in a 1-3 seat firm) is fundamental and might uncover points of friction.

I ran a few workshops with customer implementation folks to understand the minimal steps a manager in a 1-3 seat firm needed to take to get setup and learn the fundamentals. Then narrowed in on non-negotiable steps such as importing client contact records and creating client projects from pre-loaded workflow templates.

streamlining data imports

One outcome of this was that it became clear we needed a far more intuitive, self-service flow to help users bulk import their client contact data

We knew from past research that users who engage Karbon’s support team to manually import their client contact list 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, I cut the import time of thousands of rows of contact data from 48 hours to mere seconds.

Implementing scalable UI patterns to educate and onboard users at every stage of their journey

Without a dedicated Growth team or resourcing, I needed to work with patterns that would allow me to be nimble and try things quickly without breaking the bank. I pitched some new patterns to my product and design team to implement in our design system, as a starting point for more experimentation.

implementing growth metrics

To truly engage and retain users, users need to develop rewarding habits in the product that align with Karbon's core value propositions

At the time, Karbon lacked the necessary infrastructure to measure product-led growth. We knew a firm sticks at the 90 day mark but we didn't have a reliable indicator of retention (beyond daily or monthly active use) to focus our efforts. To truly engage and retain users, users need to develop rewarding habits in the product that align with real value. I hypothesised these to be:

  • Weekly inspecting work progress (Managers)

  • Daily completing tasks (Individual Contributors)

  • Daily team communication (Everyone)

To validate this, I worked with our data team to understand actions users take that lead to a higher propensity for conversion. Then, combined these insights to develop a matrix of one-time achievements that would lead users to experience value and form habits that correlate to longer-term retention. These became my north star metrics for forming new hypotheses and experiments.

Challenges faced, lessons learned, and next steps...

The power of jobs-to-be-done thinking

The breakthrough moment came when I stopped thinking about "features to demo" and started focusing on "jobs users pay for Karbon to do." Accounting firm managers weren't looking for software, they were desperately seeking visibility into their team's work. This shift from feature-centric to outcome-centric design fundamentally changed how we approached the entire onboarding experience.

Balancing simplicity with necessary complexity

Karbon's inherent complexity couldn't be wished away. The accounting workflows genuinely require detailed setup. The challenge was choreographing this complexity, not eliminating it. The wizard pattern allowed us to maintain the necessary depth while providing psychological scaffolding for users. This taught me that sometimes the solution isn't making things simpler, but making complexity feel manageable—what we termed keeping users 'on rails'.

Building for measurement in resource-constrained environments

Working without mature analytics infrastructure forced creative problem-solving. Rather than waiting for perfect measurement tools, we established proxy metrics and used qualitative signals to validate our hypotheses. This experience taught me to be resourceful with validation methods while simultaneously advocating for better measurement capabilities.

Cross-functional PLG requires organisational alignment

The most significant challenge wasn't designing the onboarding flow. It was aligning Sales, Marketing, and Customer Success around a product-led approach. Traditional sales-led organisations have embedded processes and incentives that can conflict with PLG initiatives. Success required ongoing stakeholder education and demonstrating how PLG complemented rather than replaced existing go-to-market strategies.

What would I do next given more resourcing?

Persona-specific onboarding paths: Create distinct onboarding experiences for different firm sizes and roles. A solo company owner's needs differ significantly from those of a 50-person firm's operations manager. Personalised paths could have improved both conversion rates and time-to-value.
Progressive disclosure of features: While the wizard focused on core setup, it didn't effectively introduce users to Karbon's broader feature set. I would implement a system of contextual feature discovery that reveals capabilities as users encounter relevant use cases in their daily workflow.
Stronger integration with Sales handoffs: Better coordination between the product-led trial experience and sales team follow-up. Creating clear signals for when trial users should be contacted and what context sales should have would strengthen the overall funnel.