Learn Across Brands. Act Within Them. Underwrite the Outcomes.
If AI makes martech features cheap to build and platforms easy to leave, what makes a martech company hard to replace?
The argument in one line. Martech’s old moats were software, integrations, data custody and switching costs, and AI is weakening all four. The new moat is a loop with three parts: learning across brands, acting within each brand, and underwriting the outcomes. Each part can be copied on its own. The loop cannot, because it compounds: every brand served makes the system better at delivering results for the next.
1 The Disappearing Moat
A chief marketing officer is weighing a renewal. Her team has spent six years building journeys, segments, templates and integrations on its customer-engagement platform. The platform works. But a challenger can now reproduce most of what she sees on screen, an AI-assisted migration makes moving less frightening, and her own agents can already prepare campaigns across more than one tool. The incumbent points to its features and to the years of integration work. She asks a simpler question: what do we know now that we would not know without you?
Most martech companies would struggle to answer, because their customers have stayed for a different reason. Ask anyone who has run one why customers stay, and if they are candid the answer will not be about affection. Customers stay because leaving is hard.
For twenty-five years, four things made a martech platform hard to leave. The first was switching cost: years of templates, journeys, segments and campaign logic built inside one tool, none of it portable. The second was integration: the platform was wired into the brand’s commerce system, its app, its data warehouse, its service desk and its analytics, and every wire was a reason not to move. The third was custody of customer data: profiles, event histories, consent records and preferences lived on the vendor’s servers, and moving them felt like moving house with the furniture nailed to the floor. The fourth was depth of features: a mature platform did hundreds of things, the brand used dozens of them, and any challenger had to match those dozens before it could argue about the rest.
None of these moats was about results. A brand could be disappointed with what its platform delivered and still stay, because the cost of leaving was higher than the cost of disappointment. Vendors knew this, and so did their investors. Net revenue retention, the number the industry watched most closely, measured how well a platform kept and expanded its customers, not whether those customers were better off.
AI is weakening all four moats at once, though it is not eliminating them. Features are cheaper to build: a capability that took a product team a year can now be produced in weeks, and copied in about the same time. Migration is being automated: the templates, journeys and segment definitions that once took months to rebuild can be read, translated and recreated by machines, a shift I described in The Software Foundry series. Integration is becoming routine, as standard connectors and agents that read documentation do in hours what used to take an implementation team weeks. And agents increasingly work across tools rather than inside one. When the marketer’s assistant is an agent that can operate any platform, the platform starts to look like an interchangeable part. Some friction will remain: consent histories, suppression rules and the exceptions nobody documented are still hard to move, and no bank will shift its customer engagement over a weekend because AI can write code. But the direction is clear. Customers will have more credible alternatives, and friction will become a less acceptable reason to stay.
Data custody is weakening too, from a different direction. Brands increasingly keep their customer data in their own warehouses, and the platform reads from it rather than holding it. The vendor that was once the keeper of the customer record is becoming one of several tools with permission to use it.
| Old moat |
What AI is doing to it |
The better reason to stay |
| Switching costs |
Machines read, translate and rebuild templates, journeys and segments |
Value that grows the longer a brand stays |
| Integrations |
Connectors and agents do in hours what took weeks |
Deployments that get cheaper and safer each time |
| Data custody |
Brands keep data in their own warehouses; platforms read it |
Permissioned learning without custody |
| Feature depth |
Features are cheaper to build and copy; agents work across tools |
Tested judgement about what causes results |
Figure 1. The four old moats, what AI is doing to each, and the better reason to stay.
The industry’s response so far has been consolidation. On 20 October 2026, Salesforce agreed to acquire Braze for about $5.66 billion in enterprise value, a little over six times the $910 million or so of revenue Braze expects for its current financial year. The deal still needs shareholder and regulatory approval. It is a sensible combination, and it tells us something. Acquisitions buy capability, talent and customers, and Salesforce is buying a working company with strong engineers and real AI decisioning, not merely a feature list. What an acquisition cannot buy is evidence that the combined company has learned to improve one brand’s incremental profit because it has worked with another. That is not an asset sitting on a balance sheet. It is a process that has to be built, run and proved after the deal closes.
The old martech moat was the cost of leaving. The question for every martech company now is what replaces it.
2 Thousands of Brands, Little Learned
Consider what a large martech platform sees. Thousands of brands across dozens of categories send billions of messages a month through it. Every one of those messages is an experiment of a kind: a choice of customer, offer, channel, timing and words, followed by a response or its absence. No brand, agency or chief marketing officer sees a fraction of this. If experience were measured by the number of marketing decisions observed, the martech platform would be the most experienced company in marketing by a wide margin.
Yet ask a martech company what it knows about what works, and the answer is thin. It can tell you average open rates by industry, the best day of the week to send, and that personalised subject lines tend to beat generic ones. It cannot tell you, with any confidence, which intervention would bring back a lapsed customer of a mid-sized apparel brand who bought twice, last opened an email four months ago, and responded once to free shipping but never to a discount. That is the knowledge a brand needs, and almost nobody has it.
There are four reasons, and none of them is a shortage of data.
The first is the billing meter. Martech has been paid per message sent or per user tracked, and a vendor paid for volume has no commercial reason to find out which of its messages caused anything. I set out how those meters shaped the industry in Martech Beyond Messages and MAUs, and will not repeat the argument here. The short version is that the industry was paid for what it carried, not for what it caused, and so it measured carriage.
The second is that few campaigns ran with holdouts. Without a group of comparable customers who did not receive the message, there is no way to separate the customers who bought because of it from those who would have bought anyway. Attributed revenue, the number most dashboards show, credits the message with every purchase that followed it. It is a record of coincidence, and very little can be learned from it.
The third is that results stayed in each brand’s slide decks. When a campaign worked, the brand’s team presented it internally and perhaps at a conference. The evidence of why it worked, and the evidence of everything that was tried and failed, stayed in a folder.
The fourth is that what agencies learned walked out of the door with their people. Agencies see many brands, and good agency people carry hard-won pattern recognition. But that knowledge lives in heads, not in systems, and it leaves when the person does.
None of this means vendors learn nothing. Benchmarks, testing tools and AI decisioning all exist, and some are very good. The claim is narrower: no martech company has yet made causal knowledge from its whole operating history the central asset it sells. Its experience is immense; its memory of what caused what is thin.
The result is a strange paradox. Martech has been the most experienced company in marketing that never learned from its experience.
3 Learn Across Brands: Experience at Scale
Brands already pay for cross-brand learning. They simply do not call it that.
When a company hires a chief marketing officer, it looks for someone who has done the job before, ideally at several companies. A CMO who has run retention at five brands knows things a first-time CMO does not: which loyalty mechanics wear out, which win-back offers train customers to wait for discounts, how long a lapsed customer stays reachable. Nobody suggests she has taken something proprietary from her former employers. We call it experience, and we pay a premium for it. The same is true when a brand hires an agency that has seen hundreds of campaigns. The agency’s value is precisely that it has learned elsewhere.
What I am proposing is the same thing, made systematic, measured and available to every brand rather than only to those that can hire the most experienced people.
Two fields show what shared learning can do when it is organised well. The first is medicine. Every patient benefits from evidence gathered across hospitals and clinical trials they never joined. A doctor choosing a treatment draws on what happened to thousands of other patients, none of whom is named in the evidence. Nobody regards this as a loss; it is the reason modern medicine works.
The second is aviation safety. In April 1976, NASA and the US Federal Aviation Administration set up the Aviation Safety Reporting System, through which pilots, controllers, dispatchers, cabin crew and maintenance technicians report incidents and near-misses. The system marked fifty years of continuous operation in April 2026, and it still runs on the principles it was designed around: reporting is voluntary, confidential, non-punitive and independent. Reports are de-identified before anything is shared, so that no person or company can be recognised from them. Hundreds of thousands of reports later, every airline flies more safely because of incidents that happened at other airlines. The lesson travels; the name does not.
Marketing has nothing like this. What would it look like?
The unit of learning is a decision trace: a record of one decision and what followed. It captures four things about the decision itself. The customer state: where this customer was, in recency, frequency, value and engagement, at the moment of decision. The intervention: what was done. The context: category, season, channel and what else was competing for the customer’s attention that week. The cost: of incentives, of fulfilment, of the message itself.
The next two need care, because the whole argument rests on them. It is tempting to say that each trace also records the incremental outcome for that customer. It cannot. We can see what one customer did after an intervention; we can never see what the same customer would have done without it. Lift is a property of groups, not of individuals. So each trace records its assignment: the experiment it belonged to, and whether this customer was randomly placed in the treatment group or the holdout. The experiment then supplies the incremental outcome: the difference between the randomised groups, measured in contribution rather than clicks, and stated with a range of uncertainty. Individual traces explain who responded and in what circumstances. The comparison between groups says what was caused.

