← back to ranking

VEEV · Veeva Systems Inc.

Medical - Healthcare Information Services · mkt cap $29.9B · calls: Q1 FY2027 vs Q4 FY2026
52.0 conviction · conf-adj 52

conf 7/10 🚀 reported partial

enthusiasm:27.0 · trend:8 · quantifies:5 · impact:0 · under_radar:5 · credibility:0 · business_impact:4 · disruption:0 · commitment:0 · confirmation:3

Enthusiasm latest 9 / prev 7 (rising)

Veeva's AI thesis has materially escalated from Q4 FY2026 to Q1 FY2027: management moved from 'right to win, early days' framing to announcing Falcon — a named agentic-labor platform targeting clinical document processing and safety case triage, with per-document/per-case pricing, dedicated CEO reporting, and an early-adopter launch within months. The thesis is credible in structure (deep domain data + applications + consulting = structural advantage for last-mile agents; 10+ customers live on commercial content AI; Claude Code delivering measurable internal productivity) but remains financially immaterial for FY2027, with all meaningful AI revenue upside deferred to future years. The key risk to the thesis is execution: Falcon is Veeva's first venture into digital labor, the product is unproven at scale, and management is transparent that delivering reliable agentic performance in a regulated industry is 'very hard' work.

GROUNDED NEXT-FY IMPACT vs CONSENSUS

Grounded on actual base — revenue $3.2B · net income $0.9B · net margin 28.4% · diluted EPS 5.44

These are next-fiscal-year annual uplift estimates, not next-quarter numbers.

