SaaS Club
PodcastPlaybooksCoachingSponsorFree ToolsJoin Community
saasclub

Helping SaaS founders build and scale profitable businesses since 2014. Powered by real experience from 473+ founder conversations.

Content

  • The SaaS Podcast
  • Founder Playbooks
  • Blog
  • Newsletter
  • Free Tools

Programs

  • Plus
  • Launch
  • Mastermind
  • Accelerate

Company

  • Contact
  • Become a Sponsor
  • Suggest a Guest
  • Terms
  • Privacy

© 2026 SaaS Club. All rights reserved.

Built with ❤️ for SaaS founders

Home/The SaaS Podcast/Episode 122
How Chameleon Validated the SaaS Onboarding Problem
Pulkit Agrawal, Chameleon

How Chameleon Validated the SaaS Onboarding Problem

Introduction to Chameleon and the onboarding problem

0:00Loading…
Listen on:

Like this episode?

Get real founder strategies for the AI era. Delivered weekly.

Free weekly newsletter · No spam

Episode Summary

Most SaaS companies spend heavily on customer acquisition but lose users the moment they try the product. Pulkit Agrawal saw this SaaS onboarding gap firsthand when fixing it produced a 3x improvement in retention.

In this episode, Pulkit shares how he and his co-founder validated Chameleon's idea by cold emailing YC startups, built their first version as a consulting project, and raised $1.9 million from angels and VCs - all while working evenings and weekends before going full time.

Pulkit Agrawal noticed a pattern while working at a previous startup: companies were spending heavily to acquire users, but those users would sign up, get confused by the product, and leave. When his team spent two to three months fixing the onboarding experience, retention improved by 3x. That result stuck with him.

After leaving to freelance, Pulkit kept hearing the same complaint from SaaS companies: "We need to fix our onboarding, but we haven't had time." Nobody knew what good SaaS onboarding looked like, engineering teams wouldn't prioritize it, and there was no go-to tool to solve it.

So Pulkit and his co-founder built Chameleon - a platform that lets companies create product tutorials, tooltips, and guided tours without writing code. They validated the idea by cold emailing YC startups, found one willing to let them build their onboarding, and slowly turned that consulting work into a product.

The company raised $1.9 million after an angel investor who had sold his own SaaS company validated the problem with his network. In this first part of a three-part interview, Pulkit explains how he identified the SaaS onboarding opportunity, what the validation process looked like, and why every SaaS company eventually needs to solve this problem.

Topics: Product-Led Growth|Churn & Retention

Key Insight

Pulkit Agrawal validated Chameleon by cold emailing YC startups to find one company willing to let him build their onboarding for free. That consulting-to-product approach, combined with a 3x retention improvement from fixing onboarding at a previous startup, proved the market before Chameleon raised $1.9 million in seed funding.

Key Ideas

  • Fixing SaaS onboarding at a previous startup produced a 3x improvement in long-term user retention
  • Pulkit validated the problem through informational interviews showing companies consistently deprioritized onboarding because it depended on engineering time
  • Cold emailing YC startups yielded one early customer willing to let Chameleon build their onboarding, creating a testing platform for the product
  • The team started evenings and weekends, only going full time once demand made part-time work unsustainable
  • One angel investor who had recently sold a SaaS company validated the problem with his network, unlocking the full $1.9M seed round

Key Lessons

  • 🎯 Fix SaaS onboarding before spending more on acquisition: Pulkit saw 3x retention improvement from two to three months of onboarding work at a previous startup. Better activation compounds over time while acquisition costs only grow.
  • 🛠️ Cold email potential customers to validate your SaaS onboarding idea: Pulkit emailed YC startups offering to build their onboarding for free. One said yes, giving Chameleon a live testing environment and real user feedback.
  • 🔄 Abstract consulting work into a SaaS onboarding platform: Chameleon started by building custom onboarding for one client, then parameterized each component into a reusable product. This consulting-to-product path validates while you build.
  • 💰 One credible investor unlocks the whole round: Angel investor Arne Hoffman validated the SaaS onboarding problem with his network, then introduced Chameleon to other angels. The bulk of the $1.9M seed round came through his connections.
  • 🚀 Start part-time and let demand pull you full-time: Pulkit began with a few hours per week and only went full time when customer demand made part-time work unsustainable. Gradual commitment reduces risk while testing the market.
  • 📉 SaaS onboarding is deprioritized because it depends on engineers: Companies consistently told Pulkit they knew onboarding was broken but couldn't justify pulling engineers from core features. Removing that dependency was Chameleon's key insight.

