Every CRM vendor’s roadmap slide now has a row of agent icons. Count them and you would think the platform with the most named agents wins the next five years of enterprise CRM. Amgen’s decision this week to deploy Veeva Vault CRM globally argues the opposite: the CRM that wins is the one whose data model was built for the workflow the agent has to operate in, and the agent count is close to irrelevant.
The strongest case against this argument
The obvious counter is distribution and ecosystem gravity. A horizontal CRM with a massive installed base, thousands of AppExchange-style partner integrations and a workforce already trained on its interface has real advantages a narrower, vertical platform cannot match on scale alone. Network effects compound: more customers mean more integrations, more integrations mean stickier deployments, and a partner ecosystem can, in theory, bolt on whatever industry-specific logic a vertical vendor builds natively. If agent capability is mostly a function of the underlying model plus enough integrations to feed it data, the horizontal platform with the bigger partner network should eventually close any gap a vertical CRM opens up.
Why that argument does not hold for agentic workflows specifically
An AI agent acting inside a CRM is not the same product as a human rep clicking through a UI, and the gap between “we have a partner integration for that” and “our data model was designed for that” matters more once an agent, not a person, is the one interpreting the record. Veeva built its new Agentic Call Report specifically to generate commercial evidence and surface treatment barriers from field interactions in life sciences, a feature that only makes sense inside a CRM that already encodes healthcare-provider engagement rules as first-class data, not as a custom field a partner integration bolted on afterward. Matt Farrell, Veeva’s president of commercial strategy, said the platform will provide “the agentic commercial foundation to help Amgen deliver innovative medicines for some of the world’s toughest diseases to millions of patients.” Amgen’s own chief information officer, Scott Skellenger, framed the decision the same way: “Veeva’s deep understanding of life sciences, its continued focus on innovation, and our long-standing collaboration will help support Amgen in achieving these important goals.” Neither executive mentioned how many agents the platform ships with.
Advertisement
This is the same distinction that showed up when Salesforce chose to keep Fin outside core Agentforce rather than fold an acquired agent straight into its main data model. An integration can feed a general-purpose agent more data, but it cannot retroactively give that agent the same confidence about what the data means. A partner-built field mapping is an approximation of a vertical rule set, and an agent making an autonomous recommendation off an approximation is exactly the failure mode RevOps and compliance teams should be most worried about as agent autonomy expands. Amgen has run this vendor relationship for more than a decade and is expanding it globally now, at the moment agentic commercial features are the actual product, not adding a second vendor to fill the gap. That is a vote for depth over breadth from a customer with every incentive to pick the safer, broader option if it were genuinely comparable.
What it means for the CRM buyer
A RevOps leader sitting through a vendor demo full of named agents should ask a narrower question than “how many agents does this do.” Ask whether the data model those agents operate on was purpose-built for your industry’s compliance and workflow rules, or whether the agent is reasoning over a generic object schema with your industry’s specifics layered on as custom fields and partner add-ons, the same question worth asking about any vendor now promising trust and governance alongside a new agent rollout. The first version gets more reliable as the agent gets more autonomous. The second gets riskier, because every additional agent action is one more decision made on an approximation of the rules that actually govern the work.
The honest caveat
This argument favors vertical CRM vendors in regulated, high-complexity industries specifically. Most B2B sales teams are not selling regulated pharmaceuticals to healthcare providers, and for a large share of the market, a horizontal platform’s integration breadth genuinely does outweigh vertical depth most buyers will never need. The lesson from Amgen is not that every company should chase a niche CRM. It is that the marketing question CRM vendors want asked, how many agents, is the wrong one for any buyer whose workflow has real regulatory or domain complexity, and that buyer should be asking about the data model underneath the agent instead.
Source: PR Newswire
