Lenny's PodcastJason Fried challenges your thinking on fundraising, goals, growth, and more
CHAPTERS
Bootstrapping as an alternative to the “unicorn” default
Jason opens with a case for bootstrapping as a practical path to business success, not a consolation prize. He argues most founders over-index on raising money and chasing outlier outcomes, when there are many viable “landing spots” for profitable companies.
- •Bootstrapping builds the fundamental skill of making money
- •Venture-backed success is an outlier; most companies won’t reach unicorn scale
- •Optionality: many sustainable business outcomes exist between small and massive
- •Framing: this is “a way to be,” not a prescription for everyone
37signals’ scale: small team, big profits, long-term independence
Lenny introduces 37signals as a highly profitable, long-running company that rejects typical venture outcomes. Jason shares the metrics he cares about (profit, durability) and dismisses vanity metrics like revenue or growth targets.
- •Profitable every year for 24 years; double-digit millions in annual profit (recent decade)
- •~100,000+ customers with ~75 employees
- •Profit and healthy margins enable experimentation and reduce fear
- •No OKRs/KPIs/revenue targets; focus on spending less than you make
When raising money actually makes sense (and when it doesn’t)
Jason distinguishes capital-intensive businesses from software businesses that can start cheaply. He critiques how software—typically high-margin—gets distorted into low-margin operations through overhiring and heavy acquisition spend.
- •Funding is often necessary for hardware, factories, restaurants, and capex-heavy startups
- •Software can start with laptops + a few people; margins should be very high
- •VC incentives push spending (people + marketing), eroding profitability
- •Venture funding narrows outcomes to “go huge,” skipping viable mid-scale success
How 37signals stays lean vs. overstaffed competitors
Lenny contrasts 37signals’ headcount with major competitors’ thousands of employees. Jason explains the operational choices that keep the company small: limited pricing complexity, no enterprise focus, no sales team, and simpler product scope.
- •Focus on efficiency over growth
- •No salespeople; minimal tiers; one codebase and broadly shared product
- •Basecamp caps revenue per account ($299 for unlimited users), reducing enterprise complexity
- •Small, simple offerings avoid support/customization burdens that inflate headcount
Redefining success: joy, pride, and repeatability over targets
Jason defines success as whether he’d want to do it again, emphasizing enjoyment and sustainability. He describes a values-driven approach where profitability matters in aggregate, but not every action must be optimized or measured.
- •Success test: “Would I want to do this again?”
- •Company-level profitability matters; per-product micro-optimization is de-emphasized
- •Skepticism of measuring everything; some choices are ‘right’ regardless of A/B results
- •No financial or growth goals; evaluate the whole year by net profit
Infinite games: entrepreneurship as a long career continuum
Lenny introduces the “infinite games” mindset; Jason connects it to his own experience working since age 13. He frames entrepreneurship as a job you can keep refining over decades, and explains why exits and forced endings don’t appeal to him.
- •Career as continuum: selling as a teen → building and selling software today
- •Entrepreneurship is a job; build the company you want to work at
- •Independence enables evolving the company into “anything we want”
- •Exit timelines and investor expectations conflict with long-term play
Startups vs. ‘stay-ups’: staying in business is the real challenge
Jason critiques the cultural obsession with starting companies, arguing durability is harder than launch. He talks about plateaus, motivation beyond growth highs, and the realities of multi-decade endurance.
- •Starting is easier than staying; durability is the real achievement
- •Plateaus are inevitable; you must actually like the work to persist
- •Even profitable businesses experience wavy years; year-over-year comparison can demoralize
- •The goal is to stay in the game, not chase constant novelty
25 years in: energy cycles, missed opportunities, and choosing ‘our way’
Jason reflects on periods of waning excitement and renewed motivation, especially around new product exploration. He imagines how a growth-oriented leader might run 37signals differently—and why he’s still comfortable leaving opportunities on the table.
- •Founder energy fluctuates; current excitement driven by new product work (Once)
- •Curiosity about what a different operator would do (more products, more marketing, lower margins)
- •Acknowledges ‘missed opportunities’ but embraces trade-offs
- •Resists optimizing for ‘all the things we could do’ in favor of what they’re doing
Venture scale vs. bootstrapping: mindset, not category (mostly)
Jason argues many software businesses could be run either as venture-scale or as lean profitable companies—it’s often a strategic choice. He notes some businesses (Uber/Airbnb) require rapid physical-world scale, while pure software doesn’t inherently need it.
- •Similar products can be operated with very different models (e.g., Basecamp vs. Monday)
- •Venture scale can be a mindset: growth, spending, expansion
- •Physical network effects and logistics can justify venture funding (Uber/Airbnb examples)
- •Software’s global availability reduces the need for capital beyond marketing
Shape Up: building with appetites, six-week cycles, and two-person teams
Jason lays out the core of Shape Up: work is constrained by appetite (time budget), not estimated duration. Teams are tiny, autonomy is high, and projects must ship within hard limits—otherwise they’re cut or killed.
- •Appetite vs. estimate: fix the time budget, shape the scope to fit
- •Six-week maximum cycle; often shorter; typically one designer + one programmer
- •No ticket factories or exhaustive specs; teams define tasks to deliver the shaped pitch
- •If unfinished, projects usually die unless clearly on the downhill execution side
No promises and careful change adoption: how to avoid organizational thrash
Jason explains why public promises—especially “by the end of the year”—create failure dynamics. He then describes how teams should adopt new methodologies like Shape Up incrementally using low-criticality projects to build skill and avoid backlash.
- •Promises distort execution; “by end of year” is a particularly dangerous commitment
- •Share what you’re working on, but avoid binding delivery dates
- •Organizations have momentum; large changes require energy and time
- •Adopt new methods first on low-stakes projects; bring lessons into critical work later
Cooldowns instead of endless sprints: sustainable pace and internal freelancing
Jason rejects the sprint metaphor because it implies exhaustion and repeated overexertion. 37signals uses two-week cooldowns after cycles for bug fixes, small improvements, and shaping the next cycle’s pitches—creating rhythm and recovery.
- •Sprints back-to-back create burnout; cycles imply repeatable sustainability
- •Two-week cooldowns: polishing, bug fixes, unscheduled ‘important small stuff’
- •Parallel shaping work: leaders prepare and write pitches for the next cycle
- •Varied work modes refresh teams and reduce demoralizing long projects
Gut-driven decision-making: operationalizing judgment, taste, and ‘how it feels’
Jason argues most decisions are judgment calls even in “data-driven” cultures. He describes how 37signals normalizes intuition by asking “what do you think/feel?” and avoiding ‘justify with metrics’ dynamics, while still using data as an input when useful.
- •Decision-making is inherently human and multi-factor; data is only one input
- •Create cultural permission by modeling intuition-led decisions as a leader
- •Language matters: ask “what do you think?” and “how does it feel?”
- •Avoid certainty theater and “prove it” demands; ship to learn from reality
Hiring for taste and instincts: paid projects, critique, and creative riffing
Jason shares how he evaluates designers and product people through paid one-week projects and live critique. He looks for clear execution plus an ability to riff productively—evidence of both discipline and a fertile “gut” for good ideas.
- •Selectivity enabled by low hiring volume; focus on taste and influences
- •Paid trial projects for finalists; evaluate clarity, thoughtfulness, time management
- •Critique sessions include pushback even when work is strong
- •Key signal: ability to riff on improvements and engage in resonant collaboration
Bootstrapping tactics, constraints, and the ‘practice’ of profitability
Jason gives pragmatic advice for bootstrapped founders: control costs, delay hiring, and avoid premature spending on offices or branding. He emphasizes stoic ‘negative visualization’—making peace with the worst outcome—as a way to take risks sanely.
- •Stay as small as possible; costs are the primary controllable variable
- •Do as much as you can yourself before hiring; each hire adds cost and complexity
- •Avoid unnecessary spending (office, branding); use cheap tools and simple setups
- •Negative visualization: be at peace with failure scenarios to keep moving
Work isn’t war: language, metaphors, and building as an alternative to conquest
Jason critiques war metaphors in business (“target customers,” “sales force,” “make a killing”) and argues they shape a toxic mindset. He proposes a creation-oriented perspective focused on pride, alternatives, and additive contribution rather than destruction.
- •War metaphors drive unhealthy posture and culture
- •Reject ‘Navy SEAL’ management tropes for ordinary software contexts
- •Aim to create great alternatives, not ‘destroy competitors’
- •Pride, craftsmanship, and creation produce a healthier work environment
Strategy in one line + the Once product line: pay-once software, Campfire returns
Jason summarizes his philosophy (“keep making great shit”) and then explains Once: downloadable, self-hosted business software you buy once. He previews relaunching Campfire as the first Once product, explains optional upgrades, code access, and why this is creatively energizing for the team.
- •Strategy: keep costs in check, price appropriately, share generously, let outcomes happen
- •Once thesis: SaaS dominance + subscription fatigue creates room for buy-once alternatives
- •First product: Campfire relaunch (self-hosted chat) under Once; priced under $1,000
- •Buy-once enables ‘backup/air-gapped’ use cases; code included for learning/modification
- •Release approach: limited rollout mid-December 2023; broader availability after tightening
