
Sharing the inner workings of @Razorpay Design. ✌️
Bangalore
Joined June 2020
- Tweets614
- Following32
- Followers5.7K
- Likes597
Razorpay Design retweeted
Had a blast getting a tour of the Razorpay office and seeing how @Razorpay_Design works.
Probably the most AI pilled design team in India.
Thanks @saurabhsoni_ss for making this happen 🫶
Razorpay Design retweeted
3/ @jayneil at @Razorpay_Design office
So many versions of Razorpay design team in one photo! Old, new and upcoming ;)
Razorpay Design retweeted
With one of the most stellar, creative, talented teams I’ve had a chance to be a part of in my career so far, @Razorpay_Design 💙
Drop a note here if you’d like to meet at config 🤝
Going to @figma Config Bengaluru? So are we.
@Razorpay_Design will be at Figma Config tomorrow: the people behind the checkouts, dashboards and money movement that millions of businesses rely on every day.
#Config2026 #RazorpayDesign #DesignAtRazorpay
What are your plans this Friday, post Figma config?
We're hosting another AI x Design meet-up with some amazing AI-pilled designers, 6pm onwards.
luma.com/tbsaa3zq?utm_source…
Razorpay Design retweeted
SlashDocs is insanely good for AI-native design workflows. This one is one of my favourite ones so far.
Best of both worlds, using agents to design, and then seeing them on a canvas. Collaborate, comment, use Claude/Codex/Open-models (whatever suits you).
LMK if you would like to know more.
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/
Razorpay Design retweeted
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/
Razorpay Design retweeted
𝟱𝟬𝟬+ 𝗣𝗥𝘀 𝗺𝗲𝗿𝗴𝗲𝗱 𝗯𝘆 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗿𝘀! ~70% of them are core product and feature work, rest bug fixes and maintenance. 𝗛𝗲𝗿𝗲 𝗮𝗿𝗲 𝗺𝘆 𝗻𝗼𝘁𝗲𝘀.
Design is now a very different function at @Razorpay. Product designers don't just own mocks, they own the actual experience in production, designing, building and maintaining it.
6 months back, we decided to revamp how we build software. A big part was design handoffs: an unnecessary collaboration tax in today's world. With the right context and skills, AI can now write great code. So, anyone should be able to build.
So, we reworked our engineering systems and design workflows. We experimented a lot, made some mistakes too, and built an org where shipping is part of every product designer's job.
𝗪𝗵𝗮𝘁'𝘀 𝗼𝘂𝗿 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄? That's a long answer for here. If you're interested, lmk in the replies and if enough folks are keen, we'd love to do a presentation or video on it!
----------------
𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗜 𝗸𝗲𝗲𝗽 𝗴𝗲𝘁𝘁𝗶𝗻𝗴:
𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗱𝗼𝗶𝗻𝗴 𝘁𝗵𝗲𝗻?
Building the systems that let everyone in the org build at scale: Our in-house coding harness, PR review automation, CI/CD automation, and a lot more.
𝗛𝗼𝘄 𝗱𝗶𝗱 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗿𝘀 𝗹𝗲𝗮𝗿𝗻 𝘁𝗼 𝗰𝗼𝗱𝗲?
They didn't have to learn to code. They learnt the foundations of engineering, thinking like an engineer. It happened through learning sessions and on the job.
𝗔𝗿𝗲 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗿𝘀 𝗳𝗿𝗼𝗺 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱𝘀?
Some are. Many aren't. We've built a team of generalist designers who are keen to learn anything.
𝗪𝗵𝗮𝘁 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗻𝗲𝘄 𝗿𝗼𝗹𝗲𝘀? There are two:
1. Design Builders: designers who own the production experience.
2. Design AI Engineers: folks who build the systems and workflows that let designers ship.
𝗗𝗲𝘀𝗶𝗴𝗻 𝗕𝘂𝗶𝗹𝗱𝗲𝗿 𝘃𝘀 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗗𝗲𝘀𝗶𝗴𝗻𝗲𝗿?
A Design Builder is a very different role from a typical design role. They truly own the production UI, UX, interactions, performance, bugs and quality, in code.
Huge shoutout to the entire @Razorpay_Design team! You took this up, pushed yourselves into a completely new world, took insane ownership and made it happen. 🙇♂️
The stage for an agentic future.
At GFF26, content flowed underfoot and around every launch, turning screens into an immersive experience for three days.
Boldly imagined. Meticulously crafted. Entirely in-house at Razorpay Design.
@GffFintechfest @Razorpay
So, we cooked something 🥊
Witness the greatest redemption story ever told.🥊
The story of a fallen champion.
Written off, replaced, forgotten in the age of one-tap.This monsoon, the old trusted guard returns - sharper, wiser and battle-ready
NETBANKING - BACK IN THE RING 🥊
Coming soon to your checkout screen near you. 🛒✨
Watch the official trailer now!
Built. Not just designed.
razorpay.com/ai-builders/
Our latest AI Builders page is designed, coded, and shipped by Razorpay Design.
With 20+ interactive moments. Hidden easter eggs. A game at the end. Powered by Claude.
Go explore! 🚀
Introducing RazorSense - a design language for humans in the AI era, alive in every state and expressive in every interaction.
Go experience it ↓
razorpay.com/razorsense
#Razorpaydesign #Razorpay #Productdesign #UIdesign
Today’s #SOTD goes to @Razorpay_Design for "Razorpay Sprint 26".
awwwards.com/sites/razorpay-…
An immersive journey into the future of AI-led payments.
Congratulations! 🏆
#3D #animation #interaction
















