How do I decide between vertical-by-vertical vs horizontal expansion?

Direct Answer

The vertical-versus-horizontal expansion decision is not a philosophy debate — it is a revenue-signal-driven choice that should be re-run at every $10M ARR milestone. The honest 2026 answer for almost every B2B SaaS company is hybrid: build a horizontal core with deeply opinionated vertical modules, because pure horizontal SaaS is being commoditized by AI faster than pure vertical SaaS, and pure vertical SaaS hits TAM ceilings of $500M-$5B addressable that block venture-scale outcomes.

Verticalize when (a) 30%+ of revenue concentrates organically in one industry, (b) that industry has regulatory specialization — HIPAA, FINRA, GxP, OSHA, SOC 2, FedRAMP — that horizontal competitors cannot easily replicate, (c) your founder team has industry-native credibility, (d) net revenue retention is 130%+ in that vertical versus 105-115% elsewhere, and (e) the vertical has 10,000+ addressable companies.

Stay horizontal when revenue is distributed across 8+ industries with no vertical above 20%, the product is fundamentally infrastructure, product-led growth works across personas, and cross-industry network effects exist. The decision in 2026 is rarely vertical *or* horizontal — it is how fast and how deep to verticalize a horizontal core, and which two to three verticals to bet on first.

1. Definitions: Vertical, Horizontal, and Hybrid SaaS in 2026

The vocabulary matters because it has drifted considerably from the 2010s definitions, and operators routinely talk past each other in board meetings because nobody agrees on terms. Pin the terms down first; everything downstream depends on a shared vocabulary.

1.1 What Vertical SaaS Actually Means

Vertical SaaS is software designed for a single industry, with data models, workflows, terminology, regulatory features, integrations, and go-to-market motion all optimized for that one industry. The defining characteristic is that a buyer outside the target industry would find the product unusable or absurd.

• Veeva Vault is unusable to a restaurant: its regulated content-management object model assumes clinical trials, quality submissions, and 21 CFR Part 11 electronic signatures.
• Toast is unusable to a hospital: its data model assumes tip pools, modifiers, multi-station kitchen routing, and gift cards.
• Procore is unusable to a law firm: RFIs, submittals, drawings, and change orders are meaningless outside construction.
• The product is deliberately not generic: the narrowing is the strategy, not a limitation.

Vertical SaaS companies typically have addressable markets of $500M-$5B per vertical, gross retention rates of 92-97%, net revenue retention of 115-140%, and ACVs that run 30-60% higher than equivalent horizontal tools in the same category because of bundled regulatory, data, and workflow value.

The downside is real: TAM ceilings exist, and growth past $300M-$500M ARR usually requires either international expansion into the same vertical — Veeva's global pharma push — or aggressive expansion into adjacent verticals — Toast moving from restaurants into retail and hospitality.

1.2 What Horizontal SaaS Actually Means

Horizontal SaaS is software designed to work across many industries, with a generic data model, configurable workflows, and a go-to-market motion that addresses a *function* — sales, marketing, HR, finance, support, IT, security, dev tools — rather than an industry. The defining characteristic is that a buyer in almost any industry can adopt it without significant re-architecting.

• Generic schema underneath: Salesforce CRM works for pharmaceutical reps, car dealerships, consulting firms, and SaaS account executives on the same Account / Contact / Opportunity objects.
• Massive TAMs: horizontal categories run $20B-$200B+ in addressable spend.
• Commoditization pressure: every horizontal category eventually attracts 8-30 well-funded competitors.
• Eroding pricing power: AI features compress differentiation, and pricing power erodes 4-9% per year in mature categories absent strong network effects.

1.3 What Hybrid SaaS Means — and Why It Dominates

Hybrid SaaS, the dominant 2026 model, is a horizontal core platform with explicitly verticalized layers on top: industry-specific data models, industry-specific UI/UX, industry-specific compliance and audit features, industry-specific AI agents, industry-specific pricing units, and industry-specific go-to-market teams.

• Salesforce Industries: Health Cloud, Financial Services Cloud, Manufacturing Cloud, Consumer Goods Cloud, Energy & Utilities Cloud, Public Sector Cloud, Education Cloud, Nonprofit Cloud, Media Cloud.
• ServiceNow Industries: Banking & Capital Markets, Insurance, Telecommunications, Manufacturing, Healthcare, Public Sector.
• Microsoft Industry Clouds: Healthcare, Financial Services, Manufacturing, Retail, Sustainability, Nonprofit.
• Snowflake Industry Data Clouds and HubSpot industry templates: the same pattern at the data-platform and SMB layers respectively.

The right framing for a 2026 founder or CRO: you are almost never choosing pure vertical versus pure horizontal. You are choosing how aggressively to verticalize a horizontal core, and which verticals to bet on first. The remainder of this answer treats the decision that way. The closely related GTM-motion question — product-led versus sales-led — is covered in (q88), and the segment-focus question in (q89).

2. The Strategic Trade-Off Matrix

The vertical-versus-horizontal trade-off is genuinely a matrix, not a single axis. The trade-offs operate across at least seven independent dimensions that boards routinely conflate into a single muddled debate.

2.1 The Seven Dimensions

Total addressable market: Vertical wins on quality, horizontal wins on quantity. A focused vertical targets $500M-$5B per vertical; a horizontal targets $20B-$200B. For venture-scale outcomes above a $10B exit, horizontal is mathematically easier. For high-margin scale of $300M-$1B revenue at 35-45% EBITDA, vertical is mathematically easier.

Defensibility and moat: Vertical wins decisively. Industry-specific data models, regulatory workflows, customer-success teams that speak the language, and ecosystem partnerships create a moat that takes 5-8 years to replicate. Horizontal moats are typically platform or ecosystem (Salesforce AppExchange), network (Slack interop), or distribution (HubSpot inbound machine) — all real but more attackable by well-funded entrants.

Customer acquisition cost: Vertical wins on efficiency. Tight ICP definitions mean tighter targeting, lower wasted ad spend, higher conversion rates, and stronger word-of-mouth inside the vertical.

Pricing power: Vertical wins. Specialization commands 30-50% premium ACVs because customers compare you against generic horizontal tools and recognize the regulated and specialized value.

Retention: Vertical wins. Gross revenue retention of 92-97% is the vertical norm because switching costs are massive. Horizontal SaaS averages 85-92%.