Aggregate next-FY est. rev uplift: 0.31% · next-FY EPS uplift: 0.21% · vs analysts: inline · priced in: medium (model's call-read: high; verdict above is the hard-data one used for ranking) · confidence: 7/10

ClaimFigureArithmeticNext-FY Rev %Next-FY EPS %
Ostro AI acquisition adds ~$10M commercial subs (Q2–Q4 FY2027)
revenue
~$10M across remaining 3 quarters of FY2027100×10,000,000/3,195,311,000 = 0.31% rev; incremental NI = 10,000,000×0.2844 = $2.84M; EPS vs adj NI 100×2,844,499/1,326,923,908 = 0.21% (consensus non-GAAP base; GAAP NI would be 0.31%). Ostro is the ONLY anchored AI $ figure (~2/3 of the $15M commercial-subs guidance increase), so already inside guidance/consensus.0.310.21
FY2027 AI revenue ex-Ostro — 'fairly immaterial'
revenue
immaterial / not materialManagement explicit FY2027 guide: organic AI ≈ $0 incremental vs $3,195.3M base → 0% rev; @28.44% incr margin → $0 / $1,326.9M adj NI = 0% EPS. Explicit guidance caps near-term non-Ostro AI topline at ~0.00
AI gross-margin impact 'not material' FY2027
cost · soft
not materialMgmt: no material FY2027 margin impact from AI; token cost offset by productivity. No quantified bps or $ base disclosed → cannot anchor a $ saving; bottom-line effect ≈ 0%.
Claude Code R&D productivity — 'hire a little less, accomplish more'
productivity · soft
qualitativeNo FTE count, no $ opex base, no savings figure. Token cost said to be 'easily outweighed' but unquantified → cannot anchor an after-tax saving.
Falcon clinical-doc agents — ~100M docs/yr TAM, charged per document
other · soft
~100M documents/year (TAM context)TAM volume only; no $/document price, launch ~5 months out, full adoption framed as 3-year goal → ~$0 FY2027 revenue, cannot anchor next-FY $.
MLR process '70%+' automatable with agents 'over time'
cost · soft
70%+ automatable% with no MLR-spend base (customer's cost, not Veeva's) and no timeframe → unanchored; customer value prop, not Veeva P&L.
Hypothetical customer '+$40M revenue' from faster drug approvals
other · soft
$40M (customer, hypothetical)Customer/sponsor revenue, not Veeva billings; no Veeva take-rate or date → not added to VEEV revenue. Reference only: 100×40,000,000/3,195,311,000 = 1.25% if it were VEEV (it is not).
Patient-to-medicine inefficiency 90%→50% via AI (10–20 yr)
other · soft
90%→~50%; 10–20 year horizonIndustry-level, 'Veeva will play a part' — no Veeva-attributable share or $ base, outside FY2027 sizing window. Unanchorable.
Commercial content quick-check agents — '>10 customers live'
engagement · soft
>10 customers liveCustomer count, no ASP/ARR or contract value disclosed → early-stage engagement proof point; cannot size revenue.

Assumptions: Next FY = FY2027 (Feb 2026–Jan 2027). Earnings basis = adjusted/non-GAAP to match consensus: adj NI $1,326.9M (FY2026 adj EPS $7.94×166,995,000 sh), adj EPS $7.94; GAAP NI $908.9M / EPS $5.44 used only as cross-check (bases close, not distorted). Incremental net margin on Ostro revenue = 28.44% (current corporate net margin; no higher software margin assumed given integration/amortization drag and mgmt's 'no material margin impact'). Tax embedded in net-margin flow-through. Phasing: only ~$10M Ostro lands in FY2027 (Q2–Q4); Falcon/MLR/regulatory value is out-years (3yr+ adoption, launch ~5 months out) → ~$0 FY2027. Veeva is a pure AI ADOPTER — no AI-compute/infrastructure supplier revenue.

Top line: Only one AI dollar figure is anchorable for FY2027: Ostro's ~$10M (Q2–Q4) = 0.31% of $3,195.3M revenue, and only ~2.3% of the consensus FY2026→FY2027 revenue step-up (+13.6%). Management explicitly states all other AI revenue is 'fairly immaterial' this year. Falcon (per-document/case clinical agents), the 100M-doc TAM, MLR 70% automation, the $40M customer proof-point and the 90%→50% efficiency story are real strategic optionality but unanchored and out-year. Net: ~0.3% AI-attributable revenue uplift next fiscal year.

Bottom line: Negligible near-term EPS effect: $10M Ostro @28.44% incremental net margin ≈ $2.84M = 0.21% of the ~$1,326.9M adjusted earnings base (0.31% vs GAAP). Management guides no material FY2027 margin impact from AI; Claude Code R&D productivity ('hire a little less, accomplish more') is real but unquantified (token cost said to be easily outweighed, no FTE/$ disclosed) so it cannot be sized. MLR automation and faster-approval levers are customer-side value props, not Veeva P&L items for FY2027.

Consensus already models FY2027 revenue $3,599.3M (+13.6% YoY) and adj EPS $8.86 (+11.6%), driven by core Veeva subscription growth, NOT AI. The $10M Ostro contribution (0.31% of revenue, <3% of the consensus dollar revenue bridge) is explicitly part of the $15M commercial-subs guidance increase, so it sits inside consensus. The anchored AI uplift (~0.3% rev / ~0.2% EPS) is fully absorbed within that trajectory, and management itself flags AI as immaterial outside Ostro and 'more in the out years.' No near-term consensus gap; genuine upside (Falcon, MLR automation) is out-year optionality not yet sized.

MODEL CONSENSUS (impact)

partial

Near-identical answers; both adopter-only, Ostro ~$10M = 0.31% rev / 0.21% EPS, inline, priced-in high.

Conflicts reconciled
FieldOpus 4.8GPT-5.5
Rev uplift %0.31
EPS uplift %0.21
Priced inhigh
vs analystsinline
Confidence7
Top lineOnly one AI dollar figure is anchorable for FY2027: Ostro's ~$10M (Q2–Q4), = 0.31% of $3,195.3M revenue. Management explicitly states all other AI revenue is 'fairly immaterial' this year. Falcon (clinical doc/safety-case agents, charged per document/case), the 100M-doc TAM, MLR 70% automation, the $40M customer proof-point, and the 90%→50% efficiency story are all real strategic optionality but unanchored and out-year (3-year adoption goal; launch ~5 months out). Net: ~0.3% AI-attributable revenue uplift in the next fiscal year.
Bottom lineNegligible near-term EPS effect: $10M Ostro @28.4% incremental net margin ≈ $2.84M, = 0.21% of the ~$1,327M adjusted earnings base. Management guides 'no material margin impact from AI this year,' and Claude Code R&D productivity ('hire a little less, accomplish more') is real but unquantified — token cost said to be easily outweighed, yet no FTE or $ savings disclosed, so it cannot be sized. The MLR-automation and faster-approval levers are customer-side value props, not Veeva P&L items for FY2027.
ReasoningConsensus already models FY2027 revenue $3,599.3M (+12.6% YoY) and adj EPS $8.86 (+11.6%) — driven by core Veeva subscription growth, NOT AI. The $10M Ostro contribution (0.31% of revenue) is explicitly part of the $15M commercial-subs guidance increase, so it sits inside consensus. Our anchored AI uplift (~0.3% rev / ~0.2% EPS) is fully absorbed within that +12.6%/+11.6% trajectory, and management itself flags AI as 'immaterial outside Ostro' and 'more in the out years.' No near-term consensus gap; the genuine upside (Falcon, MLR automation, regulatory AI) is real but long-dated and unquantified, hence not the interesting near-term mispricing case.

Rows highlighted where the two models disagreed.

QUANTIFICATIONS
Commercial content AI agents — live customer count: more than 10 customers live (Q1 FY2027 (as of June 2026), topline)
“the one where we were first out to marketplace was in the commercial content area, and we have more than 10 customers live, and it's going really well in our quick check agents”
Clinical document volume addressable by Falcon: ~100 million documents per year (Ongoing annual volume (context for Falcon TAM), topline)
“let's just say there's 100 million documents collected from clinical research sites around the world every year having to do with clinical trials, they have to be checked for quality and they have to be sorted into the right places. That's work that agents can do”
Medical-legal-regulatory (MLR) process automation potential: 70% or more (Forward — 'over time', bottomline)
“there's a medical legal regulatory process that is burdensome and expensive and occupies many parts of people's time in Life Sciences. I think that can largely be automated, 70% or more with the right agents over time.”
AI revenue contribution to FY2027 guidance (ex-Ostro): Fairly immaterial / not material (FY2027 full year, topline)
“our overall expectation had been for AI to be fairly immaterial outside of Ostro. And we're really focused on getting AI live in all of our customer areas, getting the product excellence, getting to customer success.”
AI gross margin impact in FY2027: Not material (FY2027 full year, bottomline)
“I don't expect there to be a material impact on margins driven by AI this year.”
Internal R&D productivity from Claude Code — net headcount effect: Hire a little less, accomplish more (qualitative) (Current / ongoing, bottomline)
“that means we'll hire a little less than we would have and accomplish more than we would have and go a little bit faster. But for us, it's more about productivity and the combination of hiring a little less, accomplishing a little more, we think easily outweighs the token cost”
Hypothetical customer revenue uplift from Veeva regulatory AI: $40 million incremental revenue (Forward — hypothetical future proof point, no specific date, topline)
“when we have companies thinking -- a big company thinking, 'I increased my revenue by $40 million because I lowered the time of drug approvals because the Veeva regulatory solution allowed me to get back faster to the health authorities around the world,' that's when things really start coming”
Life sciences patient-to-medicine inefficiency addressable by AI (including AI doctors/LLMs): 90% of value currently lost; could fall to ~50% (Forward — 10–20 year horizon, topline)
“The biggest bottleneck by far is... that 90% inefficiency goes down to 50%, and that will be a tremendous boom... Veeva will definitely play a part in that”
Ostro acquisition contribution to FY2027 commercial subscription revenue: ~$10 million across remaining 3 quarters of FY2027 (FY2027 (Q2–Q4), topline)
“we acquired Ostro late in Q1. We expect it to contribute about $10 million in the remaining 3 quarters of the year. So it's about 2/3 of the $15 million increase in commercial subs overall for the year.”
PAST (realized)
CURRENT (now)
FORWARD (guidance)
TRACK RECORD — PROMISE vs DELIVERY

/100 (no quantified promises)   no-quantified-promises  6 calls reviewed

Across six earnings calls Veeva discussed AI strategy, agents, Vault AI, and Falcon extensively but did not state numeric AI targets bound to explicit deadlines (no AI revenue, adoption, productivity, or agent-ship milestones with both a number and a timeframe). Credibility on AI promises therefore cannot be scored from this transcript set; management instead emphasized long-cycle value, early adopters, and no material AI revenue in FY26–FY27.

PRICED-IN (REFINED)
MEDIUM

Est. revisions flat  ·  Fwd P/E 22.5  ·  EV/Sales 8.7x

AI claim maps to Subscription Services Veeva Commercial Cloud, Subscription Services Veeva Research And Development

Revision momentum is mixed-to-flat: buy/hold counts are stable with only a modest shift from holds to buys, and last-month/quarter price targets are unchanged at $228.5 but well below the $281 last-year average, so analysts are not actively raising the AI thesis. Forward valuation is moderately rich at 22.5x next-FY EPS and 8.7x EV/Sales on ~12% revenue/EPS growth (PEG ~2.8), which embeds quality SaaS growth but not a full AI re-rating. AI-driven upsell, automation, and attach would most plausibly flow into subscription revenue in Commercial Cloud and R&D Cloud, not professional services. Medium priced-in: premium multiples already reflect durable growth, but flat/falling target revisions mean incremental AI upside is not fully baked into estimates.
COVERAGE — ENTHUSIASM TRAJECTORY + CATALYSTS
4Q4 FY20256Q1 FY20266Q2 FY20267Q3 FY20267Q4 FY20269Q1 FY2027

AI enthusiasm across 6 calls — trend ↗ rising

From brief AI-strategy wins to Falcon agentic labor with named clinical and safety workloads.

RECENT AI CATALYSTS & NEWS
BUSINESS IMPACT - QUALITATIVE MATERIALITY

5/10 qualitative impact   moderate  medium-term · mixed evidence

Where AI matters: R&D Falcon agentic labor + commercial Vault AI agents

Veeva has real regulated deployments (>10 commercial-content customers, CRM/safety agents) and a credible Falcon per-document/case monetization path, but management explicitly guides FY2027 AI ex-Ostro as immaterial (~0% organic uplift) with Falcon unproven at scale.

Caveats: Falcon execution and regulated reliability at scale are unproven with revenue still guided immaterial near term; Usage-based agent pricing may grow slower than or partially offset traditional per-seat expansion; Customers or partners could access Vault headlessly via generic models, bypassing Veeva standard agents; Prior agent ship timelines slipped versus stated milestones (mixed credibility)

AI DISRUPTION / CANNIBALIZATION RISK  tailwind · 3/10

Core revenue is validated vertical SaaS with high switching costs, not billable-hours arbitrage; Veeva is positioning agents as headless application users and usage-priced labor to capture work automation rather than cede it to horizontal LLMs. Seat-expansion and professional-services mix could soften over time but do not plausibly commoditize the regulated platform.

OPTIONS / MARKET STRUCTURE

option liquidity: good

ATM IV
TYPICAL BID-ASK
OPEN INTEREST

proxy inputs — dollar-ADV $535M · beta 0.924 · px $178.92

source: proxy (no options chain on FMP)
FMP /stable/ exposes no options-chain endpoint on this key, so ATM IV, bid-ask spread and open interest are unavailable. Liquidity below is a PROXY from dollar-ADV, beta and price level (a stand-in for option depth), not measured option-market data.

CONFIRMATION — INSIDERS · 13F · LANGUAGE
Mixed — insiders selling, institutions adding, management language 5/10 measured.
INSIDERS selling 4 open-market sell(s) vs 0 buy(s) — net distribution
INSTITUTIONS (13F) adding as of 2026-03-31: 129 new / 216 closed positions; 524 increased / 368 reduced; institutional ownership -1.56pp; -92 net 13F holders
MGMT LANGUAGE 5/10 measured Strong Falcon vision and some firm we-will language, but mixed with may/leaning-in and no AI revenue or rollout metrics.
commit “We will make agents to do that and do those very standard things.”
commit “Falcon specifically is at the agent layer and that's agentic labor.”
commit “It's going to be great revenue for Veeva, but it's going to deliver value far above and beyond that.”
VERBATIM AI QUOTES
“it's an exciting time for Veeva and for life sciences overall, as we execute against a clear vision for industry AI”
— Peter Gassner, Q1 FY2027
“Falcon specifically is at the agent layer and that's agentic labor. So fully replacing parts -- jobs that people used to do. People who used to do these jobs using our applications, now will deliver the agentic labor to do that. So it's a big new area for Veeva. It's something we haven't done before, and that's why it's disruptive.”
— Peter Gassner, Q1 FY2027
“Falcon is the same thing. It's the same magnitude of disruptive innovation. It's not giving tooling to people to design agents. This is to designing and operating the standard agents for the industry rather than the industry having to hire humans for those specific jobs.”
— Peter Gassner, Q1 FY2027
“let's just say there's 100 million documents collected from clinical research sites around the world every year having to do with clinical trials, they have to be checked for quality and they have to be sorted into the right places. That's work that agents can do”
— Peter Gassner, Q1 FY2027
“we may make agents that are better safety case processors and more reliable than humans. That's a heck of a lot of work, but we have a structural advantage to do that because we're deep in life sciences, we have a consulting in life sciences, and we have the applications that those agents can use”
— Peter Gassner, Q1 FY2027
“Falcon will be charged by the document, most likely. We haven't fully decided that. You can imagine that safety will be most likely charged by the case.”
— Peter Gassner, Q1 FY2027
“Definitely all accretive because this is not a market we address today. We don't play in that market today. This is not type of labor or work that we supply.”
— Peter Gassner, Q1 FY2027
“the one where we were first out to marketplace was in the commercial content area, and we have more than 10 customers live, and it's going really well in our quick check agents”
— Peter Gassner, Q1 FY2027
“At Commercial Summit, we had a number of customers live on some of our agents in CRM, actually generating commercial evidence in these agentic call reports.”
— Peter Gassner, Q1 FY2027
“there's a medical legal regulatory process that is burdensome and expensive and occupies many parts of people's time in Life Sciences. I think that can largely be automated, 70% or more with the right agents over time.”
— Peter Gassner, Q1 FY2027
“there's a small part of it that goes a little faster than it used to, and that's the actual coding of the platform in the deterministic parts where we can lean in and leverage things like Claude Code to do that faster than we did before”
— Peter Gassner, Q1 FY2027
“in product engineering, we use Claude Code, and it's come a long way. So we're seeing great efficiency from that tool. And I think in general, that means we'll hire a little less than we would have and accomplish more than we would have and go a little bit faster. But for us, it's more about productivity and the combination of hiring a little less, accomplishing a little more, we think easily outweighs the token cost”
— Brian Van Wagener, Q1 FY2027
“our overall expectation had been for AI to be fairly immaterial outside of Ostro. And we're really focused on getting AI live in all of our customer areas, getting the product excellence, getting to customer success.”
— Brian Van Wagener, Q1 FY2027
“this is our first step into digital labor. You can't -- you have to operate that effectively... Falcon is like that.”
— Peter Gassner, Q1 FY2027
“those will be some of the first consumers of things like Falcon and our other AI solutions... If we have our agent working on for one Basics customers, it will work for them all.”
— Peter Gassner, Q1 FY2027
“our customers really want us to win in AI applications. And so we have a right to win, and we just have to execute.”
— Peter Gassner, Q4 FY2026
“AI is not replacing software. That's just not happening... AI is going to enable a lot of new kinds of long-tail software... in our case, industry-specific AI applications.”
— Peter Gassner, Q4 FY2026
“The one that's farthest along... is the commercial content area. And that -- the ROI is just very clear. It's faster content, lower cost to create that content... Faster content just means better launches. That means that drives the top line before the patent on that product expires.”
— Peter Gassner, Q4 FY2026
“in safety, it's just very clear. It's about replacing that type of labor with automation, with AI software.”
— Peter Gassner, Q4 FY2026
“AI can definitely, definitely, definitely bridge that gap... maybe that 90% inefficiency goes down to 50%, and that will be a tremendous boom.”
— Peter Gassner, Q4 FY2026
“Veeva could not build the AI applications that we're going to build without these foundational LLMs. So I don't know if I'll use this word correctly. I think the word is symbiotic.”
— Peter Gassner, Q4 FY2026
“when we have companies thinking -- a big company thinking, 'I increased my revenue by $40 million because I lowered the time of drug approvals because the Veeva regulatory solution allowed me to get back faster to the health authorities around the world,' that's when things really start coming”
— Peter Gassner, Q4 FY2026
“Last year was about putting the foundation in and the platform and the first agents. This year is about rolling out agents in all of our product areas, getting customers live, refining the product, really creating a lot of value.”
— Brian Van Wagener, Q4 FY2026
“we're really expecting to be using a token-based pricing model, and so that gives us a little bit of predictability around the margin profile... It's not a material impact on FY '27”
— Brian Van Wagener, Q4 FY2026
“system migration is a great use case for AI automation to cut down the time and reduce the cost of system migration, and we'll do our part in that, too, but it's early days.”
— Peter Gassner, Q4 FY2026
ANALYST QUESTIONS ON AI
Q (Q1 FY2027, Joe Vruwink (Baird)): I was hoping to go into a bit more detail on Veeva Falcon. This certainly seems more complex and consequential in scope. I think you call it disruptive in the remarks. Can you maybe expand on what this product is targeting and how you envision customers operating in drug development with maybe now this interplay between Vault, the Vault standard agents and Falcon?
A: Gassner: Falcon is at the agent layer — agentic labor fully replacing parts of jobs people used to do using Veeva applications. Agents become users of applications (headless), while Vault AI assists humans still using applications interactively. This is new territory for Veeva enabled by probabilistic AI that did not exist before.
Q (Q1 FY2027, Brian Peterson (Raymond James)): As we think about pharma appetite for AI applications more broadly, I'm curious what areas you think they lean into first and how we should think about the transition from traditional SaaS applications to AI in pharma.
A: Gassner: Pharma is not thinking about transitioning from SaaS to AI applications but rather becoming 'agentic biopharma' using the MAAP architecture (Models, Agents, Applications). Agents will do high-volume repetitive work — processing 100M+ clinical documents, triaging safety cases — while humans do higher-value work. Veeva has a structural advantage because it has both the applications and the agents, analogous to how Anthropic has both Claude and Claude Code.
Q (Q1 FY2027, Rishi Jaluria (RBC)): How do you think about the opportunity not just to build your own custom Falcon agents to solve industry-specific problems, but also give your customers and your partners the ability to build heavily customized, heavily tailored solutions for the unique problems that they may have and kind of open up a little bit more of a platform story.
A: Gassner: Falcon is Veeva building and operating standard agents to solve the problem for the industry — not a platform for customers to build custom agents. Customers can use Vault AI for in-application custom agents or external agent-building tools that access Veeva headlessly. Falcon is like the Development Cloud vision of 2012 — standardization and simplification, not tooling.
Q (Q1 FY2027, David Windley (Jefferies)): How are you pricing Falcon? And how are you deciding which labor roles to address or to attack with Falcon agents?
A: Gassner: First targets are highest-volume, simplest tasks — document intake/control from clinical sites (inspecting quality, categorizing, filing in TMF), safety case triage/categorization, and regulatory health authority correspondence. Pricing likely per document for clinical, per case for safety. Not priced by the hour but by the unit of output.
Q (Q1 FY2027, Andrew DeGasperi (BNP Paribas)): Is there anything that you would consider timing-wise from an economics perspective. So let's say, these roles were to move in another direction? Do you think it could potentially cannibalize some of the revenue that you get from those customers? Or do you think it would be all accretive?
A: Gassner: Definitely all accretive — Veeva does not currently address this labor market at all. Agents also require systems of record to operate, so Falcon does not cannibalize Vault subscriptions.
Q (Q1 FY2027, Hannah Rudoff (Piper Sandler)): What exactly is going into the next 5-plus months ahead of your early adopter launch? And what has been done today and what still needs to be done?
A: Gassner: Building out the platform layer, assembling the team (Falcon reports directly to him), signing early customer agreements and using their data/documents to quality-control and train agents, getting first customers live. One area that goes faster than before is the deterministic coding using Claude Code. Everything else in the cycle is the same as launching any new product.
Q (Q1 FY2027, Craig Hettenbach (Morgan Stanley)): Given you're furthest along on AI and kind of the Vault CRM agents that launched back in December. Curious kind of what the initial uptake is there... And then for Brian, just a question on just kind of cost of compute and how you're thinking about the puts and takes on gross margin as AI ramps?
A: Gassner: Commercial content agents farthest along with 10+ customers live on quick-check agents; CRM agentic call reports generating commercial evidence at Commercial Summit. This year is about scaling early adopters. Van Wagener: No material margin impact from AI this year; token-based pricing for Vault AI is understood and factored into guidance; compute costs outweighed by productivity gains from Claude Code.
Q (Q1 FY2027, Adam Hotchkiss (Goldman Sachs)): For Brian, just on AI driving efficiencies within your operating expense base. Maybe talk a little bit more about the progress in the R&D or again where else in the cost structure we might see some of that start to show up?
A: Van Wagener: Most significant use is in product engineering (largest spend area) via Claude Code, which has 'come a long way.' Result is hiring a little less, accomplishing more, going faster. Productivity gain easily outweighs token cost — all factored into guidance.
Q (Q1 FY2027, David Larsen (BTIG)): It sounds like you're expanding pretty deep and pretty fast into more R&D efforts, like are you taking some of the long sort of expensive labor efforts that the CROs would do and enabling your biopharma clients to do that in-house with your AI? And then also on the commercial side, like, what is your vision for what the AI could actually do?
A: Gassner: Target is not CRO work but specialized lower-volume labor done by pharma or specialized outsourcers — Falcon does it cheaper/faster/better, potentially freeing pharma to run more trials (net positive for CROs' higher-margin work). In commercial, agents will augment field reps (drafting emails, reminders) but not replace them. MLR process (medical-legal-regulatory review of content) can be 70%+ automated. Ostro enables 24/7 HCP engagement that was previously impossible.
Q (Q1 FY2027, Stan Berenshteyn (Wells Fargo)): Is there any non-Ostro AI-related revenue embedded within guidance?
A: Van Wagener: No — AI expected to be 'fairly immaterial' outside of Ostro in FY2027. Focus is product excellence and customer success, not revenue ramp this year. Vault AI token-based usage is factored into guidance but not material.
Q (Q4 FY2026, Joe Vruwink (Baird)): Is Veeva starting to see some programs funded maybe in the name of AI readiness... I would imagine for a top 20 to commit to Veeva in any of the R&D areas... it would seem you're going eyes wide open into really viewing Veeva as a future foundation for everything AI related.
A: Gassner: Not a broad theme. Main driver is still modernizing aging core systems and eliminating deferred maintenance risk. AI readiness (e.g., cleaning reference data for 'garbage in, garbage out' reasons) is a contributor in some pockets but not a major driver. The goal is automation, and AI is one path to it but not the only one.
Q (Q4 FY2026, Saket Kalia (Barclays)): What are customers saying about AI adoption right now within the life sciences industry? Maybe what role do they see the big LLM providers playing? And what role do they see Veeva playing?
A: Gassner: Customers face extreme pressure from bosses/peers to get efficient with AI. They bucket potential providers into: infrastructure/LLM providers, point solution vendors, internal custom dev, SIs, and core application vendors like Veeva. They want tightly integrated AI from Veeva because they trust Veeva delivers quality at scale — they've been burned by failed experiments from point solutions. 'Our customers really want us to win in AI applications.'
Q (Q4 FY2026, Alexei Gogolev (JPMorgan)): Veeva clearly has mission-critical software, strong network effect, proprietary data and domain expertise. How do your customers rank those key elements when they consider Veeva's right to win against those LLM infrastructure peers?
A: Gassner: Customers view it holistically — trust is #1. Earned over 15 years of delivering on commitments. They know Veeva knows their business and is a tech expert. LLM providers are 'the new AWS' — symbiotic infrastructure that enables Veeva, not a replacement for industry-specific applications.
Q (Q4 FY2026, Rishi Jaluria (RBC)): Anthropic launched Claude for Life Sciences and Veeva is an enabling and launch partner. How should we be thinking about the opportunity for Veeva to work with Anthropic, OpenAI... rather than obviously the current market view of it being more cannibalistic?
A: Gassner: Not cannibalistic at all. AI will not replace core systems of record (Veeva, SAP, Workday). LLMs are the engine — 'the new AWS' — that enables long-tail and industry-specific applications Veeva couldn't build before. Relationship is 'symbiotic.' AI helps Veeva build/improve core systems faster. The large patterns are clear even if early days are chaotic.
Q (Q4 FY2026, Matt Shea / Ryan MacDonald (Needham)): You've noted in the past how AI could be a game changer in safety... could you comment on why you're leaning into agent development and safety given how historically reluctant to change that segment of the market has been?
A: Gassner: Safety case intake/triage/narrative generation involves large volumes of human processing that is expensive and hard to staff — a clear automation target. Risk aversion is about migrating core safety databases (regulatory risk if down), not about AI itself. Customers are realizing Veeva is the only path to a modern safety system with AI on top integrated with the rest of their stack, and that building/maintaining it themselves is harder than expected.
Q (Q4 FY2026, Adam Hotchkiss (Goldman Sachs)): As AI speeds up clinical trial timelines and trial success rates, I'm curious, first, how this dynamic impacts how customers use Veeva's R&D products. And then second... how could this impact, if at all, customer spend on Veeva?
A: Gassner: AI can speed up trial start-up and close-down but not the core trial itself — human biology runs at the same speed. Patient recruitment is not primarily an AI problem. No major impact on view of core Veeva systems. Van Wagener: Too early to forecast financial impact; focused on product excellence and getting agents live across all product areas this year; material financial contribution is an 'out years' story.
Q (Q4 FY2026, DJ Hynes (Canaccord)): Based on the adoption trends you're seeing, kind of customer willingness to pay, how you're thinking about pricing, do you expect your agentic AI offerings to be immediately accretive to margins? Or will that take time?
A: Van Wagener: Token-based pricing model provides some margin predictability, but the structure may evolve. No material impact on FY2027 margins. Focus is product excellence and value creation first, then revenue/margin structure later.
Q (Q4 FY2026, Hannah Rudoff (Piper Sandler)): What is the mix of customer adoption you're seeing right now between prepackaged agents that you've built and custom agents that they're building using Veeva AI?
A: Gassner: Bulk is with Veeva-designed agents — they are more robust and involve detailed data curation, testing pipelines, and Java-coded logic requiring strong product management. Customers prefer Veeva's solution over building themselves for complex cases. Custom/lighter-use-case helper applications will start appearing in H2 FY2027.
Q (Q4 FY2026, Tyler Radke (Citi)): Given the success in migration tools, code completion tools, are you seeing any acceleration in implementation times driven by AI?
A: Gassner: Some yes, naturally from better products and more experienced services teams. Big push on tech-enabling services hasn't borne full fruit yet but expected in the next 1-2 years. AI is helping accelerate EDC system migration from competitor systems to Veeva. System migration in general is a great AI automation use case, but it is early days.