Designing Ventures For Profits, Not Exits – Part II

The second in a two-part webinar series titled Designing Ventures for Profits, Not Exits, held on March 20, 2026.

The Built to Hold (B2H) Venture Design Lab hosted the second of a two-part webinar series on March 20, 2026, focused on the theme Designing Ventures for Profits, Not Exits. The session was co-led by Erik Simanis and Patrick Donohue, co-directors of the lab and co-founders of venture design firm Half-Solved, and who were joined again by Mark Yde, a former Entrepreneur-in-Residence at the lab who now leads work at Ajinomoto Group Ventures.

The webinar built directly on the prior session, which had examined the financial shortcomings of the Lean Startup methodology when applied to ventures built to be held rather than sold.

You can view a recording of this session at the bottom of the post.

Recap: Why Lean Startup Fails Build-to-Hold Ventures

Patrick Donohue opened with a brisk recap of the core problem established in the previous session. Lean Startup’s approach—experimenting and pivoting live in market with a customer-driven MVP—produces success rates in the low single digits when success is defined as reaching profitability. Ventures following this path routinely operate at a loss of 40% or more of revenue for over a decade before discovering whether a path to profit even exists.

While this model is workable for venture capital funds—which can diversify across hundreds of bets and exit at revenue multiples before any single venture turns profitable—it is disqualifying for builders who intend to hold. Corporations, legacy entrepreneurs, and deep impact investors all depend on realized cash flows from the business itself. The time value of money ensures that a decade-long loss trajectory pushes required long-term profits far beyond what most opportunities can actually deliver.

Donohue identified three structural drivers behind these poor outcomes:

  • First, open-ended idea generation without a profitability objective function causes founders to anchor on what is accessible rather than what is financially optimal—a problem analogous to hill-climbing algorithms that land on local optima rather than finding the highest peak.
  • Second, anchoring around customer needs leads to ideas with low monetizability, because customers are rooted in their existing routines and blind to transformational possibilities.
  • Third, optimizing the product for the customer—without regard for the full system—drives up cost structures in ways that foreclose profitability before the venture even launches.
Three structural drivers from lean startup that decrease your probability of success

Finally, a Blue Apron example was used to illustrate how all three dynamics combined to doom an entire category: despite genuine product-market fit and relentless iteration, subscription meal kit companies were structurally trapped by high logistics costs, expensive customer acquisition, and chronic churn.

The FIT Startup Method: Three Practices

Erik Simanis introduced FIT Startup as a methodology designed from the ground up for build-to-hold ventures. Rather than tweaking Lean Startup at the margins, FIT inverts its logic. Positive NPV—a measure of profit that incorporates both time value of money and risk—is treated as the central objective function. Everything else flows from it.

Two principles underpin the method: design for robustness rather than for the customer, and pivot on paper rather than in market.

FIT Startup Framework
Screenshot
Practice 1: (F) Fortify financial vital signs

The probability that a venture is profitable at launch is governed by two metrics. Customer ROI is the spread between the value a product creates for the customer and the price paid for it. A large customer ROI absorbs product underperformance and accelerates adoption. Targets range from above 50% for low-ticket items to 300–1,000% for high-priced products. Margin of safety is the spread between the lowest price customers will accept and the highest anticipated full unit cost, including cost of capital. Given that major projects routinely see cost overruns of 60% or more, a margin of safety well above that threshold is essential.

Simanis illustrated both metrics using a back-of-the-envelope reconstruction of Airbnb at launch. Treating a seven-night stay as the unit of product and Airbnb hosts as the primary customer, the analysis produced a customer ROI of 116% and a margin of safety of 133%—unusually strong numbers that help explain why Airbnb grew explosively and was cash-flow positive from operations almost immediately.

Practice 2: (I) Innovate around structural profit barriers

Every unmet market opportunity exists because something is blocking profitable commercialization—not because nobody has thought of it. Simanis calls these structural profit barriers, and the lab has catalogued ten of them across three categories: barriers related to foundational operations, barriers that prevent reliable customer adoption, and barriers that undermine customer retention and cash preservation.

The critical insight is that these barriers must be circumvented or eliminated, not optimized. The way to do that is to productize the strategy—that is, to reshape the product idea itself so that it channels the barrier-circumventing strategy directly, eliminating entire categories of business model activity and the costs that come with them.

Tesla was offered as a case study: by functioning as an energy transformation company rather than a pure electric vehicle manufacturer, Tesla’s product architecture sidestepped the cost barriers that have made every other non-Chinese EV manufacturer unprofitable.

The microfinance industry provided a second example: Mohammed Yunus’s peer-group loan structure eliminated the need for costly individual credit due diligence while simultaneously driving repayment rates above 98%, enabling low interest rates and explosive customer acquisition.

Practice 3: (T) Triangulate using testable logic

Designing robust strategies to circumvent profit barriers requires that those strategies be grounded in science rather than assumption. Testable logic means that the mechanism by which a strategy works can be explained using established scientific or behavioral theory—which in turn allows modelling with high fidelity, credible numerical estimation, and stress-testing on paper.

The human flight analogy was used to clarify the point: centuries of failed attempts to fly by mimicking birds produced no testable insight; Bernoulli’s principle finally provided the scientific foundation that made rigorous design, modelling, and simulation possible before any aircraft was built.

Simanis walked through a live case: a global food company targeting micronutrient deficiency in rural Indian children. Two years into a pilot, the company was losing $10 million annually despite selling hundreds of thousands of product packets. Applying testable logic, the team diagnosed the critical limiting operation—the enormous sustained marketing cost required to persuade mothers to supplement their children’s diets—and traced its root cause to maternal identity: in the relevant cultural context, a mother’s status is bound to feeding her family from her own cooking, making purchased nutrition supplements feel like an admission of failure. Drawing on positive psychology and self-affirmation theory, and then on the behavioral concept of temptation bundling, the team arrived at a reframed product: a gamified food vehicle that helped children eat the mother’s own cooking rather than replacing it, sold through rural pharmacies to establish health credibility and bypass conventional retail noise.

Q&A Discussion Highlights

The session closed with a rich discussion. On the question of corporate-startup partnerships, Simanis cautioned that involving a corporation’s existing capabilities early in the design process tends to constrain the solution space and push ventures toward conventional approaches—precisely the ones that already have structural barriers. Corporate assets such as customer data, distribution, and manufacturing expertise are most valuable after the right product architecture has been determined, not before.

On validating demand, Simanis argued that the type of problem targeted fundamentally determines demand uncertainty. Problems in three monetizable categories—money loss, fear and shame, and stress—differ dramatically in how objectively and reliably customers will pay to have them solved. Money problems and shame problems carry far higher and more predictable monetizability than convenience or stress problems, which is why so many ventures chasing the latter category struggle to convert initial interest into sustainable revenue.

The session wrapped with an announcement of upcoming programming including a two-and-a-half-day introductory FIT workshop, a twelve-week venture training studio, and a graduate course applying the methodology to energy-sector opportunities.

Video