The Billion-Dollar Hour at Dreamforce

There is a familiar kind of disappointment at a trade show. You arrive with a shopping list and leave with a tote bag. In the fall of 2013, David Schmaier entered San Francisco's Moscone Center with a more consequential list. The former Siebel Systems executive had been studying industry-specific software companies. Veeva, built on Salesforce for life sciences, had shown how much value could hide inside one narrow vertical. Schmaier went to his first Dreamforce looking for the next one to acquire.

The expo floor held thousands of Salesforce partners selling almost everything: quoting, telephony, field service, compensation. What it did not hold, in Schmaier's telling, was a company packaging deep software for several industries. His search failed quickly. Within roughly an hour, the absence itself became the pitch.

“We should build another company like Veeva ... only larger.”David Schmaier, recalling his call to Craig Ramsey

The first failureThere was nothing to buy

Schmaier called Craig Ramsey, an old colleague and Veeva co-founder. Ramsey's reply was short: “Great idea. Let's do it.” They joined Mark Armenante, Young Sohn, and James Ramsey to sketch a company that would start not with one industry but four: communications, insurance, health, and government. Vlocity was formally founded in March 2014 and appeared at Dreamforce that year as a Titanium Sponsor.

What changed Schmaier's mind was not a clever demo. It was an empty category. He had spent years around Oracle, Siebel, and private-equity portfolios. He knew two things that looked contradictory: Salesforce had become a dependable horizontal platform, and large enterprises still ran on peculiar rules that horizontal software did not understand. An insurer has policies, coverages, claims, agents, and beneficiaries. A telecom operator has bundles, service addresses, devices, eligibility rules, and orders that mutate after activation. Calling both of these “customers and opportunities” is accurate in the same way that calling a submarine and a bicycle “transport” is accurate.

The productSell the plumbing, not the possibility

Ordinary CRM arrives as possibility. That is useful, until a buyer discovers that possibility requires eighteen months of consultants. Vlocity sold more of the finished room. Its applications supplied industry data models, prebuilt business processes, guided digital interactions, product catalogs, configure-price-quote tools, order capture, contract management, and commerce. They ran natively on Salesforce and used its sales, service, marketing, analytics, and community products underneath.

The middle layer was the business. Vlocity called its approach “100% additive”: use what Salesforce already built and avoid recreating it. The company made a contractual commitment to stay aligned with Salesforce releases. This reduced infrastructure work, gave buyers one familiar platform, and let Vlocity spend its product budget on the rules competitors left to implementation teams.

The users were not small teams buying a clever plug-in. They were enterprises whose customer operations carried regulatory, commercial, and operational baggage. Named customers included Verizon, Cigna, New York Life, TELUS, Principal Financial, ENGIE, Hutchison Drei Austria, and the City of New York. Accenture and Deloitte helped implement and extend the software. New York Life occupied three chairs at once: customer, strategic investor, and source of industry feedback.

The economicsWhat did it cost?

Vlocity was capital-intensive by software standards because “vertical” meant going deep several times. The founding team supplied a reported $10 million. Salesforce Ventures led a $42.8 million round in 2015, with Accenture participating. Sutter Hill Ventures led a $50 million round in 2016. A $60 million Series C in March 2019 brought total funding to about $163 million and valued Vlocity at $1 billion. Bessemer Venture Partners joined Salesforce Ventures, Sutter Hill, Accenture, and New York Life.

The customer cost was less tidy. Vlocity sold large enterprise contracts, typically alongside Salesforce licenses and partner implementation. Public pricing for today's descendants varies by cloud and module. The honest comparison was never license versus license. It was packaged software versus the “phantom costs” of creating and maintaining equivalent industry customizations.

The outcomeThe platform bought its missing layer

By 2019 Vlocity said it had 700 employees in 20 countries and 150 customers. It had made the Forbes Cloud 100 three years running. The acquisition now looks less like Salesforce buying an add-on and more like a platform recognizing where its customers kept demanding depth. Salesforce announced the deal in February 2020 and closed it on June 1. Schmaier became CEO of Industries.

That September, Salesforce introduced a 12-cloud Industries portfolio. Vlocity's specialties strengthened communications, media, energy and utilities, health, financial services, and public sector products. Its low-code tools surfaced as OmniStudio. In 2021, Salesforce said the broader Industries unit - which also included Salesforce.org assets - had reached an approximate $2 billion annualized revenue run rate. The Vlocity LinkedIn page now tells visitors that it is inactive and points them to Salesforce Industries. The brand retired; the architecture won.

The copyable partOwn the layer people keep rebuilding

The tempting lesson is “build vertical SaaS.” That is too broad to be useful. Vlocity's sharper move was to find a stable platform with distribution, then identify the expensive work that customers repeatedly commissioned around it. The company hired people who knew both the platform and the nouns of the industry. It converted those nouns into a data model, the recurring exceptions into workflows, and the consulting project into a product.

A builder can copy the sequence: choose a platform customers already trust; interview the operators who live with its gaps; map the repeated custom objects, approvals, and edge cases; package only the layer the platform is unlikely to prioritize; and recruit integrators who profit when the product succeeds. Stay compatible. Resist duplicating the host. Make domain expertise visible in the software, not merely in sales material.

The conditions matter. This approach is weak when workflows are simple, buyers are small, regulation is light, or the platform owner can reproduce the feature cheaply. It is dangerous when one host controls distribution, APIs, pricing, and technical rules. Vlocity accepted that concentration completely. Salesforce was platform, partner, investor, route to market, and eventually acquirer. That alignment produced a handsome ending, but it is not a law of nature.

The better test is almost comically practical: are customers paying consultants to build the same difficult thing again and again? If yes, there may be a product hiding in the invoices. Vlocity found product catalogs, policy flows, eligibility rules, and order orchestration there. Its most valuable discovery was not that industries are different. Everyone knows that. It was that the differences repeat.