On September 15, 2026, London-based startup Telon received Select Partner status in OpenAI’s partner network. The news spread quickly through trade outlets, but the headlines missed the real point: OpenAI has officially acknowledged that the model itself isn’t the main problem. The main problem is what happens between buying a license and having a working system in production. And that part isn’t solved by developers — it’s solved by lawyers who know how to translate law into algorithms.
What Happened
Telon was founded in June 2026 by Lewis Bretts, a former PwC partner who previously built the firm’s LegalTech practice, and Tom Mellor, former COO of SYKE. In three months the team grew from 15 to 30 people, and the startup raised funding from The LegalTech Fund. The company now officially helps OpenAI’s clients deploy its models inside law firms and legal departments.
This isn’t another legal-chatbot sale. Telon hires and trains “legal engineers” — most of them former practicing lawyers — and embeds them inside the client’s team to:
- configure models and write system instructions;
- build AI agents and working scenarios;
- connect the AI to internal documents and software;
- train lawyers and oversee how the technology is used.
Worth noting separately: the payment model. Telon charges for results, not billable hours. One important caveat: results-based pricing for legal engineers isn’t a guarantee the client wins every case — it ties payment to whether the digitized pipeline actually works: correct request triage, no critical logic errors, and real time savings for in-house lawyers.
An Important Correction: 300,000 Isn’t About Lawyers
Select Partner status is only the first of three tiers in the OpenAI Partner Network (Advanced and Elite come after it). OpenAI has invested $150 million in building out this partner network and expects to certify 300,000 consultants by the end of 2026. It’s important to understand: that figure is for the entire partner network, across every industry at once (founding partners include Accenture, Bain, BCG, McKinsey, and PwC) — not specifically legal specialists. Telon is one partner within that network, focused specifically on law.
This doesn’t diminish the news. If anything, the opposite: OpenAI is building a deployment channel exactly where its own resources fall short — and in law, that channel turned out to be not a developer, not a generalist consulting giant, but a specialized team of former lawyers.
Why This Isn’t “Just Another AI for Lawyers”
Lewis Bretts frames the market’s problem this way: law firms buy the technology, run successful pilots — and a few months later, staff are using only a fraction of what the system can do. Models keep getting updated on top of that, so AI adoption can’t be a one-time project — it has to be maintained continuously.
That matches exactly what I see working with LegalTech and FinTech startups trying to build legal logic into their products. A developer knows how to write code, but doesn’t know how to determine when an algorithm’s decision becomes dangerous for the user — for example, when the AI needs to stop and hand a case to a human specialist because the request shows signs that require manual review. That’s not a coding question. It’s a question of law translated into precise “IF… THEN… ELSE” logic before a developer ever touches the task. In practice, this logic isn’t an abstraction — it’s a concrete branch you can map out in advance. Here’s a hypothetical example drawn from insurance-claims automation:
[Insurance claim submitted]
│
├──> Scenario A: damage confirmed by documents, first-time claim
│ └──> [Automatic payout calculation]
│
└──> Scenario B (Red Flag): signs of fraud OR repeat claim on the same case
└──> [Automation blocked] ──> [Escalated to a human expert]It’s important to understand: legal architecture isn’t an attempt to limit what the neural network can do. The smarter a model gets, the more sophisticated and convincing its mistakes become in edge-case legal situations — exactly where reality departs from the typical scenario. Triage Logic and a Red Flags matrix aren’t there to replace the AI with a script; they exist to put hard safeguards exactly where the cost of a single model error is measured not in awkwardness, but in real money or a person’s rights.
This is precisely the work the market has now officially recognized as its own profession — and it’s what I do: I translate legal expertise into the architecture of LegalTech and FinTech products that a working digital solution can actually be built on — condition matrices, decision trees, critical-risk registers, and data-verification specifications for developers.
Legal Architecture for LegalTech and FinTech Founders in the CIS
Telon’s model is built for large law firms and corporate legal departments abroad — that’s not the scale most startups in Russia and the CIS operate at early on. But the principle this news confirms is universal, regardless of company size or jurisdiction: without legal architecture designed in advance, AI in a legal product will eventually either produce a dangerous recommendation or stall on an edge case nobody anticipated.
If you’re designing or scaling a product where an algorithm makes the decisions, and the cost of a mistake isn’t wasted time but real money or a user’s rights, this is work worth building in from the start — not patching in afterward.
Frequently asked questions
What is legal architecture? Translating legal expertise into a format ready for building a digital product: condition matrices, decision trees, critical-risk registers, and technical specifications for data verification. It’s work at the intersection of law and systems design, done before developers write a line of code.
What is a legal engineer? A specialist — usually a former practicing lawyer — who translates legal logic into algorithms and technical specifications developers can work with, then configures and maintains how AI models operate inside legal processes.
How is a legal engineer different from an AI-product developer? A developer writes code and wires up models. A legal engineer determines which rules, constraints, and red flags need to be built into the system before the developer starts building it — without that, the AI can’t tell a safe scenario from a dangerous one. A detailed breakdown of that line is in a separate article.
Does a small startup need this expertise, not just a large law firm? Yes, if the product makes decisions — even partially — that affect a user’s rights or money. Company size determines the scope of work, not whether the right logic needs to be built in before launch.
Designing or scaling a LegalTech or FinTech product with legal logic inside? See how legal architecture works — the formats, what I do, and how it fits into your development process.