Lenny's PodcastMaor Shlomo: How Base44 hit $80M solo in six months
Through three friends sitting around a table and LinkedIn build-in-public posts; Base44 outran Lovable, Bolt, and Replit, then sold to Wix bootstrapped.
CHAPTERS
- 0:00 – 5:21
$80M exit in 6 months: the story that pulled Lenny into an early-stage episode
Lenny tees up the headline outcome—an $80M+ acquisition in six months—and why Maor’s journey is unusually instructive for founders. They set expectations: this wasn’t magic, it was intense execution under real-life constraints.
- •Six-month sprint from zero to $80M+ acquisition by Wix
- •Why Lenny made an exception to interview a very early-stage founder
- •Solo-founder reality vs the “dream outcome” narrative
- •Preview of growth, stack, productivity, and lessons to come
- 5:21 – 7:19
What Base44 is: a “batteries-included” AI app-building platform
Maor explains Base44 as a natural-language-to-software platform that goes beyond generating a React front end. The key differentiation is an opinionated, full-stack foundation—database, auth, integrations, and analytics built in—so users can scale what they generate.
- •Natural-language prompts to build apps, games, and websites
- •“Batteries included” approach: DB, integrations, user management, analytics
- •Contrast with tools that rely on third-party backends (e.g., Supabase integration)
- •Engineering the platform/SDK to work well with LLMs for complex real apps
- 7:19 – 14:55
How the idea formed: personal pain + Scouts’ software needs + a founder reset after Explorium
The initial spark came from two concrete problems: building a simple lead-capture site for his girlfriend, and seeing a huge organization (Scouts) overpay for basic internal software due to lack of developers. After years as CEO of a heavily funded enterprise startup (Explorium), Maor wanted to return to hands-on building—and took a shot with a different mindset.
- •Website builders felt painful and brittle; Maor knew LLMs could code it with the right infrastructure
- •Scouts’ repeated software needs highlighted the gap between demand and developer supply
- •Background: founded/ran Explorium for 7 years; raised $130M; enterprise-heavy motion
- •Post-war reserves and travel catalyzed a return to coding and product-building for fun
- 14:55 – 22:53
Bootstrapped solo founder: when it works, when it doesn’t, and the hidden stress
Maor breaks down why solo + bootstrapped can be a huge advantage for viral/mass-market products, but a poor fit for enterprise sales. He also shares the less glamorous side: on-call forever, brutal prioritization, and context-switching across product, growth, and operations.
- •Solo/bootstrapped is hard for enterprise/B2B sales-led companies
- •“Default alive” and profitability reduce investor-pressure stress
- •Operational burden: outages, security scares, and no DevOps safety net
- •Brutal prioritization and constant context switching as a solo founder
- •Optimizing workflows and automation becomes existential, not optional
- 22:53 – 27:25
Productivity system for solo execution: ADHD, focus blockers, and building custom internal tools
Maor shares how he structured deep work despite severe ADHD, including blocking distracting sites. He also describes using Cursor and Base44 itself to build internal tools that automate his content workflow and operational tasks.
- •RescueTime-style blocking to protect deep work (Twitter/LinkedIn temptation)
- •Cursor for coding speed; Base44 used to build internal business apps
- •Custom content pipeline: idea → LinkedIn draft in his voice → Twitter adaptation
- •“Vibe code” internal tools tailored to your personal process, not generic templates
- 27:25 – 28:41
How to start with Base44: prompt vaguely, get a skeleton, then iterate fast
Maor gives a practical way to begin: don’t over-specify—start with a rough description of your goal and current process, let the system generate a first version, then iterate. He highlights the benefit of “adaptive software” that evolves as your workflow changes.
- •Start with a vague prompt to generate the first app skeleton
- •Describe your current workflow; refine through iteration instead of a full spec
- •“Adaptive/malleable software”: update tools as your process changes
- •Example: quickly reworking the content workflow after the Wix acquisition
- 28:41 – 39:46
Raising money vs staying profitable: competing with giants, then choosing the ‘big league’ via Wix
Maor explains that Base44 became far more profitable than expected, proving a bootstrapped path could work even in a crowded, well-funded category. Ultimately, acquisition was less about survival and more about scaling impact and competing at maximum speed with a strategic partner.
- •Rapid profitability (e.g., ~$200K profit in May) changed strategic options
- •Users stuck despite many funded competitors; biggest challenge was “noise”/awareness
- •Near-zero marketing budget; paid and influencer experiments underperformed
- •Acquisition rationale: move faster in a market evolving faster than anything he’d seen
- •Ambition evolved: start for fun → realize real impact → decide to scale big
- 39:46 – 51:54
0→10→100 users: friends as testers, in-person feedback loops, and ‘launches as milestones’
Early growth came from recruiting close friends and watching them use the product in real time—fixing issues immediately and iterating in production. He reframed launches (like Product Hunt) as steps to reach the next small milestone, not make-or-break events.
- •Start with 3 close friends; meet frequently and observe usage live
- •Fix what breaks immediately; prioritize joy/value before scaling marketing
- •Measure early pull by whether users start sharing organically
- •First Product Hunt launch ‘failed’ but still added meaningful early users
- •Treat launches as tools to reach the next milestone, not company-defining moments
- 51:54 – 1:03:24
Making ‘build in public’ actually work: honesty, channel focus, and rewarding user sharing
Maor describes why his build-in-public approach resonated: transparent storytelling (good and bad), practical learnings, and metrics people could follow. He doubled down on LinkedIn as the single channel that worked, and created a credits-for-sharing loop that turned users into distributors.
- •Started on LinkedIn leveraging a few thousand existing connections
- •Authenticity over hype: share the good, bad, and ugly; teach what you learn
- •Pick one channel that works and concentrate effort; Twitter was initially low-ROI
- •Credits program: users share what they build → receive credits to build more
- •Community flywheel: users excited to post their apps, generating organic reach
- 1:03:24 – 1:08:16
Hackathons and partnerships: ‘Hackathon for Good’ and unexpected big-company sponsors
Maor launched a small-prize “for good” hackathon to amplify positive-impact apps built on Base44. It exploded to thousands of teams, attracted sponsors like Google/AWS/MongoDB/Deloitte, and became a powerful community and distribution engine.
- •Hackathon designed to showcase positive-impact software and empower non-profits/education
- •Started as a ~$5K prize funded from profits, then scaled massively
- •~3,000 teams participated; sponsors and partners amplified reach
- •Side benefits: community bonding, inspiration, and real-world use cases
- •Examples of impactful builds (e.g., Alzheimer’s support/memory app)
- 1:08:16 – 1:15:25
Velocity as strategy + the technical stack that enabled it (Render, MongoDB, LLM-first architecture)
Maor argues velocity becomes a growth engine when every feature is a mini-launch and progress is visible. He then goes deep on infrastructure and coding choices optimized for LLMs: managed hosting, flexible schemas, monorepo-style context, and routing tasks to the best model.
- •Velocity attracts users (“it’s moving so fast, I have to try it now”)
- •Infrastructure: Render.com for deployment/ops simplicity and rapid iteration
- •MongoDB for fast-changing schemas in LLM-driven development
- •LLM-friendly codebase: opinionated primitives so models write minimal code
- •Prefer plain JS/JSX over TypeScript for model reliability; keep more in one repo
- •Model routing: Claude for UI/initial generation, Gemini for complex problems/unsticking loops
- 1:15:25 – 1:18:15
Activation and the ‘aha moment’: sometimes the best UX slows conversion
Maor shares a counterintuitive activation lesson: adding an upfront “PRD/user flows” step improved app quality but reduced conversions. Removing the middle step made the “it understood me” moment faster and more surprising, which improved activation in a low-attention B2C context.
- •Initial approach: show generated user flows before coding to clarify intent
- •Problem: extra step reduced conversion and dulled the surprise/aha moment
- •Insight: optimize for getting users to value within 1–3 minutes
- •Tradeoff: faster activation can mean less refinement up front
- •Layer in sophistication after the user is hooked
- 1:18:15 – 1:31:50
Wix acquisition: how it started, deal philosophy, signing during wartime, and parting advice
Wix reached out amid community chatter, and early conversations focused on help and shared strategy before becoming an acquisition path. Maor emphasizes chemistry, negotiating from a position of being fine either way, and choosing an earn-out structure that keeps incentives aligned—then closes with founder advice and the quirky Base44 naming story.
- •Acquisition began with Wix outreach + ecosystem/customer-base fit
- •Early meetings were advisory; chemistry and “fun to work together” mattered במיוחד for a small team
- •Negotiation leverage: be genuinely okay with not selling
- •Earn-out structure as motivation to keep building and scaling post-acquisition
- •War with Iran began the night before signing; deal still closed the next morning
- •Final advice: spend at least ~50% of time in your ‘genius zone’ and build now
- •Name origin: ‘base’ + domain availability + doubled birthday (22→44) + nod to base64
