Pick one regulated industry and serve it so deeply that domain-specific compliance and workflow become a moat horizontal giants cannot justify building, locking customers in through indispensability.
Veeva
Veeva Systems is cloud software built exclusively for one industry: life sciences, meaning pharma, biotech, and medical devices, and nothing else. Founded in 2007 by ex-Salesforce technology chief Peter Gassner, it bet that a single vertical, served deeply enough, could become a multi-billion-dollar franchise, and that narrowness itself would become the deepest moat. Each story below is the same discipline viewed from a different angle: pick one regulated seam, own it completely, and let the domain lock customers in.
Beachhead: pharma CRM, the one seam horizontal giants could not fit
The problem. In 2007, horizontal enterprise software (Salesforce, Oracle, SAP) treated every industry the same, then charged consultants for years of customization. Pharma sales had needs generic CRM handled badly: FDA validation, sample-tracking compliance, and country-specific physician-targeting rules that a general-purpose tool simply did not model. The industry was large, heavily regulated, and painful enough to pay premium prices, yet unserved.
The approach. Rather than build infrastructure, Gassner launched Veeva CRM on Salesforce's Force.com platform, the very platform he had helped build at Salesforce. This got a pharma-native CRM to market fast, one that understood the regulatory and field-force reality out of the box, and the founders deliberately chose pharma precisely because it was the most regulated vertical, where compliance created natural barriers.
How it solved it. The narrow wedge worked: from a June 1, 2007 start, Veeva reached profitability early and IPO'd in 2013, going on to serve virtually every major drug maker. By owning the one seam where regulation deterred generalists, Veeva turned an "underserved segment" bet into the foundation of the entire company.
Moats: the discipline of refusing every other industry
The problem. A vertical software company faces constant temptation to go horizontal and chase a bigger market. But breadth would have put Veeva back into direct competition with Salesforce, Oracle, and SAP, where it had no structural advantage, and diluted the very domain depth that made it valuable.
The approach. Veeva refused. It never expanded beyond life sciences, and instead poured its energy into accumulating regulatory features, industry references, and trust in handling sensitive regulated data that no generalist would ever match. Staying narrow was the strategy, not a limitation.
How it solved it. The result is a moat built from domain depth rather than technology alone: Veeva serves nearly every large pharma company and, by FY2025 (year ended January 31, 2025), generated $2.75 billion in total revenue, up 16% year over year, with $691 million in operating income (up 61%) and $714 million in net income, without ever selling outside a single industry. The narrowness is the moat.
Land and Expand: from the sales rep's laptop to the clinical trial
The problem. CRM alone, even owned completely, is a bounded market. The larger and stickier budgets inside a pharma company sit in R&D, clinical, regulatory, and quality, not in the commercial sales organization where Veeva first landed.
The approach. Veeva entered each account via the commercial side, then widened it. It built Vault, its own content-and-data platform (independent of Salesforce) for clinical, regulatory, and quality workflows, and expanded into data and patient analytics, acquiring Crossix Solutions for $430 million (announced September 26, 2019, closed November 1, 2019) to add privacy-safe patient data spanning more than 300 million U.S. patients.
How it solved it. Expansion into R&D and data moved Veeva from a commercial-CRM vendor into the operational backbone of a drug company's most sensitive work. FY2025 subscription revenue of $2.28 billion (up 20%) reflects accounts that started with CRM and now run clinical trials, submissions, and quality on Veeva too, each expansion larger and stickier than the last.
Recurring Revenue: subscription cloud sold to one vertical
The problem. When Veeva launched, pharma IT was dominated by heavily customized on-premise systems and multi-year consulting projects, slow to deploy and expensive to maintain. The company needed a delivery model that produced recurring revenue and let a small vendor serve an entire regulated industry.
The approach. Veeva built multi-tenant cloud applications sold by subscription from day one, beginning with Veeva CRM and extending across the Vault product line. Recurring subscription contracts, not license-plus-services deals, became the core of the business.
How it solved it. The model compounds: in FY2025, subscription services delivered $2,284.7 million of the $2,746.6 million total, meaning recurring revenue is roughly 83% of the business, and it grew 20% year over year while net income rose 36% to $714 million. Profitability at that scale and age is rare, and it is a direct product of the subscription SaaS engine.
Switching Costs: when ripping out the software risks an FDA timeline
The problem. Software lock-in built purely on data migration cost is real but escapable. Veeva needed switching costs strong enough that even a customer unhappy about, say, its platform dependencies would not leave.
The approach. By moving customers' clinical trials, regulatory submissions, and quality records onto Vault, Veeva embedded itself in the workflows where a system failure or migration error can delay a drug's approval. The switching cost is layered on top of domain trust: it is not just data, it is regulated, timeline-critical data. Veeva even leveraged this position to announce it would migrate its own core CRM off Salesforce onto Vault CRM.
How it solved it. The strength of that lock-in showed in Veeva's confidence to walk away from its founding platform: in December 2022 it announced it would not renew the Salesforce partnership when it expires in September 2025, and it is migrating customers to Vault CRM through roughly 2029. A vendor only forces its entire base through a multi-year replatforming when it knows customers cannot practically leave, because their FDA-facing operations now depend on it.