Placeholder profile. Layout and tone are final; the founder’s real story and portrait are coming.
The journey
This is a placeholder profile. The structure, layout and tone are final; the words and the portrait will be replaced with the founder's real story.
PharmaOS started from a simple, repeated observation: pharma commercial teams are not short on data, they are short on the time between a signal appearing and someone acting on it. After years close to how field forces, brands and territories actually run, that gap, decision latency, looked like the real constraint, not headcount and not another dashboard.
The decision was to build the layer that closes it: read the CRM and BI a company already has, return the decision, in time to act. No migration, nothing stored, built for pharma rather than retrofitted to it.
Why PharmaOS
The first generation of Indian pharma built access. The second built scale. The next will run on commercial intelligence: every rep, manager and brand head acting on the real reason, while there is still a cycle left to change the outcome. That is the company being built here.
Track record
PharmaOS
Building the AI intelligence layer for pharma commercial teams.
[Previous company], [role]
Led the team that shipped [the relevant thing], where the pharma decision-latency problem first became impossible to ignore.
[Earlier company], [role]
Engineering and product foundations that shaped how PharmaOS is built: proof over promise, security first.
Recent on LinkedIn
Work with us
The team is the proof too.
See what PharmaOS does on a slice of your own commercial data. A 20-minute private walkthrough, nothing stored.