PubVisual Smart PathwaysSmart Pathways turns your approved publication into branching journeys. Physicians choose the route and the depth; every stop along the way is already approved. You publish once. They each read it their own way.
70% of HCPs feel pharma reps don’t fully understand what they need.
Indegene · The Digitally Savvy HCP · 1,000 physicians
Hard to blame the rep. Veeva clocked the average face to face visit at about three minutes.
Three minutes is a greeting, not a needs assessment.
And every physician in the room needs something different from the same data.
One approved publication becomes a journey that adapts to specialty, interest, and depth. Her question first, always. The physician steers. The science follows.
Watch two physicians take the same paper ↓
Built for medical teams at
Dr. Amara Osei
Dr. Mateo Ruiz
Dr. Ingrid WeberSame segment. Three different first questions.
Your targeting is already careful: specialty, region, stage of adoption. The list can say the specialty. It cannot say which physician wants the mechanism, which one wants the endpoint, and which one wants to know what changes for the patient in front of them.
That difference only shows up after they open it. Smart Pathways is built for exactly that moment: the same approved story, read three different ways.
Tap one of them. The route, the order, and the stops rebuild around what they came to find out. Neither of them ever sees the other’s version, and neither one had to ask for it.
Self-running · tap a physician to take over
Two journeys, one review. Both routes recombine the same approved modules, so nothing new is created and the review you already did covers them both. That is the whole idea: not one video for everyone, a way in for each physician.
A journey is not just which route. It is also how far to ride. Every Smart Pathways build carries three depths of the same approved story, and the reader decides how much science fits the moment.
One screen, one message: what changed and why it matters to her patients. Read, understood, back to clinic.
One approved core flexes to every attention span. Nobody gets the wrong version.
60+ studies on why physicians stopped reading pharma’s science, and the evidence for what works instead. Sourced, quotable, built for forwarding.
Get it now · free →
PubVisualby RedNoviusRoutes are not new content. They recombine modules from your approved core: the endpoint figure, the safety table, the expert clip. Different order, different depth, and no new claims, ever.
Everything stays modular and version-controlled, structured for review inside your existing Veeva workflow. Your reviewers see one core. Your physicians each get their own way through it.
Same six modules. A different journey every time.
One approved core follows your publication into the channels it already lives in: the portal, the inbox, the booth, and the iPad in the MSL’s bag.
The journey lives on your HCP portal, ready for the physician who arrives at midnight after clinic.
“Two physicians walked me through the same piece and told me two different stories. That was the point.”
Bring us your paper, your poster, or your value story. In 30 minutes we will sketch the routes your physicians would actually ride. Built to move through your review, not around it.
The document that settles the argument: 57 pages of evidence on why your science isn’t landing, and what to do about it.
If yours is not here, bring it along. The demo is a working session, not a pitch.
Book a 30-Minute Demo →No. The physician steers. Routes respond to the choices they make inside the experience, not to a profile built about them. They stay in control of where to go and how deep to read.
No. Every route recombines modules from the approved core, so the review you already did covers each journey. A new claim would need new content, and we never create one.
As many as the science supports. Most teams start with three ways in: the mechanism, the outcomes, and patient fit, then let depth do the rest of the personalizing.
They share one approved core. Expert clips sit one tap from the data inside a route, and interactive moments can wait at any station. Alone or together, nothing gets rebuilt.
Your approved publication and your review process. We map the routes, build the modules, and structure everything for your Veeva workflow.
