The people

Meet the team

There are three of us. Between us we build the products, keep the business running, and figure out how to tell people about them. Everything on this site was made by the people below.

03Core team
04+Products live
Still building
S
// founder_00
01 — Member

Shaz

Founder CEO Builder

I started Vergemount Labs at 18, mostly at night, around my AI/ML work.

I've always been bad at leaving an idea alone. If something's stuck in my head, the only way to get it out is to build it and put it in front of people and see what happens.

Most of what we've made started like that. A learning platform for people who won't just pick one subject. An operating system for gyms. A markets course that works more like a game than a textbook. I design them, write the code, break them, and keep going until they actually feel good to use.

I also handle the boring half of running a studio — invoices, the bugs that show up at 3am, the emails nobody wants to send. A lot of it I'm figuring out as I go, and I'm okay with that. Learning on the job is pretty much the whole point right now.

What I care about is stuff that ships and actually works. I'd rather have one real product out in the world than ten nice-looking pitches sitting in a folder somewhere.

The studio's the long-term plan for me. Somewhere to keep building the things I wish already existed, and hopefully get good enough at it that they stick around.

F
// strategy_01
02 — Member

Fardeen

CSO COO

I'm 18, and I'm more into building companies than building products.

The thing I keep noticing is that startups don't usually die because the idea was bad. They die because the day-to-day falls apart. The plan was fine, nobody could actually run it. That gap is where I spend most of my time.

So I work on the operations side — setting up how things get done, writing the processes, keeping the studio moving on the days when none of us really feel like it.

I'm usually asking the same couple of questions about anything we set up. Does this still work if I'm not standing over it? And are we putting the effort where it actually pays off, or just staying busy?

What I like is finding the one spot where a bit of work clears a whole pile of other problems. Sort out the real bottleneck once and everything behind it starts moving again.

Running things well is its own skill, same as design or writing code. I'm happy being the person keeping the engine going in the background instead of the one taking credit for it.

S
// brand_02
03 — Member

K. Shreya

Chief Marketing Officer Polymath OS

I look after brand and marketing — basically the part where we work out how to get people to care.

Something I've noticed is that most products are pretty bad at explaining themselves. There's usually a real reason someone would love the thing, it just gets lost between what it does and how it's talked about. My job is to find that reason and say it in a way that lands.

I like making stuff that feels like something rather than just an announcement — the kind of thing you actually want to be part of instead of scrolling straight past.

Mostly I want to build marketing people remember and a community that sticks around because they want to, not because the algorithm keeps putting us in front of them.

I pay a lot of attention to the small stuff — how a caption reads, where the pause lands, whether something actually feels the way we meant it to. That's usually where the trust comes from.

When it works, it doesn't really feel like marketing. It feels more like someone you trust putting you onto something good, and I think that's worth chasing.

Want to build something with us?

Alongside our own products, we take on a few client builds a year. If there's something you actually want built, send it over — we read everything that comes in.