Moat.
Speed.
Allocation.
The platform moat that survives 2028 is being chosen this year.
This briefing tells you which platform moats survive 2028 in vertical software 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 just watched a demo from an AI-native in our space. Can we talk this week?" Your VP Engineering mentioned a recruiter call from a well-funded entrant in your vertical over coffee Thursday. Your CEO has a rebuild-or-buy decision on his desk.
You are not running one R&D function. You are running two, and only one is on your scorecard. One ships the current product. The other encodes what has to exist by 2028: the ten years of customer telemetry you have never turned into a training dataset, the domain reasoning in three founding engineers' heads, the integration depth the AI-native cannot replicate without your customer base.
The moat in vertical software is your dataset, not your features.
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 vertical-software CTO is tracking. The second is the crux. The first and third 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 have that an AI-native at ten percent of our economics cannot copy?
Your feature edge commoditises every eighteen months when the next foundation model rolls. Your ten years of customer telemetry compounds. Your domain reasoning sits in three founding engineers' heads, and two of them had recruiter calls from AI-natives last month.
Rebuild, layer, or ride? Which path does your capital actually fund?
Three paths compete for the R&D budget. Rip and rebuild on foundation models. Layer AI on legacy. Ride current ARR and acquire a tuck-in. On one hurdle rate the layer-on option wins every quarter. On one scorecard the rebuild does not exist.
What you get when you download
An 11-page report for CTOs, CPOs, and CPTOs at mid-market European vertical-software 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 vertical software: AI-natives at twenty people reaching feature parity in eighteen months, named entrants shipping in construction, permitting, and site monitoring, and the moat shifting from code to the dataset underneath. What is happening inside your R&D function: Copilot adoption up, cycle time flat, and the rebuild-or-ride decision on your desk. 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 customer-intelligence corpus from ten years of usage, tickets, and QBRs. Encode the domain knowledge from founding engineers before notice periods. 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 vertical and the customer they just pilot-tested. How many months to reconstruct the reasoning if your two founding engineers leave tomorrow? Where did the freed hours from seventy-percent Copilot adoption go? Rebuild, layer, or ride. Which path has your CEO already committed to?
Calibrated for each seat at the table.