ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

Thomson Reuters Spent $40M. The Training Run Cost $450K.

ibl.aiAugust 28, 2026
Premium

Thomson Reuters built its own legal and tax model on Alibaba's open-weight Qwen 3.5, trained on Westlaw and Practical Law content. The widely quoted numbers are $40M over two years and a $450K final training run — and the gap between them is the actual lesson, because 99% of the cost was not the compute.

The Short Answer

Thomson Reuters built a legal and tax model by post-training Alibaba's open-weight Qwen 3.5 on Westlaw, Practical Law, Checkpoint and Reuters content — roughly $40M over two years, with a final training run of about $450K. The gap between those figures is the lesson: the compute was under 2% of the cost. On ibl.ai you own all the code and the data, which is where the other 98% of that investment actually lives.

The widely repeated version of this story is that a domain-leading model now costs $450,000. That is not what happened, and organizations budgeting from it will be badly wrong.

What did Thomson Reuters actually build?

Thomson Reuters built a proprietary model for legal and tax reasoning by post-training an existing open-weight foundation rather than pre-training its own.

The base is Qwen 3.5, Alibaba's open-weight foundation model. On top of it the company applied mid-training and post-training techniques concentrated entirely on professional legal work, using content from Westlaw, Practical Law, Checkpoint and Reuters.

One detail signals how much room is left: the company says it has used less than 10% of its content library for training so far.

The reported investment is approximately $40 million over more than two years in staff and computing power, with the final training run of the current version costing about $450,000. First deployment is in Tabular Analysis within CoCounsel Legal.

Why is the gap between $40M and $450K the real story?

The gap matters because it shows the training run is the cheapest component of a domain model, and it is the only component most organizations price.

$450,000 is roughly 1.1% of the total. The remaining ~$39.5 million went to two years of staff, data curation, evaluation design, and safety work.

That ratio is the honest budget shape for anyone considering the same path. The GPU invoice is not the barrier.

The barrier is having decades of proprietary content, the people who understand it well enough to structure it for training, and an evaluation methodology credible enough that domain experts accept the result.

Read the other way, it is encouraging: the expensive parts are things an established institution may already own. What it cannot shortcut is the curation.

What does starting from an open-weight base actually require?

Starting from an open-weight base requires an explicit step most coverage omits: deciding what the model inherited before putting it in front of customers.

Thomson Reuters worked with Imperial College to first retrain the base model for safety, ethics, and political neutrality — before the legal post-training.

That is the under-discussed part of this announcement, and the most transferable. Adopting an open-weight foundation is not only a capability decision; it is a provenance decision.

The base model arrives with training data you did not choose and behaviours you did not specify, and in a regulated product somebody has to own that inheritance.

It is also a reminder that "open weights" and "unaccountable" are not the same thing. You can inspect, evaluate, and correct an open-weight model precisely because you hold it. You cannot do any of that to an API.

Does the model outperform frontier models, or match them?

The reporting says Thomson performs comparably to frontier models on its domain tasks, with external testing by legal academics — not that it beats them across the board.

This distinction is worth preserving because several summaries have upgraded "comparable" to "outperforms," and the inflated version is both unnecessary and easy to falsify.

Comparable frontier-level performance on your own domain, from a base you did not pay to pre-train, at a fraction of frontier cost, is already a significant result. It is the claim that survives scrutiny, and it is the one a buyer can act on.

Overstating it invites the obvious counter — that a general frontier model still wins on general tasks — which was never the point of a domain model in the first place.

What should an organization take from this?

An organization should take the strategy, not the budget, and the strategy has four parts.

The model layer is commoditizing; your data is not. Open-weight foundations have reached a quality threshold where they serve as viable bases for enterprise post-training. That reframes the question from "can we match the frontier" to "what do we have that nobody else can train on."

Curation is the actual project. Budget for the 98%, not the 1%. If your proprietary content is not structured, labelled, and rights-cleared, that work is the program.

Post-training is not the only lever, and usually not the first. Retrieval over your own systems captures a large share of the same advantage with none of the training cost, which is where most institutions should start. Revolut's own foundation-model paper made the point in passing: strong downstream results came from a simple model over good embeddings of their data. We worked through that trade-off in Revolut built its own foundation model — most banks can't.

Whatever you train, you have to run it somewhere you control. A domain model trained on privileged material, then served from a vendor's endpoint, reintroduces the exposure the exercise was meant to remove.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM — including an open-weight base you have post-trained yourself — and pay with no per-seat pricing. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on. For the buyer's view of the product this model ships inside, see our CoCounsel alternative comparison.

Frequently asked questions

Can a mid-size firm replicate this for $450,000?

No. That figure is the final training run only, against a reported total of roughly $40 million over two years. A firm without a curated proprietary corpus and the staff to structure it should not budget from the $450K number.

Why start from a Chinese open-weight model?

Because it was the strongest available open foundation, and holding the weights allows the inheritance to be corrected — which is what the safety and neutrality retraining with Imperial College was for. That option does not exist with a closed API.

Is fine-tuning the right first step for most organizations?

Usually not. Retrieval over your own systems captures much of the domain advantage without a training program, and it is reversible. Post-training makes sense once retrieval is saturated and the corpus is genuinely large and clean.

The bottom line

The headline number that matters is not $450,000 and not $40 million. It is the ratio between them.

Domain models are within reach of institutions that hold irreplaceable data — and the cost of getting there is almost entirely the unglamorous work of curating that data, not the compute. Price the 98%.

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing — so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform — the stack itself is yours.

  • Model-agnostic

    Run any LLM — Claude, GPT, Gemini, Llama, Command, or your own fine-tune — and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY — a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

Related Articles

Co:Counsel (Thomson Reuters) Alternative: Self-Hosted Legal AI Without the Westlaw Tax

Co:Counsel (Thomson Reuters / Casetext) runs in TR's cloud and prices per lawyer. ibl.ai is the self-hosted alternative: privileged work product inside the firm's network, model-agnostic, ~10× cheaper at AmLaw scale, ABA Rule 1.6 by deployment.

Jaione AmigotJune 1, 2026

Open Weights Took 62% of the Tokens and Under 9% of the Spend

Vercel's AI Gateway put open-weight models at 62% of token volume in late August, up from 11% in April — while closed models still took roughly two-thirds of the spend. That split is not a contradiction, it is what a correctly routed AI estate looks like, and it is only available if switching models is a config change.

ibl.aiAugust 28, 2026

AI's Price Spread Has to Rationalize. Hedge Both Ways.

A million tokens costs about $26 from one frontier lab and about $0.50 from a Chinese provider — a 52x spread for capability now 3–6 months apart. Spreads that wide close, and buyers cannot know which direction. The only position that survives either outcome is one where the model is a component you can swap.

ibl.ai EngineeringAugust 5, 2026

The Open-Weight Tipping Point: Two 2-Trillion-Parameter Models

Two models above 2 trillion parameters became available as open weights in a single week: Moonshot's Kimi K3 at 2.8T with a 1M-token context, and Alibaba's Qwen 3.8-Max at 2.4T with 95B active per token. This post does the memory arithmetic on what it actually takes to serve models that size, prices the alternatives, and explains why the durable advantage is model-agnostic infrastructure rather than any single model.

ibl.ai EngineeringAugust 3, 2026

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work — so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope · fixed timeline

A time-boxed proof of value on your real data — not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time · not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data · run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Six figures

perpetual license · you own the stack

We transfer the full source code. You own and self-host the entire platform — outright.

Best for: Government, defense, and enterprises that require perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable · zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM — Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY