How do I evaluate whether a new vertical is worth the GTM investment?

Direct Answer

Evaluating whether a new industry vertical is worth the GTM investment is a capital allocation decision disguised as a sales decision — treat it like an investment committee memo, not a sales experiment. Score the opportunity on six weighted factors: vertical TAM/SAM/SOM (20%), product fit versus net-new engineering required (25% — the heaviest weight, because the "engineering tax" kills more vertical bets than weak demand), competitive density and incumbent switching costs (15%), regulatory complexity and certification cost/timeline (10%), fully-loaded GTM cost to reach the first $1M-$3M in vertical ARR (20%), and expansion/retention potential once landed (10%).

Compute a weighted composite from 1 to 10: above 7.0 is a Go to fund a cheap research gate, 5.5-7.0 is a conditional yellow, below 5.5 is a No. The fastest disqualifiers are blunt: you cannot name 10 logo-quality target accounts and have not interviewed 5 of them; the product gap requires more than 6-12 engineering-quarters before a credible v1; regulatory entry (HIPAA, FINRA/SEC, FERPA, SOC 2, FedRAMP) costs more than $1M and 18 months before you can legally sell; or you have zero organic customers in the vertical despite years of horizontal selling.

Commit capital through three staged gates — Gate 1 is research plus 10 customer interviews (~$50K-$150K, 6-10 weeks); Gate 2 is a wedge pilot with 3-5 paying design partners (~$300K-$800K, 2-3 quarters); Gate 3 is a dedicated pod with vertical product, sales, and marketing (~$2M-$5M/year).

Never skip to Gate 3. Funding a dedicated team before a pilot has proven the wedge is the single most expensive vertical-expansion mistake — it is how companies burn $3M-$8M and 18 months to "learn" what 10 customer interviews would have told them for $100K. The honest base rate: most vertical expansions look attractive on a TAM slide and fail on engineering tax, incumbent moats, or focus dilution that quietly degrades the core business.

The right answer is "no" or "not yet" far more often than founders want to hear, and the discipline of saying no on weak verticals is what makes the rare "yes" pay off. Frame the bet to your board as TAM expansion with a capped, gated downside, never as an open-ended strategic adventure.

1. Why a Vertical Is a Capital Allocation Decision, Not a GTM Decision

A new vertical is not a marketing campaign you can turn off when it underperforms. It is a multi-year capital commitment that pulls engineering roadmap, sales headcount, marketing budget, executive attention, and brand positioning all at once. The companies that get vertical expansion right treat the decision the way a disciplined investor treats a new position: with an explicit written thesis, a scorecard, pre-committed exit criteria, and an honest accounting of opportunity cost.

The companies that get it wrong treat it as an opportunistic reflex — "we keep getting inbound from dentists, let's go after dentists" — and discover 18 months and $4M later that dentists wanted three integrations they never built, that the incumbent had a nine-year data moat, and that the core business stalled while the best engineers chased the new shiny thing.

1.1 The reframe that changes every downstream decision

The single most useful mental move in vertical evaluation is to stop asking "is this a good sales opportunity?" and start asking "is this the best use of the next $3M-$8M and 6-12 engineering-quarters we have to deploy?" The first question almost always returns "yes" — there is always *some* demand in *some* new vertical, and a motivated sales leader can always find a few interested prospects.

The second question is far harder and far more honest, because it forces a comparison against the core roadmap and against every other expansion option on the table. A vertical is a portfolio position; it competes for capital with going upmarket, expanding horizontally, deepening the core platform, and doing nothing.

Evaluate it as a position, not as a campaign.

This reframe matters because it changes who is in the room and what document gets written. A GTM decision gets made by a VP of Sales in a pipeline review. A capital allocation decision gets made by the executive team with the CFO present, against a written memo, with the board informed.

The vertical-expansion bets that fail are almost always the ones made in the first room when they belonged in the second.

The investment memo itself is the artifact that disciplines the decision. It should be three to six pages, written in prose rather than bullets, and it should state the thesis in a single falsifiable sentence ("We believe construction project owners will pay $40K/year for AI-driven submittal review because the manual process costs them three full-time roles and one missed submittal can trigger a six-figure change order").

It should contain the bottoms-up SOM, the six-factor scorecard with each score justified by evidence, the engineering-tax estimate in eng-quarters, the regulatory cost and timeline, the GTM cost model, the explicit opportunity-cost statement, and the pre-committed kill criteria for each gate.

The memo is read by the executive team before the meeting, and the meeting is spent debating the weakest scores, not re-presenting the strongest. A vertical that cannot survive a written memo and a hostile read should not survive at all — and writing the memo is itself one of the cheapest, highest-yield diligence steps available, because the act of writing forces the optimism out of the assumptions.

1.2 The five resources a vertical consumes

Be explicit about what a vertical actually spends. It is never just "some sales effort."

