Framework
Portfolio of Solutions, Not a Portfolio of Software
Jason's reframe of what Kindling is actually accumulating.
How it works
- 1As the problem count grows, patterns surface at two levels.
- 2Macro: which industry does this problem belong to.
- 3Operational: where in the demand fulfillment life cycle does it sit, whether that is customer acquisition, fulfillment, HR, or finance.
- 4His phrasing for the strategy: peanut butter spread problem-solving across many solutions, and the big outcome arrives from the spread rather than from the one bet.
Hear it on the podcast
The 10-Minute Morning Routine That Replaced an Entire Project Management StackListen to the episodeMore from this episode
The Prototype-to-Production CanyonJason's core point on why vibe coding a working demo is nowhere near a shippable product.Build GovernanceKindling's decision layer for what gets built.The Chief of Staff PatternThe app Jason has in testing. Structurally it is two agents working a shared surface.The Scope DumpJason's antidote to avoidance-by-unknown-scope.The Pressure LineThe diagnostic both of them land on.Ryan's First Anti-Avoidance MoveOne item from a list of twelve, framed as Ryan's personal conviction rather than a business tactic.
Get the next framework first
One email a week with the frameworks, tools, and founder stories from the podcast. Free.
More frameworks for Strategy & Moats
License or DefendThe two-sided consumer product.The Source®, Her Creative OSThe intelligence layer under the agency.Digital DarwinismHer term, and her TEDx thesis.The 20% Better MissionCEOfriend's stated reason for existing, and why the price ceiling is deliberate.Focus Before Generalizing the PlatformLUCID could sniff Parkinson's, Alzheimer's, explosives, currency, or a missing person's shirt.Triage, Not DiagnosisA positioning discipline that doubles as the moat in a regulated category.