The people behind Trovix
Trovix is built by engineers who have worked inside the industries they now serve. They bring domain knowledge from both sides of the table.
James
James has spent eight years building machine learning systems inside UK banks and payment processors — fraud detection models, credit scoring pipelines and real-time reconciliation systems. He designed the Trovix MLOps framework and leads all financial services deployments.
Pierre
Pierre spent six years as a software architect at a global law firm before moving into AI engineering. He has built integrations into iManage, Aderant and Elite from both sides of the relationship. He designed the Trovix integration layer and leads legal sector work.
Marcus
Marcus started his career as an actuarial analyst building pricing models for a Lloyd's syndicate. He understands how underwriting and claims decisions are made, what data quality looks like in the London market, and what governance requirements apply. He leads insurance deployments.
Wei
Wei was an audit senior at a mid-tier UK accountancy practice before retraining as a software engineer. He has worked with Caseware and CCH from the practitioner side and understands what FRC guidance on AI in audit means in practice. He leads accountancy deployments.
Sophie
Sophie spent four years in a compliance role at an FCA-regulated asset manager before retraining as an engineer. She writes the governance documentation, audit trail architecture and regulatory framework mapping for every Trovix deployment — and has sat on the compliance side of every conversation she now engineers for.
Domain knowledge before the first conversation
Most technology companies learn about their clients’ industries after winning the work. The Trovix team brings domain knowledge before the first conversation. When James talks to a risk team about model documentation, he has written model risk documentation to PRA standards. When Sophie designs a governance layer for an FCA-regulated workflow, she has sat on the compliance side of that same conversation.
This is why Trovix deployments reach production in six weeks. The engineers do not need to learn your industry — they need to understand your specific systems and your specific data, and that takes weeks, not months.
Talk to the team
A 30-minute technical conversation about your systems and your workflow. No sales process.