• Engineering capacity: The net-new engineering to build vertical data models, integrations, compliance features, and workflow logic — the "engineering tax," covered in depth in Section 4.
• GTM capital: Vertical-specialist sellers, vertical marketing, conference presence, content, and channel development — $1.5M-$3M+ per year for two to three years.
• Executive attention: A new vertical needs an executive sponsor and consumes leadership-meeting time, the company narrative, and organizational focus. This is the scarcest resource and the hardest to model.
• Brand positioning: A horizontal brand does not transfer into a vertical; you build vertical brand permission from scratch, and that costs both money and time.
• Organizational focus: A company can only metabolize so many priorities before everything slows. A vertical bet spends focus, and focus does not appear on any budget line.

The discipline of vertical evaluation is the discipline of pricing all five honestly. The related question of choosing between vertical expansion and other growth vectors is covered in (q88), and the bottoms-up TAM modeling that underpins the whole exercise is covered in (q89).

2. The Six-Factor Weighted Scorecard

The framework that survives contact with reality is a weighted six-factor scorecard. Each factor is scored 1 to 10 on gathered evidence, multiplied by its weight, and summed into a single number between 1 and 10. The scorecard's job is not to produce a magic number — it is to force an honest, written, comparable conversation so the decision is made on evidence rather than on the loudest executive's enthusiasm.

2.1 The six factors and their weights

2.2 Why Product Fit carries the heaviest weight

Product Fit gets 25% — more than any other factor — because the "engineering tax" is the single most underestimated line item in vertical expansion and the most common reason vertical bets quietly fail. Sales and product leaders, eager for a new logo, reclassify net-new engineering as "configuration" because a demo can be faked.

The cost of that optimism is a two-quarter build that becomes an 18-month slog. Weighting Product Fit heaviest is a deliberate forcing function: it makes the factor that most often kills the bet the factor the team must score most rigorously.

2.3 Composite thresholds and the fatal-flaw override

The override rule matters: any single factor scoring 1-2 triggers a mandatory review regardless of the composite, because a fatal flaw on one dimension — an impossible regulatory timeline, a sub-50% product fit, an unbeatable incumbent — can sink a bet that the weighted average flatters.

A vertical scoring 8 on five factors and 2 on regulatory complexity has a 7.4 composite and is still potentially un-enterable. The scorecard is a forcing function for honest conversation, not a substitute for judgment.

3. Factor 1 — Vertical Market Sizing (TAM, SAM, SOM)

Most vertical evaluations die — or worse, proceed wrongly — on the back of a bad market-size slide. The classic failure is the top-down number: "There are 250,000 dental practices in the US and they spend $X billion on software, so the TAM is enormous." That number is true and useless.

It tells you nothing about how many accounts you can actually win, at what price, on what timeline.

3.1 The discipline of bottoms-up SOM

The discipline is bottoms-up SOM, built from three multiplied components: the number of genuinely targetable accounts, the realistic annual contract value in this vertical, and the penetration rate you can credibly achieve over five years.

• Targetable accounts, not total accounts: Start with the total universe, then subtract relentlessly. Of 250,000 dental practices, how many are multi-location groups large enough to need your product and able to pay your price? Maybe 18,000. How many are in geographies and segments your GTM motion can reach? Maybe 12,000. How many are not locked into a long-term incumbent contract at any given time? Maybe 3,000 are "in window" per year. The targetable, in-window number — not the headline — is what feeds the model.
• Realistic vertical ACV: Vertical ACV is rarely the same as your core ACV. Sometimes it is higher because the vertical has acute pain and budget; sometimes structurally lower because the vertical is fragmented and price-sensitive. Build ACV from the vertical buyer's actual budget reality and the per-unit metric that fits the vertical.
• Penetration over five years: Be honest about the S-curve. A realistic vertical penetration path runs roughly 0.5% of targetable accounts in year one, 2% by year two, 5% by year three, 9% by year four, 14% by year five. Even 14% of a well-defined targetable base is an aggressive, well-executed outcome.

3.2 The SOM model worked end to end

3.3 The minimum-SOM threshold

If five-year vertical SOM is not at least $15M-$30M of ARR — enough to be a real second act, not a rounding error — the vertical is probably too small to justify pulling engineering and executive focus from the core. A vertical that clears $30M+ SOM with a credible penetration curve scores 8-10 on Factor 1; $15M-$30M scores 5-7; under $15M or top-down-only scores 1-4.

The exception is a strategically defensive vertical or one that unlocks a much larger adjacent motion, but those exceptions must be argued explicitly, never assumed. For the deep mechanics of building a board-credible bottoms-up TAM, see (q89).

4. Factor 2 — Product Fit and the Engineering Tax

Product fit is the factor that most often determines whether a vertical bet is a quarter-long pivot or a two-year slog, which is why it carries the heaviest weight. The assessment is concrete: enumerate the vertical's must-have requirements, then classify each as already met, configurable (met with setup, templates, or no-code configuration using features that exist in production today), or net-new engineering required.

