All insights
AI market12 Aug 202619 min read

The open-weight price war is good news for British SMEs

Lower model costs widen the set of viable experiments. The strategic question is where cheaper intelligence can produce a dependable return.

Model economics
Our perspective

Falling inference cost changes experimentation economics, but sustainable value still depends on workflow design, evaluation and the freedom to change models.

280xfall in equivalent-capability inference costStanford AI Index, Nov 2022 to Oct 2024
2+models in a sensible benchmarkMinimum comparison design
1workflow baselineRequired before pilot
Key findings

01Cheaper inference permits broader testing, not weaker governance.

02Total workflow cost includes review, errors, latency and infrastructure.

03Prompts, evaluations and business rules should remain portable.

01

Capability is becoming cheaper

The Stanford AI Index 2025 documents a steep decline in the cost of querying a model at a capability level associated with GPT-3.5. Lower cost makes extraction, classification, retrieval and drafting viable in use cases that could not support earlier price levels.

For SMEs, the main benefit is strategic option value. Teams can compare approaches with representative work before committing to a large platform or a long contract.

02

The model is one line in the budget

Reliable systems still require process design, secure access to information, evaluation, monitoring and training. Lower token prices should allow more of the budget to fund these durable capabilities.

A cheap model becomes expensive when weak output creates repeated review or customer-facing error. Compare cost per accepted task, not cost per token.

03

Design for model choice

Keep prompts, retrieval logic, evaluation cases and business rules outside the model where practical. A stable application boundary makes it easier to compare quality, latency, hosting and price as the market changes.

Open weights can increase deployment control, but they also create obligations around licensing, provenance, security and operations. Control should be chosen for a clear business or risk reason.

04

Benchmark the complete task

Use real examples, including edge cases. Score correctness, review effort, response time and failure behaviour. Run the same test whenever a model, prompt or data source changes.

The winning design is the one that creates dependable value and remains easy to change.

Research context

What the wider evidence says

Findings are paraphrased from the linked original publications. Their scope and populations differ, so they inform the thesis rather than prove a universal outcome.

280x

Equivalent-capability inference cost fell sharply from 2022 to 2024

SMEs can benchmark more use cases, but lower model cost does not remove integration and quality cost.

Source: Stanford HAI, AI Index 2025
Lifecycle

NIST frames generative AI risks across design, deployment and use

Model portability should include repeatable evaluation, monitoring and incident response.

Source: NIST Generative AI Profile
Core tasks

OECD finds reported SME benefits are stronger when AI supports core company tasks

Cheaper models create the most value when attached to material workflows rather than peripheral novelty.

Source: OECD, AI adoption by SMEs, 2025
85%

Text generation and natural language processing dominate use among current UK business adopters

Rapid model commoditisation matters most where document and language workflows can be evaluated at the level of an accepted task.

Source: DSIT, AI Adoption Research, 2026
Executive playbook

A controlled route from thesis to operating evidence

Each work package ends with an explicit decision and a tangible output. The sequence keeps delivery connected to operating evidence.

01

Price the complete task

Decision
What is the cost per accepted business outcome?
Work
Combine inference, infrastructure, review, exceptions, monitoring and change effort.
Output
A total-cost model at realistic volume and quality.
02

Build a representative benchmark

Decision
Which candidate performs best on actual work?
Work
Create normal, difficult and adversarial cases with an agreed scoring rubric.
Output
A reusable evaluation set and baseline result.
03

Protect model choice

Decision
Which application boundaries reduce switching cost?
Work
Separate prompts, retrieval, rules, schemas and evaluations from provider-specific code.
Output
A portable adapter and release test harness.
04

Choose control deliberately

Decision
Does self-hosting or open weight deployment solve a material constraint?
Work
Assess data location, licensing, operations, latency, resilience and scarce skills.
Output
A documented sourcing decision with exit conditions.
Decision architecture

A practical decision sequence for leadership teams

DecisionRequired evidenceControlPerformance measure
What business result should change?Baseline volume, quality, delay and costNamed operational ownerObserved change against baseline
Where may AI contribute?Task variation, judgement and failure modesBounded use-case definitionAccepted output and exception rate
Can authority expand?Evaluation, live performance and incident recordExplicit approval thresholdPerformance by risk category
Should investment continue?Adoption, total cost, realised value and riskQuarterly value reviewRealised benefit with confidence range
Delivery and operating risk

The failure modes leadership should watch before scale

Risks become manageable when the early signal, control and accountable owner are agreed before release.

RiskEarly signalPrimary controlAccountable owner
Low token price hides high review demandUnit inference falls while cost per accepted task risesEnd-to-end task economicsProduct owner
Benchmark scores do not reflect operating workProduction corrections differ from test failuresContinuously refresh representative casesEvaluation lead
Provider features create silent lock-inBusiness rules accumulate inside proprietary interfacesStable application boundary and exportable evidenceTechnical owner
Self-hosting obligations exceed available capabilityPatching, monitoring or capacity work is deferredNamed service ownership and minimum operational standardTechnology lead
Measurement system

A scorecard that connects activity to management action

Measures are useful only when their definition is stable and their movement changes a management decision.

OutcomeDefinitionLeading evidenceDecision supported
Accepted-task economicsTotal monthly cost divided by accepted completed tasksReview minutes and retry rateChange model, workflow or scope
Quality at consequencePerformance separated by error severityHigh-risk failure countHold or narrow release
PortabilityTime and effort to rerun the service with a second modelProvider-specific dependenciesRefactor or accept lock-in explicitly
Operational reliabilitySuccessful completion within service expectationLatency, timeout and degradation eventsChange capacity or fallback design
Exhibit 1

Headline model price is only part of workflow economics

Illustrative share of total operating cost for a document-processing workflow.

Human review and exception handling42%
Integration and monitoring28%
Model inference18%
Storage and supporting services12%
Source: Quiet Gears illustrative cost model. Actual economics depend on volume, error tolerance and architecture.
Implementation pattern

A portable evaluation harness protects model choice

01cases = dataset.load("representative")02for model in candidates:03  outputs = model.run(cases)04  score = evaluate(outputs, rubric)05select(score.quality, score.totalCost)
01Test dataset
02Model adapters
03Common rubric
04Cost model
05Release decision
Leadership agenda

Translate the analysis into an operating decision.

  1. Choose one high-volume, reviewable task
  2. Create normal, difficult and adversarial examples
  3. Compare at least two model families
  4. Report cost per accepted output and the causes of rejection