What's Changing in the Moat You Build

Every CTO at a mid-sized European B2B SaaS firm has had the same Monday. Sprint velocity up twenty-two percent quarter on quarter. Copilot adoption at seventy-one percent. Cycle time from merge to production flat against last quarter. Your VP Engineering opens the review with the dashboard. He is mid-sentence when your phone buzzes. It is the CTO at your biggest customer. One sentence: "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. Your CFO forwarded the Shopify R&D line this morning: "Worth discussing before Q2 planning."

You have run this function for ten years. The pattern used to be simple. Hire strong engineers. Hold the review bar. Ship the roadmap. Meet the board on feature velocity and engineering headcount. The business was understandable.

Something changed. What used to take fifty engineers now runs on five. That compression arrived faster than the discipline to absorb it. Ninety-five percent of corporate AI deployments produce no measurable P&L impact, and the gap between what the tools can do and what your firm's system absorbs is where your seat now lives or loses. An AI-native at ten percent of your unit economics just landed its first named reference in your category. Your VP Engineering carries architectural reasoning that has never been written down, and two Sierra recruiters called last month.

You are not running one R&D function. You are running two, and only one of them 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 architectural reasoning sitting in three engineers' heads. On one hurdle rate the first wins every quarter. On one scorecard the second does not exist.

This briefing covers what is happening in your sector, what it means for the R&D function you run, and the three questions your team should answer before the next board cycle.

The AI-natives in your category are not experimenting. They are building. Sierra shipped to a hundred million in ARR in twenty-one months on outcomes priced at roughly ten percent of your per-seat unit economics. Harvey hit forty-two percent of the AmLaw 100 in one year. Decagon, Legora, Peec AI, Cursor each own a slice of what you thought was a feature moat. Your customers' procurement teams run comparison quotes where your per-seat number sits next to the AI-native's per-outcome number. They are not asking which is the better product. They are asking which pricing model their CFO can defend.

The moat your product ran on for a decade has moved. The feature layer commoditises fast now. A capability that used to take a 150-person team three years to ship can be rebuilt by a 20-person AI-native in twelve to eighteen months, on a modern architecture, priced on an outcome your customer can measure. Your feature edge was never going to hold. What can hold is the layer underneath the model: the accumulated understanding of your customers, the integration depth your product has wired into their systems, the data rights that let your agents be grounded in their reality. Those compound. They take years to build and they cannot be bought. An AI-native cannot ship them because they do not have your customer base.

Your feature shipped on GPT-5 is on an eighteen-month obsolescence curve. Your integration depth with your top ten customers is the asset the AI-native cannot replicate without your customer base.

The industry's speed mismatch is the third force. AI-natives build from scratch with no legacy, no eighteen-month roadmap cycles, no complex procurement to answer to inside their own house. Your firm has all three. You cannot pivot at their speed on their terms. What you can do is identify what is genuinely defensible in your product, stop defending what is not, and ship the moat they cannot build. The firms that are already moving are quiet about it. The ones that are shipping Copilot and calling it an AI strategy are the ones the board will replace in 2028.

Your build engine. Copilot adoption is at seventy percent. Cycle time has not moved. Velocity is up double-digit on the dashboard and people are pushing ten-thousand-line PRs barely reviewed. The foundational layer rots. Twelve months in, your team cannot execute a category rewrite when one arrives. The review discipline that worked in 2022 is training the wrong practice on agent-generated volume now.

Your platform and data. Spotify's best developers have not written code since December because Spotify spent four years on the platform foundation. You cannot replicate four years in eighteen months. You can buy the build-side discipline from the tool layer and redirect the compounding capital into the layer the tool vendors cannot sell: data rights renegotiated across your next twenty-four months of contract renewals, a model-agnostic agent-memory store portable across model swaps, an integration depth graph published for your top ten customer systems. The model layer commoditises. The data layer compounds.

Your product thesis. Your board asked for the firm's three-sentence thesis last quarter. Your answer was the one from three years ago. Your rate card assumes AI features will price like legacy features. They do not. Sierra runs three pricing mechanics. You run one. That is a capital-allocation question about where the moat gets built, not a pricing one. Your CFO and commercial leader need a joint document with you before the AI-native forces the conversation on their terms.