Chapters

00:00Introduction to Chameleon and the onboarding problem
01:53Pulkit Agrawal's background - from England to San Francisco
03:22Favorite quote on conscious choices and determinism
04:09Meditation and the 10-day silent Vipassana retreat
05:48What Chameleon does - in-product guidance without code
07:33How the idea for Chameleon originated
08:30Seeing 3x retention improvement from better onboarding
09:20Validating the problem through informational interviews
10:00Cold emailing YC startups for early customers
11:37Starting as a side project on evenings and weekends
12:23Raising the $1.9 million seed round
13:25How investor reactions shaped the fundraise
14:30One angel investor unlocking the round
15:06The market opportunity beyond onboarding
16:30Feature discovery and in-app help use cases
18:03Wrap-up of Part 1

Episode Q&A

How did Pulkit Agrawal validate the SaaS onboarding problem before building Chameleon?

Pulkit spent a month doing informational interviews asking SaaS companies about their onboarding pain points. He consistently heard that companies knew onboarding was broken but lacked the time, knowledge, and tools to fix it.

What retention improvement did Pulkit Agrawal see from fixing SaaS onboarding?

At a previous mobile startup, Pulkit's team spent two to three months refining the onboarding experience and saw a 3x improvement in long-term retention - proving that first-time user experience has an outsized impact on engagement.

How did Chameleon get its first customer for SaaS onboarding?

Pulkit cold emailed startups from the YC list, offering to build their onboarding. One small company agreed, giving Chameleon a live environment to test code and gather feedback while abstracting the work into a reusable platform.

Why do most SaaS companies neglect user onboarding according to Pulkit Agrawal?

Three reasons: companies don't know what good onboarding looks like, engineering teams won't prioritize it over core feature development, and there was no go-to tool for solving it - which is exactly the gap Chameleon was built to fill.

How did Chameleon raise $1.9 million in seed funding?

An angel investor named Arne Hoffman, who had recently sold his own SaaS company, got excited about the SaaS onboarding problem and validated it with his network. His backing gave other investors confidence, and the round came together quickly through angel introductions and one seed-stage VC.

What is Chameleon's approach to SaaS onboarding without code?

Chameleon lets companies drop in a JavaScript snippet, then use a drag-and-drop wizard to build product tutorials, tooltips, and guided tours. Teams can run A/B tests, show variations to different users, and collect analytics - all without engineering involvement.

How did Pulkit Agrawal transition Chameleon from consulting to SaaS onboarding product?

While building custom onboarding for their first client, Pulkit and his co-founder abstracted each component into a reusable platform. They found additional customers willing to pay upfront, gradually shifting from one-off projects to a scalable product.

What SaaS onboarding use cases does Chameleon address beyond new users?

Chameleon handles feature discovery for new releases, in-app help that walks users through flows instead of static documentation, and adaptive UI that changes interface components based on user type - all aimed at improving product education.

Why did Pulkit Agrawal start Chameleon as a side project before going full time?

Pulkit and his co-founder started with a few hours per week while freelancing. As demand grew, the work naturally consumed more time until going full time became necessary. This gradual transition let them validate the SaaS onboarding market without financial risk.

Book Recommendations

Child of the Dawn

by Gautam Chopra

Links

  • Chameleon: Website
  • Omer Khan: LinkedIn | X
Full Transcript

Omer (00:11.840)
Welcome to another episode of the SaaS Podcast.
I'm your host, Omer Khan, and this is the show where I interview proven founders and industry experts who share their stories, strategies and insights to help you build, launch, and grow your SaaS business.
This week, I talked to a founder who helps other startups and online businesses do a better job at explaining their products to their customers.
He realized that these companies were working really hard and spending lots of marketing dollars to acquire new customers, but they were also losing a lot of these people because as soon as they tried using the product, they'd get confused and give up.
You've probably had that experience yourself.
I know I have.
So he decided to build a software product to solve that problem.
This is part one of a three part interview, and in this episode we talk about how my guest came up with his startup idea and what he did to turn that idea into a product and business.
All right, today's guest is the co founder and CEO of Chameleon platform that helps with user onboarding for your product.
With Chameleon, you can quickly build, test and deploy product tutorials and tooltips without writing any code.
And it collects analytics to give you the data to help you learn how your users are onboarding so you can use that information to improve the onboarding process.
The company was founded in 2015 and to date has raised $1.9 million in funding.
So today I want to welcome PA Pulkit Agrawal.
Pulkit, welcome to the show.

