P360 and the Art of Getting Through

A doctor’s phone is already crowded. Patients, colleagues, family, appointments: everyone has a reasonable claim on the little rectangle. Somewhere in that queue sits a pharmaceutical representative with information to share. The information may be useful. Getting it through is an entirely different occupation.

P360 has built a business around that distinction. Its proposition begins with an almost impolite question for a software company: why should the person receiving your message have to learn your software? Let the doctor use a familiar channel. Put the templates, permissions, records, and enterprise connections on the sender’s side. The conversation can look ordinary even when the machinery behind it is anything but.

The app that never arrives

Consider the original ZING communication module, announced in November 2020. Pharmaceutical sales teams could send branded, templated texts and digital assets through established messaging channels. Templates could be approved in advance. Administrators could track messages, clicks, and asset views, with information flowing back into existing CRM records. The recipient did not need a new app or subscription.

That arrangement solves two problems at once. A representative gets a usable route to a physician. The organization gets a controlled way to distribute approved material and preserve the record. A friendly interface alone would solve only the first problem. A meticulous archive alone would solve only the second. P360 tries to join them without asking the doctor to admire the plumbing.

Today that product family is called Connect. Its feature list includes two-way messaging, a shared number for calls and texts, video, scheduling, digital signatures, co-browsing, and bots that can hand a conversation to a person. QR codes give a printed or digital asset an entrance into the same system. Each feature addresses a small interruption: the missed call, the forgotten login, the awkward jump between tools.

First came the data. Then came the conversation.

In a public interview with business host Bhavesh Naik, co-founder and CEO Anupam Nandwana described P360’s beginnings in data analytics. Working with life sciences data led the company toward the people who needed to act on it: representatives and medical science liaisons engaging healthcare professionals. A report could tell someone where to look. The next problem was helping that person do something useful.

His distinction between a system of record and a system of engagement explains the move. The record captures the relationship; engagement supplies the means to continue it. P360’s messaging work grew out of that gap. This is a useful evolution for enterprise builders to study: the next product opportunity may sit immediately downstream of the work you already do.

Nandwana leads the company alongside co-founder and COO Edward Vaz. In the same interview, Nandwana stresses service, availability, and empowering employees. Those priorities fit a business whose software must enter somebody else’s complicated organization. Getting an enterprise tool adopted involves people who did not buy it, systems nobody wants to replace, and colleagues who must live with the implementation.

Three verbs, quite a lot of machinery

In September 2025, P360 simplified its naming. ZING became Connect. BirdzAI became Activate. EdenHelp became Automate. The company unveiled the unified framework at Fierce Pharma Week, describing a CRM-agnostic approach that brings engagement, data, and automation together. The new names are more helpful to an impatient buyer than a small aviary of brands.

“This change helps clients immediately understand the value each solution delivers.”

Anupam Nandwana / September 2025

The significance goes beyond typography. A product family is easier to evaluate when its divisions correspond to jobs: communicate with someone, understand the data, perform the next task.

Activate carries the less glamorous work that makes the visible features useful. Its data-foundation tools bring commercial and engagement information together, merge duplicates, retain record lineage, and give stewards controls over changes. Other modules address sales operations, territory alignment, incentive compensation, marketing operations, analytics, and integration. A recommendation is more valuable when the organization agrees which customer record it belongs to.

Automate adds natural-language questions, content drafting, research summaries, and inbound-request automation. The internal research tool is described as searching approved material and sources such as PubMed, with citations and role-based access. These details matter more than a chatbot’s conversational charm. The organization needs to know where an answer came from and whether the person asking should see it.

There is also an unusually tangible branch of the story: Swittons. P360’s smart devices use physical buttons to trigger enterprise tasks, including service requests and supply replenishment. Their 2020 Salesforce AppExchange debut brought that action into Salesforce workflows. A button on a desk and a text on a phone share the same design instinct: reduce the human step, then connect it to the organization.

The customers are buying different kinds of relief

The named customer examples reveal why “pharma software” is too broad a description. Upsher-Smith’s need concerned reaching providers through existing channels. In a testimonial published by P360, commercial leader Jim Maahs reports 90% user adoption within the first few months and thousands of messages moving in both directions.

That is a useful adoption signal. It measures uptake, however, rather than an increase in prescriptions or an improvement in patient health. A buyer should distinguish those outcomes. Software can make a conversation easier to start; what the conversation accomplishes remains a separate question.

Biote’s CIO, John Olsen, describes engaging P360 to establish the company’s first enterprise data lake, including implementation and support. ANZGOG’s finance and business manager, Rachel Naughton, describes consolidating trial data that had been scattered across systems, making information easier to access and share across the research network. These examples concern information infrastructure as much as communication.

Together, they show a vendor selling several kinds of relief: less effort reaching a provider, less fragmentation in reporting, less work assembling a dependable data foundation. P360 says it has deployments in more than 50 countries and works with four of the top ten global pharmaceutical companies. Those are company-reported scale claims; the named examples explain the work more concretely.

A smaller front door into a very large market

P360 occupies the space between large enterprise platforms and narrowly focused tools. Pharma CRM vendors such as Veeva and Salesforce supply important parts of the surrounding environment. Generic messaging services offer channels. Data platforms offer infrastructure. P360’s competitive pitch packages industry-specific engagement and operational controls across those boundaries.

Its CRM-agnostic positioning matters because enterprises rarely begin with a blank sheet. P360 describes integrating with existing systems, while its Microsoft background and Azure-based data tools give it a familiar foundation for implementation. A team can evaluate a communication or data problem without first deciding to replace its entire commercial stack.

The business model pairs enterprise software with implementation expertise. Public product pages lead buyers toward demos and sales discussions. For procurement, the practical cost question includes data preparation, integration, content setup, training, and support alongside the software agreement. Buyers should define those responsibilities early: even a familiar recipient interface can require substantial work behind the scenes.

P360’s recognition includes a 2024 Innovator of the Year award from the Diversity Alliance for Science and an announced sample-vendor listing in Gartner’s 2023 life science commercial operations Hype Cycle. Its current materials also report SOC 2 Type II certification. These credentials can help open a procurement conversation. The actual deployment still has to earn its place in the working day.

Borrow the habit, build the controls

The lesson readers can copy is quite practical. Start with the recipient’s existing behavior. Identify the approvals and recordkeeping that the sender’s organization requires. Make the approved action easy, preserve its history, and connect the result to the systems people already use. P360 applies that sequence to a doctor’s phone; other enterprise businesses can apply it to their own crowded inboxes and neglected portals.

The conditions matter. Familiar channels require permission and relevance. Approved-content workflows require current materials and people responsible for maintaining them. AI assistance requires dependable sources, appropriate access, and review suited to the task. A more convenient channel cannot rescue an irrelevant message, and a tidy interface cannot repair a neglected data foundation.

P360’s appealing idea is that the recipient need not experience all this complexity. Someone still has to manage it. Put enough care into the backstage work, and the person in front can do something pleasantly unremarkable: receive useful information, answer when convenient, and return to the rest of the day.