LLenny's Podcast
← All episodes
Maor Shlomo06 July 2025

Solo founder, $80M exit, 6 months: The Base44 bootstrapped startup success story

7Frameworks
21Insights

Frameworks in this episode

Insights & moments

The myth-busts, hot takes, explainers, and tools worth keeping.

Hot Take· 4

Hot Take15:30

When Solo Bootstrapping Beats Raising Money

Maor argues bootstrapping solo isn't right for every company — a B2B enterprise product needs a sales team and marketing spend. But for something with viral, mass-market potential, staying solo and profitable is better on almost every axis, including the financial outcome. Being 'default alive' and profitable removes the weight he felt even with great, supportive investors at his previous venture-funded company.

  • Solo bootstrapping is wrong for B2B/enterprise — you need salespeople and marketing spend
  • For viral, mass-targeting products, bootstrapped-and-profitable usually beats the funded path
  • A profitable, 'default alive' business is far less stressful — you wake up without the weight
  • Even great, supportive investors add a weight that bootstrapping avoids

there's like this term default alive it's so much easier I've done both and the weight of uh raising so much fund even if your…

Maor Shlomo · 16:30
#bootstrapping#solo-founder#fundraising#hot-take
Hot Take32:30

Funding Isn't What Wins a Category Anymore

Maor argues that in the AI era, money and funding are not necessarily what win a category. A small team or even a solo founder can keep pace with the fastest-growing, best-funded competitors because they're managing teams of AI writing the code. He points out he hasn't written a single line of HTML or JavaScript in three months, yet Base 44's front end changes constantly because AI writes it — and predicts 10x engineers becoming 100x as models improve.

  • A solo founder can keep pace with, or outpace, the fastest-growing well-funded competitors
  • You're 'literally managing teams of AI' that write the code
  • He hasn't written a line of HTML or JavaScript in 3 months — AI writes Base 44's front end
  • An interesting angle plus speed matters more than team size or funding
  • As LLMs improve, 10x engineers become 100x engineers

I don't think I've written a single line of like HTML or JavaScript in the past 3 months

Maor Shlomo · 33:00

money and funding is not necessarily the the factor to win a category

Maor Shlomo · 33:30
#ai-coding#solo-founder#competition#hot-take
Hot Take48:30

He Doesn't Believe in MVPs or a Strict ICP

Maor pushes back on two pieces of standard startup advice. On MVPs: since software is so easy to build now and attention spans are short, shipping something that isn't good enough wastes your shot — so grab people who owe you a favor and build for them while it's still bad. On ICP: he cares less about the profile of a person and more about what they're trying to do; different types of people can share the same job-to-be-done. Lenny notes this applies more to horizontal tools than narrow products.

  • He doesn't believe in MVPs — shrinking attention spans mean a not-good-enough product wastes users
  • Instead, get people who owe you something to use it while it's still bad, and be there physically
  • He doesn't agree you need a strict ICP profile — what users are trying to do matters more than who they are
  • Different types of people can all be trying to do the same thing
  • Lenny's caveat: this fits horizontal tools; narrow products may still need a tight ICP

there are some things that I don't believe in is like MVPs first and foremost

Maor Shlomo · 48:30

it's not it's not necessarily about like the profile of a person more of like what they're trying to do is like way more important

Maor Shlomo · 50:00
#product#mvp#icp#hot-take
Hot Take1:07:00

Velocity Is Itself a Growth Engine

Maor's parting growth insight: velocity solves most problems. Shipping features every other day gets users attached, just as sharing charts and numbers in public does — people comment that the product is moving so fast they have to try it now. Most of his thinking while running Base 44 was simply how to increase velocity, because it fixes product problems, some marketing challenges, and lets you turn every release into a mini launch.

  • Shipping features every other day gets users emotionally attached to the project
  • Sharing charts and numbers in public makes people invested in the trajectory
  • People commented the product was moving so fast they had to try it immediately
  • Most of his thinking was 'how do we increase velocity' — it solves most product and marketing problems
  • Treat every release as a mini launch

velocity solves so for so many things like most of my thoughts uh when and still are when running base 44 is like how do…

Maor Shlomo · 1:07:30
#growth#velocity#product#hot-take

