Hi, I'm Anupam 👋🏼

Currently a Product Manager at Repute, Formerly a Marketer, Always a Human.

My approach to life and work is unique. Uniqueness is a virtue in itself.

In the last 5 years, I have built,

An integrations marketplace from zero to becoming the independent revenue channel for HRIS and marketplace partners.
A compliance filing app and workflows inside HRIS that took statutory compliance filing from a multi-day process down to about 10 minutes.
An AI assistant that simplifies processes around recruitment, payroll, onboarding, and compliance.

Best things I learned after crafting,

HRIS and Payroll systems are built on users' trust. They earn the right to be clever only after being reliable and relatable.
Be a fan of what you work on. It makes the unglamorous parts — talking to users, support tickets, edge cases, compliance rules — worth digging into instead of just clearing them.
Execution is everything — ship small and often.
Never stop learning.

When I'm not building products, I write for magazines that have nothing to do with product management, travel solo to art museums and festivals, pet-sit pro bono for pet parents who need a hand, and help friends get their social media pages off the ground.

Explore my alter ego →

Where I'm most useful.

Most of my work falls into a few patterns. If you see yourself in one of these, we should talk.

HRIS & Payroll Systems

Five years in, I still think in payroll cycles and filing deadlines. I know where these platforms actually lose people's trust — a wrong compliance filing, not a slow page load — and I design around that first.

0-to-1 Product Strategy

I like the mandate that doesn't have a roadmap yet. Hand me a blank page and a business goal, and I'll come back with the bets worth making, the sequencing, and what I'd deliberately leave out of v1.

Integrations & Platform Architecture

I've watched bespoke, one-off integrations quietly eat an engineering team's whole quarter. My default is a canonical data model and API layer, so the tenth partner costs less to onboard than the first.

Workflow Automation

A feature that shipped but barely gets used is a data problem before it's a roadmap problem. I go looking for the manual step people are quietly working around, and automate that one first.

Agentic AI, Grounded

I want AI in the product too, just not AI that guesses. I design the orchestration layer and the accuracy benchmarks, with human review, so it earns trust before rollout instead of costing it.

Compliance & Data Trust

Employee and payroll data isn't like other product data — a mistake there is a legal problem, not a bug ticket. I build consent, data minimisation, and audit trails into the spec itself, not a checklist after launch.

Making a product feel right.

It's the little, subtle details that decide whether people trust and actually use what ships.

Reusable before repeatable

I default to a canonical data model or a shared API layer, so the tenth integration costs less than the first. Not just faster to copy and paste.

Consent by default

Data only moves with explicit consent, and only the fields actually needed for the job. Never a full record by default.

Human-reviewed AI

Every agent response is grounded in live product data and checked against human review before it ever reaches a customer.

Metrics that survive scrutiny

I report activation, MAU, and ARR the way finance and engineering would both sign off on. Not a vanity number picked after the fact.

The unglamorous replatforming

I own the migration and schema work nobody wants to spec, because it's usually what makes the next order of magnitude possible.

One PM, full loop

Discovery through release sign-off and QA, with no separate program layer to hand off to. I carry it end to end.