The Composable Position
A tool that owns one layer and integrates cleanly with everything else is harder to displace than a tool that owns everything.
Blog
The Knowledge Layer
Data is not knowledge. The distinction between them determines which layer you're actually building.
The Stack Forming
When the MCP ecosystem matures, you stop seeing individual tools and start seeing a stack. The gap moves from 'unbuilt' to 'one specific layer.'
The Educational Wave
When domain experts start teaching AI workflows to their audience, the DIY wave is already cresting. The product wave follows.
The Enterprise Gap
Enterprise AI tools solve the problem for large firms. The gap is the everyone else.
The Sub-Module Problem
When the fragmentation reaches the sub-task level, the integration problem is larger than it looks.
The Module Valuation Trick
When a sub-module of a workflow raises at unicorn valuation, you can back-calculate the total addressable market.
The Protocol-Native Position
Building at the protocol layer is a different strategic position than building a vertical specialist. Both are valid. They compete differently.
The Vertical Fragmentation Tell
When each slice of a workflow gets its own dedicated tool, the integration layer is the next opportunity.
The Builder Who Walks the Chain
When the same team builds the same tool for adjacent domains in sequence, they're leaving a map.