4.1 The requirement audit

Run the exercise as a real audit, not a hand-wave. Pull the top 20-30 requirements a buyer in the vertical will evaluate you on — from RFPs, from competitor feature lists, from the 10 customer interviews you run in Gate 1. For each, assign the classification honestly.

The trap is "we can configure that" optimism: a requirement is only "configurable" if a customer success engineer can stand it up today with no engineering ticket. Everything else is engineering, and engineering has a cost, a timeline, and an opportunity cost.

4.2 The engineering tax in eng-quarters

Every vertical extracts an engineering tax — the net-new engineering required before the product is credible to a real buyer. Enumerate it in engineering-quarters (one engineer for one quarter = one eng-quarter) and price it honestly.

4.3 The engineering tax IS the opportunity cost

The critical move is not just totaling the number — it is comparing it against what those same engineering-quarters would produce on the core roadmap. Six eng-quarters spent on a vertical is six eng-quarters not spent on core retention features, core expansion features, or platform reliability.

If the vertical's expected return does not clearly beat the core roadmap's expected return on those same quarters, the honest answer is to keep the engineers on core. The engineering tax is the clearest expression of opportunity cost in the entire evaluation. For the detailed eng-quarter accounting methodology, see (q94); for the broader roadmap-tradeoff lens, see (q97).

5. Factor 3 — Competitive Density and Displacement

A vertical's competitive density determines how hard you fight for every deal and how durable your wins are once you get them. The analysis has three layers.

5.1 Who is already there

Map the incumbents: the vertical-specialist software companies that built their whole business around the vertical, the horizontal platforms that have bolted on a vertical SKU, and the legacy or homegrown systems customers still run. A vertical with one aging incumbent and a lot of spreadsheets is a very different fight than a vertical with three well-funded specialists who raised growth rounds in the last 24 months.

5.2 Switching costs are the real moat

Switching cost — not the incumbent's product — is the real moat, and it is built from four sources:

• Data gravity: Years of historical data living in the incumbent's system. The longer a customer has been there, the more painful migration becomes.
• Workflow embedding: The incumbent is wired into daily operations and adjacent tools; switching means re-wiring the organization.
• Integration centrality: The incumbent is the hub other vertical tools connect to; every integration is another anchor.
• Contractual lock-in: Multi-year deals, and the political cost to the buyer of a failed migration.

High switching costs do not make a vertical un-winnable, but they mean every deal is a rip-and-replace with a long cycle, and they should depress the competitive-density score.

5.3 Displacement difficulty

Given the incumbents and their switching costs, what is your actual path to win? The honest options: displace on a clearly superior product where the incumbent has stagnated; win the segment the incumbents under-serve; or win the wedge use case the incumbents treat as an afterthought and expand from there.

If you cannot articulate a specific, structural reason customers will switch despite the switching costs — not "we have a better UI" — the vertical scores low here regardless of how attractive the TAM looks.

The counterintuitive point: a vertical with zero credible incumbents is usually a warning sign, not an opportunity. It often means the vertical does not actually buy software the way you think, the budget is not there, or the pain is not acute enough to drive purchasing. Some competition validates that the vertical is a real market.

The detailed incumbent-displacement playbook is covered in (q121).

6. Factor 4 — Regulatory Complexity

Regulatory complexity is the factor most likely to be discovered late and most likely to blow up a timeline. Each regulated vertical gates entry behind a specific set of certifications, each with a real dollar cost and — more painfully — a real calendar timeline you cannot compress with money.

6.1 The regulatory cost-and-timeline table

6.2 Why timeline is the binding constraint

The scoring move is to total the dollar cost and the calendar timeline, and treat the timeline as the binding constraint. A vertical that costs $500K to enter but takes 18 months of certification before you can sell has an 18-month hole in its payback model that the dollar figure alone hides.

The honest threshold: if regulatory entry costs more than ~$1M and 18 months combined, the vertical is a major strategic commitment, not an experiment, and it needs to clear a much higher bar on every other factor.

A few specifics worth internalizing: SOC 2 Type II (governed by the AICPA Trust Services Criteria) is the baseline for selling to almost any serious B2B buyer and is the floor for any new vertical. HIPAA (HHS Security Rule and HITECH guidance) requires BAAs, technical safeguards, and the engineering to withstand a healthcare security review on every deal.

FINRA Rules 4511 and 3110 and SEC Rule 17a-4 impose books-and-records, communications-retention, and supervision requirements whose compliance review becomes the longest pole in the financial-services sales cycle. FERPA (34 CFR Part 99) governs student-data privacy. FedRAMP is the most expensive and slowest of all and should never be undertaken as a side bet.

The deep dive on entering regulated industries is covered in (q120).

7. Factor 5 — GTM Cost Modeling

