The Innovation Stack Building an Unbeatable Business One Crazy Idea at a Time

In one sentence▶ 0:08

Entrepreneurial advantage often comes not from one brilliant invention but from an interdependent sequence of original solutions—an “innovation stack”—developed while addressing a problem existing systems have ignored. The resulting business is hard to copy because competitors must reproduce the whole system, not merely its visible product.▶ 0:09

Overview▶ 0:31

McKelvey begins with the practical frustration that led him and Jack Dorsey to create Square: small merchants struggled to accept credit cards. Square’s challenge was larger than designing a card reader; it involved pricing, hardware, software, onboarding, payments infrastructure, risk, and trust. When Amazon copied Square’s product, undercut its price, and promoted the alternative, McKelvey treated Square’s survival as evidence that the company’s real advantage lay in its connected solutions rather than in the reader alone.▶ 0:32

The book broadens the argument through historical cases including A.P. Giannini’s Bank of Italy, IKEA, and Southwest Airlines. McKelvey presents these companies as examples of founders who served overlooked or excluded customers by inventing new ways to operate, thereby expanding markets instead of merely fighting for existing share.▶ 1:03

Core ideas▶ 1:25

An innovation stack is a chain, not a feature▶ 1:27

A novel customer problem exposes secondary problems that established businesses have no reason to solve. Each answer creates the conditions for the next answer, producing a mutually dependent system. Individual components may be imitable; the complete sequence is much harder to reconstruct.▶ 1:31

Start with the “perfect problem”▶ 1:50

The most promising problems are both genuinely painful and poorly served by existing institutions. McKelvey emphasizes opportunities where solving the problem makes a product accessible to people previously excluded—such as small merchants, ordinary bank customers, budget-conscious furniture buyers, or underserved air travelers.▶ 1:52

Necessity can generate better innovation than planning▶ 2:13

The book’s innovators generally did not begin with a complete master plan. They encountered an obstacle, solved it, discovered another obstacle, and continued. Innovation is therefore portrayed as adaptive problem-solving under pressure rather than as a purely visionary exercise.▶ 2:17

Competition is not always the right comparison▶ 2:34

McKelvey distinguishes creating a new market from winning an existing one. If a company makes a previously inaccessible activity simple or affordable, its growth may come from expanding participation rather than taking customers from rivals.▶ 2:37

Persistence is operational, not merely emotional▶ 2:52

“Perseverance” in the book means continuing to address concrete constraints: regulatory, technical, financial, logistical, and cultural. The founder’s job is not simply to believe in the idea but to keep building the missing infrastructure around it.▶ 2:56

The founder’s outsider position can be useful▶ 3:13

McKelvey’s lack of traditional payments expertise is presented as an advantage because it made industry assumptions visible and questionable. Outsider status is not automatically beneficial, but unfamiliarity can help reveal rules that incumbents mistake for necessities.▶ 3:16

Practical takeaways▶ 3:33

• Choose a problem that matters to people current systems neglect, not merely a market that looks large.▶ 3:34
• Map the adjacent problems your initial solution creates. Those dependencies may become the real source of defensibility.▶ 3:40
• Ask whether you are improving an existing market or making participation possible for a new group.▶ 3:48
• Treat industry conventions as hypotheses. Verify which constraints are technical, legal, economic, or simply habitual.▶ 3:54
• Build the system required by the customer outcome, even when that means entering unfamiliar domains.▶ 4:03
• When a large competitor copies the visible product, examine whether it can reproduce the underlying relationships, processes, trust, and infrastructure.▶ 4:10
• Use historical analogies cautiously: identify the specific mechanism shared by the cases rather than copying their surface tactics.▶ 4:20

Caveats and counterpoints▶ 4:30

• The argument is based mainly on memorable founder narratives and retrospective interpretation, especially McKelvey’s account of Square; it is better read as a conceptual framework than as a tested general law. A serious review notes that the book’s stronger claims about innovation stacks being broadly “competition-proof” are not fully persuasive.▶ 4:32
• The cases involve unusually capable founders, favorable timing, capital, networks, and market conditions. A stack may make imitation harder without making a business durable, profitable, or socially beneficial.▶ 4:53
• Solving many interconnected problems can create complexity, regulatory exposure, and execution risk. The approach may fail when a simpler product, distribution advantage, or fast follower is more valuable than a deeply integrated system.▶ 5:07
• The book’s inclusion-centered view of innovation is attractive but incomplete: expanding access can still produce harms, externalities, or unequal outcomes, and the narrative does not constitute independent evidence that every featured company improved its market in all respects.▶ 5:22

Questions worth revisiting▶ 5:41

• Which customer group is poorly served because incumbents consider it too small, difficult, or unprofitable?▶ 5:43
• What secondary problems would appear if I solved the initial problem successfully?▶ 5:50
• Which parts of my business are genuinely interdependent, and which are merely bundled features?▶ 5:55
• Am I building a new market or competing for existing demand?▶ 6:01
• What assumptions from the incumbent industry am I accepting without testing?▶ 6:05
• Could a competitor copy my product without copying my operating system, trust mechanisms, or infrastructure?▶ 6:09
• What evidence would show that my innovation stack is creating durable value rather than unnecessary complexity?▶ 6:16

Return to this when…▶ 6:23

Return to this book when evaluating a startup idea that serves an overlooked customer, when a competitor copies your visible product, or when you need to distinguish a defensible system from a clever but easily replicated feature. Revisit the caveats before treating the innovation-stack concept as a universal formula.▶ 6:25