Product & architecture
I help teams name what they are building, how the pieces connect, and what ships first — without process theatre or a roadmap that dissolves the week after launch.
What this means in practice
Product architecture here is not investor slides alone. It is shared domain language, sensible boundaries for services and data, integration maps that respect legacy and vendors, and release slices you can price in rupees or dollars and still defend in a stand-up.
How we work together
We start from reality: current stack, team size, compliance touchpoints, and where revenue actually moves. Workshops stay short; artefacts stay inspectable — diagrams, decision logs, and milestones that link to a MoCabs-grade backend or a focused marketing site, depending on what you are shipping.
What you can expect to walk away with
Roadmap narratives, API and event boundaries, admin versus self-service splits, risk notes for third parties, and “if we only ship one thing next” scenarios. Enough for engineering to estimate and for leadership to align — not a binder nobody opens.
India, hills, and global clients
From Darjeeling and Sikkim I work across time zones. The same discipline applies whether you are localising OTP, SMS, and payments for the Indian market or wiring a global SaaS into your own Supabase and edge functions.
A good fit when
You have ambiguity worth resolving, or a rewrite where the first failure mode is building the wrong abstraction. If you only need a decorative deck, this is not the engagement — if you need the spine under your app, web, and operations, it is.
“We came in with three products and one database. RS. gave us language and boundaries we still use when we argue about scope — and the first slice actually shipped.”
Other ways I can help
UX & UI · full-stack build