Selected engagements, written the way I’d want to read them: what was broken, what I built, what changed — metric-led where clients permit, honestly slotted where they don’t. Every claim here survives a reference call, because that’s the standard this site holds itself to.
Start with the ledger rebuild — the archetype problem: books that drifted from the bank until nobody could say by how much, rebuilt into a double-entry core that balances daily. Then the zero-downtime migration — years of live financial history moved with parallel runs and a cutover nobody’s customers noticed — the method that de-risks every other engagement on this page.
The through-line across all of them is one discipline wearing different costumes: immutable truth, projections on top, reconciliation always. Money, inventory, positions, matters — sab hisaab hai. The public version of that discipline is the fourteen-company teardown series; the engagements are where it earns invoices.
Beyond those two: the reconciliation engine — month-end archaeology turned into a daily exception queue; the portfolio system and risk modelling — event-sourced truth with Monte Carlo risk at GPU speed; the ERP migration — a factory moved without stopping; and the growth engagement — this site’s own marketing method, proven on a client first.
Reading them as a buyer? Note what’s marked and what isn’t: numbers pending client sign-off appear as slots, never as decoration. If a case study reads suspiciously smooth anywhere on the internet, ask for the reference call — I’ll offer mine before you ask: /contact.