The GTM cost of a vertical is not "we'll have the existing sales team also sell to this vertical." Selling into a new vertical means selling to an unfamiliar buying center, with unfamiliar objections, against unfamiliar competitors, with no reference customers and no brand permission. That is a different motion, and standing it up costs real money.

7.1 The fully-loaded GTM cost stack

Model the fully-loaded cost to reach the first $1M-$3M of vertical ARR:

7.2 The vertical CAC math nobody wants to model

The scorecard move is to compute the implied vertical CAC and CAC-payback from this spend against the modeled SOM and ACV — and to be honest that vertical CAC in years one and two will be 2-4x your blended core CAC, because you are paying the new-motion tax: specialist reps, longer ramps, longer cycles, lower close rates without references, and vertical marketing that has not yet compounded.

If the vertical cannot get to a defensible CAC-payback within roughly 18-24 months of dedicated investment, the GTM-cost factor scores low. The honest framing for the board: vertical economics look bad before they look good, and the plan must explicitly fund the "look bad" period.

Pretending the new vertical will have core-business CAC from quarter one is the most common way vertical financial models lie. The full CAC and CAC-payback modeling method for a new GTM motion is covered in (q92).

8. The Beachhead Customer Test

The single fastest, cheapest, most predictive test of whether a vertical is real is brutally simple: Can you name 10 logo-quality target accounts in this vertical, and have you actually talked to 5 of them?

8.1 The naming test and the conversation test

This test cuts through more bad vertical bets than any spreadsheet. It has two parts:

• The naming test forces specificity: 10 named accounts that would be credible logos, that fit the ICP, that are plausibly reachable — real companies, not "mid-size hospitals." If the team can only name three, the targetable universe is probably much smaller than the TAM slide claims, or the team does not understand the vertical's segmentation.
• The conversation test forces evidence: At least five real discovery conversations with buyers in those accounts before spending a dollar on the build. Those conversations answer the questions the scorecard depends on — the actual must-have requirements, the buying center, what they use today and why, what would make them switch, what they would pay.

8.2 Why this is the highest-ROI diligence in the process

Five honest customer conversations routinely kill a vertical bet that looked great on paper, and that is the test working correctly: it is far cheaper to learn "they will never switch off the incumbent" in a 45-minute call than in an 18-month, $4M failed expansion. Make this a hard gate.

No vertical proceeds past Gate 1 without 10 named accounts and 5 completed conversations, documented. It is the highest-ROI diligence in the entire process.

9. Channel Availability and Existing Customer Signal

Two diligence questions materially change both the cost and the confidence of a vertical entry, and both are too often skipped.

9.1 What channels can you ride into the vertical

Verticals are run by ecosystems. The diligence question: what existing channels can you ride into this vertical, rather than building distribution from zero?

• Systems integrators and consultants: In healthcare, construction, and financial services especially, SI relationships can be the difference between a 12-month and a 4-month sales cycle.
• Resellers and VARs: Established reseller channels already have buyer relationships and can dramatically lower CAC — at the cost of margin and control.
• Industry associations: Trade-association endorsements, member benefits, and conference access provide brand permission money cannot easily buy.
• Technology and platform partners: Being a certified, listed partner in the vertical's dominant platform marketplace is both a credibility signal and a distribution channel.

Do not assume channel availability — verify it in Gate 1 by talking to two or three potential partners, the same way you talk to potential customers. The channel-and-SI enablement playbook is covered in (q141).

9.2 The organic-customer signal

Before modeling a vertical from scratch, look at the data you already have. Do you already have organic customers in this vertical — accounts that found you, bought you, and stuck around without any vertical-specific GTM effort? Organic vertical customers are the single strongest validation signal available, because they are revealed preference, not stated preference.

Pull every current customer operating in the candidate vertical, and for each understand how they use the product, what they configured or worked around, what they asked for and did not get, and how their retention and expansion compare to your blended book.

The signal cuts both ways. A handful of healthy, expanding, organically-acquired vertical customers is worth more than any analyst report — it proves the core product already delivers value in the vertical, it gives you ready-made reference customers and case studies for Gate 2, and it gives you a free, honest source of requirements that no consultant report can match.

But if you have *no* organic customers despite years of horizontal selling, the optimistic read is "we never marketed there" and the realistic read is often "the product does not solve their problem" — and that should temper the product-fit score. And if you have organic customers but they are churning, struggling, or stuck at a low usage tier, that is a loud warning that the vertical's needs diverge from what you do well.

Treat existing customer signal as a multiplier on the rest of the scorecard: strong organic signal raises confidence in the product-fit and retention scores, while absent or negative signal should lower them. The team should pull this analysis before, not after, the scorecard is scored, because it is the cheapest evidence available and it materially recalibrates two of the six factors.

10. The Wedge Strategy and the Pilot