Figure 2. A decision trace. Each record describes one decision; lift is estimated only by comparing randomised groups.
Failures count as much as successes. Case studies celebrate wins, so the industry’s shared memory is a highlights reel. The knowledge of what did not work, the free-shipping offer that brought back nobody, the win-back sequence that only hastened unsubscribes, is the hardest to find and often the most valuable. A system that records every decision with its holdout learns from failures automatically, because a failed intervention is simply a trace with an outcome of zero or less.
This changes the kind of knowledge available. A best-practice library says what successful brands tend to do. It is useful, and it is how most of marketing’s shared knowledge is packaged today. Cross-brand learning does something different: it predicts which intervention is likely to work for this customer, in this category, at this point of dormancy, and how confident that prediction is. The library describes the past in general. The prediction addresses the decision in front of you.
That prediction is a starting point, not a verdict. What worked for a fashion retailer in India will not automatically work for a bank in Britain, and even within one category brands differ in margins, purchase cycles, price sensitivity and the trust their customers place in them. A model that performs well in groceries can be confidently wrong in insurance, and pooled evidence applied to the wrong brand can make results worse rather than better. So the goal is not to assume that what worked elsewhere will work here. It is to begin with evidence gathered elsewhere, test its relevance against the brand’s own history, and update the prediction as local results arrive. Cross-brand experience supplies the starting hypothesis. Brand-specific evidence decides whether it survives. The learning should make the first local test smarter; it should never replace the test.
The benefit is largest for the brands that can least afford to learn alone. A large brand with millions of customers can run enough experiments to learn a good deal from its own history. A mid-sized brand with fifty thousand lapsed customers cannot: by the time it has tested enough offers on enough segments to know what works, many of those customers are gone. Pooled evidence lets it begin where larger brands have already arrived, and spend its own experiments on the questions that are specific to it.
Every brand gets the experience of a thousand brands, without any brand’s customers leaving home.
4 Know-How Travels; Know-Who Stays Home
Shared learning works only if brands trust it. That trust cannot rest on a vendor’s good intentions; it has to rest on rules a brand can check. Here is the compact I would offer, written as a promise rather than a defence.
What travels is know-how: patterns, playbooks, and models trained on de-identified outcomes. A pattern might be that customers who lapse after a single purchase respond better to useful content than to discounts in the first ninety days. A playbook might be a sequence of interventions, with timings and cost limits, that has worked across many brands in a category. A model might predict which customers in a dormant base are still recoverable, and at what cost.
What never travels is know-who: customer records, any brand’s own results, and anything that could identify a brand or a person. No brand’s customer list is visible to another brand. No brand’s campaign results are shown to anyone else. No playbook says, or implies, where it came from.
One rule makes this work. A lesson is shared only when many brands have taught it. A pattern seen at one brand, or two, stays where it was learned. Only when the same lesson has been confirmed across enough brands that no single contributor can be inferred does it join the shared playbook. Shared learning does transfer generalised knowledge; that is its purpose. What it must never transfer is anything a rival could trace to a particular brand: its results, its distinctive tactics, its customers. What enters the pool is what many brands have independently found to be true, which is the same principle that lets an airline learn from another airline’s near-miss without ever knowing whose it was.
Removing names is not enough to keep that promise, and the compact should not pretend otherwise. The UK’s data regulator, in its guidance on anonymisation, treats identifiability as a spectrum and asks whether a determined person with the right resources could re-identify the source. In a small category, a distinctive pattern can point to its source without carrying a name. So the compact needs technical safeguards as well as good intentions: a minimum number of contributing brands for every lesson, suppression of small or unusual slices, checks against inference from repeated queries, controls on what any output can reveal, contractual limits on use, and independent audit. These measures reduce the risk to a level a brand can check. They do not reduce it to zero, and the promise should say so.
Participation is opt-in, and it works on give to get. A brand that contributes its de-identified decision traces receives the shared playbooks and predictions. A brand that prefers not to contribute can still use the platform, but learns only from its own history. Each brand can see what it contributed and what it received. The case for joining is not altruism. It is that every participant improves faster than it could alone, in the same way that every airline is safer for belonging to a reporting system it could never have built by itself.
Throughout, the brand remains the data controller. The vendor works under the brand’s permissions and consent rules, and uses its customers’ data only for the purposes the brand has authorised. Those permissions are separate: the right to read, the right to recommend and the right to act are granted one by one. A learning permission must never quietly become a sending permission, and a model’s confidence that an intervention would work is not consent to run it. The learning that travels is about decisions, not about people.
| What travels (know-how) |
What stays home (know-who) |
| Patterns confirmed across many brands |
Customer records: names, contacts, profiles and histories |
| Playbooks: sequences, timings and cost limits |
Any brand’s own results and campaign data |
| Models trained on de-identified outcomes |
Anything that could identify a brand or a person |
| Lessons that many brands have taught |
Small samples and rare, traceable results |
| Evidence of what tends not to work |
Consent records, permissions and the decision to act |
Figure 3. The trust compact: what travels across brands, and what stays home.
Know-how travels; know-who stays home.
5 Act Within Them: What Forward-Deployed Marketers Learn from Engineers
Knowing what is likely to work is not the same as doing it. Most martech companies have treated execution as the brand’s job: the vendor provides the tools and the brand’s team uses them. In practice the team is stretched, the tools are underused, and good ideas stall somewhere between the recommendation and the launch. It is the difference between an idea that has been demonstrated and one that has been installed.
The software industry has a model for closing this gap, and it comes from engineering.
Palantir built its business by sending engineers to sit inside customers’ organisations, often for months, to make its software work on their real data and their real problems. It has two main engineering roles: Devs, who build the core platforms, and Deltas, forward-deployed engineers who deploy them to achieve customers’ outcomes. According to The Pragmatic Engineer, until around 2016 Palantir had more Deltas than traditional software engineers. Deltas work alongside deployment strategists, known internally as Echoes, who carry much of the organisational work: understanding how the customer operates, managing senior relationships and finding the problem worth solving. The engineer owns the technical build. The strategist owns the navigation.
The model has since spread well beyond Palantir. Between 2024 and 2025, OpenAI, Anthropic and Cohere expanded their forward-deployed engineering teams to help businesses put their models to work, and the Financial Times reported that monthly job listings for the role rose more than 800% in the first nine months of 2025. The reason is the one Palantir faced two decades ago: a powerful product delivers nothing until someone makes it work in a messy, specific environment.
Marketing needs the same role. I call it the Forward-Deployed Marketer, and five lessons carry over from engineering.
Embed in the real problem, not the brief. A brief describes what a brand thinks it wants. The real problem is usually somewhere else: in a data feed that misses returns, an approval process that kills timely sends, or a discount habit that has trained customers to wait. A Forward-Deployed Marketer works inside the brand’s own systems and numbers, close enough to see the problem rather than its description.
Pair judgement with building. The Echo and Delta pairing maps closely onto marketing. A brand strategist, in the Echo role, understands the brand’s customers, politics and priorities, and decides what is worth doing. An agent builder, in the Delta role, configures the agents, data flows and interventions that do it. Behind them, as the Devs stand behind the Deltas, a product team turns what works into product.
Have agreed authority to ship. A consultant who can only recommend is easy to ignore. A Forward-Deployed Marketer has agreed authority to launch controlled interventions: within a budget, with a holdout, inside guardrails the brand has approved. The contract specifies which actions run automatically, which need approval, which are prohibited, and how a mistake is reversed. The brand sets the limits; the marketer does not need fresh permission for each move inside them.
Pave the road. Bob McGrew, an early Palantir executive, describes field work as building a gravel road that solves one customer’s problem, which the product team then turns into a paved highway the next customers can drive on. For Forward-Deployed Marketers, every successful deployment should become a playbook or an agent. The first win-back programme in a category is built by hand. The fifth should be mostly assembled from parts.
Measure productivity. If the road is being paved, the evidence shows up in one number: brands and outcomes per marketer. As agents take over routine work, each Forward-Deployed Marketer should serve more brands and deliver more verified lift. Count the trust numbers alongside it, such as incidents and reversals, so that speed is never bought with carelessness. If brands and outcomes per marketer stay flat, the company is not building a product; it is staffing a service.
That last lesson is where the model most often fails. In The Palantirization of Everything, a16z’s Marc Andrusko notes that job postings for forward-deployed engineers are up hundreds of percent as companies copy the model, and argues that most are copying the look without the platform underneath. Without reusable parts, he warns, a company that sends people to its customers ends up as “Accenture for X” with a nicer front-end. Copying the job title without paving the road produces a services business. A simple replication test applies here directly: if the tenth deployment costs as much as the first, there is no factory, only a very good team. And as I argued in The Expensive Last 10%, the hard part of any deployment is not producing the capability but making it dependable, which is exactly what a paved road has to absorb.

