Sriram
Murali

I build the invisible infrastructure that lets ambitious products become inevitable — the layer beneath the interface that users never see and never have to think about.

Sriram Murali
<5 min
Complexity to simplicity
Cashfree — merchant onboarding, re‑architected
Scale without failure
Xoxoday — platform rebuilt during hypergrowth
80–85%
Machine indistinguishability
crisp — AI that passed blind human tests
<3s
Infrastructure that earns its keep
Beetle — full compliance check on a single server
The work

Building the invisible.
Proving the principle.

Engineering leadership
Cashfree Payments
When a merchant goes live before the conversation ends
Took a regulatory bottleneck and rebuilt it into a competitive advantage. The system didn't just cut time — it changed how the business thought about compliance.
Xoxoday
The platform that absorbed $875M without a single incident
During hypergrowth, re‑architected the core into domain‑oriented services so the product team could ship without ever wondering if the floor would hold.
crisp / Tenreads
Readers couldn't distinguish machine from human
Before LLMs existed, built a summarisation engine with 80–85% blind accuracy. Four engineers delivered what others required entire editorial staffs to match.
Beetle · getbeetle.in
The gap
Merchant compliance is still a manual, expensive process
Indian payment aggregators face a widening regulatory surface, yet the tools available are enterprise‑priced and still require armadas of human reviewers.
The build
A compliance check that runs before the merchant hangs up
Intelligent scraping, content‑aware verification, and risk classification — all in under three seconds on a single 1GB server. No GPU. No API bill. No lock‑in.
The philosophy
Constraints drive elegance
Beetle isn't lean because of budget. It's lean because the hard way regularly produces the best architecture. Every component earns its existence.
How I think

Principles for building
what hasn't been built.

I.
The org chart is an architecture decision — clarity of lanes and communication rhythms determines whether fifty engineers move like one or fifty.
II.
Every product has one engine. Find it early, invest relentlessly, protect it from the roadmap. The engine is where compounding lives.
III.
Technical debt is a position, not a failure. The question is what it prevents you from doing next quarter — and whether that tradeoff was deliberate.
IV.
Constraints produce better architecture than comfort. A tight deadline, a single server, a four‑person team — these force clarity about what's actually load‑bearing.
On record

What they said.

YourStory
"Tenreads' Timelines currently operate at an accuracy of 80–85 percent, which is extremely high for an AI system."
Read →
Inc42
"Tenreads aims to stem the filter failure problem and help people find the ten best stories everyday on the things they care about."
Read →
New Indian Express
"Whatever other apps are doing with dozens of writers and editors, we are doing as four engineers."
Read →
Capabilities

What I bring to
a moonshot.

Technical organization design Platform & infrastructure strategy AI/ML as a strategic lever P&L‑oriented tech leadership Compliance infrastructure Content infrastructure Payments & fintech Lean systems engineering Founder‑mode EM

If you're building something
that hasn't been built before.

I work where technical depth, product intuition, and an obsessive focus on quality converge. The invisible infrastructure that makes iconic products possible. Let's talk.