The right way to enter a vertical is almost never "build the full vertical product and launch." It is to land with a narrow wedge — a specific, painful, well-bounded use case your product can serve credibly today or with minimal build — prove it with paying customers, and expand from that beachhead.

10.1 The three properties of a good wedge

• Narrow: Bounded enough that you can be unambiguously the best at it without an 18-month build.
• Painful: Acute enough that the vertical buyer will pay and adopt without a heroic change-management effort.
• Expandable: Winning the wedge earns you the relationship, data, and credibility to sell the next use case, and the next, until you are the platform.

10.2 Risk staging through the pilot

The strategic logic is risk staging. A wedge pilot lets you validate the vertical with 3-5 paying design partners for a few hundred thousand dollars and two or three quarters, instead of betting $3M-$5M and 18 months on a full vertical product up front. The pilot answers what no analysis can: will real buyers actually pay, actually adopt, actually expand, actually refer?

It also produces the assets — reference logos, case studies, refined requirements, a tuned pitch — that make the Gate 3 investment dramatically de-risked. Resist the pressure to skip the wedge: going big before the wedge is proven is precisely how companies turn a recoverable $500K research-and-pilot cost into an unrecoverable $5M dedicated-team write-off.

The operational detail of running a design-partner pilot that genuinely de-risks a bet is covered in (q95).

11. Pricing Power, Sales Cycle, and Retention

Three factors determine whether the economics of a landed vertical compound or leak.

11.1 Pricing power in the vertical

A vertical is more attractive when you can charge more there than in your core market. Some verticals support premium pricing because the pain is acute, the budget is real, and the alternatives are weak — regulated industries and verticals where your product touches revenue-critical workflows often fall here.

Others are structurally price-compressed: fragmented, low-margin industries with thin software budgets. The same product can support a 2x ACV in one vertical and a 0.5x ACV in another, and that difference flows straight through the SOM model.

Vertical buyers also want to be priced on a metric they already use to think about their business — per-bed and per-provider in healthcare, per-location and per-seat in restaurants and retail, per-project in construction, per-account or per-transaction in financial services. A pricing metric that matches the vertical's mental model raises willingness to pay and makes the value story self-evident.

11.2 Sales cycle physiology

Every vertical has its own sales-cycle physiology, driven by the buying center's complexity and the vertical's procurement culture. Selling to independent restaurants is fast; selling to hospital systems, banks, or government agencies is slow — 9-18 months is common, with security reviews, compliance reviews, procurement, and committee dynamics each adding weeks.

The cycle in a new vertical is also longer than your steady state because you have no reference customers; budget the first cohort at 1.5-2x your eventual steady-state cycle.

11.3 Retention is where vertical bets are won or lost

Acquisition gets the attention, but retention is where vertical bets are actually won or lost. The sources of vertical retention strength:

• Regulatory lock-in: Once you are the system of record for a compliance-critical workflow, switching means re-validating, re-auditing, and re-training under regulatory scrutiny.
• Workflow embedding: When the product becomes the screen staff have open all day, switching cost becomes organizational and human.
• Data gravity: Years of accumulated vertical data make migration progressively more painful — a moat that strengthens automatically.
• Integration centrality: If you become the hub the vertical's other tools connect to, every integration is another anchor.

A vertical with multiple structural retention sources should score high on Factor 6; a vertical where the product is a peripheral, easily-swapped point solution should score low — and that low score should make you skeptical of the whole bet, because a vertical you cannot retain is one you are renting, not owning.

12. Build vs. Buy vs. Partner, and the Internal Capability Audit

Once a vertical clears the scorecard, two further questions remain: how do you acquire the vertical capability, and does the team have what it takes to execute.

12.1 The build/buy/partner decision

Many of the best vertical entries are sequenced — partner to test the vertical's pull, then build or buy once the thesis is proven. The full build/buy/partner decision framework for a new capability is covered in (q93).

12.2 The internal capability audit

A vertical bet is only as good as the team's ability to execute it. Before committing, run an honest internal capability audit across four dimensions: product and engineering (does anyone genuinely understand the vertical's workflows and data model), sales (do you have or can you hire reps with real credibility and a network in the vertical), marketing (can your team produce content a vertical insider finds credible), and leadership and advisory (is there an executive sponsor and access to advisors with deep vertical experience).

The point is not to require the team already be expert — it is to make the capability gap explicit and budget for closing it. The unforgivable mistake is the unaudited assumption that "we're smart, we'll figure out the vertical as we go." Verticals punish tourists, and the buyers can tell.

13. The Staged Investment Gates

The discipline that makes vertical evaluation safe is staged investment with real gates — committing capital in tranches, each unlocked only by evidence from the prior stage, so the downside is always capped and the team can never quietly skip from idea to dedicated team.

13.1 The three gates

13.2 The cardinal rule: never skip to Gate 3