Guest (01:53.200)
Thank you very much.
Excited to be here.

Omer (01:55.200)
Now I'm very excited because you are a fellow Brit and we are both on the west coast of the US and, you know, I think you have more of an English accent than.
My mind sort of has been fading away over the last 10 or 12 years.

Guest (02:10.640)
Well, I try.
It's a competitive advantage.
It's one I feel guilty about, but I want to make use of it.

Omer (02:18.890)
Oh, you're from England.

Guest (02:19.850)
Cool.

Omer (02:21.930)
Yeah.
I always tell these people this story about going into Starbucks.
Like, the first three months I was here in Seattle and I just wanted a bottle of water.
And the person working, they just could not understand what I wanted.
And I had to say it three times.
And then eventually I had to say, I want a bottle of water.
And then it was like, oh, okay, I get it.

Guest (02:47.490)
So, yeah, well, it's like my first few months and probably still even now, you know, I go into Starbucks and ask for a bottle of water and the conversation is about, oh, you're from England, how's London?
Just give me the water please.

Omer (03:00.370)
So you moved, you moved over to San Francisco.
When?

Guest (03:04.530)
A few years ago?
Yeah, 2013.

Omer (03:08.850)
Cool.
Okay.
So one thing I always like to start by asking my guests is what drives them.
Some people have a quote, some people don't like quotes.
So do you have a quote?
If not, what is it that gets you out of bed every day?

Guest (03:22.870)
I do have a quote.
So it's maybe because it's a simple quote that I can remember it, but here it goes.
When we are conscious of the choices we make in each moment, the future takes care of itself.
And that's a quote by Gautam Chopra, who's son of Deepak Chopra in his book Child of the Dawn.
And that quite resonates with me because it puts a lot of focus on the present moment and it kind of makes the future less uncertain, less unpredictable, less risky because it tells me that, well, the things that are going to happen are being created today.
I resonate with the philosophy of determinism.
And so that's something that always recenters me to, well, what am I doing?
And knowing that I'm the owner of the choices that I'm making today.

Omer (04:09.190)
Did I read in on your about page somewhere that you also meditate?

Guest (04:15.750)
I do, yeah.
I first, I guess growing up in Indian culture, you know, heard of meditation, yoga, etc.
As a kid.
But my first real experience of it was while I was in India doing some social development volunteering work.
And at the end of the time I went on this 10 day retreat, silent retreat for a meditation course where they teach you this technique and it's a non religious technique called vipassana.
And so that's been pretty seminal I think, in helping me stay calm and relaxed and take things and do perspective.
So I'm not shamefully, not as regular as I'd like to be, but it definitely has helped me along in many times.

Omer (04:58.840)
So a 10 day retreat, like nobody talked for 10 days?

Guest (05:02.600)
Like nobody talked for 10 days.
Yeah.

Omer (05:04.600)
Sounds like a fun retreat.

Guest (05:07.320)
It's not very social for sure, but it was great.
People are surprised about the silence thing.
It's not as hard as it sounds.
What it does do is clear space in your head.
So when you're having conversations with people, there are so many new thoughts being generated about those things.
And when you have some quiet from that, you're able to focus a lot more in things that are a little bit deeper.
So you know, I think if you really want a break from this very interconnected and noisy world, that is probably the best place to Go.
Is to really disconnect and focus on yourself.

Omer (05:40.990)
Yeah, I meditate.
I've been doing it for every day for about two years now.
And I can't imagine starting the day any other way now.

Guest (05:47.630)
That's great.

Omer (05:48.190)
It takes time to get.
Get into the.
The rhythm or I guess the habit of doing it, but it's definitely worthwhile.
All right, so we.
I kind of gave the audience a quick summary of what Chameleon is, but tell them in your own words what, what the product is about.

Guest (06:07.950)
Yeah, absolutely.
So the example that I often give is suppose your father or an uncle or somebody signs up for Facebook for the very first time.
You, of course, are very comfortable understanding how Facebook works, but for them it's really confusing.
There's a lot of stuff going on.
There's a lot of different things you can do.
You're not really sure where to begin.
And if you don't understand it, you'll not go back to it.
You'll be overwhelmed.
So Facebook then guides you through some of the key activities that a new user needs to take to really grasp the value of Facebook.
And they might point you in the direction of adding a friend or uploading a picture or something.
And that guidance that in product guidance they build through these tooltips or a tool and they have, you know, big engineering teams, they write the code for it themselves, they, you know, run AB tests, they show variations to users, they collect the data and they have a big effort around it.
But a lot of companies don't have the resources to do that.
And so they really neglect their first time experience or guiding their new users.
And so Chameleon provides a way to build that guidance without writing code, so without being dependent on your engineers for.
Through a wizard that's kind of drag and drop.
So it's very simple for somebody to create this tool and then publish it and you can do all of those other things like show variations or collect the analytics or run tests.
And that will allow you to really improve your onboarding and in product guidance so that most of your new users are successful.

