Services · Smallest door first
Systems, agents, and the software underneath them.
I build the machinery an organisation actually runs on. Websites that work as intake systems, custom applications, AI agents wired into real processes, and the operating structure that holds all of it together.
Nine years, two hundred and more systems, twenty five countries. I trained and practised as a lawyer before I built software, which is why the builds survive contact with regulated, high-stakes work.
Fixed price · Remote first · Currently taking new work
What I am
A builder. I design and ship systems, applications and AI agents.
What I am not
I do not provide legal services. No legal advice, no drafting for clients, no representation. My legal training is why I understand obligations, evidence, deadlines and consequence well enough to build systems that hold under scrutiny. It is the reason the work is good, not the work itself.
This page is for working with me directly, one builder, one client at a time, for any organisation. If you run a law firm, an in-house legal department or a government legal function and want organisation-wide transformation, run as its own structured engagement, that's adnah, the studio I founded strictly for legal organisations.
Three ways in
Three doors, not ten decisions.
The full ladder below still has all ten rungs, priced and detailed, for anyone who wants to see the whole picture. Most people only need to pick one of these.
Door one
Buy a system
MatterOS, LexOS, or a guide, template or blueprint from the store. Off the shelf, installed by you, no engagement to schedule.
See what's off the shelfDoor two
Book a build
One agent, an intake site, one system, an agent pack, or the full systems engagement. Fixed price, scoped on a call, built and installed.
See the buildsDoor three
Advisory
A system audit, a process map before you commit to anything, or litigation and evidence technology on a live matter.
See the advisory work9
Years independent
200+
Systems delivered
25+
Countries served
2
Products live in market
3
Jurisdictions practised in
Clients across India, United Arab Emirates, Singapore, United Kingdom, Australia, Israel, Russia, Sri Lanka, Germany, Netherlands, and most US states, Texas, New York and California especially. Practised in India, the UAE and Singapore before building software.
The service index
Ten services. One ladder.
Every rung is the same discipline at a different depth. Start where the risk is smallest. Most people who end up at 07 arrived through 03 or 05.
01 – 03
Start small
Complete deliverables, not trials. The smallest doors in.
04 – 06
Build something
A site, a system, or agents wired into one you already run.
07 – 08
Go all the way
The whole sequence: name it, systematise it, automate it.
09
Specialist practice
Litigation and evidence technology, project or retainer.
10
Off the shelf
MatterOS, LexOS, and the free readiness audit.
- 01One AgentFrom $500
- 02System Audit & Technical Documentation$450
- 03Process Map & System Spec$750
- 04The Intake SiteStarter $2,500 · Full $5,000
- 05One SystemFrom $3,500
- 06Agent PackFrom $2,500
- 07Systems EngagementFrom $12,000
- 08Enterprise Systems EngagementFrom $25,000
- 09Litigation & Evidence TechnologyProject or retainer · retainer from $2,500 a month
- 10Off the shelf: MatterOS, LexOS & the auditFrom free
01 · Start small
One Agent
One working agent, engineered rather than chained.
A single agent that does one job properly. Trigger, classify, extract, validate, act. Typed output that fails loudly instead of silently. Retry with backoff. A confidence gate that routes to a human when the model is unsure. A run log you can read.
Not a no-code chain with an AI step bolted on the side. Coded logic, real error handling, and observability at every step.
Common first agents
Inbound email intake
Every message classified, filed and routed the moment it lands.
Document extraction
Uploads read into structured fields instead of a folder.
First-draft correspondence
Replies drafted from your own records, sent by a human.
Scheduled reports
The numbers you keep compiling by hand, generated on time.
Classification & routing
Items sorted and sent to the right queue automatically.
Status updates
Progress notes drafted from live data, not from memory.
What you get
- The agent deployed and running
- Credentials held server side
- A run log you can read
- A written handover: how it works, how to change it
Best if
You have one repetitive process eating hours a week and you want to see whether this actually works before committing to more.
02 · Start small
System Audit & Technical Documentation
A written picture of what you are running, and where it breaks.
Read-only access to your stack. I map what exists, how data moves, where the manual handoffs are, what has no owner, and what would fail an audit.
Frameworks I map technical controls against include SOC 2, ISO 27001 and 27701, NIST CSF, GDPR, DPDP, PDPA and HIPAA.
What comes back
System inventory
What you are actually running, including the things nobody remembered.
Data-flow map
Where data enters, moves and leaves, drawn so anyone can follow it.
Access & permissions review
Who can see what, including the accounts that should have been closed.
Control checklist
Each control marked compliant, partial or gap, with concrete remediation.
Runbooks
The procedures currently held in one person's head, written down.
Dated PDF export
A document you can hand to a client, an auditor or an incoming engineer.
This is documentation of technical controls, produced for your counsel, auditor or compliance function to review. It is not legal or regulatory advice, and it is not a certification.
Best if
You are heading into a security review, a client due-diligence questionnaire, or an audit, and nobody can currently answer basic questions about your own systems.
03 · Start small
Process Map & System Spec
Two weeks. You own the map either way.
Read-only access to whatever holds the work: the case system, the drive, the calendar, the billing, the spreadsheets. Five completed pieces of work read end to end. One working session with whoever actually runs the process.
You get back a written map of how the work moves, in your own language, with the gaps circled. Then a system specification: what should be built, in what order, what it would cost, and what you should not build at all.
No prescriptions attached and no obligation. Some people take the spec, build it themselves and never come back. That is a legitimate use of it.
If you commission a build within sixty days, the fee comes off it.
Best if
You know something is broken and you cannot name it, or you have been quoted for software and cannot tell whether the quote makes sense.
04 · Build something
The Intake Site
A website that works as the front door of the business, not a brochure.
Most professional websites are marketing nobody reads. This is the other kind. It qualifies the lead, routes it, and hands it to the right person with the context already attached.
Two builds
Starter, $2,500
Multi-page site, service and practice-area architecture, an intake flow that qualifies against your own criteria, structured data and search fundamentals, deployed and live.
Full, $5,000
Everything in Starter, plus a client portal for status, documents and next steps. An insights and guides engine structured for search engines and the AI assistants that now answer clients' first questions. Wiring into your CRM, case management and calendar so nothing gets re-keyed.
What you get
- A deployed site on your own domain
- Real database and authentication where the portal is included
- Admin access, in a repository you own
- A handover session
Best if
Your site is currently a brochure, you live on inbound work, or you are re-keying every enquiry by hand.
05 · Build something
One System
The machinery behind the business, built properly.
Every organisation has one process that keeps breaking and one spreadsheet everybody is afraid of. This replaces it with something accountable.
The sequence is fixed: audit, build, install, measure. Software nobody uses is a cost, so I install it into the working day of real people until it is the path of least resistance. If the numbers do not move, the build is not finished.
Pick the system
Compliance management
Obligation registers, statutory calendars, evidence trails and owner-level accountability that survive an audit.
Matter & case management
Intake, structure, tasking, hearings, documents and supervision. The core of most of what I build.
IP portfolio
Registers, prosecution stages, renewal windows, oppositions, licensing and chain of title in one live view.
Tax & filings
Filing calendars, document collection, reconciliations and approval chains built around who actually signs.
Receivables & billing
Time capture through invoice through collection, with ageing bands, escalation ladders and chase sequences that run themselves.
Litigation & evidence
Evidence registers, chronology builders, exhibit tracking and discovery logs.
Real estate & tenancy
Assets, tenancies, renewal windows, dues, maintenance and title documents as one portfolio.
Inheritance & estates
Asset schedules, beneficiary structures, consents and instrument versions, with strict access control and a defensible audit trail.
Trackers & workflows
Approvals, handoffs, escalations, reporting. The connective tissue where most of the time is actually lost.
Every build includes
- Four-level role hierarchy plus a per-user access matrix merged over role defaults
- Privileged actions checked server side and logged
- Bulk import that maps your existing columns
- A dashboard that answers the question you keep asking
Best if
The spreadsheet has outgrown itself, or you have three tools and you are the integration layer between them.
06 · Build something
Agent Pack
Up to five agents wired inside the system, not sitting beside it.
A chat window does not know your client's name. An agent wired into your data does. That difference is the whole point.
Choose from: intake, document extraction, drafting and correspondence, review and summarisation, research, time capture, invoice preparation, status updates, and knowledge capture on close.
Engineering that comes as standard
Typed output
Rejected on parse failure, so a bad response never reaches your data.
Retry, then dead-letter
A transient failure does not become a lost record.
Human review gate
Below the confidence floor, a person decides, not the model.
Per-tenant isolation
Server-side keys, no credentials in the browser.
Credit budgets
A per-tenant ceiling so costs cannot run away.
Full audit log
Every run traceable, every action attributable.
Best if
You already have a system and you want it to start doing the work rather than just holding it.
07 · Go all the way
Systems Engagement
Name it, systematise it, then automate it. The whole sequence.
For an organisation with little legacy structure to protect, where the answer is not one system but a rebuild of how the work runs.
The order is fixed. Automation applied to an unnamed process only makes the mess faster.
The sequence
Name
The process gets written down. Every handoff, deadline, owner, and place the record breaks. Most organisations have never done this, and it is the actual reason software fails inside them.
Systematise
Templates, action libraries, role charts, deadline structure. Built so the organisation would keep running cleanly even if every AI tool vanished tomorrow.
Automate
Only now do agents deploy, against actions that have already been named, inside explicit roles, with the evidence rule enforced.
What you get
- The written map of how the work runs
- The system built around it
- Agents in production
- A measurement layer, and installation into the working day
- Working artefacts inside the organisation from week two
The engagement ends with your organisation running the model, not with me running it forever.
08 · Go all the way
Enterprise Systems Engagement
The same sequence, installed inside a structure that already exists.
A larger or heavily regulated organisation cannot rebuild itself on any honest timeline, and I will not pretend otherwise. This runs the same sequence inside your existing departments, sign-off chains and risk constraints, rolled out desk by desk on live work.
What the engagement installs
Structural audit
Organisation-wide, against how work actually moves, not the org-chart version.
Governance & evidence rules
Every assertion anchored to a source before it ships. Fabrication becomes impossible to send, rather than merely discouraged.
Explicit roles
Doer, reviewer and decider on every action. The structure that makes AI safe to deploy inside regulated work.
Per-department playbooks
Action libraries built for each department's own work and language.
Agents in your tools
Wired into the software you already run, not bolted beside it.
Working sessions
With the people who do the work, until the new path is the easier path.
Institutional engagements run to procurement timelines rather than mine. I will say so plainly at intake.
09 · Specialist practice
Litigation & Evidence Technology
Digital evidence, structured to survive court.
A separate practice, and a technical one. I am not counsel on the matter and I do not advise on the law. I build the evidence record and the systems that hold it.
How the retainer runs: scope and conflict check, evidence and record review, build the exhibit, then standing availability across live matters.
The work
Digital footprint & forensic analysis
Reconstructing an entity's digital activity into a timeline that holds up under cross-examination: devices, accounts, communications, metadata and movement.
Digital discovery
End-to-end e-discovery. Collection, processing, review workflows and production, run so the record stays defensible from custody through to the exhibit list.
Evidence structuring
Financial and digital records for complex matters, asset tracing, transaction trails, title chains, correspondence and communications, organised into a record a court can follow without a translator in the room.
Building the exhibit
Turning raw technical material, logs, forensic images, code and data, into an understandable record: the submission, the demonstrative and the supporting technical narrative built as one package.
Evidence systems
Registers, chronology builders, exhibit tracking and discovery logs, built as software for the discipline litigation actually demands.
Technologist expert testimony in US courts is available to counsel I have an existing working relationship with. It is not sold from this page.
10 · Off the shelf
Products, and a free place to start.
Not every practice needs a bespoke build. Two products carry the same operating model off the shelf, and the readiness audit tells you honestly where you stand.
Agentic case management
MatterOS
For the solo and small firm. Drop the files in and the matter assembles itself. Intake, structure, due diligence, analysis and drafting handled by agents while you supervise instead of type.
7-day free trial
The operating model, on Notion
LexOS
Every matter, deadline, client, document and hour in one connected workspace you run yourself, with a guided setup portal. One-time price, lifetime access, no per-seat fees.
One-time · lifetime access
Free · 2 minutes
The readiness audit
Twelve questions. Scores your organisation against four stages of maturity, manual, assisted, augmented and AI-native, with a breakdown and a recommended next step. Free, no obligation, no call.
No email required
Retainers
After the build, if you want me around.
Available after a build or an engagement. One month notice, either side, always.
From $900 a month
Systems retainer
New actions added as needed. Agent tuning against real usage. Quarterly review. Extensions as the organisation grows.
From $2,500 a month
Evidence technology retainer
Standing availability for structured evidence, discovery, chronology and exhibit work across live matters.
How every engagement runs
Four steps, no theatre.
01
Tell me what is breaking
Send the shape of the organisation and the bottleneck you cannot get past. I read and reply to everything myself. No forms into a void, no qualification gauntlet. Sometimes the honest answer is that you do not need me, and I will say so.
02
One call to scope and fix the fee
Twenty minutes to name the work and the deliverables. The fee is fixed and quoted before anything starts. No change orders for scope I should have anticipated. If your needs genuinely change mid-build, I say so and re-quote in writing.
03
Build in the open
You see it weekly. Working artefacts early, rather than a reveal at the end.
04
Install and hand over
Installed into the working day of real people, with admin access, documentation and a handover session. You own it. You are not renting it.
You get me. Not an account manager, not a vendor team, not a handover to someone you have never met. The person who understood your problem is the person who builds it.
Who I work with
Any organisation. One route for legal ones.
- Corporates & business houses
- Startups & founders
- Professional services firms
- Government organisations
- Law firms & in-house teams
Questions
Asked before most calls.
- Do you provide legal services?
- No. I build technology. No legal advice, no drafting for clients, no representation. I trained and practised as a lawyer, which is why I understand regulated process well enough to build systems for it, but the service I sell is engineering.
- What is the smallest thing I can buy?
- One agent at $500, or a system audit at $450. Both are complete deliverables, not trials.
- Can I start with the process map instead of committing to a build?
- Yes, and most people should. $750, two weeks, and the fee comes off any build commissioned within sixty days.
- What do you build with?
- React, TanStack, Supabase with row-level security, Postgres, pgvector, Tailwind, Deno edge functions, and the current generation of model APIs. Notion where Notion is genuinely the right answer. The stack follows the problem, not the other way round.
- Do I own what you build?
- Yes. Your repository, your database, your domain, your keys. No lock-in and no per-seat tax on your own system.
- Do you work with my existing tools or replace them?
- Whichever is more sustainable. Replacing working software to justify a build is how consultants make money and clients lose it.
- What happens if the build does not work?
- Measurement is part of the sequence. Turnaround, supervision load, realised time, leakage. If the numbers do not move, the build is not finished.
- How fast can you start?
- Start-small work usually within a week. Builds within two to three weeks. Engagements are scheduled at intake.
- What is the difference between working with you directly and going through adnah?
- Working with me directly covers everything on this page, for any kind of organisation, plus litigation and evidence technology. adnah is scoped only to law firms, in-house legal departments and government legal functions, run as a structured fixed-fee engagement with its own two-track model. Either way, I am the one doing the work.
Bring me the messiest process you have.
Tell me what is breaking and I will tell you honestly whether it needs one agent, one system, or the whole sequence. Sometimes it needs none of them. I have probably built your problem before. Let us find out in twenty minutes.