The Trusted Source: How Veeva’s Acquisition of Ostro Is Rewriting How Patients and Doctors Get Drug Information

Veeva Systems — the enterprise software giant that has long dominated clinical, regulatory, and commercial operations for life sciences — just made a bet that the next frontier isn’t back-office efficiency. It’s the conversation a patient has at midnight when they can’t remember what their doctor said about side effects. In March 2026, Veeva acquired Ostro, an AI-powered brand engagement platform, for $100 million, signaling a deliberate move into direct patient and HCP communication. Paul Shawah, EVP of Strategy at Veeva, argues the acquisition isn’t a pivot — it’s a logical extension of a vision that was always pointing here. What makes this moment consequential isn’t just the dollar figure. It’s what the deal reveals about where Veeva believes the entire information architecture of biopharma is heading, and why building that capability from scratch would have been harder than it looks.

Moe: What first convinced you Veeva needed to be in this space?

Paul Shawah: We saw the trend: healthcare professionals and patients are increasingly turning to large language models to get information — more accurately and more instantly than before. We believe that trend will only continue. It could become even more disruptive in a good way, changing how patients get treated, how they receive prescriptions, how HCPs consume medical information. That pattern is a core part of our vision — making it easier for patients and easier for doctors. You project where things are going and you build toward it.

Moe: Veeva has already invested heavily in Veeva AI. Why not build what Ostro does internally?

Paul: We are building Veeva AI into the Vault platform across clinical, quality, regulatory, and commercial — that’s a massive initiative and a major investment. But an AI application like Ostro is a fundamentally different thing. It requires a curated universe of approved content, specific guardrails, and business rules tuned to the use case of delivering information to patients and HCPs.

Could we build it? We could build it over time but Ostro already works — it’s accurate, it has traction, and it has customers. That proves the use case is feasible and the market opportunity is real.

Moe: Where do you see Ostro’s applications going beyond commercial engagement?

Paul: We’re starting exactly where Ostro is focused today — a brand engagement platform that uses AI to connect patients and HCPs with accurate information. That’s the lane we’re entering. But it’s not hard to imagine use cases extending into clinical settings such as  patient engagement in trials.

I don’t want to speculate too far ahead. We have to see how those markets develop and if we enter them. What I can say is the potential is clearly there.

It’s not enough to be accurate with some questions some of the time. The agent has to be accurate and consistent across all kinds of varieties of questions — and it has to know what it can answer and how.

Moe: The press release says Ostro never hallucinates. How is that technically enforced?

Paul: Building this kind of accuracy and consistency is genuinely hard — that’s actually part of why we acquired rather than built. Ostro starts by operating within a universe of already-approved content. The foundation is exclusively accurate and approved content. On top of that, it has guardrails, context, and industry-specific business rules that keep it accurate even as underlying models change over time.

There is also an audit trail. You can track how it’s reasoning, how it’s arriving at answers, and continuously improve it. We see this challenge across all of our agents — accuracy, consistency, and ultimately scalability at the volume and variety of questions that come in from a real user base. That demonstrates the value of Veeva delivering deep industry-specific agents where we shift that burden away from our customers. That’s what Ostro has solved for this specific use case.

Moe: How does this change the experience for a patient or HCP who wants real answers — not a dead end?

Paul: Pharma companies sit on some of the deepest, most accurate scientific information about a disease state and a medication that exists anywhere. That information gets approved. The problem isn’t the information — it’s how you consume it when you’re a patient asking very specific, personal questions. Ostro changes that experience of making it easy to consume this information.

The other piece is the learning loop. With a platform like this, you start to see patterns — what are patients actually asking about? Where are the gaps? That becomes an opportunity to get additional information approved and surface it better. It’s a virtuous cycle: better data, better answers, better experience over time.

And patients and HCPs may still want to escalate to a human. But the platform builds a common foundation first — so when that handoff happens, everyone already knows what the real questions are.

Moe: How does an HCP- and patient-facing product change Veeva’s identity as a B2B enterprise company?

Paul: Our mission has always been to help life sciences companies become more efficient and more effective. We have software and data products across Commercial Cloud and Data Cloud that do exactly that. This is an extension of that mission, not a departure from it.

The future is one where patients engage directly with information — more frequently, facilitated by large language models — and where HCPs do the same. We want to be the infrastructure that enables that. Our vision expands as the market evolves. This is a meaningful piece of where it’s going.

Moe: How does this acquisition separate Veeva from Salesforce?

Paul: We’re doing very different things. Veeva is building an industry cloud — deep commercial software, data products, content infrastructure, engagement channels— all natively integrated, all purpose-built for life sciences. Salesforce is a horizontal platform. Their approach is essentially to take a general-purpose tool and customize it for vertical use cases. That’s largely custom-built work, and it’s more like a project than a product.

This acquisition is a concrete example of what it means to go deep in a very specific industry process. I think that creates further separation between Veeva and horizontal or point product vendors.

Paul Shawah is Executive Vice President of Strategy at Veeva Systems.