Prabu Ram (@_praburam) profile picture

SVP, Engineering, Razorpay. Opinions posted here are mine.

Bengaluru, India
Joined January 2012
Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)Photo by Prabu Ram (@_praburam)
At @Razorpay we run read-first, talk-later meetings. Agents write most of what gets reviewed, so we moved from docs to HTML: visually rich, agent-agnostic, easy to share. Today we’re open sourcing Slash docs, the tool behind it. razorpay.com/slash-docs github.com/razorpay
AI agents are changing how we work and collaborate, but documents are still stuck in the pre-AI era. Agents can now create beautiful, interactive decks, dashboards, and reports in HTML. But the moment you want to collaborate on them, everything breaks down. Google Docs wasn’t built for rich, interactive HTML or AI agents. Feedback gets scattered across Slack and email. Every edit means going back to the agent, generating a new file, and sharing another link. No real-time collaboration. No single source of truth. We built SlashDocs to fix this. Think Google Docs, but built for AI agents and the documents they create. Host HTML and Markdown in one central hub. Share documents, manage permissions, and comment directly on the content, just like Google Docs. Agents can read feedback and update the same document in real time. No duplicate files, no endless back-and-forth, and everyone stays in sync. What started as a small internal experiment in one team has now scaled across @Razorpay. 28,000+ documents created. Over 50% of all documents generated at Razorpay now live on SlashDocs. And today, we’re opening it up to everyone. Self-hosted. Agent-agnostic. Fully open source. AI agents have changed how we create documents. It’s time we changed how we collaborate on them. Try it: razorpay.com/slash-docs/
6
216
I started running during COVID, mostly for fun. Going from zero to 5K was much harder than going from 5K to half-marathons. The longer I run, the more it reminds me of careers, including my own. A few thoughts on both. linkedin.com/pulse/tiny-rock…
1
5
255
Slash is @Razorpay's autonomous agent platform. Writes code, reviews PRs, debugs incidents, answers questions across teams. ~1,000 PRs/week. 1 in 3 with zero human review. PMs raising their own PRs. Wrote about how product building has shifted: blog.razorpay.in/blog/razorp…
1
1
5
101
Six weeks ago, 122 tasks. Last week, 14,000+. The compounding has been the most surreal part to watch. And the most fun project I've been on in a long, long time, not just in @Razorpay
We recently built an AI assistant inside @Razorpay called Slash. It reads our entire codebase, debugs production incidents, reviews specs, writes code, reviews every single PR, answer tech queries and also raises PRs for small features. It's easily accessible through Slack. We can tag it in any Slack thread, describe the problem in English, and it gets to work. Six weeks ago, Slash handled 122 tasks in its first week. Last week it handled 14000+. Queries, analysis, bug fixes, PR reviews, test runs and work that earlier lived across scattered tools and teams can now be done with Slash right within Slack. 1000+ people used it in a single week because it got their work done faster. The whole adoption has been completely organic. The numbers from last week have been very encouraging - 14,854 tasks completed. 2,150 PRs raised, 1,152 merged, 45% of those PRs shipped with zero human rework. A payout gets stuck mid-retry during a live incident, an engineer tags Slash and within seconds, it cross-references logs with code and pinpoints a state machine bug blocking the retry-to-failed state transition. Tells the team exactly which logs to check and how to resolve the incident. With its K8s analyzer skill, Slash scanned a single namespace, right-sized all 11 workers using 48-hour P95 pod metrics, and raised the PR. One run saved $560/month. A marketing banner bug was fixed with few prompt iterations with a PR raised, merged to prod and deployed in minutes. No front-end developer touched the code. Security teams ran static security testing and remediation through Slash at org scale. Thousands of findings were purged and many more got validated autonomously. But Slash isn't just an engineering tool. Account managers now trace stuck customer payments and integration failures through Slash instead of pinging engineers on Slack. L2 product support tickets get triaged by Slash before they reach engineering. 250+ non-engineers ran thousands of sessions last week. PMs used it for research on our payments infra, customer interviews and product features sometimes raising PRs of their own. Analytics teams built SQL pipelines. 11% of all sessions came from people outside tech and product. On our company bakkar (watercooler) Slack thread, someone asked Slash jokingly to assign tasks to everyone and it responded in the same tone. It seamlessly started participating in inside jokes and conversations. The quality compounds with use. Engineers who shipped 11+ Slash PRs averaged a 63% merge rate without rework. First-timers averaged 37%. Across the org, human review comments per PR have dropped more than 40% with Slash starting to do in-depth review of every single change. We're still early. Large cross-repo refactors, fully agentic sdlc and plan mode are next. But Slash has already changed how people at Razorpay build, debug, and ship every day.
6
180
😂 emacs is better though!
This Post is from an account that no longer exists. Learn more
2
While I got lucky with my naturalization, I have so many friends who moved to the US 20 years back and still don’t have their green cards, let alone citizenship.Instead of expediting GC and naturalization for legal immigrants, the country is going several steps backwards (2/7)
1
These immigrants are still confused about what “home” is. While their kids, born in the US, are stepping into their teens, they still can’t call the country their home. Coz someone just to get a few political points can block their entry into the country (3/7)
Frodo: I wish it need not have happened in my time. Gandalf: So do I, and so do all who live to see such times. But that is not for them to decide. All we have to decide is what we to do with the time that is given us. - JRR Tolkien, LOTR – at Texas, USA
6
46
3
167
Move your applications to the Cloud and back - nutanix.com/blog/cloud-mobil…
The morning after a @rogerfederer loss is the hardest thing ever. Like someone actually died! Gut wrenching. The first 5 seconds after you wake up, you think about the game, lose hope for humanity and bury your face under the pillow, not wanting to ever wake up!
8
With @StorSC at #NEXTConf. Celebrating 10 years of Nutanix!
1
3
33
Nutanix Move 💪
Xtract for VMs is so easy to use! Helped a dark site customer install it over the phone (no webex) and migrate their VMs from their previous hypervisor to Nutanix AHV! Hard part was remembering what buttons to click for previous hypervisor - I haven’t used it in over two years.
1
3
Sapiens - A Brief History of Humankind. Day 7/7. No reviews, No explanations. 1 book/day for 7 days. With each post nominate someone else to take up the challenge (Thanks @anupadmaja for nominating me).Today I nominate @kukrejaj
1
3
The Elephant in the Brain - Kevin Simler and Robin Hanson. Day 6/7. No reviews, No explanations. 1 book/day for 7 days. With each post nominate someone else to take up the challenge (Thanks @anupadmaja for nominating me). Today I nominate @tparekh
2
Skin In The Game - Nassim Nicholas Taleb. Day 5/7. No reviews, No explanations. 1 book/day for 7 days. With each post nominate someone else to take up the challenge (Thanks @anupadmaja for nominating me). Today I nominate @rajmatazz
2