Omer (07:33.550)
How did you come up with the idea for this product?

Guest (07:37.390)
So I used to work with my co founder at another startup and we saw the benefits of improving user onboarding and at that startup and it was a mobile, consumer mobile app.
And we spent two or three months looking and refining our onboarding experience and we saw that not only did activations increase, but long term retention increased a lot as well.
We had something like 3x improvements in retention and it was really obvious to us that a first time experience has a very key impact in a user's engagement with the product.
So that was the first kind of strike where we were like, oh wow, this is substantial and important.
We should be thinking about this before we do more marketing or before we do other product development.
And then once I'd left and I was freelancing for a few other companies, I heard a consistent theme which was, yeah, we need to fix our onboarding.
We'll get round to it.
We haven't had time.
And digging into that a little bit more, it was just found that people didn't really know what good onboarding should be about.
People didn't really have the time or found it difficult to prioritize it when comparing it to core feature development because it all depended on engineering time.
And thirdly, there was no real go to tool or solution.
Now in the world of SaaS there's often for every problem that you have, there's a go to platform to go and solve that problem.
So that didn't really exist at that time.
And so when we were thinking about, well how can we help fix this, such an important aspect of a user experience, we realized that actually with JavaScript technology that was available, we could allow companies to just drop in a snippet and then provide the controls to then build stuff with that snippet in an interface, which is essentially what Chameleon is about.

Omer (09:20.000)
Okay, so you got the idea, you can see the opportunity there.
What did you do to try and validate the idea before you started working on it?

Guest (09:29.920)
Yeah, well, you know, I'd read the books and I'd been to the startup course that you know, YC did at Stanford and it was like, okay, well we gotta get, we're, we've got to validate, you know, got to validate the market, got to validate demand.
So the first approach, and actually around the time when we were thinking of other ideas to the first approach was to spend a month basically talking to people.
So, you know, validating the problem.
Is this a problem that you have so going and just doing informational interviews with anyone in our network or people that we could find be like, okay, how do you do onboarding?
What are your pain points?
How do you solve it?
And very quickly we learned that okay, there is a problem here.
So that was validating the problem.
Like people didn't have a solution.
It was painful.
Then we had this idea, okay, well this is how we think we'll solve it.
So then the process was about validating a possible solution.
And so for that we said the best way to do it really, is to see if somebody will actually give us the reins to do this.
So I remember I, you know, found.
I thought, okay, well, startups are the place to be.
Really early startups.
We have nothing.
It's just two of us.
We're, you know, could essentially be consultants or freelancers.
So I email, cold emailed a bunch of startups, got the YC list and said, okay, well, these are startups that might be going somewhere, and emailed them and told them, okay, well, this is what we're doing.
Would you be interested in this?
And that led to a couple of conversations and eventually one small company said that, yes, they would let us build their onboarding.
And that was good because we were going to have a platform to really test our code and our product.
So we then started building their onboarding and it was part custom and part kind of parameterized into a platform.
So as we were building stuff for them, we would try to abstract that into a platform.
And so we built it for them.
And then we went live and we got some feedback and they told us things that weren't working.
And that was a really great learning curve.
And then from then on, we basically tried to find some other people like that and eventually found a couple of people who were willing to put money behind it and pay us and pay us upfront.
And so that kind of was a slow process towards testing and validating more and more of what we were doing.

Omer (11:37.520)
So you guys weren't working on this full time.
You only started working on this full time fairly recently, right?

Guest (11:45.120)
Yeah, well, I mean, probably for the last year, but we definitely started off, you know, evenings, weekends.
I remember, you know, the first few weeks was like a few hours a week.
And then as we got more interest or as we got more serious, it just started taking up more time.
And so naturally we ended up having to spend more and more time doing this stuff.
And that was the kind of.
It kind of showed us that, yes, there is something that's going to sink more and more time until it got to the point where it was like, okay, we need to do this full time, otherwise we're shooting ourselves on the foot.
People want this, people want more of it.
So how, you know, so we need to switch over.

