Vertical Market Segmentation Framework

Vertical Market Segmentation

Segmentation is the decision with the most riding on it in a vertical SaaS company, and the one most often skipped. A bad segmentation locks you into the wrong buyer, the wrong product surface area, and the wrong comp plan for years. A good segmentation is the foundation every downstream system (ICP, pricing, motion, org) compounds on.

1. The Shift: From Demographic Buckets to Operating Segments

The classic SMB / Mid-Market / Enterprise split was built for horizontal SaaS where the buyer is a function (sales, marketing, IT) and segment is a proxy for deal size. In vertical SaaS the buyer is an operator, the workflow is industry-specific, and the meaningful segmentation is operational, not demographic.

The AI-native motion makes this even sharper. Once you can enrich every account in your TAM with vertical-specific signals (license type, equipment installed, regulatory status, location count), the segmentation can be operational, dynamic, and machine-maintained. The CRO doesn't pick segments in a slide once a year. The system surfaces and resurfaces segments as the market moves.

This playbook walks through how we build an operating segmentation, one that the rest of the GTM org (pricing, motion, comp, product) can run against.

2. The Operating System: The Segmentation Stack

The shift in posture: segmentation moves from an annual slide to a living asset every team operates on.

3. The Plays

Play 1: Define Segments by Operating Reality, Not Employee Count

The Move: Replace generic SMB / MM / Enterprise tiers with segments defined by the operating reality of the buyer. For a construction SaaS that might be "single-trade specialty" / "multi-trade GC" / "regional builder" / "enterprise GC." For a restaurant SaaS that might be "single location independent" / "multi-unit franchisee" / "regional chain" / "enterprise chain."

Why It Works: The motion, pricing, product surface, and reference set are wildly different across operating segments even when employee counts look similar. A 50-employee specialty subcontractor buys nothing like a 50-employee multi-trade GC. Segmenting by employee count creates blended cohorts that no motion can win cleanly.

AI Integration: A segmentation agent enriches every account in your TAM with vertical-specific signals (license type, trade mix, jobsite count, franchise affiliation) and assigns segment membership continuously. New signals push accounts between segments as the operating reality changes. Link to Module 2, The Context OS.

Vertical Example: Procore's direct sales team is "specialized by geography, followed by size and type of stakeholder," and the company says it typically does not charge "a per-seat or per-user fee" (Procore 10-K, FY2025). Stakeholder type there means the general contractor, the specialty contractor and the owner, three buyers who look alike on a headcount report and don't buy alike.

Segment Definition Schema:

Play 2: Size Each Segment With Real TAM Math

The Move: Build the TAM, SAM, and SOM for each segment using public data sources native to the vertical (license registries, association membership, permit data, equipment install bases, regulatory filings). Update annually at minimum.

Why It Works: Horizontal SaaS founders default to top-down TAM math from Gartner or IDC, and vertical SaaS founders can't. The good news is that vertical markets usually have public registries that give you a clean bottom-up number. The bad news is that it takes real work, so plenty of teams skip it and quote the top-down number anyway.

AI Integration: A TAM agent ingests vertical data sources (state license registries, OSHA filings, USDA permits, FDA registrations, Yelp business listings, equipment install bases) and produces a continuously updated TAM per segment. Reviewed quarterly. Link to Module 2, The Context OS.

Vertical Example: Toast's IPO filing shows the bottom-up version. It multiplied average subscription revenue per location by roughly 860,000 U.S. restaurant locations, then sized payments as non-cash restaurant sales times its take rate (Toast S-1, 2021). That's the point of the method, because a bottom-up number shows its inputs and people can check them.

TAM Sources by Vertical (Examples):

Play 3: Map a Motion to Each Segment Explicitly

The Move: For every segment write a one-page motion brief: who calls, what they sell, what they charge, what reference proof closes the deal, what the post-sale handoff looks like. No segment ships into the field without one.