Talent acquisition: Horizontal often wins. Vertical SaaS struggles to hire engineers who care about an industry they have never worked in, and needs industry-native VPs — a thinner labor market.

Optionality: Horizontal wins. A horizontal SaaS can pivot, expand, verticalize selectively, or be acquired by anyone. A vertical SaaS is locked into one industry's data model, brand, and team.

The clean summary: vertical wins on every economic metric except absolute TAM and exit-buyer breadth. Horizontal wins on optionality, talent, and ceiling. Hybrid attempts to keep horizontal optionality while capturing vertical economics — which is why the dominant strategy past $100M ARR is hybrid.

2.2 The Trade-Off Matrix in Table Form

2.3 Why the Matrix Beats a Single Axis

The mistake operators make is collapsing seven dimensions into one "are we vertical or horizontal" question. A company can be horizontal on TAM ambition, vertical on CAC discipline, and hybrid on product architecture simultaneously. The matrix forces a board to score each dimension independently, which exposes where the company's *actual* strategy diverges from its *stated* strategy.

The owned-product-versus-marketplace platform decision sits adjacent to this matrix and is handled in (q90).

3. TAM Math by Approach: The Numbers That Determine Your Ceiling

The single most important spreadsheet a CRO or founder builds in this decision is the TAM map across realistic verticals, with both raw addressable spend and serviceable obtainable share. Most operators do this badly.

3.1 Vertical TAM Per Vertical

A vertical's addressable software spend is typically 0.4-1.8% of the industry's total revenue, depending on how software-intensive the industry is.

• Life sciences: roughly 1.2% software spend on $1.6T industry revenue equals $19B vertical software TAM, of which clinical and regulatory subsets are $4-6B.
• Construction: roughly 0.5% software spend on $1.8T US construction industry equals $9B vertical software TAM.
• Restaurants: roughly 1.1% software spend on $900B US restaurant industry equals $10B TAM; Toast plays in a $20-25B global subset including hardware and payments.
• Home services: roughly 0.8% software spend on $600B US home services equals $5B TAM.
• Fitness and wellness: roughly 1.6% software spend on a $35B industry equals $560M-$1.4B TAM — small enough that Mindbody got acquired at $1.9B rather than IPO'd at $20B.

The pattern: vertical TAMs are $500M-$5B per vertical for the focused use case, $5B-$25B if you broaden the product surface to include payments, hardware, marketplace, lending, and ancillary services.

3.2 Horizontal TAM Per Category

The horizontal numbers are 5-20x bigger than per-vertical numbers, but the realistic serviceable obtainable market within any horizontal category is rarely above 8-12% because competition is so fragmented — Salesforce at roughly 20% of CRM at peak, HubSpot at 5-7%, Microsoft Dynamics at roughly 15%, the rest split among 30+ players.

3.3 Expansion Potential — Vertical Versus Horizontal

Vertical companies expand via three vectors: (1) deeper product surface — Toast added payments, payroll, lending, marketing, online ordering, and inventory, going from a $300/month POS to a $2,000/month platform per location; (2) adjacent verticals — Toast into retail, hospitality, golf, and stadiums; Procore into infrastructure and civil engineering; (3) international same-vertical — Veeva's global pharma push from $1B to $2.4B+ ARR.

The expansion multiple is typically 4-8x the original wedge over 7-12 years.

Horizontal companies expand via: (1) product line breadth — Salesforce from CRM to Marketing Cloud to Service Cloud to Commerce to Analytics to Platform to AI; (2) upmarket movement — HubSpot from SMB to mid-market to enterprise; (3) AI-native re-bundling in 2025-2027.

The expansion multiple is 10-30x the original wedge over 10-15 years for the winners — but only the top 1-3 winners per horizontal category capture that.

3.4 The Compound Math That Drives the Decision

A vertical SaaS reaching $500M ARR at 35% EBITDA is roughly a $5-8B exit — 8-15x ARR private market or 6-10x public. A horizontal SaaS reaching $500M ARR at 25% EBITDA is roughly a $4-7B exit — 6-12x ARR. The vertical exit multiple is meaningfully higher per dollar of revenue, but the horizontal company has a chance to reach $5B+ ARR where vertical companies hit ceilings.

For the founder choosing today, the right question is: am I optimizing for $1-3B outcomes with 70% probability, or $10-30B outcomes with 5-10% probability? Vertical gives you the former, horizontal gives you the latter, hybrid gives you a credible shot at both.

4. Customer Acquisition Cost: Why Vertical CACs Run 30-50% Lower

CAC differences between vertical and horizontal SaaS are larger and more durable than most operators realize, and they compound over time into materially different unit economics.

4.1 The Five Structural Mechanics

• Targeting precision: A vertical SaaS marketing team knows exactly who the buyer is — the COO of a 40-100 location restaurant chain, the VP of Clinical Operations at a 200-500 employee biotech, the GM of a 30-80 truck home services company. Paid media targeting is razor-sharp. MQL-to-SQL conversion runs 35-55% in well-run vertical SaaS versus 12-25% in horizontal SaaS.
• Channel cost: Vertical conferences are smaller and more expensive per attendee but the buyer concentration is 5-20x higher. Sponsoring HIMSS for $80K puts a healthcare SaaS in front of 40,000 health-system decision-makers; sponsoring Dreamforce for $250K puts a horizontal SaaS in front of 180,000 attendees of which maybe 8,000 are in the real ICP.
• Word-of-mouth velocity: Vertical communities are tight. A restaurant operator who loves Toast tells five others within 90 days because they all attend the same National Restaurant Association chapter meetings. Vertical NPS-to-referral conversion runs 18-32% versus 6-14% horizontal.
• Sales cycle: Counterintuitively, vertical sales cycles are often *shorter* at similar ACV bands because trust is pre-built and proof-of-concept requirements are simpler. A $40K ACV vertical deal often closes in 45-90 days; a $40K ACV horizontal deal often takes 90-180 days.
• Pre-built proof: A vertical vendor already has a configured demo "for restaurants like yours," compressing evaluation.

4.2 The Hard CAC Numbers

The 30-50% efficiency gap is durable because it stems from structural funnel mechanics, not tactical execution.

4.3 The Exception That Proves the Rule

PLG-led horizontal SaaS — Notion, Linear, Figma, Slack at early stages — can match or beat vertical CAC because the product itself does the selling. But PLG horizontal faces its own ceiling: monetization is harder at $8-$24 per seat versus $200-$2,000 per vertical user, and enterprise expansion still requires a sales motion that ends up looking pseudo-vertical anyway.