Omer (12:23.300)
Got it.
Okay.
And initially, at what point did you raise the 1.9 million?

Guest (12:32.100)
So that was after we'd got some customers, we'd gone full time.
What we did was we asked some friends and family, so we didn't have a network in the Valley.
We didn't know really many investors and we didn't have a background or track record of starting companies, so not the best position to go and raise money.
And so we said, okay, well, you know, we need to go full time.
We don't.
Can't really afford to not pay ourselves because, you know, whatever our financial requirements were.
So we asked some friends and family.
So he said, okay, could you, if we need it, could you put some money behind us?
And, you know, out of about 10 people, you know, out of about 10 people committed in a small amount, we had about 40 or 50k that we could take, which we didn't take.
But then we came across an angel investor a little serendipitously around the summer of last year, which then led to our funding round.

Omer (13:25.170)
What has been the reaction to this kind of idea from investors?
Or was that the only investor that you talked?
I mean, how much convincing did you need to do to get the money?

Guest (13:38.930)
You know, it's surprisingly little.
And that's not to disregard the process.
But we met this one angel investor, Arne Hoffman, and I didn't really know much about him at the time.
He was somebody one of my friends had worked for and got us, put us in touch with.
And he talked to us and he got excited really quickly about the idea.
He had a SaaS company that he'd founded and sold recently, and he was familiar with the problem and he then validated the problem with some of his friends.
And we, we must have met four or five times.
And he got to know us a little bit.
And I think at that point he decided and he, you know, he saw the product and he saw some of the customers and we were live.
And at that point he dec, yes, like, this is something I can get behind.
And then I think once he got behind was a lot easier because we had one clear point of validation from someone that was well respected within the investor community.
And at that he introduced us to a lot of other angel investors and we were able to raise kind of a bulk of our seed round from angels very, very quickly.
At that point.
We then said, okay, well, you know, we've got a lot of angel money.
We'd like to get at least one VC on board.
Seed stage, vc, small firm.
And so then we spoke to a few VCs and then that amount as well.
And again, a lot of.
Even they took a lot of their signal from other people that had invested.
So that really helped our cause that they respected the other investors in our

Omer (15:06.880)
Round what is the opportunity here with Chameleon?
It's interesting because I look at the site and a lot of it focuses on, obviously onboarding is one of the kind of the primary keywords when you sort of look at the site.
But at the same time you said, you talked to companies who said, yeah, we need to do onboarding at some point in the future.
So it sounded like it's, it's something that, what is it important but not urgent?
And so there seems to be kind of, is there a sense of urgency for people to come and address this?

Guest (15:54.060)
So I think the way that it's been done typically is because it's a pain to do.
People batch it up into a project that, okay, we're going to work on onboarding this quarter of this year.
Well, actually it's not something that should be done as a standalone project.
It's something ideally you have a team that thinks about all the time or somebody that thinks about all the time because you want to iterate on it over time.
So right now, because it's, we're fairly early in the market demand for this, people don't really always know that there's a solution like this available.
It has been done in kind of batches.
But it is something that everyone thinks about and that's across the board.
At some point someone, every company is going to think about this.
And so there is an opportunity to help every company solve this problem.
And there's potentially a big enough market just with onboarding, but the same kind of product can be used in other situations.
So new user engagement, of course, is a predominant one that we know there's a pain point around.
But actually anytime you release a new feature, feature discovery is a problem.
People don't always know how to educate users about a new feature or publish a blog post or send an in app notification, but that doesn't really handhold or walk the user through the new feature when they need it, when they are ready for it.
So that's a use case.
Similarly, you know, even when people are searching for help, what you see is help sites with screenshots and text and documentation on how to do a certain flow where actually what might be more valuable is pointing someone to a tool which then takes them through that.
So there are other cases for using in product guidance for users.
And beyond that, you know, there's even more that we can do which is around being able to adapt the interface and adapt the UX for different types of users.
So instead of just being on top of the product as a tip or a tool, you can actually start changing the components of the interface again for customer education to help them succeed.

Omer (18:03.320)
That wraps up part one of this interview.

Related Episodes

100K Signups, 100 Users: Fixing a SaaS Retention Crisis - Richard White

Richard White, Fathom

100K Signups, 100 Users: Fixing a SaaS Retention Crisis

