Work

Case studies with the hard parts left in

Architecture, constraints, the alternatives we rejected and why. Clients are described rather than named, with their agreement — except where they have asked to be named.

—
Four engineers, twenty million dollars a month

A consumer lending platform that underwrites, prices and disburses a loan in about five minutes — and decides seven thousand applications a day without a human reading most of them.

—
Two frameworks, one dashboard

A customer success platform competing with Salesforce, serving tens of thousands of users across five continents — and the architectural decisions that let a small team keep pace with a company a thousand times its size.

—
The cheapest repair is the one nobody drives to

A remote management platform for three thousand EV chargers worldwide — where the design goal is not to detect faults faster, but to resolve them without dispatching anyone.

—
Sixteen thousand ATMs, most of them where the roads run out

Our client runs about seven per cent of India's ATM estate, largely in tier-4 and tier-5 towns. We build and run the switch integration, the UPI and IMPS stack, and the reconciliation underneath.

—
The model proposes. A person decides.

An internal AI platform for a lending-technology company: an assistant that can act across forty-seven tools, finance queues where the model proposes and a person confirms, and a browser agent whose limits are written in code rather than in the prompt.

—
A model that asks instead of guessing

An AI coding engine for a US healthcare revenue-cycle company. It reads anaesthesia charts, assigns every billing code with its reasoning, flags what the record leaves out — and puts each code in front of a coder to accept or reject.

One per practice area.