Figure 4. How the engineering roles map to marketing roles.
Consultants advise. Forward-Deployed Marketers ship, and then make sure the next brand needs them less.
6 Underwrite the Outcomes
The third part of the loop is the one that turns learning and deployment into a business.
It is easy to confuse underwriting with outcome pricing. Anyone can offer a performance fee: we will charge you a share of the results. Most such offers are a pricing tactic, often a discount in disguise, made in the hope that results will be large enough to cover the vendor’s costs. Underwriting is different. An insurer that underwrites a risk has to predict it, price it, hold capital against it, and make money across a portfolio even though some individual policies lose. A martech company that underwrites outcomes has to do the same: predict the lift a programme is likely to deliver, fund the work before any result arrives, design holdouts the brand accepts as credible, manage the downside when a programme underperforms, and make a profit across its portfolio of brands.
Few companies can do all of that. Prediction needs the cross-brand learning of section 3. Execution needs the Forward-Deployed Marketers of section 5. Capital and discipline need a company willing to carry risk on its own balance sheet.
The unit matters. Underwriting attributed revenue is meaningless, because attributed revenue includes purchases that would have happened anyway. The unit is incremental contribution: the extra revenue caused by the programme, measured against a concurrent randomised holdout, less the cost of the incentives used to produce it and of fulfilling the extra orders. A simple illustration shows why the distinction decides everything.
An illustration, not a result. A brand has 100,000 dormant customers. It assigns 90,000 at random to a recovery programme and holds out 10,000. Over the measurement window, 6% of the treated group buy, against 4% of the holdout. Of the 5,400 treated buyers, 3,600 would have bought anyway; 1,800 are incremental. Each order is worth $120 and earns $50 after product and fulfilment costs. A dashboard credits the programme with all 5,400 orders, or $648,000 of attributed revenue. The incremental revenue is $216,000, and the incremental margin is $90,000. Now add the incentive. A $10 discount is paid on every treated order, including the 3,600 that would have happened anyway: $54,000. Incremental contribution is $36,000. Double the discount to $20 and the same programme, with the same lift, costs $108,000 in discounts and loses $18,000, while the dashboard still shows $648,000.
That last case is the trap. A programme that brings customers back with a deep discount can show handsome incremental revenue and negative incremental contribution, because the discount also pays the customers who would have come back on their own. Underwriting on contribution keeps everyone honest about that.
I have set out the commercial structure elsewhere: in No Lift, No Bill, the baseline the brand would have earned anyway, the verified lift above it, and the vendor’s share of that lift alone; and in Martech Beyond Messages and MAUs, the 6× floor under everything the brand spends. I will not restate either here, because the point for this essay is a different one.
Alpha is also how the system learns. A contract paid only on verified lift forces honest measurement, because neither side will accept a number it cannot check. Every programme runs with a holdout, every result is incremental, and every cost is counted. That is exactly the evidence the decision traces of section 3 need. A vendor paid on volume generates activity data. A vendor paid on verified lift generates causal evidence, and causal evidence is the best training material the loop can get. The contract is not only how the vendor is paid. It is how the system finds out what is true.
The difference between promising results and underwriting them is evidence, capital and discipline.
7 The Loop
Each part so far can be copied. A competitor can hire marketers and give them a new title. It can build agents. It can offer a performance fee. What it cannot copy quickly is what happens when the three parts are joined.
The evidence loop: Learn, Act, Underwrite, Learn. Cross-brand learning produces better predictions of which programmes will work for which brands and which customers. Better predictions let the company choose better opportunities to underwrite: brands where lift is likely, programmes where the cost is justified. Forward-Deployed Marketers deliver those programmes inside each brand. The contract verifies the results against holdouts. And the verified results, de-identified and pooled across brands, improve the predictions. The next round starts from a better place than the last.
Each turn makes the next one more profitable. Predictions sharpen, so fewer programmes fail. Fewer failures mean smaller losses across the underwriting book. Smaller losses let the company price more keenly, or take on brands that others would turn away. More brands produce more decision traces, and more traces sharpen the predictions again.
The replication loop: every paved road lowers the cost of the next deployment. The first programme in a category takes a strategist, an agent builder and weeks of work. By the tenth, most of the programme is an assembled playbook, and the marketers’ time goes to the parts that are specific to the brand. Lower deployment cost changes which brands are worth serving. A programme that once needed a large brand to justify the effort becomes viable for a mid-sized one, and then for a small one. That opens a long tail of brands that competitors without paved roads cannot afford to serve, and the long tail feeds more experiments back into the evidence loop.
Picture both loops in a single category. The first time a team recovers dormant customers for a home-furnishings brand, almost everything is new: which customers are still reachable, which offers bring them back without training them to wait for sales, how long a holdout must run before the result can be trusted. The strategist and the builder work it out by hand, and the contract is priced cautiously, because the prediction behind it is weak. By the fifth brand in the category, the team knows roughly which customers will respond and which will not, the sequence exists as a playbook, and the agents run most of it. The prediction is good enough to price the contract more keenly, and the deployment is cheap enough to offer the programme to brands a tenth the size of the first. Each of those smaller brands adds its own traces, and the sixth programme is better again. Nothing in this story requires a breakthrough. It requires that every programme is measured, recorded and reused.
The two loops reinforce each other. The evidence loop makes each deployment more likely to succeed. The replication loop makes each deployment cheaper. Together they mean the system gets both better and cheaper with every brand it serves.

