Dear SaaStr: We Can Sell to a New Vertical. Should We?

You know that feeling when a shiny new vertical walks by and winks at your pipeline?
Suddenly your team is saying things like, “We’re already kind of selling there,” and “It’s the same product,”
and the most dangerous sentence in B2B: “How hard could it be?”

Expanding into a new vertical can be a huge winbigger TAM, faster growth, more resilience when one market cools off.
It can also be an expensive hobby that turns your roadmap into a group project where nobody did the reading.

So let’s answer the actual question behind the question:
Should you sell to a new vertical now, or are you about to adopt a second market like it’s a needy rescue puppyadorable, costly, and destined to chew up your weekends?

The “Dear SaaStr” Letter (A Version You’ve Definitely Heard)

Dear SaaStr,
We’re doing well in our current vertical. We’ve got a repeatable sales motion, our product is stable, and we’re seeing inbound from a totally new industry.
A couple of prospects there said, “If you just add one small feature…” (they said it like a lie).

We can sell into this new vertical. Should we?

Tempted, But Tired

The Answer in One Line

Yesif it’s adjacent, already pulling you in, requires minimal product change, you can staff it without starving the core, and it can become meaningful revenue.
Otherwise, treat it like dessert: enjoyable, optional, and not a foundation for your diet.

Start With 5 Gating Questions (Before You Touch the Roadmap)

1) Is the new vertical truly adjacent?

“Adjacent” doesn’t mean “they use laptops.” It means your buyer persona, pain, and sales motion are close enough that you can reuse
most of what already works:

• Same buyer type? (e.g., Ops leader to Ops leader, Finance to Finance)
• Similar sales cycle? (procurement, approvals, proof-of-value expectations)
• Similar risk profile? (compliance, data sensitivity, contractual overhead)
• Similar “why now”? (the trigger that makes them buy this quarter)

If the new vertical has a completely different buyer (say, you sell to RevOps and the new market buys through IT Security),
it’s not “a new vertical.” It’s a new company you’re building inside your company.

2) Do you already have some traction there?

The best vertical expansions are rarely pure invention. They’re more like following footprints in the snow.
Look for pull, not push:

• Inbound demos from that industry
• Users signing up from those domains (if you’re product-led)
• Referrals from a customer who also serves that vertical
• Two or three deals that closed with light (not heroic) effort

If you have zero traction, you’re not expanding. You’re starting a new GTM experiment from scratchfine, but call it what it is.

3) Can your product deliver value without major changes?

The moment you hear, “It’s the same product, just…,” check your wallet.
The right expansion usually needs:

• Minor configuration
• A small set of templates/workflows
• One or two integrations that unlock adoption
• Messaging that matches their reality

The wrong expansion needs:
custom fields that multiply forever, a one-off reporting module “just for this customer,” and a support team that starts
recognizing legal clause numbers the way sports fans recognize jersey stats.

Rule of thumb: if the product work is measured in quarters (not weeks), you’re probably early.

4) Can you staff it without taking your eye off the core?

New verticals don’t fail because the product can’t do it. They fail because the team can’t do it and keep winning where they already win.
A vertical expansion needs dedicated ownership across:

• Sales: someone who learns the language and doesn’t confuse “pipeline” with “hope.”
• Marketing: vertical-specific proof points (case study, webinar, landing page, ROI story).
• CS/Implementation: onboarding that fits the vertical’s workflow and constraints.
• Product: a protected slice of roadmap timeor you’ll steal from core customers and call it “strategy.”

If you can’t staff it, you’ll “kind of” do it. And “kind of” is not a go-to-market motion.

5) Can it become meaningful revenue?

A new vertical is worth the distraction only if it can matter. A practical bar:
could it credibly become ~10% of revenue within a reasonable time window?
If it can’t, it’s more like a side quest than a strategy.

The Hidden Costs Everyone Underestimates (Because Optimism Is Free)

Selling to a new vertical isn’t just “selling.” It’s building a mini operating system for that market.
Here’s what tends to show up on your invoice later:

Messaging debt

Your current homepage might say, “Automate workflows.” Cool. Every SaaS product since fire does that.
Vertical buyers want: “Automate this exact workflow, for this exact role, with this exact outcome.”

Proof debt

