Snow Lee is a 3x founder who is currently solving a problem he faced at his last company by building Runbear.
After struggling to find his ICP, he finally dialed it in and grew his company to $400k ARR.
Here's Snow on how he did it. 👇
I'm a 3x founder and have been building software startups for the past 16 years with my co-founder, Liam. I previously founded and sold two companies, and also led products as CPO at Buzzvil, where I helped grow annual revenue to $80M.
At my previous company, I led seven teams simultaneously. It was exciting, but exhausting. I was constantly context-switching, and the cognitive overload was brutal.
That experience made me realize how much time teams waste on repetitive communication. I wanted to build something that could help people offload that mental load, something that works with you, not for you.
That's why I’m building Runbear, a platform that helps non-technical teams create their own AI agents effortlessly. Our mission is to make AI feel like a real team member — one that can understand conversations, take initiative, and proactively help teams get work done.
We're currently at $400k ARR.
Our biggest challenge to date was defining our ideal customer profile. Since Runbear could technically help anyone build AI agents, we had to learn who got the most value.
Our first version was an AI copilot for DevOps engineers, but we quickly realized we were competing with our own customers — engineers wanted to build their own agents. So, we pivoted to helping teams utilize AI agents more easily.
Then, we discovered something surprising: Non-technical users — leaders, customer success, account managers, and operations teams — were the ones most eager to use our solution. The reason was that these communication-heavy roles benefited hugely from Runbear's ability to monitor messages and automatically take over tasks.
What surprised me most was how clear their intent already was. Even without understanding how AI works technically, our customers knew they needed it. They weren’t curious about the technology itself; they were focused on outcomes.
So, we refocused Runbear on helping non-technical teams harness AI effectively. And now, our strongest champions are team leaders, people who want to stay ahead and empower their teams through AI. And almost every customer starts with the same use case: answering repetitive questions.
It’s a simple but powerful entry point that quickly demonstrates value and builds trust in what AI can do for them.
If I had to start over, I’d focus on finding the killer use case first, before expanding the product’s capabilities.
To find our ICP, we started by analyzing existing use cases and identifying which customers were getting the most consistent value from Runbear. Then, we conducted in-depth customer interviews to understand their workflows, pain points, and expectations for AI assistance.
From there, we mapped out industry opportunities and prioritized problems that were either urgent, frequent, popular, or expensive, ideally hitting more than one of those criteria.
This framework helped us narrow down to customers who rely heavily on communication, such as account managers, support teams, and operations leaders, who now form our core ICP.
Until July, we had a single subscription plan, which helped us simplify growth early on. We had only one hard limit: the number of AI agents customers could create.
Many of our customers started reaching out to remove that restriction, which showed us a clear demand from power users. So, instead of just unlocking the limit, we decided to introduce a new business plan that better supported those teams, while charging more fairly for the added value. We wanted to test if enough customers were willing to pay more, and the strong response confirmed that they were, giving us confidence to move forward. We have already onboarded over 20 higher-paying customers, which has significantly boosted our revenue per account. There has been no churn from these users so far.
Here's our tech stack:
TypeScript
Vercel
Supabase
Multiple AI models
Claude: Core generation model
OpenAI: Evaluation, knowledge extraction, and response compression
And we support Gemini and Perplexity if users want them as their core generation model
Runbear’s biggest advantage is our team-member approach.
Instead of asking users to build complicated rule-based workflows, our AI learns how to work like a human teammate: observing, understanding, and acting naturally.
The agents analyze message intents to understand what’s happening in conversations, then decide whether to step in or stay silent, just like a thoughtful coworker would. When action is needed, the AI can plan the task completion process, execute steps, and even learn how to improve through ongoing conversations. Over time, it adapts to the team’s workflow naturally, extending its capability.
Although there are many ways that we ensure that AI acts as a teammate in this way, one example explains it best. When you ask the AI to do something it can’t do yet, it will ask you how to complete the task, just like a new hire would. You might say, "You can find the revenue data from Stripe," and it will learn and remember that instruction for the future. Over time, it builds knowledge across 2,000+ services, gradually becoming smarter and more capable, truly acting like a teammate who learns by doing.
That simplicity means anyone, not just engineers, can have AI agents that truly collaborate with their team.
We’ve grown mainly through content marketing and creator collaborations.
For content marketing, we mostly publish use cases, building guides, and customer success stories. For creator collabs, we publish youtube videos, X posts, and LinkedIn posts to introduce use cases of AI agents, and how to build them using Runbear.
Our SEO strategy has been effective, too. We’ve secured keyword positions that keep bringing in new users organically. To get there, we published content that was centered on keywords related to using AI agents in communication channels. Now, we're changing our focus slightly to keywords related to our ICPs and their use cases.
Just start. Don’t overthink it. But once you start, keep evolving fast.
The market moves constantly, and your job as a founder is to adjust quickly. Build, learn, pivot — repeat.
Success comes from staying in motion.
My life goal is to build a company that lasts 100 years. For Runbear, our vision is to become the de facto standard for hiring AI teammates.
In the short term, we’re focused on reaching $2M ARR and continuing to expand our customer base globally.
You can follow along on my personal blog. And check out Runbear!
Leave a Comment
Great sharing, I should also quickly realize my own ideas and help those in need
Such an inspiring journey! Love how you turned your own challenges into something that genuinely solves a team problem. Can’t wait to see where it goes as AI becomes more collaborative and context-aware. Huge congrats on hitting $400K ARR!
Impressive journey — love how you turned your own challenges into a product that actually solves a real pain point. The vision behind Runbear feels very grounded in real team dynamics, not just hype. Excited to see how it evolves as AI becomes more collaborative and context-aware. Congrats on hitting $400k ARR!
Thanks for sharing
Really inspiring journey, Snow 👏 The pivot from DevOps-focused users to non-technical teams makes so much sense — identifying your ICP through real use cases instead of assumptions is such a key lesson. Love how Runbear treats AI as a true “team member” that learns like a human. The organic growth through SEO and creator collaborations is also a smart, sustainable approach. Wishing you continued momentum toward that $2M ARR goal 🚀
In your experience, how long does it usually take 2 cofounders to reach $400K ARR?
How long did it take for Runbear?
Pensando em como posso fazer uma solução aqui no Brasil, alguma ajuda mestre?
I believe this roughly translates to
Really inspiring journey, Snow. What stood out to me most was how you found your ICP not by guessing but by observing real usage patterns and being willing to pivot—even when it meant walking away from your initial assumption. That’s something a lot of builders struggle with.
Love the idea of AI acting as a real team member - not just a tool, but a proactive collaborator. 💡 At ActlysAI, we’re building something similar: AI agents that integrate into the Google ecosystem (Docs, Gmail, Calendar, etc.) to automate daily and business workflows. You just describe what you need, and the agent figures it out. Great to see others pushing in the same direction. 🚀
Love how you framed the ICP journey here. It’s wild how often the “real” audience ends up being completely different from who you thought you were building for. The “killer use case first” point really hit home.
This comment was deleted 13 hours ago