Linear and Notion both ship industry-specific templates as they hit $50M+ ARR — verticalizing within the horizontal core. The detailed PLG-versus-sales-led trade-off is in (q88).

5. Retention: Why 95%+ Gross Retention Is Vertical Standard

Gross revenue retention is the most under-discussed advantage of vertical SaaS, and the gap versus horizontal is large and persistent: well-run vertical SaaS targets 92-97% GRR, well-run horizontal SaaS targets 85-92%.

5.1 The Five Retention Drivers

• Switching costs: Vertical SaaS embeds itself in industry-specific workflows that take months to re-implement. A health system migrating off Epic to Oracle Health is an 18-36 month, $20-80M project. A construction firm migrating off Procore must rebuild 200-500 active projects and re-integrate subcontractor systems — a 9-18 month nightmare. A restaurant chain migrating off Toast means new hardware in 80 locations, new tip-pool configurations, and 4-8 weeks of staff retraining.
• Regulatory lock-in: Vertical SaaS in regulated industries — healthcare HIPAA, life sciences GxP, financial services FINRA and SOX, public sector FedRAMP, education FERPA — has audit-trail, validation, and compliance configurations that take 6-12 months to re-establish. This regulatory friction *is* the moat.
• Industry-specific integrations: Toast integrates with Resy, OpenTable, DoorDash, Grubhub, Uber Eats, Toast Payroll, US Foods, Sysco, and 200+ restaurant-specific tools. Procore integrates with Sage 300 CRE, Viewpoint Spectrum, Foundation, ProEst, Plangrid, Bluebeam, and 400+ construction-specific tools. A competitor must rebuild 100+ integrations before being competitive.
• Customer success specialization: A Toast CS rep can talk about food costs, modifier configurations, tip pools, and kitchen display systems. Vertical CS adds 4-8 percentage points to GRR.
• Net retention multiplier: Expansion within a single industry is straightforward — same buyer, more locations, more providers, more projects, more loans.

5.2 Net Revenue Retention Benchmarks

5.3 The Compound Effect

The difference between 95% GRR plus 125% NRR (vertical) versus 88% GRR plus 110% NRR (horizontal) over five years is enormous. Starting with $10M ARR and adding nothing else, the vertical book compounds to roughly $30.5M from the existing customer base alone; the horizontal book compounds to roughly $16.1M.

Almost double the revenue compounding from the same starting book. This single mathematical fact is why vertical SaaS valuations often exceed horizontal valuations per dollar of revenue.

6. Pricing Power: The 30-50% Premium and Why It Is Defensible

Vertical SaaS commands meaningful pricing premiums over horizontal alternatives — typically 30-50% higher ACV for comparable functionality, and sometimes 2-5x higher in regulated or specialized verticals.

6.1 The Six Pricing Mechanisms

• Bundled value capture: A horizontal CRM at $150/seat/month does customer relationship management. Veeva CRM at $400-$1,200/rep/month does CRM plus PhRMA-code-compliant call reporting plus sample management plus medical inquiry routing plus formulary access integration. The buyer compares Veeva to "Salesforce plus 6-9 months of custom dev plus $400K of integration work plus ongoing regulatory maintenance" — and Veeva is cheaper in total cost of ownership.
• Specialized pricing units: Vertical SaaS prices per the unit the *customer* uses to measure their business — per provider, per property, per location, per loan, per FTE, per project — capturing growth automatically.
• Lower price-comparison pressure: A construction GC comparing Procore against Buildertrend does not price-anchor against Smartsheet or Asana.
• Annual price escalators: Vertical SaaS commonly includes 5-8% annual escalators that customers accept because they have nowhere else to go; horizontal SaaS struggles to push 3-5%.
• Industry-specific add-ons: Toast attaches payments at a 3-4x ARR multiplier, plus payroll, lending, marketing automation, and online ordering.
• AI-resistant value driver: The premium is tied to value the customer recognizes, not arbitrary markup.

6.2 Pricing Models by Vertical

The pattern: every vertical has a customer-recognized pricing unit, and using that unit results in better deal economics, easier renewal conversations, and clearer expansion paths than per-seat pricing. Restructuring a pricing change without churning customers during a vertical transition is covered in (q91), and per-provider versus per-seat unit selection in (q103).

6.3 The Defensibility of the Premium

When AI commoditizes generic features, vertical pricing premiums hold up better than horizontal because the value driver — regulatory compliance, industry data model, ecosystem integration — is harder for AI to replicate. The 2024-2026 AI wave compressed horizontal SaaS pricing 5-15% in commoditizing categories such as basic CRM, basic marketing automation, and basic helpdesk, while vertical SaaS pricing held flat or grew 3-7%.

7. Vertical SaaS Case Studies: Five Modern Archetypes

7.1 Veeva Systems — Life Sciences

Founded 2007 by Peter Gassner, a former Salesforce VP, and Matt Wallach. Started as a CRM for pharmaceutical reps built on Salesforce's platform — a deliberately vertical wedge into an industry where horizontal Salesforce was already adopted but not optimized for pharma's call reporting, sample tracking, formulary access, and regulated content delivery.

IPO'd 2013 at a $4B valuation. By FY2024: $2.4B+ ARR, $25-30B market cap, 1,200+ life sciences customers including all top 20 pharma companies. Veeva built Vault — regulated content management for clinical trials, quality, and regulatory submissions — in 2011, and Vault became a bigger business than CRM by 2020.

The lesson: a deeply vertical wedge of $500M-$2B initial TAM can compound to a $25-50B market cap if the founder team has industry-native credibility and the vertical has enough downstream product surface.

7.2 Procore — Construction

Founded 2002 by Tooey Courtemanche. Construction project management for general contractors and owners. Spent 15 years building deep workflows — RFIs, submittals, drawings, change orders, daily logs, time tracking, safety — before reaching $100M ARR around 2017.

IPO'd 2021 at a $9.6B peak market cap. FY2024 ARR roughly $1B+, around 16,000 customers managing $2T+ in construction volume annually. The lesson: vertical SaaS in a deeply under-digitized industry — construction's software-spend ratio is roughly 0.5% — can grow steadily for 20+ years because the paper-to-digital conversion runway is so long.

7.3 Toast — Restaurants

Founded 2011, IPO'd 2021 at a $30B+ peak market cap. Restaurant POS and operations platform. FY2024 ARR roughly $1.3B, around 120,000 restaurant locations.