Funding a dedicated team before a pilot has proven the wedge is the single most expensive vertical-expansion mistake — it is how companies burn $3M-$8M and 18 months to learn what Gate 1's customer interviews would have told them for $100K. Most vertical ideas should die at Gate 1, and most that get a Gate 1 should not get a Gate 3.

The gates are not bureaucracy; they are the mechanism that converts an unbounded strategic gamble into a series of bounded, evidence-gated bets. The generalized staged-gate process for any strategic bet is covered in (q91).

14. Opportunity Cost Framing and Investor Communication

The most important question in a vertical evaluation is often not "is this vertical good?" but "is this vertical better than what we would otherwise do with the same resources?"

14.1 Making opportunity cost an explicit line

Opportunity cost has three components: engineering (the 6-12 eng-quarters not spent on core retention, expansion, or reliability), GTM (the $1.5M-$3M/year not deployed against the core pipeline), and executive and organizational (the hardest to quantify and often the largest — leadership attention, the company narrative, organizational focus).

The framing discipline is to make opportunity cost an explicit line in the evaluation. State plainly what does *not* get done: "Funding this vertical means the core platform-reliability initiative slips two quarters and we do not pursue the enterprise-tier expansion this year." That sentence, written down and debated, is worth more than another TAM slide.

Often a vertical scoring a respectable 6.5 in isolation is still the wrong move because the core roadmap's return on the same resources is higher — and the only way to see that is to put them side by side.

14.2 How to frame the bet to the board

How you frame a vertical bet to your board shapes both whether you get support and how you will be held accountable.

• Frame it as TAM expansion with a capped, gated downside: "We have identified a vertical that expands our addressable market, we have evidence it is real, and we pursue it through staged gates so our committed downside is capped at the current tranche." That is fundable because it is disciplined.
• Pre-commit the gates and the kill criteria: Tell the board what each gate costs, what evidence unlocks it, and what evidence would make you stop. A board that agreed in advance to the kill criteria will support a disciplined "no" later.
• Address focus dilution head-on: Sophisticated investors' first worry is that a vertical distracts from the core. Show the opportunity-cost analysis; do not pretend there is no tension.
• Report against the gates, not vanity metrics: Report design-partner adoption and refined CAC-payback, not a pipeline number that looks good in a deck.

The communication of a strategic bet to the board without overpromising is covered in (q96).

15. The Vertical AI Angle and the Five-Year Outlook

The 2026-and-beyond version of this question has a new dimension: is there an AI-native entry point into the vertical — an industry-specific AI agent or AI-driven workflow that can serve as the wedge?

15.1 How AI shifts the calculus

• AI can be the wedge itself: Instead of replicating an incumbent's feature set, you may enter with an AI agent that automates a specific, painful, high-volume vertical workflow — claims review in healthcare, document review in legal, inspection workflows in construction — that the incumbent's older architecture cannot easily match.
• AI changes the engineering tax in both directions: AI-assisted development can lower the cost of building vertical logic, but doing AI well in a regulated vertical adds its own tax — data governance, model validation, auditability, hallucination control, and the compliance scrutiny regulated buyers apply to AI specifically.
• AI changes competitive density: Incumbents with deep workflow embedding but legacy architectures may be slow to ship credible AI, opening a displacement window — but well-funded AI-native entrants may be crowding into the same vertical for the same reason.
• AI does not repeal the gates: An AI-native vertical bet still needs the bottoms-up SOM, the beachhead test, and the wedge pilot. AI changes what the wedge looks like; it does not repeal evidence-gated investment.

The structural restructuring of GTM motions under AI disruption is explored in (q1899).

15.2 The five-year landscape

A vertical evaluation made today is a five-year bet, and the landscape is shifting. Vertical SaaS consolidation continues — the successful vertical platforms keep expanding across workflows and acquiring point solutions, raising the bar for what "entering" their vertical requires.

Hyperscaler industry clouds reshape the baseline — AWS, Microsoft, and Google Cloud have built industry-specific clouds that provide compliance scaffolding and data models, which can lower the engineering tax but also raise buyer expectations. AI verticalization accelerates — the next five years will see AI-native vertical applications proliferate, opening new wedges while adding AI-native competition to every vertical you evaluate.

The practical adjustments: weight the durability of your wedge and retention moat more heavily because the environment will get harder; build the SOM curve against a forward competitive picture, not a current snapshot; and prefer verticals where you can become a platform over verticals where you will always be a point solution.

16. Five Verticals Done Right, Five Done Wrong

16.1 Verticals done right

The pattern behind successful vertical companies is remarkably consistent: land a narrow wedge, build the vertical-specific product and data model, embed into the workflow until switching is unthinkable, then expand into adjacent use cases until you are the vertical's operating system.

The through-line: each won by being unambiguously vertical-native — the data model, the workflows, the integrations, the go-to-market all built specifically for the vertical — rather than by bolting a vertical SKU onto a horizontal product. The Toast POS-to-platform expansion is examined in depth in (q200).

16.2 Verticals done wrong

