The Regime Investor· · ·8 min read
What decides the winners in LLM platform competition
Model quality alone does not decide AI winners. Compare distribution, enterprise adoption, cost per accepted outcome, portability and cash flow by business model.

A Money Comics discussion forecast that, someday, roughly four LLMs would remain, naming Gemini, ChatGPT, xAI and Anthropic. That is a forecast about LLM providers and services, not a complete map of every AI business model. If it is treated as covering the whole AI platform market, four names are too coarse a unit of competition: a consumer assistant, a coding model, an enterprise workflow, an application programming interface (API) and a model embedded in a phone or office suite do not compete for the same decision or generate cash in the same way.
Model quality matters. Access to a model can also be repriced and routed through someone else’s product. To judge durable advantage, follow a user from first access to a paid outcome, then identify who owns the channel, contract, compute bill and switching decision.
The market is a set of jobs, not one leaderboard
A single benchmark can rank models on a defined test. It cannot determine which product wins legal review, integrates with company data, appears by default in a device or earns an acceptable margin.
Split the market into at least five jobs:
consumer search, writing and personal assistance;
software development and technical operations;
enterprise knowledge work inside existing applications;
model APIs used by independent products;
specialised or local models run for cost, privacy or control.
One provider may lead a benchmark while another wins distribution or procurement. Several models can survive because they serve different jobs, and one platform can offer rival models rather than betting on a single laboratory.
Distribution decides who gets the first attempt
Distribution is the right to appear at the moment a user has a task. Mobile operating systems, browsers, search, office suites, cloud consoles, developer tools and popular applications each provide that right.
A default position lowers customer-acquisition cost, but it does not guarantee retention. Users can ignore a bundled assistant, disable it or move a demanding task to another service. Measure activation after the default prompt, repeat use after several weeks, paid conversion and the share of tasks completed without switching products.
Bundling can also hide the economics. If an assistant is included in a wider subscription, revenue attributed to AI may be an avoided cancellation, a higher renewal price or greater use of the surrounding cloud rather than a separate AI fee. The platform still benefits, but the cash-flow path differs from a stand-alone model subscription.
Enterprise contracts are won after the demonstration
A compelling demonstration begins an enterprise sale; it does not complete one. Procurement can require identity and access controls, audit logs, retention choices, data-location terms, security testing, service levels, model-change notices, terms for who bears legal losses and an exit plan.
The contract also has to reach production. Record the number of eligible seats, activated users, weekly users, workflows in production and accepted outputs. A large headline contract with low activation can produce less value than a smaller deployment used every day.
Integration creates both value and switching cost. Connectors, permissions, sets of real tasks used to test models, prompt and agent logic, monitoring and staff training can make a system useful. They can also trap the customer if those assets cannot move to another model. A durable provider should win because the workflow improves, not because the cost of leaving is concealed.
A cheaper token can still produce a larger bill
Model prices often fall while total AI spending rises. The apparent contradiction disappears when usage and task complexity are included.
For each accepted output, add:
text sent to and returned by the model, including cached material and extra computation used for reasoning;
search, databases, connected tools and requests to outside software services;
workflow coordination, system monitoring and security;
human checking, correction and rework;
failed attempts and duplicated runs;
staff training, process change and legacy integration.
Then divide by accepted outcomes, not calls. The enterprise AI total-cost framework shows how to connect that denominator to integration, review, rework and realised cash effects. If the model price falls 50 per cent but the organisation runs four times as many, longer tasks, the model bill can double before integration and review costs. Lower unit prices can expand the market and still compress the supplier’s margin if efficiency gains are passed to customers faster than usage grows.
Model performance must hold up in real work
Benchmarks are useful when the test matches the job and is run before selection. Production work contains proprietary vocabulary, long context, tool errors, changing data and uneven user instructions.
Create a fixed evaluation set from real tasks, remove private information where required and score correctness, completeness, latency, cost and the severity of failures. Keep the same set across candidate models and preserve every result. A provider should not be credited for a benchmark it selected after seeing the answer.
Performance also changes over time. A model update can improve average quality while breaking a critical workflow. Contracts and architecture need version controls, regression tests and a fall-back route.
Open and portable alternatives cap lock-in
Open-weight and specialised models do not need to lead every benchmark to influence the market. They can provide a credible alternative for predictable tasks, local processing or organisations that need greater control. Their full cost includes infrastructure, optimisation, security, monitoring and skilled operators, so the licence price alone is not the comparison.
Portability is an economic option. Keep prompts, search indexes, instructions for connected tools, evaluation cases and business rules outside a proprietary interface where practical. Test a second model before an outage or price change. The easier it is to route a task elsewhere, the more of an efficiency gain the customer can retain.
Cloud and mobile platforms may still hold strong positions because they supply identity, data, billing, devices and compute. The question is whether they earn that position through lower total deployment cost and better outcomes or merely use a default that users later bypass.
Map the cash flow by business model
The same increase in AI use reaches providers differently.
| Business model | Revenue driver | Main cost or leakage | Evidence of durability |
|---|---|---|---|
| Stand-alone subscription | paid users and price | running the model, customer acquisition and cancellations | retention by sign-up group and revenue left after serving users |
| Enterprise seats | contracted and active seats | sales, integration, support | production use, renewal and expansion |
| API model | accepted workload volume | computing cost and price competition | workload retention and revenue left after direct service costs per outcome |
| Cloud platform | computing capacity, storage and attached services | capital spending, power and equipment depreciation | asset use, customer margin and cash earned on invested capital |
| Mobile or software platform | bundle retention and adjacent revenue | revenue displaced from existing products and partner payments | activation, renewal and incremental cash flow |
| Open or self-hosted stack | support, hosting or saved vendor fees | engineers and infrastructure | total cost, reliability and portability |
This prevents the same workload from being counted as model revenue, cloud revenue and enterprise productivity without recognising that one company’s payment is another company’s cost.
A quarterly competition record
For each provider, record one row per job rather than one overall rank:
independent task quality on a frozen evaluation set;
cost and latency per accepted outcome;
distribution channel and whether access is default or chosen;
contracted, activated and weekly active enterprise seats;
customer retention, account expansion and dependence on a small number of workloads;
customer ability to export data, evaluations and workflow logic;
committed computing capacity, how fully it is used and profit after direct service costs;
product incidents, model regressions and regulatory restrictions.
The record can support several winners or none. It should not be forced to confirm a four-name forecast.
What would change the assessment
A model laboratory has a stronger independent position if it retains workloads after competitors match its benchmark scores, expands enterprise use, controls acquisition cost and earns a durable profit after direct service costs without relying on one cloud or platform. Its position weakens if customers routinely route tasks elsewhere, prices fall faster than cost, or distribution partners capture the relationship.
A platform advantage is stronger when default access becomes repeated, paid use and improves renewal or attached cloud cash flow. It weakens when users bypass the default, regulators restrict bundling, customers demand model choice or open alternatives reduce switching costs.
The likely outcome is not knowable from a list of brand names. It will be revealed by who owns repeated workflows, who can deliver an accepted result at the lowest total cost, and who converts that position into cash after compute and distribution partners are paid.
This article provides general information and is not a recommendation to buy or sell any technology company.
Update note