
Physics trains you to build models of reality from first principles. You are not simply looking for a rule that fits the data, but for the underlying structure that explains why the data behaves as it does. At Oxford, I developed mathematics to describe wave interference and coherence in X-ray lasers. We later abstracted some of those mathematical ideas into Eigen’s document-understanding technology. In both cases, the challenge was fundamentally similar: extracting meaningful signals from noise in a high-dimensional system.
That background gives me a high tolerance for abstraction but a low tolerance for technology that appears to work without a clear account of where and why it will fail. AI is probabilistic, so you cannot treat an impressive demo as proof that you have a reliable product. You need hypotheses, controlled experiments, measurable failure rates and an architecture designed around uncertainty.
Software engineers bring an essential instinct for making systems robust and scalable, while lawyers understand professional judgment, risk and the consequences of getting an answer wrong. Physics adds another perspective: reduce the problem to its essential variables, distinguish the underlying mechanism from the interface, and test every assumption. The best AI companies need all three disciplines. My own advantage is that I have worked across each of those worlds, so I tend to approach AI simultaneously as a mathematical system, an enterprise product and a tool that must survive real-world scrutiny.
We do not try to encode four professions into one generic model. The common platform solves a common underlying problem: in every knowledge business, valuable expertise is fragmented across people, emails, meetings, documents and messaging systems. Twin1 gives each professional a continuously evolving digital twin grounded in their own knowledge, context, judgment and communication style, then connects those twins through a governed network.
The horizontal layer is the infrastructure: integrations, retrieval, memory, orchestration, identity, permissions, governance and human approval. Domain depth comes from the customer’s own experts, data, precedents, language and workflows. A lawyer’s Twin learns from matters, negotiations and drafting patterns; a banker’s from transactions, clients and risk decisions; a consultant’s from engagements and methodologies; and a technology professional’s from products, systems and engineering decisions. The platform remains consistent, but the context and workflows are inherently sector-specific.
We also configure use cases, controls and deployment models around each institution. A law firm may require matter-level segregation and ethical walls, while a financial institution may require private-cloud deployment, more extensive auditability and different approval thresholds. Twin1 supports SaaS, single-tenant and private-client-cloud models, with persistent data, indexes, permissions and orchestration capable of remaining inside the customer’s environment.
So the answer is not to average four industries together. It is to build a common governed context and coordination layer that allows each organisation’s own expertise to remain distinctive, while giving it the infrastructure to scale.
I do not believe LLMs are useless. They are extraordinary reasoning and language engines, but they are not complete enterprise systems. They can lose context, backtrack in long conversations, hallucinate and produce different answers to the same question. They also do not inherently understand an organisation’s permissions, relationships, institutional history or risk boundaries. Treating the model itself as the product therefore creates a fragile architecture.
Twin1 separates the model layer from the governed context and coordination layer. We connect to the systems where work happens, retrieve only the relevant permission-filtered material, maintain memory and interaction history, and assemble the context required for a particular task. The model then reasons over that bounded context, with source citations, enterprise policies, inherited permissions and human approval applied around it. The complete customer corpus is not sent to a model for every question.
We are also model-agnostic. We can route work across proprietary or open-source models and support SaaS, single-tenant or private-cloud deployments. That matters for resilience, economics and AI sovereignty, but it also reflects a deeper architectural belief: the language model is a component, not the product or the moat.
Our durable value lies in the context the public models cannot possess: an individual’s knowledge, judgment, relationships and working history, together with the governance framework that determines how that knowledge can be used. The Twin Network then allows people and agents to find the right expertise and coordinate work without removing control from the humans they represent.
So we are not betting against foundational models. We are building the memory, retrieval, governance, orchestration and human-control layers required to turn increasingly capable but imperfect models into a dependable enterprise system.
The future of law is at LegalTechTalk – events for legal transformation
The legal industry is undergoing a major transformation, driven by technological advances, changing demographics, and new business models. Lawyers who are able to adapt to these changes will be well-positioned for success in the future.
Upcoming Events:
EUROPE · 16 – 17 June 2027 →
USA · 13 – 15 December 2027 →
Get news and insights delivered straight to your inbox!
Join 5,000+ legal leaders shaping the future of law for two days of insight, innovation and unmissable networking — now with your biggest saving!