Built on the realization that restaurants are uniquely complex — tip pools, modifiers, multi-station kitchens, gift cards, loyalty, online ordering, marketplace fees, tipped-employee payroll — and that horizontal Square Restaurant could not cover the long tail. Toast attached payments at a 3-5x revenue multiplier, plus payroll, Toast Capital lending, marketing automation, and online ordering.

The lesson: vertical SaaS with payments attach monetizes at 5-15x the SaaS-only revenue; Toast's effective per-location ARPU is $20K-$40K including payments versus $3-5K for SaaS-only.

7.4 Mindbody — Fitness and Wellness

Founded 2001, IPO'd 2015, taken private by Vista Equity Partners in 2019 at $1.9B. Booking and management software for fitness studios, spas, salons, and wellness businesses. Reached $260M+ revenue at the take-private.

Smaller TAM than restaurants or construction at $560M-$1.4B, which is why the outcome was a private equity recap rather than a public-market growth story; Mindbody is now combined with ClassPass under Vista. The lesson: vertical SaaS in a smaller industry can still build a $1-3B outcome, but the buyer pool narrows to PE and same-vertical acquirers — pick verticals with enough TAM if you want a venture-scale exit.

7.5 ServiceTitan — Home Services

Founded 2007 by Vahe Kuzoyan and Ara Mahdessian. Field service management for HVAC, plumbing, electrical, garage door, and other home services contractors. Achieved $772M ARR pre-IPO, IPO'd December 2024 at a $9B valuation, 11,000+ contractor customers covering roughly 110,000 technicians.

The vertical playbook executed cleanly: industry workflows for dispatching, pricebook, financing, and marketing, with per-technician pricing of $200-$400/tech/month and attached payments and consumer financing. The lesson: even in unsexy verticals, software-spend conversion plus payments attach can build a $9B IPO outcome — do not dismiss the unsexy verticals.

8. Horizontal SaaS Case Studies: Five Archetypes

8.1 Salesforce

Founded 1999, the original horizontal CRM. Reached $1B ARR in 2009, $10B ARR in 2017, $35B+ ARR by FY2024 at a $250B+ market cap. Built the horizontal playbook: CRM core, platform extension via Force.com and the Lightning Platform, acquisition-driven expansion — ExactTarget into Marketing Cloud, Demandware into Commerce, MuleSoft into integration, Tableau into analytics, Slack into collaboration — and aggressive verticalization past $5B ARR via Salesforce Industries.

The lesson: the largest horizontal SaaS companies all eventually verticalize.

8.2 HubSpot

Founded 2006. Started as marketing automation, expanded to sales, service, CMS, operations, and commerce. Reached $2.6B+ ARR by FY2024 at a $30B+ market cap.

The horizontal playbook tilted toward SMB and mid-market, built on one of the strongest inbound marketing machines in SaaS history. The lesson: horizontal can win at $2-3B ARR scale via brand and inbound distribution moats even without aggressive verticalization, but growth slows past $3B unless verticalization deepens.

8.3 Notion

Founded 2013, an all-purpose collaborative workspace. Reached roughly $400M ARR by 2024 at a $10B+ valuation. PLG-led horizontal expansion via templates that effectively verticalize the product into use cases — engineering wikis, marketing playbooks, sales playbooks, OKR templates.

The lesson: PLG horizontal can scale to $500M ARR efficiently, but monetization caps at $8-$24 per seat, so revenue compounding is slower.

8.4 Slack

Founded 2009 from the ashes of Glitch, a failed game. Horizontal team messaging. Reached $1B ARR by 2021 and was acquired by Salesforce for $27.7B that year.

Built the deepest horizontal network effect in SaaS history. The lesson: horizontal SaaS with strong network effects can build sustainable defensibility, but network-effect horizontals tend to get bought rather than dominate independently.

8.5 Atlassian

Founded 2002. Developer tools — Jira, Confluence, Bitbucket, Trello, and Loom acquired in 2023. Reached $4B+ ARR by FY2024 at a $40B+ market cap.

The horizontal playbook focused on developer-led adoption, selling to engineering teams across every industry — a horizontal motion tilted to a functional persona. The lesson: horizontal targeting a specific function such as engineering is structurally easier than horizontal across all functions.

9. Five Hybrid Strategies: How the Largest Companies Verticalize

• Snowflake Industry Data Clouds: A horizontal data warehousing platform with layered Industry Clouds for Financial Services, Healthcare and Life Sciences, Retail, Media and Entertainment, Telecom, Public Sector, and Manufacturing. Each bundles industry-specific data sets — S&P Capital IQ data in Financial Services — partner apps, and reference architectures. Industry Cloud customers spend 30-60% more annually than generic Snowflake customers per company disclosures.
• Salesforce Industries: Originally the $1.3B 2020 acquisition of Vlocity, now expanded into nine industry clouds. Industry Cloud revenue is $5B+ of Salesforce's $35B ARR and growing faster than the core platform.
• ServiceNow Industries: A horizontal workflow automation platform with industry products for Banking and Capital Markets, Insurance, Telecommunications, Manufacturing, Healthcare, and Public Sector. ServiceNow's $11B+ ARR includes an Industries segment monetizing at 40-70% higher per customer than core IT Service Management.
• HubSpot Vertical Templates: A lighter hybrid play — industry-specific templates, playbooks, and integration sets for construction, professional services, real estate, healthcare, and education that cut time-to-value from 90 days to 15-30 days.
• Microsoft Industry Clouds: Cloud for Healthcare, Financial Services, Manufacturing, Retail, Sustainability, and Nonprofit, each bundling Azure, Microsoft 365, Dynamics 365, and Power Platform at a 15-30% premium, generating $8B+ in annual revenue.

The lesson at every scale: a horizontal platform reaching $10B+ ARR almost requires verticalization to keep growing. Sequencing the industry cloud roadmap is covered in (q94), and sequencing expansion across 3-5 industries in (q96).

10. Land Strategy: Vertical Versus Horizontal Customer Acquisition

10.1 The Vertical Land Playbook

Vertical land strategy is fundamentally different from horizontal land strategy, and operators routinely fail at vertical land by applying horizontal tactics.