New verticals don’t want your best case study from a different industry. They want a mirror.
No mirror? Expect longer cycles, more objections, and more “send me something similar.”

Process debt

New buyers create new deal shapes: security reviews, procurement steps, implementation expectations, stakeholder maps.
If your current motion is fast and scrappy, a regulated or procurement-heavy vertical can slow you down like you’re running through molasses in dress shoes.

Roadmap debt

This is the big one. A few vertical tweaks can be healthy. But a pattern of “just one more” requests becomes:
two products, one engineering team, and zero happiness.

A Practical 90-Day Vertical Test (So You Don’t Bet the Company)

If you’re leaning yes, don’t “roll out.” Run an experiment.
Your goal is to learn if there’s a repeatable win patternnot to win every deal.

Step 1: Pick one wedge use case (not the whole industry)

“We’re going after Healthcare” is not a plan. It’s a genre.
Pick a single use case where your product already overperforms, like:

• Scheduling + capacity planning for outpatient clinics
• Compliance evidence tracking for specialty insurers
• Asset maintenance workflows for multi-site facilities

The wedge gives you a crisp ROI story and limits product sprawl.

Step 2: Define your ICP for this vertical slice

Don’t confuse “any company in the vertical” with your ideal customer profile.
Your ICP should specify firmographics and buying reality:

• Company size range (and why)
• Systems they already use (integration reality check)
• The buyer and champion roles
• A trigger event (growth, audits, headcount constraints, new regulation, etc.)

Bonus points if you can describe your ICP in one sentence that a new AE can understand without a 47-slide deck.

Step 3: Build the “whole product” pack (minimum version)

Vertical buyers aren’t just buying features. They’re buying an outcome.
Your minimum “whole product” pack could be:

• One vertical landing page with specific pain/ROI language
• Two templates/workflows that reduce time-to-value
• One demo script tailored to the wedge use case
• One implementation checklist that matches their reality

Step 4: Staff it like a real thing (but keep it small)

The lean test team can look like:

• 1 AE (or founder + AE) focused on that vertical slice
• 1 solutions engineer shared part-time
• 1 marketer for vertical messaging/content (even if fractional)
• CS lead to define onboarding + success criteria

“Everyone owns it” usually means “no one owns it.”

Step 5: Set stop/go metrics ahead of time

Decide what success looks like before the first demo, while you’re still rational.
Examples:

• At least 15 qualified conversations with your ICP in 90 days
• 3 serious opportunities that match your normal ACV profile
• 1–2 lighthouse customers willing to be references
• No roadmap items larger than “small fixes + templates” during the test

If you hit the metrics, expand. If you don’t, pause or narrow the wedge further.
The point is to learn, not to “prove you were right.”

What “Adjacent” Looks Like in the Real World (With Examples)

Here are a few patterns that tend to be adjacent (and therefore easier):

• Same department, different industry: selling a RevOps tool from SaaS to marketplaces (still RevOps).
• Same workflow, different context: scheduling in home services vs. field maintenance (similar operational backbone).
• Same compliance bar: moving from mid-market fintech to adjacent regulated segments where the security posture is similar.

And a few patterns that are often not adjacent:

• New buyer persona: Marketing-led sale becomes IT-led sale.
• New delivery model: self-serve becomes heavy implementation.
• New risk/compliance reality: light contracts become long security reviews and complex legal terms.

Common Vertical-Expansion Faceplants (So You Can Avoid Them)

Faceplant #1: “We’ll just customize for the first few customers.”

That’s how you end up maintaining 12 versions of the same feature and calling it “enterprise readiness.”
If the vertical requires deep customization, either productize it quickly or stop.

Faceplant #2: You “peanut-butter” the roadmap

When you try to please the core market and the new vertical with the same sprint,
you create lots of lukewarm customers and very few thrilled ones. Concentrated value wins.

Faceplant #3: You copy-paste positioning

Vertical buyers have their own vocabulary. If your messaging doesn’t sound like their world,
your CAC goes up and your win rate goes downquietly, and then suddenly.

Faceplant #4: You hire the wrong “vertical expert”

Industry experience helps, but only if the person can still sell your product, your way.
Beware someone who wants you to rebuild everything to match “how it’s always done.”

