Back to Profile
Professional Journey

Startup

When product jobs don't exist in your city, you build the path yourself. This is the story of Infnai Tech - a solo-founded studio that turned personal savings and a learning obsession into real products, real clients, and hard-earned clarity about what it actually takes to build.

The Origin

When there's no path, you build one

I left a stable job due to a mix of family priorities and stagnant growth. What I didn't anticipate was a structural reality: product management as a discipline barely exists in Rajkot. It's an industrial city. The IT sector leans heavily on services, not product culture. There were no PM roles to apply to - not within commuting distance, not in the ecosystem I was part of.

I tried a brief stint as a Digital Consultant at a steel industrial company. Left within two months - it wasn't where my growth lay. The AI boom was beginning, GPT was becoming mainstream, and I had savings, time, and genuine conviction. The calculus was simple: if the environment won't give you the experience, create it yourself.

"When there are no available paths, it seems you need to create one for yourself."
The Studio

Infnai Tech: building for real clients

Infnai Tech started as a digital studio. The first phase was client work - building business websites, CRM integrations, and admin portals for real businesses with real deadlines and real expectations. No sandbox. No safety net. Every project was a lesson in scope, delivery, and managing someone else's trust in your output.

These weren't template drops. Each required understanding a business, defining what the website needed to do for that business, and then designing and building it to that standard. Client work built the discipline of shipping under external accountability - something no personal project can fully replicate.

The Big Bet

Relloid: interior management, end to end

Relloid was the leap from services to product. A full-stack SaaS built for interior design firms, designed to manage the entire project lifecycle in one place. The scope was ambitious for a solo builder.

Org Planning
Team structure, role management, and firm-level administration for design studios.
Project Management
End-to-end project tracking: timelines, milestones, task assignments, and status visibility.
Client Dashboard
Dedicated client-facing portal for real-time project updates, approvals, and communication.
Budget Tracking
Line-item cost management with forecasting and spend-vs-estimate visibility.
Items Management
Product catalogue and procurement tracking: furniture, fixtures, materials, vendors.
AI Summaries & Reports
Multi-agent AI layer generating daily progress reports and project health summaries.

Beyond the webapp, the Relloid ecosystem includes a marketing website (relloid.in), an admin portal, a subscription management system, and an interior repository - a curated reference layer for designers. Pre-launch, with early trial users onboarded.

Wearing every hat - research, UX/UI, development, testing, deployment, integrations - leaves little room for market thinking. The product was ready. The distribution wasn't.
Hard Lessons

What this chapter actually taught me

Solo founding is clarifying
When you're the only decision-maker, every tradeoff is explicit. No one absorbs your blind spots. You learn fast what you're good at, and what you're not.
Distribution beats product
I chased product quality and let market-building slip. Months of building. Some trial users. Then silence. A great product without distribution is a well-kept secret.
A co-founder isn't optional
Managing research, UX, dev, testing, and deployment solo works until it doesn't. A complementary co-founder doesn't split the work, they multiply the thinking.
Constraints force creativity
Limited capital meant deliberate choices. No bloated tech stack, no over-engineering. Constraints shaped every design and architecture decision into something intentional.
The Takeaway

What I carry forward

The startup chapter wasn't a career detour - it was the fastest growth period of my professional life. I shipped production software across multiple domains, managed real client relationships, made architectural decisions with no one to second-guess them, and built a genuine appreciation for what founders face every day.

More than any skill, what I carry forward is a posture: product work is never just building. It's understanding who you're building for, why they'd care, and whether you're solving a problem worth solving. The startup taught me to hold all three simultaneously - even when resources are thin and pressure is real.

  • Full-stack product thinking: from user research to deployment
  • Client accountability and external stakeholder management
  • Solo decision-making under resource constraints
  • AI-native product architecture and multi-agent system design
  • Honest understanding of why distribution matters as much as product
  • The conviction that growth requires building, not waiting