Sixty-two thousand dollars a month in recurring revenue. Three months after launch. Zero dollars spent on ads. If you stopped reading there, you'd think Kleo is yet another overnight success — scrappy founder builds an AI tool in their bedroom, posts it on Reddit, watches the money roll in. The reality is messier, more instructive, and depending on how you look at it, either inspiring or deeply annoying.
The Origin Story Has a Cease-and-Desist in It
Kleo started life as a free Chrome extension that scraped LinkedIn data to help users write better posts. Cameron Trew built version 1.0, which gathered 60,000 users organically. Things were going well until LinkedIn's legal team sent a cease-and-desist letter.
Rather than fold, Cameron and his cofounders — Jake Ward, Lara Acosta, and Rob Hoffman — rebuilt the entire product from scratch in four weeks. New Kleo doesn't scrape anything. It uses Claude for content generation, Claude Vision for analyzing images and documents, and Deepgram for voice-to-text input. A full product rebuild in 28 days, from architecture to deployment.
The Stack
Cameron runs a modern serverless setup: Next.js with TypeScript on Vercel, Neon for serverless Postgres, Clerk for auth, Inngest for background jobs, PostHog for analytics, and Langfuse for AI observability. The AI backbone is Anthropic's Claude — both for the product's core features and for writing the actual code via Claude Code.
Nothing exotic. You could spin up the same infrastructure on a weekend.
But the Stack Didn't Get Them to $62K
Kleo didn't reach $62K MRR because Cameron picked the right database. It got there because Jake Ward has 180,000 LinkedIn followers and Lara Acosta has over 300,000.
Before the product officially launched, Lara ran three webinars that each pulled in over 5,000 in pre-sales. Jake posted behind-the-scenes build updates that racked up engagement. They released 500 lifetime discount spots at 59/month — sold out in four days. Then another 500 at 79/month — gone in nine days. Standard pricing now sits at 99/month.
No cold outreach. No Product Hunt hustle. No paid acquisition funnel. Four people with an existing audience who built something they genuinely used every day, then told their followers about it.
The Uncomfortable Question
Does this story help you if you don't have half a million followers between you and your cofounders?
Parts of it do.
The technical execution is worth studying. Cameron rebuilt a complete SaaS product in four weeks, leaning heavily on Claude Code as a development accelerator. The serverless stack keeps costs near zero in the early stages — Vercel, Neon, and Clerk all have generous free tiers. He wasn't paralyzed by framework debates; he picked proven tools and shipped fast. That playbook works regardless of your follower count.
The pricing strategy is also portable. Launching with capped discount batches created urgency and generated immediate cash to fund further development. Each sold-out batch became social proof for the next tier. Polar handled subscription management. You can run this same playbook with 200 email subscribers — the batches just get smaller.
But the distribution advantage? That took years to build. Jake and Lara didn't wake up with 480K combined followers one morning. They posted consistently on LinkedIn for years before Kleo existed. The lesson isn't "go viral and then launch a product." It's that if you're planning to launch anything in the next 12 months, the time to start building distribution was six months ago.
What's Worth Stealing
Build in public, but make it real. Not the performative kind where you tweet terminal screenshots. Cameron shared genuine progress updates — bugs found, architecture decisions debated, features scrapped. Their private Slack community gave early users direct access to the team, and bug fixes shipped within hours of reports. Users became evangelists because they felt ownership over the product's direction.
Escalate pricing from day one. The limited-batch model (500 at 59, then 500 at 79, then open at $99) creates a pricing narrative. Early buyers feel smart. Late buyers see the previous tiers as validation. It's not a new trick, but Kleo executed it cleanly.
Use AI to compress your timeline. Four weeks for a full SaaS rebuild would've been a three-to-four-month project in 2024. Cameron used Claude Code throughout development. Whether you prefer Cursor, Copilot, or something else, the point holds — AI-assisted development lets tiny teams move at speeds that used to require a full engineering department.
Scratch your own itch, literally. All four cofounders are active LinkedIn creators. They didn't research "LinkedIn tools" on Google Trends and decide to build one. They were the target user. Feature priorities came from personal frustration, not a Notion board of hypothetical personas.
The Footnote That Says the Most
Here's a detail that got buried: while building Kleo, Cameron simultaneously became CTO of Mentions — a separate product that tracks brand mentions in AI-generated search results, currently sitting at 20K MRR. The person shipping a 62K MRR product is also running another at $20K.
This says something uncomfortable about where things are heading. The gap between builders who have AI-fluency, technical depth, and distribution — and those who don't — is compounding fast. Cameron can run two products because AI tools multiplied his output. His cofounders convert that output into revenue because they spent years accumulating an audience.
For the rest of us working without a built-in megaphone, the takeaway isn't to quit. It's to pick the unfair advantage you're going to build and start compounding it now. That might be an audience, a niche community, deep domain knowledge, or raw technical speed. But you need something that grows over time.
The code was never the hard part. And in 2026, with AI making the code even easier, distribution is the only moat left standing.