Company

Built by people who have done the job it replaces.

The person specifying this software ran clinical data management before building it. The advisers are running clinical operations and CROs today. Nothing here is translated from a brief.

Gurugram and Jaipur, India
Leadership

Who runs it, and what they own.

Four people. Each entry says what they did before this, because that is the part that decides whether the software is any good.

Jahnavi Rohil

Co-Founder & Chief Executive Officer

Clinical data leadership; formerly Consultant at IQVIA and Senior Consultant at Vidia. BITS Pilani. Has held the operational role that the platform is built to serve.

Narendra Singh Rathore

Co-Founder — Strategy, Growth & Technology

Full-stack cloud engineering and startup leadership; Founder of Aerial Borne; formerly Vimana, Vidia and founding product member at Doc Plus. BITS Pilani.

Ashis Kumar Yadav

Technical Lead

Full-stack engineering, AI/ML and AWS infrastructure. Formerly Vidia and Aerial Borne. Owns the platform build.

Vaibhav Pareek

Chief of Staff

Operational leadership; formerly adviser to Master Trust Ltd. BITS Pilani.

Advisers

The people we check ourselves against.

Practitioners running clinical operations and CROs today. Not a board of names on a slide.

  • Dr. Akash Gadgade

    Clinical operations and regulatory strategy

    Formerly Associate Director, Navitas Life Sciences. MBBS, clinical investigator and medical adviser.

  • Mr. Sushant Singh

    Customer proximity and channel access

    Founder, Clinical Veda CRO; formerly General Manager, Clinical Research at Accenture.

  • Dr. Gaurav Srivastava

    Enterprise commercial scaling

    Formerly VP Growth and Marketing, Comviva (Tech Mahindra); Content Head, NBA (APAC).

  • Mr. Yash Mehta

    Infrastructure and security

    Senior IT Solutions Engineer. AWS infrastructure and cybersecurity. BITS Pilani.

  • Mr. Sameer Siddiqui

    Devices and wearables

    Senior IoT Engineer specialising in the integration of wearables and external hardware devices.

How we work

The habits a regulated system demands.

Written specifications before code

A change is specified, reviewed and agreed before it is built. In a regulated system the specification is part of the deliverable, not overhead around it.

Auditable change

Every change to the platform carries its own record — what changed, who approved it, and against which specification.

Clinical and engineering side by side

Data managers who have shipped a database lock sit with the engineers building the thing. Neither side translates through a document.

One owner per module

Each module has a single named owner accountable for it end to end. No shared ownership, no gaps at the seams.

Want to work with this team, or join it?