Concept card

Platform Risk

As of 2026-07-23

Edited by Cédric-Olivier Mâry, 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

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.
Classified under Brand & Influence (Advanced) — depth-of-field knowledge, used to anchor rate negotiations.
Tagged: foundation — surfaces in the Academy search alongside related tracks.
Platform Risk is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.

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.
Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.
Adoption metric: The measurable behavior proving that the concept changed actual work after go-live.
Reusable IP: An artifact, checklist, or model that can be reused across clients without copying client-specific data.

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.

Open in the app →