For every Toast there are many quieter failures. The patterns are composite but recurring:

• The TAM-mirage retreat: A company is seduced by a huge top-down TAM, funds a dedicated team, and discovers the targetable in-window SOM is a fraction of the headline. Lesson: bottoms-up SOM or you are building on a fantasy.
• The engineering-tax overrun: A two-quarter build becomes an 18-month slog at triple budget, by which point the window has narrowed and the core roadmap has suffered. Lesson: enumerate the tax in eng-quarters honestly.
• The regulatory-quicksand stall: A company commits to a regulated vertical without scoping the certification timeline and spends a year in compliance before selling a single deal. Lesson: regulatory timeline is a binding constraint money cannot compress.
• The incumbent-moat bounce: A better product with no answer to the incumbent's switching costs; deals stall in "this is great but migration is too risky." Lesson: a better product is not a displacement strategy.
• The focus-dilution collapse: A vertical pulls the best engineers, strongest reps, and executive attention off the core; the vertical underperforms and the core stalls too. Lesson: focus dilution is the most expensive and least visible cost of a vertical bet.

The meta-lesson: vertical failures are rarely caused by one catastrophic error. They are caused by optimistic assumptions on several factors at once that compound. The scorecard's discipline of forcing an honest, evidenced score on each factor is precisely the antidote.

17. Counter-Case: When a Vertical Looks Attractive But Isn't

The scorecard and the gates exist because vertical bets fail in predictable, recurring ways — and almost all of them start with a vertical that looked genuinely attractive. A serious operator should stress-test every promising vertical against these failure patterns before funding even Gate 1.

17.1 The seven traps

• The TAM mirage: The most seductive trap. A vertical presents a huge top-down market, the number is real — which makes it dangerous — and it tells you nothing about the targetable, in-window, can-actually-pay SOM. If the evaluation cannot produce a bottoms-up SOM, the TAM is a mirage and the bet should not proceed.
• The underestimated engineering tax: Sales and product leaders classify net-new engineering as "configuration," fake the demo, and commit to a two-quarter build that becomes an 18-month slog. Any vertical where the team is optimistic about the build, rather than rigorous in eng-quarters, is a red flag.
• Regulatory quicksand: Committing to a regulated vertical without scoping the certification timeline. The company spends a year in compliance before selling a deal, burning runway while the payback model silently breaks. Over ~$1M and 18 months of certification before first revenue is quicksand unless every other factor is exceptional.
• Incumbent moats a better product cannot cross: A vertical can have weak-looking incumbents and still be nearly un-enterable, because the moat is the switching cost, not the product. "This is great but we can't rip out the incumbent" is the sound of a vertical bet dying slowly.
• Focus dilution killing the core: The most expensive failure and the least visible while it happens. The vertical underperforms, which is bad; the core, starved of focus, also stalls, which is worse. This cost almost never appears on the scorecard unless deliberately forced there.
• The "zero competition" false positive: A vertical with no credible incumbents is usually a warning, not an opportunity. It often means the vertical does not buy software the way you assume, or the pain is not acute enough. Some competition validates the market.
• The organic-signal vacuum: A vertical can look great on every analytical dimension and still be missing the one piece of evidence that matters most — organic customers. Years of horizontal selling with zero organic customers in the vertical should discount the product-fit score, not be taken on faith.

17.2 The honest verdict

The uncomfortable truth of vertical evaluation is that the right answer is "no" or "not yet" far more often than founders, boards, and ambitious GTM leaders want to hear. Most verticals that get evaluated look attractive — that is exactly why they get evaluated — and most still should not be funded past a cheap research gate.

The discipline is not in finding reasons to say yes; it is in saying no early, cheaply, and with evidence, so organizational energy is not consumed by a slow-motion failure. The companies that win at vertical expansion are not the ones that say yes the most; they are the ones whose rare yes is backed by the discipline of many disciplined nos.

When a vertical looks attractive, assume it might be one of these traps until the evidence proves otherwise. The single biggest counter-case — focus dilution — and how to avoid it is the subject of a dedicated treatment elsewhere in the library, as is the broader pattern of vertical-entry failures.

18. The Final Decision Framework

Pulling it all together, the explicit checklist for deciding whether a new vertical is worth the GTM investment:

18.1 The nine-step checklist

18.2 The honest base rate

Most verticals that get evaluated should not get funded past Gate 1, and most that get a Gate 1 should not get a Gate 3. The framework's value is not in helping you say yes — it is in helping you say no cheaply, early, and with evidence, so that the rare vertical that clears every gate gets the focus and capital it needs to actually become a second act.

A disciplined no costs a slide deck. An undisciplined yes costs millions of dollars, multiple years, and sometimes the momentum of the core business. Evaluate accordingly.

The adjacent question of choosing between vertical expansion and going upmarket is covered in (q88), and the retention benchmarks that calibrate Factor 6 are detailed in (q98).

