Meet our founders

I grew up in Chandigarh, India, where I'm still based. B.Tech in Computer Science and Engineering from Punjab Engineering College.

Before Scriptivox, I built a Flutter app called Scan Clan from scratch and grew an Instagram brand from zero. Most experiments failed. One worked, and that one taught me how attention actually moves on the internet. It also got me editing my own videos, which is how I ran into the transcription problem that eventually became this company.

I was the only student in my batch at PEC who didn't sit in the placement cycle. That decision is the cleanest summary of how I work: I think in years, not weeks. I commit to ideas slowly, and once I commit, I don't quit.

I'm the kind of engineer who refuses to ship something that won't scale. My early work at Scriptivox wasn't just frontend and backend, it was the optimization and scalability layer that turns a working product into one that holds up under real load. These days I'm focused almost entirely on marketing and growth, because that's where my edge is sharpest and that's the next chapter for us.

I'm stubborn about doing my own research. I'd rather be slow and right than fast and wrong on someone else's map. Startup Bell has shaped a lot of my thinking on what it actually takes to build something serious from India.

Winning, for me personally, looks like building something big enough that families are supported because of the work we're doing here.

I was born in Mohali, Punjab, India, grew up there, and moved to Canada, which is where I'm based now. B.Tech in Computer Science.

After I graduated, I freelanced as a software developer for a while, then went all in on Scriptivox. I'm the one who got us moving. I'd been waiting for the right thing to commit to, and when Abhishek walked me through the transcription gap he'd been seeing, it clicked immediately. Abhishek had the idea. I had the urgency.

I built the AI models that power Scriptivox, the API, and the meeting bot from the ground up, along with most of the heavier technical infrastructure that keeps the product running. The GPU transcription pipeline, the email and growth automation, the audio and video conversion layer, all of it. I also handle customer responses, because I think the people building the thing should be the ones talking to the people using it.

My ideology is to move fast. Build the thing first, then make it perfect. I don't chase perfection upfront. Perfection comes from iteration and from how real users actually touch the product. Ship, watch what breaks, listen, fix, ship again. A lot of what's in Scriptivox today is the second or third version of something I built. The first version's job was to teach me what the right version looked like.

I work best in long uninterrupted blocks. Once I'm inside a problem, I usually don't surface until it's done. That style is wrong for plenty of companies, but it's exactly right for the kind of infrastructure work Scriptivox needs. Zero to One is one of the few business books I actually keep coming back to. Other than that, the reason I'm here every day is simple. I want to see what this thing can become, and the only way to find out is to keep building it.