• ICP-perfect customer hunting: Start with a list of 200-2,000 named accounts that match the ICP exactly. For a construction SaaS targeting GCs with $50M-$500M annual revenue, that is roughly 4,000-7,000 US GCs by ENR rankings and Dodge Data — a finite, listable universe. Vertical sales teams literally print the target list and work it account by account.
• Vertical conference sponsorship: Sponsor 4-12 vertical conferences per year heavily. Construction: World of Concrete, BUILDEX, ENR FutureTech, Procore Groundbreak, AGC conventions. Healthcare: HIMSS, RSNA, J.P. Morgan Healthcare Conference, AHA Annual Meeting. Restaurants: NRA Show, FSTEC, NRF Big Show.
• Industry-association partnerships: Partner with the National Restaurant Association, AGC, ASHRM, or IFA as the "preferred technology partner." Association endorsement takes 18-36 months to earn but pays back for a decade. Vertical conference ROI measurement is in (q105) and association partnerships in (q106).
• Vertical content marketing: Build industry benchmarking reports — Toast's annual restaurant industry report, Procore's construction industry data — industry podcasts, and professional certifications. Vertical content outperforms horizontal content by 4-10x on cost-per-lead.
• Outbound by industry persona: SDR sequences referencing industry-specific pain points run 4-12% reply rates versus 1-3% for horizontal outbound.
• Customer advisory board by vertical: A 12-24 person CAB of recognized industry leaders becomes evangelists, references, and conference co-presenters. Building a vertical CAB is detailed in (q92).

10.2 The Horizontal Land Playbook

• PLG funnel: Free or freemium tier capturing broad usage — Notion, Figma, Slack, Linear, Loom, Calendly, Zapier, Airtable. 100K+ free signups per month at $0 CAC convert at 1-4% to paid.
• Broad SEO: Rank for 1,000-50,000 keywords across all industries. HubSpot's marketing blog is the canonical example — millions of organic visits per month.
• Content marketing breadth: 4-12 content assets per month spanning many use cases, with lead-magnet conversion of 8-18%.
• Integration ecosystem: Salesforce AppExchange has 7,000+ apps, HubSpot App Marketplace 1,500+, Slack App Directory 2,500+, Zapier 8,000+ integrations.
• Paid acquisition: Google Ads, LinkedIn Ads, and Meta Ads at $5K-$80K daily, with CAC payback of 12-30 months.
• Community and developer programs: Atlassian, HashiCorp, MongoDB, Confluent, and Snowflake built developer communities that drove enterprise adoption over 5-8 years.

10.3 Channel Cost Comparison

11. The "Vertical Within Horizontal" Pattern

The most important strategic dynamic in 2024-2026 SaaS is that every horizontal company past $1B ARR is aggressively verticalizing, and this changes the competitive landscape for vertical-only companies.

11.1 The Pattern Across Platform Leaders

• Salesforce Industries: From the $1.3B Vlocity acquisition in 2020 to nine industry clouds generating $5B+ ARR. Post-$10B ARR, horizontal growth slows because the addressable base has been mostly captured; verticalization unlocks the next leg.
• Microsoft Industry Clouds: Six clouds bundled with Azure, Microsoft 365, and Dynamics 365 — strategic weapons against AWS and Google Cloud in industries where compliance and data sovereignty create switching friction.
• Workday Industries: Industry-specific versions for healthcare, financial services, retail, hospitality, professional services, public sector, and higher education.

11.2 The Implication for Vertical-Only Companies

Vertical specialists must move faster and go deeper than the horizontal verticalizers. A vertical SaaS competing against Salesforce Health Cloud or Microsoft Cloud for Healthcare must offer deeper integrations with industry-specific systems, more comprehensive industry data models, or industry-native AI agents the horizontal cannot replicate at parity.

Retaining horizontal customers through a verticalization transition is covered in (q98), and balancing horizontal optionality with vertical execution in (q108).

11.3 The Implication for Hybrid Companies

Companies that are credibly hybrid — horizontal core plus 2-4 mature vertical clouds — are increasingly the strategic winners because they capture both horizontal optionality and vertical economics. ServiceNow, Salesforce, Microsoft, Snowflake, and HubSpot are all positioned this way.

12. Vertical vs Horizontal vs Hybrid Decision Tree

13. Sales Team Specialization: Vertical Reps, SEs, and CSMs

Vertical sales team specialization is one of the highest-ROI structural decisions a CRO makes.

13.1 The Four Specialization Roles

• Vertical rep specialization: In a vertical or hybrid SaaS over $50M ARR, account executives should be aligned by industry. Vertical reps close at 30-50% higher rates than horizontal generalists in industries with significant buyer-side specialization.
• Vertical SE specialization: Sales engineers are even more critical to specialize than AEs. A healthcare SE who speaks fluently about HIPAA, HL7/FHIR, Epic integration, value-based care, and 340B is dramatically more credible. SE-led demos by industry-specialized SEs convert 40-70% better.
• Industry-specific demo libraries: Vertical SaaS should have 5-15 demo configurations per industry, each pre-built with realistic industry data.
• Vertical CSM specialization: CSMs aligned by industry retain customers 5-12 percentage points better than horizontal generalists.

13.2 The Compounding Math

A 30-50% conversion improvement from vertical AE and SE specialization combined with a 5-12 point GRR improvement from vertical CSM specialization compounds to roughly 1.4-2.0x the LTV per customer versus horizontal generalist teams. The investment in industry-specialized talent — slightly higher OTE, slightly longer ramp — pays back in 6-12 months.

Hiring industry-native sales executives is detailed in (q93).

14. Product Architecture for Verticalization

The product architecture decisions that enable verticalization are deeply technical and must be made early — before $30M ARR ideally — or retrofitting becomes painful.

14.1 The Five Architectural Pillars

• Industry data models: Each vertical needs its own canonical data model — Patient, Encounter, Provider, Order, Claim in healthcare; Location, Order, Item, Modifier, Tip, Employee in restaurants; Property, Unit, Lease, Tenant, Payment, Owner in real estate; Loan, Borrower, Application, Underwriter, Servicing in fintech lending. These should be first-class objects, not retrofit on generic Account / Contact / Opportunity. Building a vertical data model from scratch is covered in (q101).
• Regulated workflows: HIPAA audit logging, GxP electronic signatures under 21 CFR Part 11, FINRA recordkeeping, FedRAMP authorization, SOX controls, PCI DSS, GDPR and CCPA. These take 12-36 months to build correctly and are the most defensible part of vertical SaaS. Building compliance into product is detailed in (q104).
• Vertical AI agents: Industry-specific agents — an underwriting agent for commercial lending that knows DSCR, LTV, and debt-to-equity; a clinical-note agent that knows ICD-10, CPT, and HCC codes; an estimation agent for construction.
• Vertical APIs and integrations: A healthcare SaaS without Epic, Oracle Health (Cerner), and Athenahealth is uncompetitive; a restaurant SaaS without DoorDash, Uber Eats, Resy, and OpenTable is uncompetitive. Integrating with vertical systems of record is covered in (q102).
• Per-tenant compliance settings: The platform must accommodate per-tenant HIPAA business-associate agreements, GxP validation packages, and SOC 2 audit scopes without code changes.