Sources

1. "Crossing the Chasm" — Geoffrey Moore — Foundational text on beachhead market selection and the discipline of landing a narrow segment before expanding; the wedge strategy is a direct application.
2. "Play Bigger" — Al Ramadan, Dave Peterson, Christopher Lochhead, Kevin Maney — Category design and the strategic framing of market-expansion bets.
3. Bessemer Venture Partners — State of the Cloud and Vertical SaaS research — Ongoing analysis of vertical SaaS as a category, including the platform-expansion pattern that defines successful vertical companies.
4. a16z — Vertical SaaS and "The New Business of AI" essays — Andreessen Horowitz analysis of vertical software economics, AI-native entry points, and why vertical specialization creates defensibility.
5. OpenView Partners — SaaS Benchmarks and Expansion Strategy research — Benchmark data on CAC, CAC-payback, sales-cycle length, and net revenue retention used to calibrate vertical economics.
6. Toast, Inc. — S-1 filing (SEC EDGAR) — Primary-source documentation of the restaurant-vertical wedge: POS as beachhead, expansion into payroll, payments, capital, and online ordering.
7. Veeva Systems — S-1 and 10-K filings (SEC EDGAR) — Documentation of the life-sciences vertical strategy on a platform foundation and the role of regulatory specialization in pricing power.
8. Procore Technologies — S-1 filing (SEC EDGAR) — The construction-vertical case study: the workflow-complexity wedge of RFIs, submittals, and change orders.
9. ServiceTitan — S-1 filing (SEC EDGAR) — The home-services vertical case study: operating-system positioning for a large, fragmented, under-served vertical.
10. Samsara — S-1 filing (SEC EDGAR) — The connected-operations / fleet vertical case study: hardware-plus-software defensibility in physical-operations verticals.
11. AICPA — SOC 2 framework and Trust Services Criteria — Authoritative source on SOC 2 Type II scope, observation periods, and cost drivers for the baseline B2B security certification.
12. HHS — HIPAA Security Rule and HITECH Act guidance — Primary source on healthcare compliance obligations gating the healthcare vertical.
13. FINRA Rules 4511 and 3110; SEC Rule 17a-4 — Primary sources on books-and-records, communications-retention, and supervision requirements gating the financial-services vertical.
14. US Department of Education — FERPA regulations (34 CFR Part 99) — Primary source on student-data privacy obligations gating the education vertical.
15. FedRAMP.gov — Authorization process documentation — Primary source on the cost and multi-year timeline of public-sector cloud authorization.
16. PCI Security Standards Council — PCI-DSS v4.0 — Primary source on payment-card data handling requirements.
17. Gartner — Magic Quadrant and Market Guide methodology — Industry framework for mapping competitive density and incumbent positioning within a vertical.
18. First Round Review — essays on go-to-market motion and vertical expansion — Operator-sourced writing on the organizational cost of standing up a new GTM motion.
19. SaaStr — content on net revenue retention, expansion revenue, and the cost of new GTM motions — Practitioner benchmarks on retention and expansion economics.
20. McKinsey & BCG — industry cloud and vertical software market analyses — Consulting research on hyperscaler industry clouds and vertical SaaS consolidation trends.
21. AWS, Microsoft, and Google Cloud — industry cloud product documentation — Primary sources on healthcare, financial-services, retail, and manufacturing industry clouds and their compliance scaffolding.
22. "The Lean Startup" — Eric Ries — The validated-learning and staged-investment logic underlying the gate framework.
23. Harvard Business Review — "Blue Ocean" and market-entry strategy literature — Academic framing of competitive density and displacement strategy.
24. CB Insights — startup failure post-mortem analyses — Aggregated data on why companies fail, including market-sizing errors and focus dilution.
25. Battery Ventures and ICONIQ — vertical software and growth-stage GTM research — Growth-equity perspective on vertical SaaS unit economics and scaling.
26. Epic App Orchard / EHR partner program documentation — Primary source on the certified-integration approval timelines that add to the healthcare engineering tax.
27. "Obviously Awesome" — April Dunford — Positioning methodology relevant to building vertical-specific brand permission.
28. Public investor letters and shareholder communications from vertical SaaS leaders — Primary-source framing of how vertical-expansion bets are communicated to investors.
29. NRF, AHA, AGC, and other industry-association materials — Examples of the trade-association channel infrastructure that vertical entrants can leverage.
30. Tomasz Tunguz — blog analyses on SaaS CAC, payback periods, and expansion — Quantitative benchmarks for calibrating vertical economics.
31. Andreessen Horowitz — "The Vertical SaaS Knowledge Network Effect" and related essays — Analysis of why vertical incumbents compound defensibility through data and workflow embedding.
32. SEC EDGAR — public 10-K filings of vertical SaaS leaders — Primary-source disclosure of retention, net revenue retention, and expansion economics in mature vertical companies.