Figure 5. Two loops. The evidence loop makes each deployment more likely to work; the replication loop makes each one cheaper, which brings in the brands that feed the evidence loop.
One distinction matters more than any other here: data scale is not learning scale. A platform serving a thousand brands does not necessarily know more than one serving a hundred. It may simply have ten times as many poorly measured campaigns, and a specialist serving fifty similar brands may learn more than a generalist serving a thousand unlike ones. The advantage depends on how much of the activity produces comparable, causal evidence. Three measures capture it better than any count of brands or messages. Evidence density: the share of deployments that run as proper experiments with credible holdouts. Prediction advantage: how much better pooled learning predicts lift than each brand’s own history alone. Replication efficiency: how much time and cost a proven play saves at each successive brand. Put together, they answer the question investors rarely ask: how much more reliably and cheaply does the system produce a dollar of incremental contribution at the hundredth brand than it did at the tenth?
The compounding has to be earned, not assumed. Learning may fail to transfer. Cheaper deployments may erode quality. A tactic used across many brands may fail across all of them at once in a downturn, giving the portfolio correlated losses. And contracts paid on lift can tempt a provider to take only the easy recoveries and leave the hard customers behind. A serious system tests for all four, and does not claim compounding merely because its customer count is rising.
It is worth being precise about what is the moat and what is only the machinery. Agents can be built by anyone, on models available to all. Data integration is becoming routine. Good marketers can be hired, at a price. These are the machinery, and none of them, alone or together, is defensible. What cannot be copied quickly is the accumulated combination: a history of decisions and verified outcomes across many brands; the rights to act inside those brands, granted through contracts and trust built over years; repeatable processes that turn field work into product; and the capital and track record to underwrite outcomes at prices others cannot match. A competitor starting today with the same software and equally good people would start with none of these, and the only way to acquire them is to run the loop for years.
This turns the old moat inside out. In the old model, a brand stayed because leaving was costly. In the new one, a brand stays because staying keeps getting more valuable: its programmes draw on more experience every quarter, its deployments get cheaper, and its contract pays only for what works. Leaving would mean giving up all three and starting again with a vendor that knows less. The brand’s own data and workflows stay portable, and it remains free to go. That is the point: it stays because of what it gains, not because of what it would endure. The answer to the CMO’s renewal question is a record, against her own holdouts, of what the system has learned and delivered for her.
The new martech moat is the value of staying.
8 Three Objections
“Google, Meta and Salesforce already have this intelligence.” Much of this is true. They have vast data across advertisers, far more than any martech company, and excellent AI engineering. The engagement platforms are moving fast too: Braze now offers AI agents that build journeys from conversational prompts, and Salesforce will add that to its own stack. Pretending a challenger will have more data or better general-purpose AI is not a serious argument. Incumbents may well have components of the loop. What few have shown is the complete combination: permissioned cross-brand causal learning, repeatable deployment, and portfolio-level underwriting of outcomes. Much of the advertising platforms’ learning is about acquisition: which audiences to buy, which ads to show, at what bid. The learning in this essay is narrower and different in kind. It is permissioned, built on the brand’s own relationships with existing customers rather than on rented reach. It is about retention and recovery rather than acquisition. And it rests on causal evidence from holdouts rather than on attributed conversions. More data does not substitute for the right data. There is also a harder test, and it is the one that matters: cross-brand learning must beat what each brand could learn from its own history alone. A large brand with years of well-run experiments may need little help. It also has to beat a strong incumbent’s recommendations. Until that head-to-head test is won, the moat is a hypothesis, and the first kill test in section 10 is designed to find out.
“This is consulting in disguise.” It is, unless two numbers move. The cost of deploying a proven programme must fall with each brand, and brands and outcomes per marketer must rise. A consulting firm’s revenue grows in step with its headcount. A loop’s revenue should grow faster than its headcount, because each marketer is supported by a growing set of agents and paved roads. If those numbers do not move, the objection is right.
“Outcome pricing is a discount.” For a vendor that cannot predict results, it is. It will win the deals where lift is easy and lose money on the rest. Outcome pricing is a good business only for a provider whose prediction and execution are better than the market’s. Then it can underwrite programmes at margins others would refuse, because it knows which bets are good. The pricing does not create the advantage; it is how the advantage gets paid.
9 What the Company Must Change
A martech company that wants to build this loop has to change more than its pitch.
Finance. Performance fees are paid in arrears. The work is done, the holdout is read, and only then does the vendor earn. Meanwhile it has paid its marketers, run its agents and, in some programmes, funded incentives. Outcome work therefore needs working capital, and the need grows with success. Each engine that runs on outcomes needs its own capital plan, with clear limits on how much risk the company carries at any time.
Organisation. Forward-Deployed Marketers need a career track of their own, with progression based on outcomes delivered and roads paved rather than accounts managed. They work in pairs, strategist and builder, and the pairs need a product team behind them whose explicit job is to pave roads: to take what works in the field and make it reusable. Without that team, field work stays field work.
Incentives. Marketers should be paid partly on the verified outcomes they deliver and partly on what they turn into product. The second matters as much as the first. A marketer who delivers excellent results through bespoke work that nobody else can reuse has helped one brand. One who turns that work into a playbook has helped every brand that follows. Trust belongs on the same scorecard: an intervention that makes money but breaks a customer permission counts as a failure, not a trade-off.
The investor story. Markets give variable revenue a lower multiple than subscription revenue, because it is harder to forecast. A company moving to outcomes should not hide this. It should show compounding instead: rising evidence density, a widening prediction advantage over brand-only learning, the falling cost of deployment, and the growing contribution margin across the underwriting book. Those numbers, if they move, tell a better story than recurring revenue, because they describe a business that improves with use.
Who can do this. The trade is easier for a profitable, founder-controlled company than for one that reports recurring revenue every quarter. Moving from subscriptions to outcomes means accepting a period in which reported revenue looks worse while the loop is being built, and a company judged each quarter on subscription growth will find that hard to explain. A company that funds itself and answers to no quarterly scorecard can make the trade and wait for the loop to compound. That is an advantage of structure, not a guarantee: large companies can build outcome programmes too, and buy capability quickly when they choose to. The opening lasts only as long as the challenger improves its evidence, economics and trust faster than they do. The Braze deal shows where the subscription path often leads: into a larger platform’s portfolio, valued as a multiple of the revenue it brings. That is a fine outcome for shareholders. It is not the only one available.
10 How This Could Fail
Every argument should name the evidence that would refute it, and the tests should be designed before the company scales, not after. The cleanest test of cross-brand learning is to take a group of consenting brands and randomise the decision system itself: pooled learning for some programmes, an equally capable system trained only on each brand’s own history for others, with execution and measurement held constant. Compare the lift, and compare how well each system’s forecasts held up out of sample. Track the cost and time of deploying the same proven play across successive brands. Stress-test the underwriting book against bad years. And have the trust safeguards audited by people who are not selling the programme. These are the conditions that would refute the thesis.
| Test |
Kill condition |
| Cross-brand learning |
No out-of-sample gain over an equally capable system trained on the brand’s own history alone |
| Trust |
Brands decline to opt in, or protected brand information is shown to have leaked |
| Forward-Deployed Marketers |
Time and cost to deploy a proven play don’t fall across successive brands |
| Underwriting |
Forecast accuracy and contribution margin don’t improve as the portfolio grows, after losses and make-goods |
| The loop |
A competitor with the same software but no portfolio matches results within a year |
Figure 6. Kill tests. If any of these conditions is met, the loop is not a moat.
The commitments should be staged in the same order. Prove that one intervention creates incremental contribution. Prove that it can be repeated cheaply at another brand. Prove that pooled experience predicts better than local history. Prove that a diversified portfolio can be underwritten at a profit after failures and make-goods. Each stage earns the right to fund the next. All five tests can be read within two or three years, and the first four much sooner. If the loop fails them, the company that built it will have built a well-run services business with an unusual pricing model. That is not a disaster, but it is not what this essay claims. If the loop passes them, the moat will be visible in the numbers long before anyone describes it in a pitch: deployment costs falling brand by brand, predictions getting more accurate, and contribution margins widening as the portfolio grows.
The old martech moat was the cost of leaving. The new martech moat will be the value of staying, because every customer makes the system better at delivering results for the next.