Platform Data Wars: SAP Closes the Gate While Anthropic Storms the Castle
Two Moves, One Pattern: The Data Layer Is the New Moat
A product manager at a mid-market ERP vendor spent Tuesday morning reading two news items and closed the tab with a worse roadmap than she woke up with. SAP blocked all third-party AI agents from its APIs, reserving access for its own Joule and Nvidia's NemoClaw, and in the same week committed €1B to acquire Prior Labs for a proprietary lab focused on structured enterprise data. The same week, Anthropic shipped 10 purpose-built finance agents covering pitchbooks, credit memos, KYC, and month-end close, wired through Microsoft 365 and Moody's data. FactSet dropped 8% in a session.
Read together, the two moves describe one pattern. SAP is pulling the fence inward. Anthropic is routing around the fence by partnering with alternative data (Moody's) and reaching the workflow through Microsoft's pipes. The thing being pitched is "AI agents." The thing actually being done is a renegotiation of who charges rent on enterprise data access.
The question on a PM's desk is no longer 'how good is our AI' — it is 'who owns the pipes our AI needs, and have they started charging rent yet.'
Sierra Proves the Standalone Agent Category Is Real
Sierra crossed $150M ARR serving more than 40% of the Fortune 50, and raised $950M at a $15B+ valuation. Those are production deployments at companies whose procurement takes two quarters to say yes. Bret Taylor separated the thing most teams conflate: an "AI assistant for X" is not the same product as "AI that owns the outcome of X." Enterprise buyers paid separately, rather than wait for the incumbent's marketplace, because the second framing commands roughly 10x the monetization.
Short Sellers Confirm the Displacement Clock
Viceroy Research, the firm that shorted Wirecard, is now publicly screening for "high margin businesses with clean balance sheets that happen to be in the crosshairs of a new technology roadmap." That is professional capital running the displacement thesis as a systematic filter. Competitive narrative has to answer the AI-moat question before the short report lands, not after.
The 2x2 for Your Integration Roadmap
| Platform API Dependency | Thin Integration / Own Data | |
|---|---|---|
| Platform admin buyer | ⚠️ Danger cell — SAP just redrew this | Moderate risk |
| Line-of-business buyer | Vulnerable — migrate this quarter | ✅ Safe cell — build here |
Any integration roadmap that assumes a major platform's API will stay open should be rewritten this sprint, with longer procurement cycles and rev-share priced in. The work this week is naming the one integration on the roadmap to kill before engineering spends another six weeks on an API that may be gone by the time the feature ships.
What to do
Audit all integrations that depend on SAP, Salesforce, ServiceNow, or Workday APIs and classify each as 'endorsed partner' vs 'at risk of lockout' by end of this sprint
Evaluate whether your product owns the data, the workflow, or the approval step — document which for your top 5 revenue-generating features by next planning cycle
Model a 'Sierra-style' outcome ownership positioning for your core use case — what measurable business result could you guarantee end-to-end?