Horizontal vs Vertical SaaS: What 5 Public Companies' 2026 Numbers Show
The horizontal vs vertical SaaS debate comes down to two numbers: Procore holds 17,850 customers at 106% net revenue retention, and HubSpot holds 288,706. Same business model family, opposite shapes. One caveat before we start: this is about market shape, not cloud scaling or corporate integration.
Key takeaways
- Horizontal SaaS sells one product to every industry; vertical SaaS owns one industry's workflow.
- Procore earns about $74,000 per customer; HubSpot about $10,800. Buyer concentration sets the economics, not the label.
- Vertical AI changes the business model, not the market shape. The model is a commodity; the workflow is the moat.
- Pick vertical only if you can name 20 target customers today; horizontal only if you can name a one-sentence wedge.
Horizontal vs vertical SaaS: the short answer, in one table
What is horizontal vs vertical SaaS? Horizontal SaaS sells one product across many industries: Salesforce and HubSpot serve any business with a sales team. Vertical SaaS sells into one industry's workflow: Veeva serves life sciences, Procore serves construction. The vertical vs horizontal SaaS meaning question resolves to one line: who signs the contract, a role buyer in a broad market or a whole company in a narrow one.
| Dimension | Horizontal SaaS | Vertical SaaS |
|---|---|---|
| Who you sell to | Any industry, one job role | One industry, often the entire business |
| Total addressable market | Millions of potential buyers | Thousands to tens of thousands |
| Typical ACV | Low-to-mid four figures | Five to six figures, set by buyer size |
| Customer acquisition cost | Cheap per raw lead | Cheap per qualified buyer |
| Retention ceiling / NRR | Land-and-expand across teams | High; Procore files 106% NRR, 95% GRR |
| Competitive pressure | Giants and foundation-model vendors | The incumbent system of record |
| Compliance load | Generic audits (SOC 2) | Industry-specific (HIPAA, FINRA, state rules) |
| Monetization beyond subscription | Seats and add-ons | Payments, lending, marketplace take rates |
| Time to first revenue | Fast, self-serve funnel | Slow; sales cycles and industry trust |
That is the vertical vs horizontal business model split in nine rows; horizontal SaaS vs vertical SaaS, typed in either order, resolves to this same table. For buyers weighing vertical vs horizontal B2B SaaS, the rows that decide most deals are ACV, retention, and compliance load, and the next section puts filed numbers on all three.
What the 2026 filings actually say about vertical and horizontal economics
Every article ranking for this keyword repeats the same folklore with no sources. So we went to the primary documents: five public companies, three vertical and two horizontal, with every company name below linked to its SEC filing or investor release and every row labelled with its fiscal period.
| Company | Model | Fiscal period | Revenue | Growth | Characterizing metric |
|---|---|---|---|---|---|
| Veeva Systems | Vertical, life sciences | FY2026, ended Jan 31, 2026 | $3,195.3M | +16% | Subscription revenue: $2,684.2M, +17% |
| Salesforce | Horizontal, CRM | FY2026, ended Jan 31, 2026 | $41.5B | +10% | GAAP operating margin: 20.1% |
| HubSpot | Horizontal, marketing and sales | Calendar 2025 | $3.13B | +19% | Customers: 288,706, +16% |
| Procore | Vertical, construction | Calendar 2025 | $1,323M | +15% | NRR 106%, GRR 95%, 17,850 customers |
| Toast | Vertical, restaurants | Calendar 2025 | $6.153B total | +26% (ARR) | ARR: $2.047B, about 164,000 locations |
Every company name in that table links to the primary filing for its row. Read the periods carefully: Veeva and Salesforce close their fiscal years on January 31, 2026, so "FY2026" means a year that ended in calendar 2026. Procore, HubSpot, and Toast report calendar 2025. Those periods are not interchangeable, and conflating them is the easiest way to misquote a filing.
Now the arithmetic nobody else in this search result has done. Our calculation from the filings linked above:
- HubSpot: $3,130,000,000 ÷ 288,706 customers ≈ $10,800 per customer per year
- Procore: $1,323,000,000 ÷ 17,850 organic customers ≈ $74,000 per customer per year
| Derived metric (our calculation) | HubSpot (horizontal) | Procore (vertical) |
|---|---|---|
| Revenue, latest fiscal year | $3.13B (CY2025) | $1,323M (CY2025) |
| Customer count | 288,706 | 17,850 |
| Revenue per customer | ≈ $10,800 | ≈ $74,000 |
| Customers, as a share of HubSpot's | 100% | about 6% |
HubSpot itself reports average subscription revenue per customer of $11,683 for Q4 2025, an annualized figure that sits close to our top-line math. We use our own number because it divides full-year revenue by a full-year customer count.
One caveat matters more than any ratio here. Toast's $6.153B of calendar 2025 revenue is not a software number. It includes payment processing and hardware, so lining it up against HubSpot's subscription revenue makes the vertical side look bigger than it is. Toast's own recurring measure is $2.047B of subscription-and-fintech ARR across roughly 164,000 restaurant locations. Comparing total revenue to software revenue is exactly the mistake the rest of this SERP invites, which is why we print both numbers.
Procore earns roughly seven times more per customer than HubSpot, from about six percent of the customers.
Here is what the growth column says, because it surprises people. Veeva grew 16%, Salesforce 10%, HubSpot 19%, Procore 15%, and Toast's ARR grew 26%. Two vertical, two horizontal, one fintech-heavy vertical, and no pattern at all. The label does not predict growth, and it does not predict revenue per customer either. Our read of the filings: the vertical or horizontal label tells you which failure mode you are signing up for. Buyer concentration tells you the economics.
Horizontal vs vertical SaaS companies: who's actually which
The most-searched version of this question is just "horizontal vs vertical SaaS companies." People want names. Here are the cleanest public examples, with why each one is shaped the way it is.
Vertical SaaS examples
- Veeva Systems: life sciences. Its $2,684.2M of FY2026 subscription revenue comes from pharma R&D, quality, and commercial workflows. A drug company signs, not a "user."
- Procore: construction. Its 17,850 customers run projects, RFIs, and drawings on it; the general contractor buys and the whole jobsite follows.
- Toast: restaurants. About 164,000 locations run POS, payroll, and payments on it. The software is the restaurant's operating system.
Horizontal SaaS examples
- Salesforce: CRM for any industry with a sales team. $41.5B in FY2026 revenue is scale only a cross-industry product reaches.
- HubSpot: marketing and sales software for any small business. 288,706 customers, none of whom had to belong to a trade.
- Zoom: video for every company with meetings. No industry boundary at all.
The vertical vs horizontal software distinction follows from who signs the contract and what workflow the software owns, not a marketing category; the vertical vs horizontal industry bet is what separates Veeva from Zoom. Collecting vertical vs horizontal SaaS examples for your own market? Ask who the buyer is before you ask what the product does. And if your product automates trade-specific work, be honest about how deep a workflow you're actually automating: shallow automation aimed at one trade is a horizontal product wearing a costume.
Which should you build? A decision framework that actually decides
Build vertical SaaS when you can name 20 target customers today, you have real access to that industry, and the workflow you want to own is painful enough that buyers already pay for software. Build horizontal SaaS when your wedge is one feature you can make best in the world, sold to a role that exists in every industry.
Most advice on this topic ends at "it depends." This does not. Score yourself against the thresholds below, then read the disqualifiers, which decide more deals than the matrix does.
| Question | Threshold that says "build vertical" | Threshold that says "build horizontal" |
|---|---|---|
| How many potential buyers exist? | Under ~50,000 reachable companies, concentrated in one trade | Millions; the buyer role exists in every industry |
| Do you have domain access? | You can get 20 named targets on a call this month | You have product insight, not industry relationships |
| Is the workflow regulated? | Yes, and regulation is a moat you can build behind | No; speed matters more than certification |
| Does an incumbent own the system of record? | No, or it is hated on-prem legacy | Yes, but you can wedge beside it with one feature |
| Does the buyer already pay for software? | Yes; you replace budget, you do not create it | Yes; self-serve, credit-card-sized budget |
Two notes on reading the table. First, "domain access" means you can get target customers on a call this month, not that you find the industry interesting. Interest is not access. Second, the system-of-record row is where most vertical ambitions die: if an incumbent already owns the data a trade runs on, you are not building a product, you are building a migration project.
Pick vertical only if you can name 20 specific target customers today. Pick horizontal only if you can name the single wedge feature you intend to be best in the world at. Fail either test and you don't have product-market fit, you have a category guess.
Our plain recommendation: if you have domain access to a concentrated buyer group that already pays for software, build vertical. The sales cycles run longer, but every signed customer compounds into retention and referral inside one industry. If your insight is a feature rather than an industry, build horizontal and accept that distribution, not product, will be the fight. If neither disqualifier passes, do not build either yet. Go sit with 20 buyers until one of them does.
Whichever side you land on, your future customers are running the build-versus-buy math on the other side of this decision, so expect the same objections you would raise yourself. Once the shape is settled, scope the first build properly; the shape choice is cheap to get wrong on paper and expensive to fix in code. If the retention terms above are new to you, our SaaS metrics guide defines NRR, GRR, and ARR. Here they are just inputs.
Does vertical AI change the answer?
No. Vertical SaaS is a market shape: software built for one industry. Vertical AI is a business-model claim: an AI product whose moat is industry data and workflow, not the model itself. The models are commodities available to every competitor; what differs is whether you own the process the model runs inside.
The standard reference, TechTarget's vertical SaaS definition, was last updated September 26, 2023, before any of this started. Two of Google's related searches for this topic are now "vertical AI vs horizontal AI" and "vertical SaaS AI," and nothing current serves them.
The bull case is real. In its State of AI 2025, Bessemer Venture Partners argues vertical AI "has the potential to eclipse even the most successful legacy vertical SaaS markets." Read that as a thesis, because it is one: no ARR figures, no numerical comparison between vertical and horizontal. A direction flag, not a measurement.
The bear case, from the r/ycombinator thread quoted below. u/admin_default: "'Vertical AI' is a term that was made up to contrast with generalist AI… So 'Vertical AI' was conceived to sound more investible than the more derogatory term, 'AI Wrapper', though it's essentially synonymous."
Our position: when the model is a commodity, the defensible part is the same thing it always was. Own the workflow and the data that flows through it. Calling the result vertical AI or vertical SaaS is a fundraising question, not an architecture one. Shipping an AI product anyway? Start with the AI stack a SaaS product actually runs on and getting an AI feature past the demo. That gap is where vertical-AI pitch decks go to die.
What founders who've actually built say
Search "vertical vs horizontal saas reddit" and the top result is this r/ycombinator thread from around February 2025, ranking #2 on Google for this exact query in our July 2026 check. That placement is the finding: six professional articles on page one, and none quotes a founder. Here are five, verbatim.
"The investor interest in vertical SaaS stems from the idea that it's hard for startups to compete in horizontal AI SaaS. The thinking is that 'thin wrapper' companies will get subsumed by the foundational leaders (OpenAI, Google, Anthropic, etc.)" … "Winning companies will need 'thicker' wrappers that embed subject matter expertise, integrations, and opinionated workflows" , u/Remarkable-East, 41 points
"all the VC backed startups are doing some horizontal AI deep tech SaaS… The one who do a vertical AI SaaS have almost all choosen a very big and crowded market. We're doing the opposite. We're building a vertical SaaS in a very small niche with less competition. But we're also not interested in getting funded." , u/CDBln, 6 points
"you should go for solving a horizontal problem but market strong vertical use cases that can be unlocked" , u/Nishkarsh_1606, 3 points
"vertical, horizontal, diagonal, caddy-corner, whatever. Just make something defensible that matters." , u/abaker80, 7 points
"when we approach vc they don't seems to be excited. They still have married to the term vertical SaaS" , u/Academic-Voice-6526, the thread's founder, on fundraising
The last quote is the most useful data point in the set: capital pulls one direction, and the filings show the economics do not care.
The third path: hybrid, on-top, and vertical-GTM-with-a-horizontal-core
Pure shapes are rarer than the debate suggests. Three real variants do most of the work:
- Horizontal core, vertical go-to-market. Salesforce's Industry Clouds, Health Cloud and Financial Services Cloud, are one horizontal platform packaged per industry. The filing shows a single $41.5B company, not several vertical ones.
- Vertical first, adjacent verticals later. Veeva started in pharmaceutical R&D and quality, then expanded across the wider life-sciences workflow. One industry's adjacency map, not a pivot.
- Built on top. Klaviyo began as an email tool sitting on top of Shopify stores, then widened to any e-commerce business. The platform was the distribution; the vertical was the wedge.
The fourth variant is the one nobody has written down, and the r/ycombinator thread converges on it: start narrow, keep the architecture horizontal, expand once the wedge holds. u/Nishkarsh_1606's point about solving a horizontal problem while marketing vertical use cases states it cleanest. Build narrow; architect wide.
When each model is a trap
Neither shape is safe by default. The failure modes are just different, and naming them beats any framework.
Vertical traps
- A regulated vertical you have no access to. Compliance becomes the moat against you. Run the pre-launch security checklist before promising a regulated buyer anything.
- An incumbent that owns the system of record. You stop selling software and start selling migration risk. Most buyers decline.
- Buyers who have never paid for software. You are creating budget, not winning it. That is a different company.
Horizontal traps
- A product a foundation-model vendor can ship as a feature. If OpenAI, Google, or Anthropic can demo your whole product in a keynote, your barriers to entry are zero and market saturation is already running.
- A wedge you cannot name in one sentence. Horizontal distribution rewards one sharp feature. Two features is a roadmap; zero is a vibe.
How Techsy approaches this
We build SaaS products for clients at Techsy, and the shape question comes up in every scoping call. Three questions settle it. Who signs the contract, a role or a whole company? What workflow does the product own? Does the buyer already pay for software? "A whole company," "the core workflow," and "yes" means vertical. One feature every industry needs means horizontal, and we spend the saved time on distribution. Weighing a build? Talk to us: the scoping call is free and usually settles the shape.
Frequently Asked Questions
Is Salesforce vertical or horizontal SaaS?
Salesforce is horizontal SaaS. Its CRM serves any industry with a sales, service, or marketing team. It reported $41.5B in FY2026 revenue at a 20.1% GAAP operating margin, a scale only a cross-industry product reaches. Its Industry Clouds are vertical go-to-market on a horizontal core.
What is an example of horizontal SaaS?
HubSpot is a clean example: marketing and sales software for any business with a customer funnel. It reported 288,706 customers at end-2025, a base that size only because buyers never have to belong to a trade. Salesforce fits the same pattern.
What is vertical SaaS in simple terms?
Vertical SaaS is software built for one industry's workflow, sold to whole companies rather than a job role. Veeva runs drug development for life sciences, Procore runs construction, Toast runs restaurants. The industry is the boundary; the buyer is usually the owner.
Is vertical SaaS more profitable than horizontal SaaS?
Not in any way the filings let you state cleanly. Vertical often carries higher revenue per customer (Procore about $74,000 against HubSpot about $10,800), but total revenue misleads: Toast's $6.153B includes payments and hardware; its software ARR is $2.047B. Compare subscription lines to subscription lines.
Can a SaaS product be both horizontal and vertical?
Yes. Most durable companies end up that way. The common path is a horizontal core with vertical go-to-market, one platform packaged per industry, as Salesforce does. The reverse also works: start vertical, expand to adjacent industries once the first holds. Launch shapes rarely survive year five.
Is vertical AI the same as vertical SaaS?
No. Vertical SaaS is a market shape, software for one industry. Vertical AI is a business-model claim, an AI product whose moat is industry data and workflow, not the model itself. The models are commodities every competitor can buy. Owning the workflow stays the only durable advantage.
Which is easier to fund, vertical or horizontal SaaS?
Right now, vertical. The r/ycombinator thread's founder put it plainly: investors "still have married to the term vertical SaaS," and horizontal founders report cooler rooms. Investor fashion is not fundamentals, though: HubSpot grew to $3.13B selling horizontal software. The funding climate changes faster than economics.
Which has lower customer acquisition cost?
Vertical usually wins per qualified buyer, because the whole market congregates in one place: one trade show, one publication, one community. Horizontal wins per raw lead, because self-serve funnels convert without a sales call. Neither is cheaper absolutely; the unit you measure decides.
Do vertical SaaS companies grow more slowly?
Not really. In the latest filings, vertical Veeva grew 16% and Procore 15%, while horizontal Salesforce grew 10% and HubSpot 19%; Toast's ARR grew 26%. The label does not set growth; saturation and retention do. Vertical deepens a small base, horizontal widens a large one.
The bottom line
Five filings, one verdict. The horizontal vs vertical SaaS choice is not about which shape is better; growth scattered between 10% and 26% says there is no better shape, only the shape your unfair advantage fits. Build vertical if you can name 20 buyers today and they already pay for software. Build horizontal if your wedge is one feature you can make best in the world. And compare subscription lines to subscription lines: the SERP's favorite mistake is also its most expensive.