Moat.
Speed.
Allocation.
The platform moat that survives 2028 is being chosen this year.
This briefing tells you which platform moats survive 2028 in B2B SaaS and tech 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.
Monday 9:15, R&D review. Sprint velocity up twenty-two percent quarter on quarter. Copilot adoption at seventy-one percent. Cycle time flat. Your VP Engineering opens with the dashboard. He is mid-sentence when your phone buzzes. The CTO at your biggest customer: "We've started a Sierra pilot on the support-resolution module, happy to talk." Your VP Engineering mentioned a recruiter call from Cursor over coffee Thursday. Your CEO has a CAIO shortlist from the board on his desk.
You are not running one R&D function. You are running two, and only one is on your scorecard. One funds what you already ship. The other funds what has to exist by 2028: the data rights you have not renegotiated, the agent-memory store you have not built, the integration depth that outlasts three model swaps.
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 R&D review.
Build Velocity. Product Defensibility. R&D Capital Allocation.
Three questions every B2B SaaS CTO is tracking. The third is the crux. The first two are how you earn the right to answer it.
Is our engineering speed shipping production-grade output, or demos that fall over?
Copilot adoption at seventy percent. Cycle time flat. Ten-thousand-line PRs barely reviewed. Spotify spent four years on the platform that lets agents ship cleanly. You cannot replicate four years in eighteen months. Buy what the tool layer can carry. Own the discipline that makes it ship.
What does our product do that a Sierra at ten percent of our unit economics cannot copy?
Your feature edge commoditises every eighteen months when the next foundation model rolls. Your integration depth and data rights compound. Your architectural reasoning sits in three engineers' heads, and two of them had recruiter calls from an AI-native last month.
Is our R&D budget one instrument or two?
One funds the existing product at lower unit cost. The other builds the 2028 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 mid-market European B2B SaaS and tech firms. Designed to be read in one sitting before your next R&D review.
Your industry, your R&D function, and why they are one problem
What is happening to mid-market B2B SaaS: AI-natives at ten percent of your unit economics, the feature layer commoditising every eighteen months, and named customer losses. What is happening inside your R&D function: Copilot adoption up, cycle time flat, and the board 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 R&D bench
Instrument review depth per line, not just cycle time, and make ADRs and eval harnesses first-class infrastructure. Build the moat underneath the model layer through data rights, a portable agent-memory store, and an integration depth graph. Stand one outcome-priced line on protected P&L. Rebuild the junior pathway around senior and agent pairing.
Five questions for your next R&D review
Is your R&D budget one instrument or two, and what is the kill criterion on each? Name the AI-native in your category. How many months to reconstruct architectural reasoning if your VP Engineering leaves for Cursor tomorrow? Where did the freed hours from seventy-percent Copilot adoption go? Is your Q1 boundary agreement with the CEO written?
Calibrated for each seat at the table.