14.2 The Retrofit Cost

15. Investor Communication: Two Different Metric Stacks

15.1 The Vertical Strategy Metric Stack

Vertical SaaS companies pitch a different metric stack to investors than horizontal SaaS.

• Gross retention by vertical: Show 92-97% GRR with cohort detail.
• Net retention by vertical: Show 115-140% NRR with expansion-revenue decomposition — new locations, providers, units.
• Dollar retention concentration: Show that the top vertical's NRR is 130%+ and growing.
• CAC payback by vertical: Show payback under 14 months in the primary vertical, ideally under 10.
• LTV/CAC: Vertical specialists target 5x-10x versus 3x-5x for horizontal.
• Vertical TAM penetration: Show what percentage of the addressable vertical you have captured — typically 1-5% early stage, 8-20% at scale.
• Adjacent vertical expansion roadmap: Toast moving from restaurants to retail to hospitality is the canonical narrative.

15.2 The Horizontal Strategy Metric Stack

• PLG funnel mechanics: Top-of-funnel signups, free-to-paid conversion, time to paid conversion, viral coefficient.
• Net revenue retention: Show 110-130% NRR with seat expansion as the primary driver.
• Gross margin: Show 75-85% with infrastructure efficiency.
• Land-and-expand mechanics: Show how landing in one team expands to others.
• Logo concentration: Show that no single industry exceeds 15-20% of revenue.
• Category leadership: G2 Grid leader, Gartner Magic Quadrant position, Forrester Wave leader.
• Platform and ecosystem metrics: Integrations, marketplace partners, certified consultants, developer signups.

16. The "When To Verticalize" Decision Framework: The Five Signals

Verticalization is a high-conviction commitment with long lead times — 18-36 months to build a credible industry cloud — so the signals that justify it must be strong.

16.1 The Five Positive Signals

• Signal 1 — Revenue concentration above 30% in one vertical: When more than 30% of revenue organically clusters in one industry without you having targeted it, the industry has specific pain your product solves uniquely well.
• Signal 2 — Regulatory specialization: HIPAA, FINRA, GxP, FedRAMP, SOX, or PCI requirements competitors cannot easily replicate make the vertical moat defensible.
• Signal 3 — NRR in the vertical is 130%+ versus 105-115% elsewhere: Customers in the vertical expand faster, meaning more downstream product surface.
• Signal 4 — ICP signals concentrate: Sales calls in the vertical consistently reference specific industry workflows, pain points, and competitive products.
• Signal 5 — Founder team has industry-native credibility: Verticalization requires industry expertise — the most overlooked signal.

When 4 of 5 signals are present, verticalize aggressively. When 2-3 are present, verticalize selectively with a single industry cloud. When 0-1 are present, stay horizontal.

16.2 The "When NOT To Verticalize" Counter-Signals

• Counter-signal 1 — Insufficient revenue concentration: No vertical above 20% and the top three roughly equal-sized.
• Counter-signal 2 — No regulatory moat available: Without compliance requirements competitors cannot replicate, the premium is smaller and the wedge more attackable.
• Counter-signal 3 — AI is commoditizing the vertical's features: If the distinguishing workflows are AI-replicable, verticalization is a fading moat.
• Counter-signal 4 — Product is fundamentally infrastructure: Databases, observability, CDPs, data warehouses, identity, and security are horizontal categories where verticalization is structurally hard.

When 2+ counter-signals are present, stay horizontal and resist the temptation. Evaluating verticalization at every $10M ARR milestone is detailed in (q107).

17. Vertical AI Strategy: The 2025-2027 Wave

Vertical AI is the most important strategic theme in SaaS for 2025-2027, and it changes the vertical-versus-horizontal calculus materially.

17.1 The Three Sub-Strategies

• Industry-specific LLMs: Fine-tuned or RAG-augmented models trained on vertical data — medical literature for healthcare, legal corpora for legal, code repositories for dev tools, financial filings for fintech. Industry-specific models outperform horizontal foundation models by 15-40% on industry-specific tasks per published benchmarks.
• Vertical agents: Industry-specific agents that perform end-to-end tasks — underwriting agent for commercial lending, clinical-documentation agent for healthcare, estimation agent for construction, claims-adjuster agent for insurance. Vertical agents are the most defensible AI moat in 2026.
• Regulatory compliance built in: Vertical AI agents in regulated industries need built-in audit trails, explainability, human-in-the-loop oversight, and regulatory-aligned output formats. Generic AI agents fail compliance reviews; vertical AI agents pass because the compliance is in the architecture.

The strategic implication: vertical SaaS that ships vertical AI agents in 2026 will compound faster than vertical SaaS that does not, and the gap is widening monthly. Building vertical AI agents that win against horizontal foundation models is covered in (q99), and pricing vertical AI agents in (q100).

The broader question of what replaces SDR teams if AI agents replace SDRs natively is in (q1899).

17.2 Vertical AI Impact Numbers

18. Geographic Plus Vertical: The Two-Axis Wedge

A subtler strategic variant combines geographic specialization with vertical specialization to create a multi-dimensional wedge.

• France financial services: ACPR-specific compliance, French GDPR application specifics, and French open-banking PSD2 rules create a defensible moat against pan-European horizontals. TAM roughly $1-3B.
• German manufacturing: Mittelstand manufacturers have SAP-heavy ERP needs, Industry 4.0 / MES requirements, and German labor-law specifics. TAM roughly $4-8B.
• India e-commerce: GST compliance, RBI payment regulations, and pin-code-level logistics specifics create a real moat against global Shopify-clones. TAM roughly $500M-$2B.
• Brazil B2B payments: PIX, Boleto, multi-currency, and complex tax create a vertical-geographic wedge. TAM roughly $300M-$1B.
• Japan B2B SaaS: Printed contracts, hanko stamps, and specific procurement processes that global SaaS struggles with. TAM roughly $500M-$2B per niche.