Your R&D bench. You stopped hiring juniors in 2024. The routine work that trained juniors into seniors is now running on agents. No routine work, no training ground, no senior bench in 2030, no internal CPTO candidate the year after. OpenAI and Anthropic both resumed junior hiring in late 2025 specifically to pair juniors with seniors on judgment-intensive work. The firm that cuts for this year's number has a cheaper function in Q4 and an empty bench in five years.

Your board-level authority. Thirty percent of European AI-strategy ownership sits with the CIO, twenty-three percent CDAO, twenty-one percent CAIO, one percent COO. You are not on the list. Not because you abandoned the mandate. You have not yet claimed it. Your CEO has a CAIO shortlist. Every month without a visible claim, the thesis drifts further from the seat that can defend it. Your Q1 boundary agreement with the CEO lands before the CAIO shortlist, not after.

Your sector is repricing from below because AI-natives are shipping outcomes-priced products at ten percent of your unit economics. Your function is compressing because five engineers now produce what fifty did, and the review bar that worked for fifty cannot hold the volume five produce with agents. Same force, two altitudes. There is a third thing happening that most mid-market B2B SaaS CTOs have not named yet.

The moat that matters in 2028 is not above the model layer. It is underneath it. The product feature you ship this quarter on GPT-5 is on an eighteen-month obsolescence curve. The next foundation model rolls in 2027 and your feature commoditises. What does not commoditise: the data you have rights to, the agent-memory corpus you own, and the integration depth you have published for your top ten customer systems. A two-person AI-native cannot build that layer because they do not have the customer base that generates the signal. You do. The window closes in roughly eighteen months, which is the time between now and when the AI-native has enough of their own customer footprint to start building the same layer.

In 2006, a handset manufacturer shipped the best-engineered product in the world. The queue for their next flagship was eighteen months out. Their CTO's scorecard was battery life, keyboard quality, enterprise email reliability, carrier relationships. Every metric was green. Apple shipped a platform. By 2011 that handset manufacturer's market share in its own category had fallen from forty-three percent to ten. The 2006 scorecard never turned red. It just stopped being the one the market was scoring. The job had not changed. The unit of judgment had.

You have twelve to eighteen months. The CTOs who claim the authorship of this decision in Q1 author the decade. The ones who wait until the CAIO hire arrives inherit a seat that has narrowed to platform uptime and feature velocity, and a scorecard that stopped mattering the quarter their biggest account opened a Sierra pilot.

Every CTO has had the AI conversation. Most are making the same four decisions. A smaller group is making different ones.

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.

Four concrete moves any B2B SaaS CTO can start this quarter. Each addresses one sub-function. Pulled together, they become one architecture the firm builds on.

The B2B SaaS CTO has four places to go. None can do what we do.

The big tech-transformation practices ship a standardised AI-governance framework scaled across a sector book. Their cost structure requires reusability. Your seat is idiosyncratic. A reusable framework on an idiosyncratic seat produces governance theatre you cannot defend to the board.

The hyperscaler professional services arms price the engagement as enablement for cloud consumption. Their business model requires platform lock-in. Every build-or-buy decision routes through their pricing for three years.

The developer-productivity tooling vendors have a quote on your desk. Cursor, Copilot enterprise, Claude Code, agent-workflow platforms. Their product is a build-velocity intervention measured on seats. Telling you to spend freed capacity on the data moat instead of expanded seats is structurally impossible for them to say.

An in-house or fractional CAIO splits the seat. Strategy CAIO is revenue-measured; Platform CAIO is velocity-measured. One person cannot hold both. Two-thirds of newly-appointed CAIOs spend year one compiling inventories instead of setting direction.

The four options you have already looked at. None can run the capital-allocation conversation the seat requires. GRAIL is the fifth.

We start with your R&D leadership team because the change cannot outrun the team's personal understanding of what is possible. Three workshops. Each delivers standalone value. Each earns the right to the next.

The questions where your R&D leadership cannot agree on an answer are the ones worth an hour on the agenda. Ask these honestly.