Faceplant #5: You underestimate customer success

Adoption patterns differ by vertical. If onboarding isn’t tailored, churn will teach you a very expensive lesson.

If the Answer Is “Not Yet,” Here’s How to Still Capture the Opportunity

“No” doesn’t have to mean “never.” It can mean “not staffed, not packaged, not measured.”
Options that keep you opportunistic without derailing focus:

• Inbound-only lane: take deals that fit the existing product with minimal change, but don’t promise a roadmap.
• Partner-led entry: work with a consultant/SI/ISV that already has vertical trust and can bring qualified demand.
• Content probe: publish 2–3 vertical-specific pieces and see if the right leads raise their hands.
• Customer-led adjacency: expand with customers that operate in multiple verticals and can introduce you.

Conclusion: A Simple Decision Rule You Can Actually Use

If the new vertical is pulling you in, looks adjacent in buyer and motion, needs only modest product work,
can be staffed without starving the core, and has a credible path to meaningful revenuetest it.
Start narrow, measure aggressively, and earn the right to scale.

If it’s not adjacent, has no traction, requires major product rebuilds, and you’re stretched thindon’t confuse ambition with strategy.
Protect the core, and keep the new vertical in a controlled experiment lane until the signal is real.

Experiences and Field Notes: What Founders Commonly Discover When Going After a New Vertical (500+ Words)

When founders talk about expanding into a new vertical, the first stories are usually about upside:
“The deals are bigger,” “They have budget,” “They’re desperate for a solution.”
And honestly, sometimes that’s all trueespecially if your product solves a painful workflow that’s been ignored by generic tools.
But the most useful lessons tend to show up after the first few calls, when the novelty wears off and the operational truth arrives.

One common pattern: the first customer in the new vertical looks easy because they’re an outlier.
They’re unusually tech-forward, they already think like your existing customers, and they’ll forgive rough edges because they want the outcome badly.
That first win can be a giftor a trap. The trap is assuming the whole vertical behaves like your outlier.
Founders who succeed treat Customer #1 as a learning lab, not a market proof.
They ask: “What made them different?” and “Can we find ten more like them without heroic effort?”

Another recurring lesson: the vertical doesn’t buy your producta specific role buys your product.
Teams often say “we’re going into manufacturing” when what they really mean is “we’re selling to plant operations managers who need fewer downtime surprises.”
Getting precise about the buyer and champion does two things:
it sharpens messaging (you can describe a day-in-the-life problem), and it prevents the dreaded situation where you’re pitching three departments at once and nobody owns the decision.

Many founders also report a “language tax.” Your product might fit, but your words don’t.
If your demo talks about “tickets,” “pipelines,” or “campaigns,” and the vertical talks about “work orders,” “cases,” or “compliance checks,”
you’ll feel friction that has nothing to do with features. The best teams don’t just translate the website.
They translate the entire go-to-market: discovery questions, ROI narrative, implementation plan, and success metrics.
The fastest way to earn trust in a new vertical is to sound like you’ve been therewithout pretending you’ve been there.

Then there’s the “one small feature” phenomenon.
In almost every expansion story, there’s a request that feels tiny but isn’t: “Can you support this reporting format?”
“Can you add approval workflows like we do today?” “Can you integrate with this legacy system?”
The teams who thrive get disciplined quickly. They either (a) build it in a way that’s broadly reusable, (b) make it configurable,
or (c) don’t build it at all and adjust the target ICP to customers who don’t need it.
What they don’t do (at least not for long) is build bespoke one-offs for every early deal.
Because that’s how your product becomes a Franken-suite held together by Jira tickets and regret.

Finally, founders frequently discover that vertical success is less about “entering” and more about “compounding.”
Once you have two credible references, your sales cycle shortens.
Once you have a proven onboarding checklist, CS stops reinventing the wheel.
Once you have a template that matches the workflow, time-to-value drops.
Vertical expansion works when you can repeat a win pattern with less effort each time.
So the real milestone isn’t “we closed a deal in the new vertical.”
It’s “we can close the next deal with a playbook, not a miracle.”

If you keep that mindsetnarrow wedge, measurable experiment, repeatable motionyou’ll make the decision with data,
not vibes. And vibes, while fun, are notoriously hard to forecast in QBRs.