About
A lawyer who
builds.
My name is Raghav, and I've never quite been able to pick one label. I qualified and practised law in India, the UAE and Singapore first, which is the part most bios lead with. What actually shaped how I work came after: a stretch helping scale a legal technology company past a hundred thousand lawyers, and nine years since, on my own, building systems for people whose work cannot survive a process falling over.
None of that is textbook knowledge. It's what happens when you spend enough years parked inside someone else's mess, a partner's overflowing inbox, a compliance head's tangle of spreadsheets, a founder describing a process they've never once written down, and refuse to leave until the mess resolves into a shape. Every engagement I take on still starts exactly that way.
Featured in Livemint, Bar & Bench, and LegalEra.
Practised across
India · UAE · Singapore
Delivered into
Australia, Israel, Russia, the UK, Europe, Sri Lanka, India and most US states, Texas, New York and California especially.
The story
Three things at once.
01
The lawyer
Where the instincts came from
I trained and practised across India, the UAE and Singapore before I ever wrote software, and that order matters. I learned to read a matter, facts, obligations, risk, consequence, in real courtrooms first. Every system I have shipped since is that same reading habit, aimed at a keyboard instead of a bench.
02
The founder
Learning what scale actually breaks
In about a year I helped take a legal technology company past 100,000 Indian lawyers, then went independent, consulting into American firms and running an AI and business venture out of Dubai. That stretch taught me where scale breaks a legal process, which is not where lawyers usually think it breaks. Eventually I stopped consulting on other people's systems and built my own: MatterOS and LexOS.
03
The builder
Nine years of the same question, asked 200+ times
For over nine years I have worked as an independent builder, starting with no-code tools for whoever needed a working system, then following the tooling forward through every generation up to agentic AI today. Roughly 200 projects, delivered for solo lawyers and large business houses alike, all of them the same underlying question: what is this process actually made of?
In the work
“I read a problem the way a lawyer reads a matter, then build the system that resolves it.”
No teams of juniors, no handover to someone you have never met. If you hire me, the person who understood your problem is the person who builds and installs the answer.
Off the record
A few things a CV would not tell you.
Where I grew up
Around case files and courtroom talk before I could really follow it. Law was less a career choice than the language already spoken at home.
How I actually work
Badly, if you're watching for typing. Most of a project is me sitting with the problem on paper, saying nothing, until the shape of it stops moving. The build itself is the easy part once that happens.
What pulls me away from the screen
No fixed itinerary, just walking until I find an old square or a courthouse with no reason for me to be inside it, and more gelato than the schedule can justify.
How to reach me
Skip the account manager, there isn't one. Every message lands with me, and I'm the one who writes back.
The path
From the courtroom to the codebase.
Law
Practised in the courts of India, the UAE and Singapore
Scale
Grew a legal-tech company to 100,000+ Indian lawyers
Solo
Independent legal-technology consultant to US firms
Dubai
AI and business consulting venture
No-code
Began building systems for anyone who needed one
LexOS
Launched the legal operating system on Notion
MatterOS
Built agentic case management for the small firm
Now
Custom AI systems for firms, corporates and government
What I work in
The MATTER Method
My operating doctrine. Six primitives every practice runs on: Matter, Actions, Time, Team, Evidence, Research, and one fixed sequence: name it, systematise it, then automate it. Both my products are built on it. Read the full manifesto.
The systems work above also runs through adnah, a small studio I founded for firms and legal teams that want the same transformation applied to their own practice, the MATTER Method, built out as a structured engagement.
Pro bono, at scale
Not everything I build is for sale.
MatterOS and LexOS pay the bills. Delivering legal services to the public, voluntarily, is a separate, older commitment, and ShouldISignAI is where I put it into software.
What it is
A free tool that reads a contract, agreement or document the way I would, and tells you plainly what's favourable to you, what isn't, and whether you should sign it, push back on it, or walk away. Built for young entrepreneurs, creators and influencers signing their first deals, freelancers, first-time employees, and anyone else who was handed a document with no lawyer in the room.
Why it's free
Because the people who most need to understand a contract are usually the ones who can least afford to have one reviewed. That gap is the entire reason it exists, so it stays free, forever, no plan to change that.
Where it sits
Alongside MatterOS and LexOS on the products page, but on its own terms: no pricing tier, no upsell. It's the philanthropic, voluntary side of the same practice, delivering legal clarity to the public at large instead of billing for it. See all three.
What I believe
01Learn AI properly and it's a tool. Skip that step and it's just a threat wearing a demo.
02A good system produces good professionals more reliably than raw hard work does.
03Name the process on paper before a single line of software gets written for it.
04Passion doesn't ship anything. Years of unglamorous repetition do.
05I won't run a pilot for a room that can't say yes. A demo for a committee isn't a project, it's a delay with a calendar invite.
06Procurement portals and ownerless RFPs get ignored, on principle. I build for a named person, not for a process built specifically to avoid having one.
Outside the work
A bit more human.
Nine years of building for other people means a lot of hours at a desk. The rest of it looks like this: old cities, long walks, courthouses I had no business visiting, and the people who put up with my working hours.
Working together
What it is actually like.
- 01The person who understands your problem is the same person who builds it, start to finish, no handover.
- 02Nothing gets built until the process is written down in plain language first.
- 03What I build is yours outright, no lock-in, no ongoing per-seat tax on your own system.
- 04If a build isn't actually the honest answer to your problem, I'll tell you that instead of selling you one.
That is the background. The interesting part is what we build next.