Concept card

Platform Risk

As of 2026-10-09

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Platform Risk?

An audience built entirely on someone else's platform (LinkedIn, Substack) can be destroyed overnight by a single policy change — the hedge is owning an email list and a website.

What it is

Platform risk is the exposure a consultant carries from specialising in a stack whose demand, licensing model or strategic direction is controlled by a single vendor.

Why it matters

Deep specialisation is how a consultant commands a premium, and it is simultaneously the concentration of their entire book into one vendor's roadmap. Both facts are true, and the mistake is treating the risk as a reason not to specialise rather than as something to price and hedge.

The risk rarely materialises as a collapse. It materialises as a slow re-pricing: a skill that cleared a premium becomes a commodity as tooling improves and the trained population grows, and the consultant who has not noticed is the last to adjust.

How to read your own exposure

Three questions. What fraction of your last four engagements depended on one vendor's product line? How much of your differentiated knowledge would survive that product being repackaged or absorbed? And how quickly does the vendor itself re-platform — a vendor that consolidates SKUs regularly is one whose specialists re-learn regularly.

SAP's own direction is a live example worth tracking rather than assuming: platform consolidation changes which skills are scarce and which become table stakes (SAP News Center — the autonomous enterprise).

Why it matters in practice

Platform policy changes have destroyed audiences overnight in practice — this isn't a theoretical risk, it's a documented pattern.
An owned email list and website survive any single platform's algorithm or policy shift — a rented audience does not.

Key points

The exposure you carry when your audience lives on someone else's platform (LinkedIn, Substack).
Platform policy changes have destroyed audiences overnight.
The hedge: own an email list, own a website.
SAP's own 2026 AI consolidation (Business AI Platform unification at Sapphire in May 2026; Dremio and Prior Labs acquisitions completed on 6 and 17 July 2026, SAP-RPT-1.6 superseding 1.5 within weeks) is the fastest-moving live example of the re-pricing signal this card describes.
A specialism named after a specific SKU (e.g. 'SAP-RPT-1.5 expertise') has a shelf life measured in SAP's release cadence — currently weeks for the AI Platform line, not the 18-24 month cycle typical of mainstream certifications.
SAP's AI Agent Hub is a double-edged factor: a symptom of SAP consolidating governance, but also a partial hedge for consultants whose skill is portable across vendors via MCP rather than tied to one stack.

Terms used on this page

Inbound lead: A prospective mission where the client reaches out first — the leading indicator of brand health.
Content pillar: A recurring topic (e.g. Datasphere design, SAC pitfalls) that anchors a freelance's public voice.
Reusable IP: An artifact, checklist, or model that can be reused across clients without copying client-specific data.
SKU-named specialism: A skill or content pillar defined by a specific product version (e.g. 'SAP-RPT-1.5 expert') rather than by the underlying decision it supports — the fastest-decaying form of platform-anchored positioning.
Re-pricing signal: A public vendor action (an acquisition, a renamed product, a repackaged SKU) that precedes a shift in which skills the market pays a premium for, typically by a year or more — SAP's 2026 acquisition cascade is the clearest recent example.
MCP-portable skill: Expertise expressed through an open, cross-vendor protocol (Model Context Protocol) rather than a single vendor's proprietary interface — structurally more hedge-resistant to any one platform's re-pricing.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →