Every operator who has considered starting a software company has had the same conversation with a well-meaning advisor: "Have you looked at what's already out there? Maybe you don't need to build something new." It's reasonable advice for someone who's never actually tried to run an HVAC business on existing software. For someone who has, it lands differently.
The vertical SaaS build vs. buy decision is not an IT question. It's a market validation question. When operators get it wrong — and they often do — they spend two years customizing something that was never built for their workflow, then pivot to building anyway, but eighteen months behind and significantly more frustrated.
Why the existing options are almost never good enough
Horizontal SaaS platforms are built for the median use case across many industries. That's a feature for the vendor and a bug for operators in specialized verticals. The median HVAC company looks nothing like an actual high-performing HVAC company. The median landscaping business doesn't run its dispatch the way the top shops do. When software is built for the median, operators who've spent a decade optimizing for performance find themselves working around it constantly.
Legacy vertical SaaS — the stuff that's been around since 2005 — often went the other direction. It was built for specific workflows, but by people who were building software in 2005. The architecture is outdated, the UI is unusable, and the vendor has no incentive to modernize because their customers are locked in. It's the worst of both worlds: specific enough to avoid, but expensive enough to replace.
The three signals that mean you should build
Not every gap in the market is a building opportunity. Some gaps exist because the market is too small to justify the investment, or because the problem is genuinely solvable with existing tools that just need to be configured correctly. But three signals reliably indicate that building is the right call:
The workflow is load-bearing and unique. If the core process that drives your business — dispatch, quoting, job costing, compliance tracking — is specific enough to your vertical that horizontal tools require more than one meaningful workaround, that's a build signal. The workaround count is your market research. If you've built more than two, your customers have too.
The data from that workflow is a competitive asset. In vertical SaaS, the best moats are data moats. If the data that flows through the core workflow — job history, pricing patterns, customer behavior — becomes more valuable over time and is currently locked in spreadsheets or disconnected systems, building gives you the infrastructure to capture it. Buying gives that infrastructure to someone else's platform.
Existing buyers describe the problem as unsolvable. This is the strongest signal. When you do customer discovery and people say "we've tried everything and nothing works," that's not a technology problem — it's a market failure. The solutions that exist don't actually solve the problem. That's the definition of a build opportunity.
When buying is actually right
Buying — or more accurately, integrating — makes sense when your differentiation lives above the infrastructure layer. If you're building a workflow layer on top of payments, scheduling, or accounting infrastructure, you can use existing APIs as the foundation and build your vertical logic on top. The risk is platform dependency, which is real and should be planned for. But the risk of spending 18 months rebuilding a payments stack is worse.
The test: if your core value proposition could be replicated by the platform you're building on top of, you're not building a company — you're building a feature that will eventually be eaten. The platform layer should be commodity infrastructure, not the thing you're selling.
The mistake operators make when they decide to buy
It usually goes like this: an operator evaluates the market, finds something that's "close enough," and signs a contract with the plan to customize it into the thing they actually need. The customization project starts. The vendor says yes to everything in the sales call and no to everything post-signature. Six months in, the operator has spent more on implementation than the software costs, the core workflow still doesn't work the way it needs to, and the team is resentful of a system they didn't choose.
The tell is the phrase "we can configure that." In vertical SaaS, "configurable" almost always means "it will take 40 hours of professional services and still won't be quite right." Real customization means custom code, which means you're already building — you're just building on top of someone else's architecture for someone else's margin.
What this means if you're thinking about starting a company
If you've spent a decade in a vertical and you've watched your industry try and fail to solve a core workflow problem with off-the-shelf tools, the build vs. buy analysis is already done. You've been doing it for years. You know which tools your peers have tried, what the workarounds look like, and exactly which part of the process still breaks on a Tuesday afternoon when it matters most.
That knowledge is worth more than any market sizing deck. The operators who build great vertical SaaS companies don't start by asking "is there a gap in the market." They start by stopping tolerating the gap they've been working around for years.
If that's where you are, the question is whether you have the infrastructure to build the right thing — product, go-to-market, and the capital to move fast enough to matter. That's where a venture studio changes the math.
If you know what needs to be built, tell us what it is. Two paragraphs is enough to start.