The Application Layer Kill Zone: Feature Differentiation Just Died — Here's What Survives
The Data Is In: Integration Beats Apps
The most consequential product strategy signal this week comes from a single comparison: Palantir grew U.S. commercial revenue 109% in 2025 by being the integration and orchestration layer atop enterprise stacks. Meanwhile, Salesforce, SAP, and Adobe — companies with massive product portfolios and entrenched customer bases — managed roughly 10% growth. Palantir doesn't build LLMs. It lets customers use "the best proprietary and open source models" while providing the data integration across Snowflake, Salesforce, SAP, and custom systems that makes AI actually work. The lesson is stark: in the age of AI agents, the orchestration layer is capturing nearly all incremental enterprise spending.
When World View's CEO said 'I'd like to have a pure Palantir-enabled solution without having to have other SaaS tools,' he articulated every enterprise buyer's dream — and every SaaS PM's nightmare.
Foundation Models Are Eating Your Vertical
In the past quarter alone, Anthropic launched Claude Code (competing with every AI dev tool), acquired desktop assistant Vercept (Madrona's own portfolio company), and Cowork shipped a legal review tool competing directly with startups like Luminance. Three verticals, one quarter. Felix Rieseberg of Anthropic was explicit: specialized AI vertical wrappers face compression as general models improve. Their Skills ecosystem — simple markdown files describing API endpoints — means adding a new vertical capability to Cowork is "writing a text file, not building an integration." March Capital's Sumant Mandal posed the existential question at the Montgomery Summit: 'Where does the model end and the application begin?'
OpenAI Frontier Threatens Per-Seat SaaS
OpenAI's Frontier platform is designed to sit above your entire enterprise software stack as a unified intelligence layer. If a CIO can deploy one orchestration layer providing AI across Salesforce, ServiceNow, Workday, and your product simultaneously, per-seat premiums for native AI features evaporate. Salesforce is already pivoting to consumption-based pricing — a multi-billion-dollar incumbent signaling the moat around embedded AI features may be gone.
What's Still Defensible
Ryan Hoover's new defensibility framework is brutally honest about what survives: social graphs, distribution, licensing, data, and hardware. Notice what's missing: software logic, feature cleverness, workflow design — the things PMs typically obsess over. The surviving companies share one trait: products that get meaningfully better the more a specific customer uses them. Runway customizes models with studio film libraries. Paradigm automates PE research with proprietary financial data. Luminance leverages legal case history. Every feature that works equally well for a Day 1 user and a Day 365 user is a feature Anthropic can clone.
| Category | Defensible? | Example |
|---|---|---|
| Proprietary data flywheel | Yes | Runway (studio libraries) |
| Distribution / embedded workflow | Yes | Palantir FDE model |
| Social graph / network effects | Yes | Cal scheduling primitive |
| Software logic / feature parity | No | Any AI wrapper |
| Model access / API wrapper | No | Jasper ($80/mo → disrupted) |
What to do
Run a defensibility audit on every planned feature: tag each as (a) replicable by a foundation model update or (b) dependent on proprietary data/workflows that compound over time. Deprioritize category (a) this sprint.
Identify and accelerate one 'data flywheel' feature that gets meaningfully better with customer usage — create a 2-page proposal by end of next sprint.
Stress-test your pricing model: model what happens if 30% of users shift from per-seat to consumption within 18 months.
Evaluate whether your product is a 'platform,' an 'orchestration layer,' or a 'data source' in the emerging stack — and present findings to leadership.