Map the Five Pillars of Defensibility
Categorise the venture's defensive assets strictly into patents, trade secrets, proprietary data loops, network effects, and structural moats. Deconstruct how each mechanism operates in practice to impede competitors, boost customer retention, or lower acquisition costs over time. Pinpoint the precise interaction between technical IP and market-based defensibility drivers.
Categorising these elements isolates the precise mechanisms that create long-term enterprise value and pricing power. This focus prevents founders from relying on weak, easily copied product features as their sole defensive strategy.
A structured Defensibility Matrix detailing the five pillars, explicitly mapping how each asset deters copying or creates switching costs. The mapping must specify whether each pillar relies on legal protection, technical complexity, or scale.
Five questions an expert would ask when reviewing your output
Use these to challenge assumptions, pressure-test your logic, and check the quality of this action's output in the context of the parent task and wider venture development.
- 1
Which of your five claimed defensibility pillars provides immediate protection versus requiring substantial scale before becoming active?
- 2
How exactly does your product architecture create a flywheel where each new user measurably increases value for existing users?
- 3
What specific proprietary data are you capturing that competitors cannot easily purchase, scrape, or synthesize?
- 4
If a well-capitalised competitor copied your core user interface tomorrow, what technical trade secret prevents them from matching your performance?
- 5
Why do you assume your proposed network effects will create high switching costs rather than merely multi-homing behaviour?