Founder Mindset Playbooks
The mental side of building — staying motivated through the flat stretches, making decisions under uncertainty, and the hard-won perspective founders share about the journey.
286 tactics · page 4 of 10
“The two steps in making a successful app business are: make something worth using, and then put it in front of the people who would use it. It's remarkably hard to do either one of those.”
Two steps to a successful app business — and both are remarkably hard
Alex's whole marketing philosophy in one line. Most founders nail the product half and avoid the distribution half because it's outside their comfort zone — but both are non-negotiable. Naming the two steps clearly is the first step to actually executing on each.
“What is the industry that I want to be working in? Startups often don't go the way you expect, but you can learn so much, so I was thinking what do I want to become an expert at — if it doesn't work out, what would I like to have learned four, five, seven years worth of information about.”
Pick the industry, not the idea — assume the startup might not work
Alex's framework for picking what to work on: assume the startup may not work, then ask what domain you want to be an expert in after years of full immersion. He chose plants because the underlying science, climate-change tailwinds, and consumer adoption made the bet pay off regardless of whether Greg specifically succeeded.
“There's kind of three main buckets of why people might turn from a consumer subscription: they hit a natural breaking point with your use case, something happened with their payment method, or they didn't see the value. Not all churn is literally bad — some of it is natural.”
Not all churn is bad — three buckets (natural, billing, value-gap)
Caroline splits churned subscribers into three audiences — natural lifecycle exit (e.g. students graduating), involuntary/billing, and value-gap — because each needs a different lifecycle treatment. Treating all churn as failure leads to wrong win-back messaging; sizing each bucket changes where you spend effort.
“We call ourselves the 38-year-old startup. We were founded in 1985 — originally a 1-900 phone number, then a fax, then a free website. We launched our subscription in 2001, six years before Netflix. So we're better than Netflix in at least one way.”
The 38-year-old startup — Surfline launched paid subscription in 2001, 6 years before Netflix
Surfline started as a 1-900 surf-forecast hotline in 1985, then ran a fax service, then a free web product, and finally launched paid subscriptions in 2001 — six years before Netflix. Today's success is the cumulative output of four decades of brand and content compounding, not a hockey-stick launch.
“If you're contemplating starting a freemium business, there's going to be pain in the beginning. You're adding an extra step. It's going to take time for people to understand what you're offering. You're going to get it wrong a bunch of times in the beginning.”
Freemium has pain in the beginning — Duolingo took 6-7 years to monetize
Paul's warning to anyone choosing freemium over a hard paywall: you're trading short-term conversion for a long optimization slog. Duolingo took six or seven years before they meaningfully monetized. Plan for that horizon — or pick a different model.
“Pre-2023, unless you were building a marketplace, the idea that you would want to or be able to monetize your users in the first 5 or 10 years was pretty crazy. ChatGPT anchored a lot of people on $20 a month if not more, and when you incorporate usage-based pricing you can have whales paying hundreds if not thousands of dollars a month.”
ChatGPT anchored consumers on $20/mo — the $60/yr ceiling is dead
For a decade pre-AI, consumer apps couldn't monetize directly — users were the product, you served ads. ChatGPT trained a generation to pay $20/month, and that's the new floor, not the ceiling. The willingness-to-pay shift benefits every consumer app, not just AI ones.
“Sam Altman actually said something interesting on the OpenAI town hall a couple weeks ago. Someone asked him 'are you going to kill my startup?' and he was basically like: look, if you as a company are happy when the models improve, you're safe. That's a great place to be.”
Sam Altman's safety test — are you happy when the models improve?
The litmus test for whether your consumer AI app is durable: do you get stronger when GPT-5 ships, or weaker? If model improvements help you, you're on the right side of the labs. If they directly threaten you, you're a thin feature waiting to be eaten.
“The best thing that you can do to build intuition on these products is just to use them. The quality of consumer AI apps on mobile is so much better and more sophisticated than they were 6 months ago. Things are changing so fast — the best way to stay on top is just to use them.”
Use the products yourself — intuition is the moat
Olivia's tactical advice for founders trying to read the market: stop reading hot takes and actually use the AI apps shipping each month (Wabi, Gizmo, Sakai, Poke, Tasklet). Mobile AI quality jumped massively in 6 months — hands-on use is the only way to see what's resonating.
“I think that was Apple's point — the purpose of the way they've complied was to induce maximum pain while staying as close within the regulations as they can, because frankly they've got a monopoly on their users' time and dollars and they don't want to let that go.”
Apple's malicious compliance — maximum pain inside the rules
Jacob diagnoses Apple's DMA response as a deliberately punishing implementation designed to discourage developers from switching, while technically complying with the letter of the regulation. This is the start of a negotiation, not the end — expect more rounds.
“Gruber had a good line — the last thing you want to do if you're a sports team in a high-stakes sporting event is piss off the refs. That's what Apple's doing. They're just inviting more regulation. South Korea is already threatening to fine them. They're squandering developer goodwill.”
Apple is pissing off the refs in a game it's already winning
David's read on Apple's strategic blunder. By choosing maximum hostility in DMA compliance, Apple signals to every other regulator in the world that they won't cooperate — which guarantees more aggressive future regulation in other jurisdictions and slowly erodes the developer goodwill that built the platform.
“My greatest failure in life will be if I cling on to an existing business model to the point that I'm regulated by the EU. So make sure that we adapt to the changing market and respond to consumers.”
Greatest failure: clinging to a business model until regulators take it from you
Jacob's parting principle for any founder. Don't let inertia turn your business into Apple — be the one who concedes early when the market signals change, instead of being forced into change by Brussels. The lesson generalizes far beyond mobile platforms.
“Every single year we could find an indie, a big company, a midsize company, a bootstrap company, a funded company... every cohort has somebody in it still alive, still thriving, still growing.”
Every cohort since the App Store opened has produced winners — there's always another boat
RevenueCat's cohort data shows successful apps founded every single year since the App Store opened, including the years pundits declared the gold rush over. The pattern: recognize an unfilled niche the moment new capabilities ship (AI, AR, new sensors) rather than waiting for proof — by then the cohort is closed.
“How I want to set it up is that I want the brand person to have a specific budget, because I feel that without a budget a brand person, they're lost. What do they do?”
Give your brand hire a dedicated budget, or they have nothing to actually do
A common failure mode is hiring a brand director and then making them beg performance for budget. Bicego's structural fix: carve out a dedicated brand budget upfront and limit stakeholder approvals so the role can actually execute instead of negotiating. Otherwise you've hired a strategist with no runway.
“A couple years ago engineers were sort of considered assets to tech companies and so people are trying to hire... if I can hire 100 people I'm worth $100 million... people are not thinking that way anymore.”
Engineers went from assets to liability — surface area is now a cost to minimize
Charlie describes a shift from headcount-as-value to headcount-as-risk. Companies with working native iOS and Android apps are migrating to React Native because maintaining two specialized teams is brittle, slow, and dangerous when a single specialist leaves. Engineering surface area is now a cost to minimize rather than a moat to grow.
“If somebody walks into a golf shop they would expect somebody to walk up and say hey what are you interested in today. That's not annoying. But then if you say oh no I'm just browsing and they follow you around the store, that's awkward.”
Roleplay user conversations to spot used-car-salesman tactics
Free-trial toggles, wheel-of-fortune offers, and backup offers all measurably lift conversion but stack into a used-car-salesman feel that raises churn and damages brand. The fix is roleplaying user reactions to each onboarding screen: if a feature would feel pushy from a salesperson in a store, it reads the same in-app.
“Brand is the only thing that transcends technology, so technologies will come and go, products will come and go — the Apple Watch didn't exist when we started the company... if you have a brand and you build trust and you have that community, whatever the thing is, if you can innovate in it you'll have an audience.”
Brand is the only thing that transcends technology
Fares's reason for grinding content for years with low view counts: technologies and product surfaces shift (Apple Watch, Vision Pro), but a trusted brand and audience carries forward. The investment isn't really in views, it's in earning permission to ship into a new format later. This is what kept him going through 75-view videos.
“SaaS, getting four to five times EBITDA isn't [unreasonable]... I would recommend getting like two to three here at consumer.”
Don't underwrite consumer-sub deals against SaaS comps — buyers price the gap
When raising debt or pitching acquirers for a CSS company, do not benchmark against B2B SaaS multiples. Consumer retention curves are structurally weaker (70% Y1 vs 90%), so debt and valuation math scale down proportionally. Crowley's M&A view: position the business honestly inside CSS norms instead of overreaching on SaaS comps and watching deals fall apart in diligence.
“So many of them have been pumped full of revenue at the time of sale. After you buy them they start to die. But also because they're quite shallow products, their longevity is very limited and we learned the lesson the hard way.”
The spray-and-pray app portfolio: pumped revenue dies on close
Blue Throne's first version bought nearly 100 small utility apps (flashlights, QR scanners) treating them as pure financial assets and ignoring product metrics. The sellers had juiced the numbers right before sale, and the apps decayed fast post-acquisition. Shallow products with no real retention have no longevity, no matter how clean the P&L looks.
“Building again from that and trying to build a second app comes with very similar risks to the first app and there's no guarantee you'll do it again. Which is why I would encourage a lot of founders out there to actually start exploring buying apps. Here it's much easier to measure the ROI of your dollars spent.”
Most founders should buy their second app, not build it
Founders who hit one win overestimate their ability to repeat the playbook. Josh's framework: compare the ROI of $1 invested in your current app vs. $1 invested in acquiring one. Apps in the $10-30K MRR range often haven't even paywall-tested or run paid; if you have a distribution edge, you can buy that traction far cheaper than you can rebuild it from zero.
“I believe the success of a test is at least 50% dependent on how you plan it how you strategize it how you hypothesize it and how you execute it and execution is just the what part maybe it's even sometimes less than 50%”
Planning and hypothesizing drive at least 50% of a test's success
Most teams over-index on execution and under-invest in test design. Alper argues the structure of your hypothesis — what you are testing, why, and what outcome changes behavior — matters as much as the creative or spend itself. Skipping this makes results uninterpretable and iteration impossible.
“don't wait to think about your monetization strategy you know you don't feel bad to charge your users they wanted to pay you and they deserve it because you're going to provide better experience for them”
Don't defer monetization — charge early and reinvest revenue into product quality
Shawn consistently advises early-stage founders to stop treating monetization as something to earn later. Revenue is the fuel for building a better product — charging users early creates a virtuous cycle where investment back into experience keeps subscribers. The reluctance to charge is usually a founder bias, not a user one.
“you can be a good CEO and a bad manager I'm legitimately not a very good manager... the craft changes They're certainly going to bring a different set of like personal values right to the process of building stuff”
CEO and manager are orthogonal skills — own it
Hulls explicitly distinguishes CEO skills (vision, capital allocation, culture, willingness to pick fights) from management skills (developing individuals, executing ops). Product managers at large companies often are not builders at all — they are strategy aligners — and the skills that make a great founder rarely produce a great middle manager. Founders who believe they are failing because they struggle with people management may actually be excellent CEOs; the two roles are not a linear progression.
“I had this safety net that I built up before... I didn't have many financial obligations of course... I didn't have kids no loans for a house... this is hard to reason about for most people like conceptualization of risk right when you are near the bottom... you can jump off a cliff and you're only falling a foot”
Jump before the rope — risk is relative to obligations
Sebastian quit his corporate job before having a single user — with one year of savings, no debt, and no dependents. David frames the underlying logic: low-obligation founders have a rare window where the downside is recoverable. 'You can jump off a cliff and you're only falling a foot.' Jumping before you have a rope also creates motivation — it forces the business to work. The risk is not as large as it looks from inside a job.
“I have two time frames it's now or later are we working on it now cool let's do it or we're working on it later sometimes later never comes and then that feature just wasn't important”
Two time frames only: now or never
Aaron ran his entire backlog with a binary priority system — features were either being worked on now or they were in a later pile where they might never surface. This isn't laziness; it's a forcing function. If a feature never fights its way back to 'now' status, the team has revealed that it wasn't important enough to build, which is valuable information on its own.
“I went back to all the other people that and said hey look we're not running a process but we got this offer because of that we had our choice”
"Two is one, one is none" when negotiating acquisition
When Nomorobo received an inbound acquisition offer, Aaron immediately contacted all prior interested parties — not to run a formal process, but to create competitive tension. A single offer gives the acquirer all the leverage; multiple simultaneous conversations put the founder in control of timing, terms, and buyer selection. He ultimately chose a smaller acquirer over a bigger one because it was a better fit — something only possible because he had options.
“I kind of got to the end of what I'm really good at what makes me special what makes like it needed to grow up it needed to graduate and that was a thing that I had a lot of time wrestling with but ultimately that was the right decision”
Know when your role as founder is complete
Aaron didn't pursue the exit because of financial pressure or burnout — he sold because he honestly assessed the boundary of what he was uniquely capable of building, and recognized the company had outgrown it. The acquisition came after a decade of profitable, self-funded growth, not as a rescue. Identifying when your specific contribution is complete, and acting on it rather than holding on, is what turned a lifestyle business into an 8-figure exit.
“product-led growth is always kind of shiny you mean just make the product better and they will come right... if you're like a business person accept it and work on paid and make that the best LTV on CAC”
Don't fall into the product-led growth trap if it's not your DNA
Francescu warns against chasing product-led growth as a default because it sounds noble. If an app doesn't have an inherently viral distribution loop, spending six months on a referral feature won't change that. Know your actual growth DNA and invest in the engine that matches it, whether that's paid acquisition, paywall optimization, or built-in sharing.
“our CEO encouraged a quote from Brian Armstrong at Coinbase where action gets information... in hindsight it might be a flash in the pan but in forward sight it might actually help guide your future decisions... we're always coming from the lens of like how does this improve the user experience not wouldn't it be cool if we shipped this thing”
Action gets information: flash-in-pan features still teach you real things
When features do not retain users long-term, ElevenLabs frames them as data-gathering wins rather than failures. The act of shipping generated market intelligence no pre-build research would have revealed. The condition for this framing to hold is starting from a genuine user problem rather than from 'wouldn't it be cool if.' Features built on real problems teach real things even when they eventually get replaced.
“our sense is probably each product will have a growth person who has like really great taste and really great ideas and then you work with the engineering team and you go okay I'm going to launch a product so say we're launching image and video creation in our app you then chat with an agent and you're like hey we're launching this product it then like literally checks through your codebase it checks through online like competitive landscape it reads through all your internal docs”
The future marketer is one person directing AI agents through the entire launch pipeline
Luke's prediction: within a couple of years, a single growth-minded person with taste will direct a suite of AI agents that handle the entire launch pipeline — competitive research, messaging, storyboard, video production, localization, ad variants, and performance monitoring. The job title shifts from 'marketer' to 'creative director of agents.' For solo founders today, this is already partially achievable by stitching existing tools together.
“we started the year with 9,000 paying subscribers and we'll beat aggressive targeting closed the year north of 50,000 paying members”
9K to 50K paying subscribers in one year running TikTok as the only paid channel
Ladder entered 2023 with 9K subscribers and closed the year at 50K+ — a 500%+ gain — running a single paid channel (TikTok) while maintaining top-of-benchmark monthly retention. The growth came from an entirely in-house motion: no agencies, founder and creative director running ads personally, organic signals feeding paid decisions, and a web quiz converting cold traffic. The business was profitable on a per-user basis in low single-digit months throughout.