Why It Works: The single most common GTM failure is running one motion across multiple segments. The 50-AE org "covering" SMB through Enterprise with one playbook is the standard pattern, and the standard reason segment-level economics quietly diverge from plan. An explicit motion-per-segment forces honesty.

AI Integration: Motion briefs are versioned knowledge nodes. The discovery skill pack for each segment is tuned (different qualifying questions, different proof points, different objections). The pre-call agent reads segment membership and serves the right brief. Link to Modules 1 and 3.

Vertical Example: ServiceTitan is best known for residential trades, and it also hires a dedicated enterprise sales team for large mechanical and commercial service businesses (ServiceTitan enterprise sales listing). Two buyers that different get two motion briefs, even inside one company.

Play 4: Price the Segment, Not the Logo

The Move: Build segment-specific pricing models with the segment-specific value lever (locations, volume, jobsite count) as the primary unit, not seats. Publish list pricing per segment. Discount only against segment list.

Why It Works: Generic seat pricing across mixed segments leaks margin in two directions. You under-price high-value segments (the multi-location operator gets a deal designed for a single-location operator) and over-price low-value segments (the single-location operator sees a price built for a 200-location chain). Segment-aware pricing fixes both leaks.

AI Integration: A pricing agent watches deal data per segment and surfaces deviation patterns to deal desk. Link to Module 4, The Measurement System, and the Pricing Strategy playbook.

Vertical Example: Toast charges a monthly software fee plus a card-processing rate on every transaction, and quotes multi-location groups on location count and volume. Mindbody prices per location, and its entry plan includes unlimited users (Mindbody pricing), so neither one prices on seats.

Play 5: Review Segments Quarterly, Re-Cut Annually

The Move: Hold a quarterly segment review where RevOps walks through per-segment performance (CAC, win rate, ACV, NRR, ramp), and flags any segment whose economics have drifted. Re-cut segments annually at minimum.

Why It Works: Markets move, and segments that worked at one stage of growth break at the next. Companies that don't re-cut segments can end up with one big segment that loses money and one small segment that funds the company, and it can take several quarters before anyone notices.

AI Integration: A segment economics agent assembles the quarterly review deck. Drift triggers (CAC up more than 15%, win rate down more than 10%, NRR below target) auto-flag for the review. Link to Module 4.

Vertical Example: Veeva's filings describe separate R&D and commercial sales teams, each divided by customer size, plus a distinct team selling into regulated industries outside life sciences (Veeva 10-K, FY2020). That last team can be what a re-cut looks like from the outside. It's a segment that grew big enough to earn its own motion.

4. The Operating Scorecard

5. The Hiring + Org Implications

Segmentation drives org design, not the other way around. Once segments are defined operationally, the org structure (pod design, manager span, CSM ratio, deal desk) follows. The CRO who imposes a generic org structure on top of unsegmented motion will end up rebuilding it.

You hire: Segment Owners (player-coach AEs who own the motion brief for their segment), Vertical RevOps Lead.

You retire: the "covering territory" model in any vertical where segments operate distinctly. The generic mid-market AE assigned mixed-segment accounts.

Comp shifts: pay against per-segment scorecard, not against a blended quota. Link to Module 5.

6. 30-Day Activation Path

• Draft initial segment definitions using operating reality (not employee count) for the top vertical
• Enrich the TAM with one to two vertical-specific signals per segment
• Build the bottom-up TAM math per segment from public sources
• Write the motion brief for each segment (one page each)
• Define per-segment pricing with the right unit (location, transaction, jobsite, etc.)
• Stand up the segment economics dashboard with the five scorecard metrics
• Schedule the first quarterly segment review

7. Resources

• Module 1: The Skills Layer
• Module 2: The Context OS
• Module 3: The Operations Playbook
• Module 4: The Measurement System
• Module 5: The AI-Native Org
• The worksheet version of this playbook is the Notion template in the download box on this page.