The two-axis wedge creates a TAM of $100M-$1B per slice with very high defensibility — perfect for $300M-$1B revenue outcomes but rarely for $10B venture outcomes.

19. M&A Strategy and Long-Term Outcomes

19.1 M&A Patterns by Approach

• Vertical M&A — roll-up of adjacent specialists: Toast acquired xtraCHEF for restaurant cost management and Sling for employee scheduling. Procore acquired Honest Buildings, Construction BI, LaborChart, and Levelset. ServiceTitan acquired Pointman and ServicePro. The vertical roll-up buys customer relationships and adjacent capabilities in the same vertical.
• Horizontal M&A — capability acquisitions: Salesforce's history is a masterclass — ExactTarget, Demandware, MuleSoft, Tableau, Slack, Vlocity, Spiff, Airkit, Own Company. Each expanded the horizontal surface area.
• Hybrid M&A — both: Microsoft, Salesforce, and ServiceNow combine capability acquisitions with vertical specialist acquisitions. Evaluating vertical M&A targets is detailed in (q97).

19.2 Long-Term Outcome Probability

The conclusion: founders optimizing for predictable wealth should choose vertical; founders optimizing for the long-tail moonshot should choose horizontal. Hybrid is the only strategy that credibly preserves both options. Exit-multiple math for vertical SaaS is detailed in (q110) and for horizontal SaaS in (q111).

20. Capital Efficiency Curve — Vertical vs Horizontal Over 5 Years

21. Counter-Case: When Verticalization Fails and Horizontal Wins

The bull case for verticalization is strong, but verticalization fails frequently enough that any honest analysis must address the failure modes.

21.1 The Verticalization Failure Modes

• Wrong vertical selected: Three early enterprise logos in a vertical do not constitute industry product-market fit — they are three relationships that happened to close. Building a full industry cloud on weak signal is the most common failure mode. The vertical needs sustained, organic 30%+ concentration over 6-12 months with strong NRR signal first.
• Insufficient industry depth: Some verticalization attempts add superficial industry templates and color palettes rather than genuine data models, regulated workflows, and ecosystem integrations. Buyers see through superficial verticalization within 90 days. Half-verticalization is worse than either pure strategy.
• Sales team cannot pivot: 40-60% of generalist AEs fail to transition to industry-specific selling, and the hiring and retraining cost can erase the verticalization gain for 18-24 months.
• Horizontal AI swallows the vertical premium: The most important 2025-2026 risk. Where the moat was workflow specificity — basic dispatching, basic intake, basic onboarding — horizontal foundation models can replicate it via well-prompted agents and the premium evaporates.
• TAM ceiling reached too quickly: Some wedges hit revenue ceilings at $50-$200M ARR. Mindbody is the classic case — a great $260M revenue business that exited at $1.9B but could not reach $1B+ revenue scale.
• Vertical talent shortage: Some verticals have such thin labor markets for industry-native VPs that verticalization stalls at the leadership layer.
• Hybrid competitors eat the wedge: Pure vertical specialists increasingly face hybrid hyperscalers — Salesforce Industries, Microsoft Industry Clouds, Snowflake Industry Data Clouds — who bring deep platforms with verticalized overlays.
• Acquirer pool narrows: A pure vertical SaaS has 5-12 likely strategic acquirers versus 30-100 for a horizontal. The narrow pool reduces exit-price competition.
• Industry downturns concentrate risk: Restaurants in 2020-2021, construction in 2008-2010, commercial real estate post-2022, fintech lending post-2022 rate hikes. A horizontal SaaS spreads industry risk across 8+ verticals.
• Regulatory compliance costs scale faster than expected: A $20M ARR vertical SaaS in a regulated industry might spend 12-18% of revenue on compliance — well above horizontal SaaS at the same revenue.
• Ecosystem fragility in niche verticals: Vertical SaaS depends on industry-specific data feeds and partner ecosystems that are themselves small companies; when a key vendor pivots or shuts down, costly migrations follow.
• The vertical lifestyle-business trap: Some founders verticalize, reach $30-$100M ARR with healthy margins, then discover they have built a lifestyle business rather than a venture outcome. Avoiding this trap is covered in (q109).
• Geographic and cultural concentration risk: Vertical SaaS often concentrates customers geographically, exposing the company to regional regulation or cultural shifts.
• Founder boredom and burnout: Five to ten years running a single-industry company is monotonous for some founders; horizontal companies offer more variety.

21.2 When Horizontal Wins Outright

Pure horizontal wins when (a) the product is infrastructure with no clear vertical specialization — Snowflake's core engine, Datadog's APM, MongoDB's database; (b) PLG monetization is strong enough to bypass enterprise sales — Figma, Linear, Notion at scale; (c) network effects favor maximum breadth — Slack's interop, Salesforce's AppExchange; and (d) the target customer truly does not care about industry — engineering, finance, and IT teams often do not.

Horizontal also wins via verticalization at scale: the largest horizontal companies amortize vertical-specific R&D across a massive base, so a vertical specialist at $200M ARR competing against Salesforce Health Cloud — backed by a $35B platform R&D base — faces structural pressure that pure verticalization does not solve.

21.3 The Honest Verdict

Verticalization is the right choice for roughly 40-60% of B2B SaaS companies past $10M ARR, particularly those with regulatory moats and industry-native founders. Horizontal is the right choice for roughly 15-25%, particularly infrastructure and PLG-led products. Hybrid is the right choice for roughly 30-45%, particularly larger platforms.

Pure-strategy bets without an honest assessment of the failure modes above are how companies lose 18-36 months of execution and millions of dollars of GTM investment. For most companies between $20M and $500M ARR in 2026, hybrid — a horizontal core plus 2-4 industry clouds — is the right strategy precisely because both pure strategies have predictable failure modes.

22. Final Decision Framework: The CRO/CEO Checklist

To synthesize the entire analysis into a checklist a CRO, CEO, or head of strategy can run through in a board meeting:

Run all 10 checks honestly — as a test, not a confirmation exercise. If 7+ favor verticalization, verticalize aggressively. If 4-6 favor verticalization, build a single industry cloud.

If fewer than 4 favor verticalization, stay horizontal and revisit at every $10M ARR milestone. The decision is never permanent — re-running this framework annually, and especially at each $10M ARR milestone, is the discipline that separates companies that compound from companies that drift.

