Moat.
Speed.
Allocation.
The platform moat that survives 2028 is being chosen this year.
This briefing tells you which platform moats survive 2028 in media and communications as AI rewrites build economics. Read it before your R&D allocation locks for the decade.
The 10-page briefing. Worth 20 minutes.
One email. One PDF. Worth twenty minutes of your week.
We send it once. Work emails only.
Tuesday 09:30, platform review. Subscription churn at eleven point four percent, slightly above plan. The new paywall A/B test live in week two. Streaming app rating climbing. Your VP Engineering opens with the dashboard. He is mid-sentence when your phone buzzes. CFO email: "Schibsted's Q1 numbers are out. They named the OpenAI licensing line as recurring revenue. What is our equivalent?" Editorial asked yesterday for KB-Whisper deployment in the Stockholm newsroom. The board's strategy day next month has "AI in media" on the agenda and you have not been invited as the topic owner.
You are not running one technology function. You are running two, and only one is on your scorecard. One funds the CMS, the streaming pipeline, the ad-ops stack. The other funds what has to exist by 2028: the rights graph that ties every piece of content to every monetisation surface, the audience corpus with first-party data rights renegotiated, the integration depth that survives three model swaps and one platform-vendor relationship.
The moat that matters in 2028 is not above the model layer. It is underneath it.
This is the question your CEO is already asking. The briefing below is what you want in your hand before the next platform review.
Build Velocity. Product Defensibility. R&D Capital Allocation.
Three questions every Nordic media CTO is tracking. The third is the crux. The first two are how you earn the right to answer it.
Is our platform speed shipping production-grade infrastructure, or demos that fall over on election night?
Copilot adoption at sixty-eight percent. Cycle time flat. Platform changes barely reviewed. Election night and breaking-news traffic spikes are the production tests, not the Tuesday dashboard. Buy what the tool layer can carry. Own the discipline that holds the platform under four-times traffic.
What does our platform do that an AI-content engine and the foundation-model vendor cannot copy?
Your editorial AI feature commoditises every eighteen months when the next model rolls. Your rights graph, audience corpus, and integration depth compound. Your senior platform engineers carry the architectural reasoning your CMS, streaming, and ad-ops are built on.
Is our technology budget one instrument or two?
One funds the CMS, the streaming pipeline, the ad-ops stack. The other builds the 2028 rights-and-audience moat. On one hurdle rate the first wins every quarter. On one scorecard the second does not exist. The CTO who walks in with one budget runs the same programme every peer is running.
What you get when you download
An 11-page report for CTOs, CPOs, and CPTOs at Nordic operating media groups. Designed to be read in one sitting before your next platform review.
Your industry, your platform, and why they are one problem
What is happening to Nordic media: the Schibsted-OpenAI February 2025 deal as the new pricing comp, AI-content engines arbitraging your commodity beats at one tenth of unit economics, and the structural advertising decline. What is happening inside your platform: Copilot adoption up, cycle time flat, and the AI-strategy ownership list your seat is not on. And the intersection: same force, two altitudes, one problem.
Four moves across build engine, platform and data, product thesis, and ML bench
Instrument review depth per change, not just cycle time. Build the rights graph, audience corpus, and integration depth that compound underneath the model layer. Stand the licensing-and-pricing architecture before the deal arrives. Rebuild the junior pathway around senior and agent pairing on rights-and-audience work.
Five questions for your next platform review
Is your technology budget one instrument or two, and what is the kill criterion on each? What is your equivalent of the Schibsted-OpenAI licensing line? How many months to reconstruct architectural reasoning if your Head of Platform leaves tomorrow? Where did the freed hours from sixty-eight percent Copilot adoption go? Is your Q1 boundary agreement with the CEO and editor-in-chief written?
Calibrated for each seat at the table.