Explainer· 2

Explainer1:13:00

How Base 44 Routes Prompts to Different LLMs

Maor explains Base 44's model strategy: it uses a mix of models for different tasks. Claude does a great job on the initial prompt and anything UI/design; Gemini is better on very complex problems, algorithms, or when Claude gets stuck in a bug loop. A pipeline analyzes the user's prompt and routes it to the right LLM. Separately, the 'heavy guns' produce high-level changes while smaller, faster models (like Flash or 4o-mini) patch the actual code inside files.

  • Base 44 uses a mix of models for different tasks, not one model
  • Claude is great on the initial app-from-scratch prompt and all UI/design work
  • Gemini is better for very complex problems, algorithms, or when Claude gets stuck in a bug loop
  • A pipeline analyzes the user's prompt and routes it to the right LLM
  • Heavy models create high-level changes; smaller fast models (Flash, 4o-mini) patch code inside the file

I have this pipeline that tries to figure out the user prompt and then um route it to the right LLM.

Maor Shlomo · 1:13:30
#ai-architecture#llm-routing#engineering#vibe-coding
Explainer1:15:30

Why He Killed a 'Better' Feature to Protect the Aha Moment

Maor shares a counterintuitive activation lesson. Base 44 originally generated user flows (like a mini PRD) before writing code, which produced better apps by confirming it understood the request. But that middle step lowered conversions to the aha moment, which in vibe coding is the shock of seeing your app appear and thinking 'it actually understood me.' A middle stage made the reveal less surprising, so he ditched it — get users to the aha moment as fast as possible, even at some cost to quality.

  • Base 44 used to generate user flows / a mini-PRD before writing code, producing better apps
  • That step lowered conversions to the aha moment despite being the 'right' product decision
  • The aha moment in vibe coding is the shock of seeing the app and feeling 'it actually understood me'
  • A middle stage made the surprise less surprising, so he removed it
  • In B2C, attention spans are so low you want users at the aha moment in a minute or two

get your users as fast as possible to the H movement. Sometimes there's a price to that. make sure it's not too big.

Maor Shlomo · 1:17:30
#product#activation#aha-moment#retention

Story· 7

Story08:00

The Two Problems That Sparked Base 44

Maor explains that Base 44 grew out of two real problems he was trying to solve, not a top-down market bet. His girlfriend, an artist, needed a lead-capture website and the existing drag-and-drop tools were painful, and separately he was volunteering IT help for a huge Israeli scouts organization that kept getting quoted a million bucks by agencies for software he knew LLMs could write. Both convinced him that models could already write the code — they just lacked the right infrastructure (database, user management) to do it.

  • His girlfriend needed a lead-capture website; non-AI website builders were a pain, especially on mobile
  • He volunteered software help for a huge Israeli scouts org (tens of thousands of people) with constant software needs and no internal devs
  • Agencies quoted the scouts ~a million bucks for tools he knew could be built cheaply
  • His insight: LLMs can write the code, they just need the right infrastructure — database access, user management — set up for them

I know models can write the code to do exactly what I'm trying to do right now

Maor Shlomo · 08:30

they didn't have any internal devs, you know, any software engineers. So they'd reach out to other agencies and agencies usually would quote them like…

Maor Shlomo · 09:30
#origin-story#idea-validation#ai-coding#founder
Story17:30

The 'Crypto Scam' Panic at His Brother's Wedding

Maor tells a story about the stress of running production solo. During his brother's wedding photo shoot — where he was also meant to run the ceremony — a friend from MIT called saying someone had hacked Base 44 with a crypto scam. He made an excuse, opened a laptop for two terrifying hours, and discovered it was just the LLM using a Node.js package literally called 'cryptography', which a non-technical user mistook for a crypto hack.

  • The scare happened at his brother's wedding, the one night he couldn't open a laptop
  • A friend warned that Base 44 had apparently been hacked in a crypto scam with user data at risk
  • It turned out the LLM used a Node.js package called 'cryptography' — unrelated to crypto
  • A non-technical user saw the word and assumed a crypto scammer had hacked their app
  • Being solo means you can't share the burden or hand it off to anyone

