C-DAC / EPFO ā Accident & Recovery ā SpotBook ā 15-Day Build ā ā¹9 Crore (~$1.1M) ā Platform Architecture ā Lessons
The Foundation Nobody Sees
Two years contributing to backend systems for one of India’s largest government digital platforms.
EPFO's UAN portal ā India's national social security system, equivalent to Social Security in the US. Millions of citizens. Real PF withdrawals. 10M+ transactions every month. The kind of system where a slow query doesn't cause a spinner ā it causes a helpline to light up.
I contributed to claim workflows, REST APIs, Aadhaar-based eSign integration, and database work within that team environment. It taught me what production constraints feel like when reliability matters to millions of people.
What it built inside me: strong SQL, multithreading, and query optimization instincts. The kind you can't learn from a tutorial ā they come from environments where a bad index costs you an SLA breach, not a code review comment.
"Two years of solid, high-concurrency government engineering. Building systems at national scale laid the technical foundation for everything that came next."
The Road Accident & The Pivot
In February 2025, a severe road accident completely disrupted my trajectory.
Following months of medical recovery, I attempted to return to my role at C-DAC. However, the ongoing physical and operational demands post-accident made it impossible to sustain the job. In August 2025, I made the tough decision to step down from my government position.
Turning Recovery into Real Engineering
Instead of letting a medical gap stall my growth, I used software development as my path forward. That path became SpotBook: building a real product around real-world business challenges and keeping my engineering skills sharp in production.
I targeted Surat ā India's textile and garment capital. Businesses doing crores in annual revenue were still running on paper slips, WhatsApp forwards, and Excel sheets held together by one guy who "knows the system."
"Recovery became a path back to production engineering: build software that solves a business problem, then stand behind it when real users depend on it."
The 15-Day Build
24 August 2025 ā the first SpotBook client opportunity arrived through a major jeans manufacturer. Their annual trade expo was 15 days away. Every year, same chaos:
- 200+ Retailers from multiple cities invited
- Salespeople writing orders by hand on paper slips
- Reconciliation took days ā tallying hundreds of slips manually
- Two salespeople could book the same product simultaneously ā overbooking disputes everywhere
- Admin had zero real-time visibility
The business was scaling. The process wasn't. This became SpotBook's first production deployment: digitizing the workflow from scratch.
25 August ā I started building. 15 days later, SpotBook was live for its first production deployment: a full-stack, mobile-first order-management web app with three user roles, real-time inventory, and automated WhatsApp receipts.
The Expo Floor
The Day 1 Incident ā "Rutvik Bhai, Locha Ho Gaya"
Just imagine sitting on a plastic chair in the middle of a noisy trade show floor, staring at a terminal on your lap, trying to figure out why a ā¹3.76 lakh (~$4.5K) order just vanished.
Two sales agents tried to book the last remaining piece of a low-stock product at the exact same millisecond. One transaction went through. The second one failed ā and wiped the agent's 60-product draft from the screen.
Agent panicked. Business owner shouted across the floor: "Rutvik bhai, locha ho gaya."
I pulled up a chair right there on the expo floor, checked logs over my phone hotspot. Then stayed up till 3 AM:
- Added versioning and stock checks to prevent concurrency crashes
- Built frontend and backend draft persistence ā so if one item fails, the rest of a 60-item draft stays safe
"Localhost never teaches you what happens when two people fight for the last unit of stock in a crowded expo hall. But an angry client on the expo floor does."
Season 2 ā Validation
Same app. Second season. ~ā¹4 Crore (~$480K) booked. Zero errors. Zero complaints. Peace of mind.
No 3 AM fixes. No panicked phone calls. No DNS debugging on the expo floor. The system worked. The fixes from Season 1 held. The architecture was right.
"This was the real validation ā not that the app could survive a crisis, but that the engineering was solid enough that there was no crisis to survive."
SaaS Architecture ā SpotBook
During those 15 days building SpotBook's initial production deployment, I consulted with other manufacturers at the expo. Fabric wholesalers, garment makers, different segments. Every conversation revealed the same pattern: they all had similar operational pain points.
As Co-Founder & Full-Stack Developer, I evolved SpotBook into a prototype multi-tenant Modular Monolith (Spring Boot 3 + Java 21) designed specifically for wholesale apparel size matrices, prepacks, and inventory locks.
I worked closely with team members on the floor ā salespeople, inventory managers, and dispatch leads. Business owners describe what they want. Team members describe what they actually need.
The Honest Part
Building software as an independent developer taught me a vital lesson about distribution.
The GTM Realization: Running digital ad campaigns (Facebook lead ads) without an in-house sales team proved ineffective for traditional wholesalers who rely on personal trust and relationship-based selling.
The code was rock-solid and the architecture was proven in production. But a software system without a dedicated sales engine cannot scale into a full business, and that realization shaped my desire to return to a high-impact engineering team.
"AI is a force multiplier, not a replacement for engineering judgment. But engineering judgment isn't a replacement for aligned sales and distribution."
The One-Liner
I went from building government-scale systems at EPFO, to recovering from a serious road accident and co-founding SpotBook ā shipping its first production deployment in 15 days and supporting ā¹9 Crore (~$1.1M) in wholesale bookings. Now Iām ready to bring that battle-tested Java / Spring backend and product-engineering experience to a strong engineering team.
