I’m Lakshya Pratap Singh, an independent systems architect. I design and build financial and operational systems — ledgers, reconciliation engines, ERPs, CRMs — for companies in India, the UAE and the UK. I work alone, one engagement at a time, based in India.
The arc
India is home base and the market I know in my bones — the GST rhythms, the udhaar economics, the way a Surat trader and a Bengaluru founder describe the same reconciliation problem in completely different vocabularies. DR Congo is where I ran field operations and learned the lesson that now underwrites everything I build: a system that needs perfect infrastructure is a system that doesn’t work. Networks fail, power fails, roads fail — the system’s job is to keep the truth intact anyway, and that assumption is baked into every offline-first field app and every replay-safe ledger on this site. London is the next chapter. Three very different places; the same lesson from each: the system has to survive reality, not the demo.
The series
In 2026 I published architecture deep-dives of fourteen fintechs — Stripe, Revolut, Monzo, Nubank, Mercado Pago, Kaspi, PhonePe, OPay, TymeBank, Airwallex, Afterpay, Visa, Mastercard, LemFi. Not summaries — teardowns: how their ledgers, risk engines and settlement systems actually work, read from their artefacts, including where I think they got it wrong. It’s the interview you get to conduct before ever paying me, and it’s free: /blog.
The series is also the honest answer to the obvious question — why should anyone trust a one-man shop with money infrastructure? Because the thinking is public and checkable. Every method I sell is written up openly: why ledgers drift, how double-entry actually works for engineers, how a migration lands without downtime. Read first, judge, then call. Bharosa is earned in public.
Where it actually came from
The expertise never came from the books. It came when I was swimming in it — not reading about swimming.
Four years of that, which is a number I would rather state plainly than dress up. What matters is what those four years were spent doing: inside live systems that were already carrying money, at the point where a mismatched number was somebody’s actual problem that week. Not architecture diagrams on a whiteboard — production, at the hour the discrepancy surfaced, with the pressure of someone waiting on an answer.
That is a different education from the one that produces confident opinions about systems nobody has had to fix at eleven at night. I have read the books too; they are useful, and they are not where any of this was learned. The parts of this work that are hard to teach — knowing which discrepancy is timing and which is a bug, hearing the difference between a system that is slow and one that is lying — arrived from being in the water.
The languages thing
My clients speak Hindi, Gujarati, Marathi, Tamil, Kannada, Arabic and five kinds of English. I speak some of these badly and one of them well. But every one of those languages has a word for hisaab — hisaab in Hindi, hisab in Gujarati, hisheb in Bangla — and hisaab is my mother tongue. I may not get your idioms right; I will get your books right. That trade has yet to bother a single client whose numbers finally matched.
Why one person
Because accountability doesn’t scale and I refuse to pretend otherwise. When you hire me, the person who designed the schema is the person who answers the phone — no bench, no account manager, no “let me check with the team.” One engagement at a time is the operating constraint that makes the promise real, and the decision-log habit makes it auditable: everything significant, in writing, yours to keep.
The trade-off is honest too: I’m not the right choice for a fifty-engineer programme or a body-shop contract, and I’ll say so on the first call. What I am is the strongest version of one specific thing — a senior architect who has built the money path many times, works with the door open, and stakes a public reputation on every engagement, because the reputation is the business. The man, the myth, the ledger — take it or leave it, but you’ll always know exactly who you hired.
The operating habits
Written scope and fixed quotes, so the meter never runs open. Weekly shippable slices, so progress is visible instead of narrated. Bad news early and in writing — the habit that has saved more engagements than any technical trick. And the preview-tag policy on the products: anything not demonstrable to a stranger says so on its own page, because trust spent on small honesty returns with interest on the large ones.
Elsewhere
LinkedIn — the teardown series lives there too, syndicated with canonical pointing here. GitHub — the public code. And this site itself is a working sample: static, schema’d, answer-first, built the way the GEO service says sites should be built — the tin doing what the tin says.
Say hello
/contact — shukran, dhanyavaad, and yes, chai works over video. Describe the problem in your own words; the first thirty minutes are free and honestly refereed, even when the honest answer is that you don’t need me.