spend two hours, two very scary hours of my life. It ended up being just the LLM. Tried using a package called cryptography which is…

Maor Shlomo · 19:00
#solo-founder#stress#story#ops
Story40:00

First 10 Users: Beg Friends and Sit With Them

Maor got his first users by begging close friends to use the tool — starting with three, two of whom were unemployed at the time. He had them sit down with him every other day; they'd try to build something, it would break, and he'd fix it live and push to production. His signal to scale wasn't enjoyment but sharing: when users started showing the tool to their friends, he knew it was working. He kept doing in-person feedback sessions even past 100k users.

  • He started with 3 really close friends, two of them unemployed at the time
  • They sat down every other day; it would break, he'd read the logs, fix it, push to production
  • Don't scale until users show value — the key metric is that they start sharing it with someone
  • Only once strangers (the 11th user) appeared did he invest in marketing
  • He kept running in-person 'focus group' sessions of 20-30 people even at 20k/50k/100k users

Just begging people close to me that I feel like that they have uh that I have really good connections with uh to use it.…

Maor Shlomo · 40:00

the best metric to to seeing them enjoying it or or at least making value out of it even if they're not enjoying because there…

Maor Shlomo · 41:30
#growth#early-users#product-feedback
Story46:30

Building in Public + Paying Users in Credits to Share

The growth unlock was building in public on LinkedIn, suggested by a founder friend, because Maor's audience were builders who resonated with his honest journey. He noticed people loved sharing what they built on Base 44, so he created a program: share anything about the app or the building process on social, and get extra build credits. Building in public plus the credits incentive worked extremely well together.

  • A founder friend suggested he share his journey since his audience were builders
  • Building in public on LinkedIn created a strong synergy with his builder audience
  • People naturally loved posting about what they built on top of Base 44
  • He launched a program giving extra build credits for sharing on social — even not about Base 44 itself
  • Building in public plus the credits program worked extremely well

dude, how much are you paying those people to to like write posts about space 45? I was like, I'm not paying anyone

Maor Shlomo · 46:30

if you share just about the process of building the app or the app itself, it doesn't even have to be about B 44. If…

Maor Shlomo · 47:00
#growth#building-in-public#incentives#community
Story1:04:00

The 'For Good' Hackathon That Drew 3,000 Teams

With Base 44 around 5-10k users and no budget, Maor ran a hackathon for apps that do good in the world, funding a 5k prize out of Base 44's own profits. It exploded to ~3,000 teams — possibly the largest 'for good' hackathon ever — and spread across social, attracting sponsor requests from Amazon, Google, MongoDB and others who opened their offices globally. He calls it one of the top moments of his career, citing an app built to help a grandmother with Alzheimer's memorize family members.

  • He ran the hackathon with no budget, funding a 5k prize from Base 44's own profits
  • It grew to ~3,000 teams, possibly the largest 'for good' hackathon so far
  • Sponsor requests came in from Amazon, Google, MongoDB and others, who opened offices globally
  • Scaling software cheaply lets nonprofits and neglected domains build tools they couldn't afford
  • A memorable app: a game helping a grandmother with Alzheimer's memorize family members by photo and name

It ended up being 3,000 teams. Uh so like really big I think like the largest I think it's the largest for good hackathon uh…

Maor Shlomo · 1:05:00
#growth#hackathon#community#partnerships
Story1:23:30

War Broke Out the Night Before Signing

Maor recounts that the deal — life-changing for him and his kids — was set to sign Thursday night. The lawyers finished at 2 a.m. but decided to fix wording in the morning rather than rush it while exhausted. At 4 a.m. he woke to news that war had broken out between Israel and Iran. He couldn't believe the timing, but everything went fine — they woke up and signed the papers, making it, in his words, the least boring month of his life.

  • The deal was hard-set to sign Thursday night; due diligence was fast with little baggage
  • Lawyers finished at 2 a.m. but chose to fix wording in the morning rather than rush
  • At 4 a.m. he woke to news that war had broken out between Israel and Iran
  • Despite the shock, everything went fine and they signed the papers the next morning

4:00 a.m. waking up like this announcement like hey a war broke out between and I was like again this is so classic

Maor Shlomo · 1:24:30
#acquisition#story#israel
Story1:28:30