Sources

1. Veeva Systems Annual Report 10-K (FY2024) — $2.4B+ ARR life sciences vertical SaaS, $25-30B market cap. investor.veeva.com
2. Procore Technologies 10-K (FY2024) — $1B+ ARR construction vertical, 16,000+ customers, $2T+ construction volume under management. investors.procore.com
3. Toast Inc. 10-K (FY2024) — $1.3B ARR, 120,000 restaurant locations, payments attach driving ARPU. investors.toasttab.com
4. ServiceTitan S-1 Filing (December 2024 IPO) — $772M ARR pre-IPO, $9B IPO valuation, ~110,000 technicians serviced.
5. Mindbody / Vista Equity Partners take-private transaction (2019) — $1.9B acquisition; smaller-TAM vertical exit pattern.
6. Salesforce 10-K (FY2024) — $35B+ ARR, $250B+ market cap, Salesforce Industries nine industry clouds at ~$5B ARR.
7. Salesforce acquisition of Vlocity (2020) — $1.3B acquisition, foundation of Salesforce Industries strategy.
8. HubSpot 10-K (FY2024) — $2.6B+ ARR, $30B+ market cap, horizontal SMB-to-enterprise playbook.
9. Notion private valuation (2024) — $10B+ valuation, ~$400M ARR; PLG horizontal monetization ceiling case study.
10. Slack acquisition by Salesforce (2021) — $27.7B deal; network-effect horizontal acquired by hybrid platform leader.
11. Atlassian 10-K (FY2024) — $4B+ ARR, $40B+ market cap; developer-focused horizontal motion.
12. Snowflake Industry Data Clouds — product documentation — horizontal data warehousing with verticalized industry overlays.
13. Microsoft Industry Clouds — Healthcare, Financial Services, Manufacturing, Retail, Sustainability, Nonprofit — $8B+ annual Industry Cloud revenue per Microsoft disclosures.
14. ServiceNow Industries product documentation — industry products across Banking & Capital Markets, Insurance, Telecom, Manufacturing, Healthcare, Public Sector.
15. Workday Industries — industry-specific products for healthcare, financial services, retail, hospitality, professional services, public sector, higher education.
16. HubSpot Industry Templates and Playbooks — lightweight verticalization model for SMB and mid-market horizontal SaaS.
17. Gartner Magic Quadrant — Vertical-Specific CRM (2024) — Veeva, Salesforce Industries, Microsoft, Oracle positioning.
18. Forrester Wave — Industry Cloud Platforms (2023-2024) — vendor positioning across industry-cloud strategies.
19. IDC Worldwide Vertical Software Spending Forecast (2024-2028) — industry-by-industry software spending projections.
20. Bessemer Cloud Index — Vertical SaaS Subsector Analysis — public-market multiples and growth rates by subcategory. bvp.com/cloud-index
21. SaaS Capital Vertical SaaS Industry Survey (2024) — benchmarks for vertical SaaS NRR, GRR, CAC, gross margin.
22. OpenView Product Benchmarks Report (2024) — PLG horizontal SaaS benchmarks for free-to-paid conversion and viral coefficient.
23. Bain Capital Ventures Vertical SaaS Thesis (2024) — investor framework for evaluating vertical SaaS opportunities.
24. Andreessen Horowitz Vertical SaaS Playbook — industry-cloud strategy and vertical platform thesis.
25. Tomasz Tunguz / Theory Ventures Vertical SaaS Analysis — public benchmarks and exit-multiple analysis.
26. Gainsight NRR Benchmarks (2024) — NRR by industry and category benchmarks.
27. HFS Research Industry Cloud Spend Forecast — industry-cloud spending trajectory through 2028.
28. Wall Street equity research — Veeva, Procore, Toast, ServiceTitan notes — sell-side multiples and growth analysis.
29. PitchBook Vertical SaaS M&A Tracker — acquisition multiples and deal volume by subcategory.
30. CB Insights State of Vertical SaaS Report (2024) — funding and exit-multiple data for vertical SaaS companies.
31. HIMSS Healthcare IT Spending Survey — healthcare vertical software-spend data.
32. Dodge Construction Network Technology Adoption Report — construction software adoption curves and spending.
33. National Restaurant Association Technology Adoption Study — restaurant software-spend and POS market data.
34. 21 CFR Part 11 — Electronic Records and Electronic Signatures — GxP compliance standard for life sciences software.
35. HIPAA Security and Privacy Rules — healthcare software compliance baseline.
36. FedRAMP Authorization Program — public-sector cloud compliance program. fedramp.gov
37. FINRA Rule 4511 — Books and Records — financial services software compliance baseline.
38. Andreessen Horowitz "The AI Architecture for Vertical SaaS" (2024-2025) — industry data model and vertical agent thesis.
39. Sequoia Vertical AI Thesis (2024) — investor framework for vertical AI agents.
40. G2 Grid Vertical Software Categories — user-rated vendor positioning in healthcare, construction, restaurant, real estate, and fintech verticals.

Related Pulse Library Entries

• (q88) — How do I decide between PLG and sales-led GTM?
• (q89) — How do I decide between SMB, mid-market, and enterprise focus?
• (q90) — How do I decide between owned product vs marketplace strategy?
• (q91) — How do I structure a pricing change without churning customers?
• (q94) — How do I prioritize an industry cloud roadmap?
• (q96) — How do I sequence vertical expansion across 3-5 industries?
• (q97) — How do I evaluate vertical M&A targets?
• (q98) — How do I retain horizontal customers when verticalizing?
• (q99) — How do I build vertical AI agents that win against horizontal foundation models?
• (q100) — How do I price vertical AI agents?
• (q101) — How do I build a vertical data model from scratch?
• (q102) — How do I integrate with vertical systems of record?
• (q103) — How do I price per-provider versus per-seat?
• (q104) — How do I build vertical compliance into product?
• (q105) — How do I evaluate vertical conference ROI?
• (q106) — How do I partner with industry associations?
• (q107) — How do I evaluate verticalization at every $10M ARR milestone?
• (q108) — How do I balance horizontal optionality with vertical execution?
• (q109) — How do I avoid the lifestyle-business trap in vertical SaaS?
• (q110) — How do I think about exit multiples for vertical SaaS?
• (q111) — How do I think about exit multiples for horizontal SaaS?
• (q1899) — What replaces SDR teams if AI agents replace SDRs natively?