Richard White is the founder and CEO of Fathom, the number one rated AI note-taking app that automatically captures and summarizes meetings. In 2019, after running UserVoice for over a decade, Richard decided it was time for a change. Like many people, he struggled to take notes while talking in meetings. When the pandemic hit, he saw his opportunity. He recruited four of his best engineers from UserVoice and raised funding on day one. But growth was painfully slow. After nearly a year, they only had 50 stable users. The problem was trust. People would not bring an unknown bot into real meetings. They wanted to test it first, but testing on their own did not work because the bot would mute itself. So his team built a clever fix - a bot that played pre-recorded video, giving users a "fake" meeting to help them build confidence. Then Zoom launched its app marketplace and included Fathom. They exploded to 100,000 signups in the first month. But only 100 people were actually using it daily. Turns out 99% of signups had zero meetings on their calendars. Zoom had sent them tons of free users who were not using the platform for business. Richard's SaaS retention numbers looked catastrophic. Instead of giving up, Richard saw opportunity. The thousands of low-quality signups were actually the perfect testing ground to fix their broken onboarding and solve their SaaS retention problem. Just as growth took off in 2022, the funding market crashed. VCs started demanding revenue over user growth. Richard gave his team 60 days to monetize. They started selling a team plan before it was built - just two features ready and a slide deck showing what was coming. It worked - they hit $100K ARR in the first month and reached $1M ARR in a year. Today, Fathom generates eight figures in ARR with 80 employees and serves around 175,000 companies.

7 User Flows That Drive SaaS Onboarding and Growth - Peter Loving

Peter Loving, UserActive

7 User Flows That Drive SaaS Onboarding and Growth

Peter Loving is the founder of UserActive, a UX/UI design agency based in Barcelona that works as a subscription-based design team for SaaS companies. About 60% of their clients are based in the US, with the rest across Europe and beyond. In this conversation, Peter walks through 7 key user flows that every SaaS company should optimize to drive growth. He starts with the signup flow - where unnecessary friction, conflicting CTAs, and missed opportunities to show the product kill conversions before users even get inside the app. He shares examples from List Kit and Carrd of loginless product demos that let users experience value before signing up. The SaaS onboarding discussion goes deeper into how throwing too much information at new users backfires, why personalized onboarding matters for different user profiles, and how to think about onboarding like a five-star hotel check-in - orient users, then let them explore. Peter explains how North Star metrics like Statstrone's "add five affiliates" goal reveal whether users are actually activating during trials. From there, Peter covers activation - why powerful features often get buried in settings menus and never get discovered - and the upgrade flow, where he draws on a great analogy from the TV show Frasier to explain why hitting users with upsells immediately after they pay creates buyer's remorse instead of loyalty. The conversation wraps with core product workflows, integration flows, and a detailed breakdown of the cancellation flow. Peter shares how UserActive designs cancellation experiences that offer discounts, account pauses, and competitor intelligence gathering - turning customer exits into actionable product feedback. He cites Audible's retention strategy as a model for how SaaS companies should handle cancellations. Throughout the episode, Peter references his work with Prospect CRM, where redesigning personalized dashboards for three different user profiles lifted free-trial-to-paid conversion from 18% to 26%, adding roughly $300K in ARR. That single example shows how optimizing SaaS onboarding and user flows creates measurable revenue impact.

From $1M ARR to 40% Churn in One Month - Brett Martin

Brett Martin, Kumospace

From $1M ARR to 40% Churn in One Month

Brett Martin is the co-founder and president of Kumospace, a virtual office platform that helps remote teams to collaborate in real time. In 2020, Brett was running a venture capital fund and hosting monthly in-person networking events. When the pandemic hit, he was forced to use Zoom for these events, which he felt wasn't a great experience and kept thinking to himself that there had to be a better way. So when long-time friend and former co-founder Yang said he wanted to launch a startup, Brett suggested solving this video meeting problem and initially advised on the concept. After seeing early traction, Brett soon joined as co-founder. They launched in the middle of the pandemic and quickly attracted hundreds of thousands of users. When they started charging money the following year, their revenue skyrocketed to over $1 million ARR in just 2.5 months. But their celebrations were short-lived. Churn spiked to 40% in a month as customers used the product more for one-off events than daily work and so had little reason to renew their subscription. This crisis forced the founders to make the tough call. They scrapped their initial model, losing much of their revenue, and pivoted to a virtual office platform. But growing revenue was much slower and challenging this time around. However, fast forward to today, Kumospace serves millions of users, generates 7-figures in ARR with a team of just 16 people, and has raised $25 million in funding.

←All Episodes