The Silly Reason It's Called Base 44

Maor admits the name has the stupidest reason behind it. He wanted 'base' because it'd be the base where people start building software, but base.com wasn't available and he had no money for a fancy domain. His birthday is February 2nd, so base22 was the instinct — but it was taken, so he doubled it to base44. He liked that it sounded like base64, the encoding scheme, and the nerd in him saw Base 44 as encoding natural language into software.

  • He wanted 'base' as the base where people start building software
  • base.com was unavailable and he had no money for a fancy domain
  • His birthday is February 2nd, so base22 — but it was taken, so he doubled it to base44
  • He liked that it echoed base64, the data-encoding scheme
  • The metaphor: Base 44 encodes natural language into software

base 44 is going to do the same. It's like encode natural language into software

Maor Shlomo · 1:29:30
#branding#naming#story

Q&A· 1

Q&A29:00

Why Sell a Profitable Company to Wix?

Asked whether he could have stayed independent, Maor says Base 44 was more profitable than he expected — close to 200k in profit by May — and he could have made good money solo. But the market was moving faster than anything he'd seen, and he came to believe the product could genuinely change lives at global scale. Selling to Wix was a deliberate choice to 'play in the big league' with a partner sharing the same DNA and customer base, plus an earnout keeping his upside tied to success.

  • Base 44 was fairly profitable — close to 200k in profit by May
  • He believed he could compete and make good money even staying bootstrapped
  • The market moved faster than anything he'd seen, pushing him to go for global scale
  • Wix offered the same DNA, same customer base, and a strong management relationship
  • The deal's earnout ties much of his compensation and upside to Base 44's ongoing success

in May I already did close to 200k in profit

Maor Shlomo · 29:30

the acquisition is like taking a stance and saying, you know what, let's let's let's play in the big league

Maor Shlomo · 31:30
#acquisition#strategy#ambition

Tool· 2

Tool23:30

He Vibe-Coded His Own Content Tool on Base 44

Maor built custom internal tools for himself on Base 44, including a content generator tailored to his exact workflow. He'd jot rough post ideas, and the app would expand a vague skeleton into a LinkedIn post in his own tone, then break it down into a Twitter thread — using an in-app LLM trained on his previous posts. The point: don't fight a generic tool like ChatGPT over tone and emojis; vibe-code a tool that fits your personal process.

  • He built a personal content app on Base 44 that turned rough ideas into LinkedIn posts, then Twitter threads
  • The in-app LLM used his own tone of voice and saved previous posts to sound like him
  • It replaced a painful ChatGPT loop of fighting over 'too salesy' output, emojis and hyphens
  • 'Adaptive'/malleable software: when his process changed after the acquisition, two prompts updated the app

you can vibe code your way into like productivity tools that really fits what you want to do

Maor Shlomo · 24:30

That's a cool phrase adaptive software. Uh I heard malleable software is another way to describe this.

Lenny · 28:30
#tools#vibe-coding#productivity#content
Tool1:08:30

The Base 44 Tech Stack (and Why He Avoids TypeScript)

Maor gets geeky about the stack that let him move fast: Render.com for infrastructure (which he raves about despite no sponsorship), MongoDB because vibe-coded schemas change constantly, and Python on the back end which held up under heavy traffic. His controversial take: use plain JavaScript (JS6), not TypeScript, because it's easier for models to write. He also keeps front end and back end in the same repository so the AI has full context.

  • Render.com handles infrastructure — he praises it heavily despite no sponsorship deal
  • MongoDB fits vibe coding because schemas change a lot as LLMs adjust the data model
  • Back end is Python; it held up under heavy traffic without performance issues
  • Controversial take: use plain JavaScript (JS6), not TypeScript — easier for models to write
  • Keep front end and back end in the same repository so the AI gets full context

There's one uh uh controversial take uh for me working with LLMs is uh don't use TypeScript, use plain JavaScript, use JS6. Uh it's easier…

Maor Shlomo · 1:11:30
#tech-stack#tools#vibe-coding#engineering

Takeaway· 5

Takeaway13:30

Build Something You'll Actually Use — and Actually Love

