Teaching the Market to Buy: Buyer Education in Vertical SaaS

← All posts

The HVAC company owner has been running field dispatch on a whiteboard and a group text for 22 years. His crew works. His customers mostly call back. He knows what day is going to be messy before it starts. He's not looking for software. He doesn't know he should be.

That's your first customer archetype in most vertical SaaS markets. They have the problem. They don't have the category. You're not competing against another product — you're competing against "this is just how it works in this business."

The sales problem isn't competitive. It's educational. And most early-stage founders are building a sales motion designed for a competitive problem they don't have.

What category creation actually looks like at the SMB level

Category creation is usually described as a marketing concept — you define a new space and become the leader in it. At the enterprise level, it involves analyst reports, thought leadership campaigns, and years of brand investment.

At the SMB level in a vertical market, it looks nothing like that. It looks like a founder calling 15 shop owners and saying "the thing you've been doing with spreadsheets for 15 years — I built software for that." No market positioning. No category naming. The direct claim that the specific pain they have is the exact thing you've built for.

The educational sale starts with recognition. Not "here's a software solution." It starts with naming the cost of the problem in language the buyer uses. They don't call it "operational inefficiency" — they call it "I spent three hours on Thursday tracking down why a truck was in the wrong city."

Before you sell the solution, make sure the buyer agrees they have the problem. That sounds obvious. Most demos skip it. They show features before the buyer has acknowledged — to themselves, out loud — that the current state is actually costing them something.

Building the case before you pitch

In competitive markets, the buyer comes in pre-educated. They've looked at three competitors, they know what the category does, they have a budget. Your job is differentiation.

In an educational market, the buyer hasn't formed a budget line item yet. The sales process has to include the budget creation step — the conversation where you help a business owner add up what the current state actually costs: hours spent on coordination, errors that create callbacks, customer churn rate from scheduling failures, owner time on tasks software should handle.

This is where your operator founder background becomes a direct selling tool. You can say "when I was running operations at a company like yours, the coordination problem alone cost about 8% of revenue in rework and customer churn." They'll either nod or tell you your number is wrong. Either way, you've started a business conversation, not a product demo.

The buyer who has quantified the cost of the problem has already started building the internal case for the purchase. Your demo is the last step, not the first.

The reference customer problem in untapped markets

When you're creating the category, you don't have reference customers. That's the paradox. Buyers in tight-knit industries don't buy software without talking to someone else who's already bought it. They want to hear from a peer that it works, not from the vendor.

The answer is personal relationships. Your first five customers in a buyer-education-heavy market are people who already trust you. Not people who've been through a normal sales process. People who buy because you called and said "I built something specifically for the problem you told me about at the industry conference three years ago."

The design partner model exists for this reason. A design partner is a customer who buys in before the product is fully built because they trust the founder and want to shape the outcome. They're not evaluating the product — they're investing in a relationship. You can't manufacture that trust. You can only deploy it from the trust you already have.

What the first 12 months of GTM looks like in an educational market

Most founders in untapped markets try to scale too early. They build a marketing function before they have a repeatable sales motion. They hire a salesperson before they understand why their reference customers bought. They focus on the funnel before they've figured out what moves a buyer from "never thought about software" to "ready to buy."

The first 12 months should be almost entirely personal. Founder-led everything. You're not building scalable go-to-market — you're learning what the education journey looks like, which conversations unlock problem recognition, and which stories make buyers believe it's solvable.

The signal that you're ready to scale is when a buyer you've never met calls because someone in their industry told them about you. That's the first evidence that the education is spreading through the network without you. Until that happens, you're still in the learning phase — and the learning phase shouldn't have a sales team.

Content as a long-form sales conversation

In a market where buyers don't know they have a problem, content works differently than in competitive markets. It's not comparison content or "why us over them." It's problem articulation content.

A blog post that says "The Hidden Cost of Running Field Dispatch on Group Texts" isn't targeting someone searching for software. It's targeting someone googling their specific operational pain — scheduling chaos, callback complaints, dispatch errors — and finding that someone has thought about this problem in detail.

That content builds category awareness before you've ever talked to the buyer. When they come inbound, they've already been through part of the education journey. The sales call is shorter. The problem recognition step is done. You're selling to someone who already knows they need a solution.

This is the compounding advantage of content in an educational vertical market. It isn't marketing — it's a distributed version of the sales conversation that scales without you in the room.

Related reading

Building a market, not just a product. That's the hard work.

If you're working through early GTM and customer education in a vertical where buyers don't yet know they need software, tell us about the problem you're solving.

Pitch us