Maor revisits two startup cliches he once dismissed: build something you'd use yourself, and keep doing something you genuinely like. He now believes both are underrated — building tools he personally used (for his girlfriend, the scouts, friends) let him move far faster, and loving the work made the hard hours easier. He also realized after seven years as a CEO that what he actually loves is building products, not managing sales, HR and everything else.

  • Building something you'll use yourself makes you move forward much faster
  • Doing work you love makes it easier to work very hard
  • He initially dismissed these as cliches, prioritizing revenue and deals instead
  • After 7 years as Explorium's CEO he realized he loves building and scaling products, not managing sales/HR

it's so much easier one building something that you'll actually use

Maor Shlomo · 13:30

it took me too much time to realize that what I really like doing is just building products and scaling products and not necessarily like…

Maor Shlomo · 14:30
#founder-advice#motivation#product
Takeaway43:00

A Failed Product Hunt Launch Is Totally Fine

Maor's first Product Hunt launch in mid-January flopped, but he reframes launches as milestones, not make-or-break events. That 'failed' launch still got him ~15 new users and his first paying customer, roughly tripling his tiny user base. He warns founders against treating a single launch as make-it-or-break for the whole company — it's just a tool to reach your next 30 or 50 users.

  • His first Product Hunt launch was 'very bad' but got him ~15 new users
  • It produced his first paying user — an insane feeling coming from enterprise
  • Launches are milestones to reach the next 30-50 users, not make-or-break moments
  • Don't treat a product launch as all-or-nothing for the company

I feel like people some sometimes treat their launches like product launches as like make it or break it for the company. This wasn't the…

Maor Shlomo · 43:30
#growth#product-hunt#launch
Takeaway55:30

Pick One Channel and Triple Down

Maor advises taking a bet on a single distribution channel rather than spreading across all of them. LinkedIn was his highest-ROI channel; he tried replicating on Twitter and it was largely a waste of time despite eventually building a following there. He notes the winning channel differs by founder and product — it could be Reddit or Substack — but once you see something work, double or triple down instead of spraying and praying.

  • Take a bet on one channel you see working rather than spreading thin
  • LinkedIn gave him the highest ROI; Twitter was largely a waste of time
  • The right channel differs by founder and product — could be Reddit or Substack
  • Once something works, double or triple down; 'spray and pray' doesn't work at this stage

once you see something work, just double triple down on that. Keep on like don't try to spray and play. It doesn't work at this…

Maor Shlomo · 56:00
#growth#distribution#marketing-channels
Takeaway1:21:30

The Best Negotiating Position: Be Fine Not Selling

On the acquisition, Maor says the strongest position to negotiate a deal — or even reach one — is being genuinely fine with the alternative of not getting acquired. He compares it to early dating: don't show too much interest. His honest stance was that it would be amazing if it worked out and amazing if it didn't. He also praises the earnout structure because it keeps him personally invested and showing up every day rather than selling and disappearing.

  • The best position to negotiate is being genuinely fine with not getting acquired
  • He likens it to early dating — don't show too much interest
  • His stance: it'll be amazing if it works out, and amazing if it doesn't
  • Chemistry and being fun to work with are critical when a buyer acquires a small team or solo founder
  • The earnout keeps him personally invested and showing up daily rather than disappearing

the best position to negotiate such a deal or or even to get there is to be also very fine with the other path of…

Maor Shlomo · 1:21:30
#acquisition#negotiation#founder-advice
Takeaway1:26:00

Spend at Least Half Your Time in Your Genius Zone

Maor's closing advice: make sure at least 50% of your time is spent on the parts of the work you genuinely like and are great at — your 'zone of genius.' That's what keeps you showing up every day and it's radically different from being talented but doing work you don't enjoy. He notes even CEOs of public companies he's met keep a major part of their job in what they love, whether product, design, or building a marketing machine.

  • Keep at least 50% of your time in the sweet spot of what you're great at and enjoy
  • That 'genius zone' is what keeps you showing up every day
  • Being talented but doing work you dislike is unbelievably different and draining
  • Even CEOs of public companies keep a major part of their job in what they love

make sure that at least 50% of your time you work on some on the the parts of you that you really like and that…

Maor Shlomo · 1:26:00
#founder-advice#motivation#productivity