Article 4: The view from the top

There's a version of this series that stays entirely at the product level. Switching costs, regulatory moats, data assets, go-to-market depth: all of it matters, and I'll have nine articles making the case for why. But there's a variable that cuts across all of it, that can neutralise every structural advantage a vertical SaaS business has, and it doesn't show up in any financial model. It's the person running the business, and whether they're genuinely willing to change.

I've sat across from enough founders and leadership teams over the last decade to have developed a fairly strong sense of this. The businesses that navigate transitions well, whether it's a new competitive entrant, a shift in how customers buy, or a technology change that rewrites the rules, almost always have one thing in common. The person at the top is curious rather than defensive. They ask questions before they have answers. They're willing to entertain the possibility that the way they've always done things isn't the only way, or even the best way anymore.

The businesses that struggle tend to have a different character at the top. Pride in what's been built, which is entirely reasonable and often well-earned, has curdled into attachment to how it was built. The product strategy that worked in 2015 is still the product strategy in 2025, not because anyone has thought hard about whether it's still right, but because questioning it feels like questioning the founder's judgment, which nobody in the building is going to do out loud.

Why this matters more now than it did

Vertical software businesses have historically been able to get away with a degree of leadership inertia that other categories couldn't. The moats were strong enough, the customer relationships sticky enough, and the competitive environment quiet enough that a founder who wasn't especially hungry for change could still run a perfectly good business. The category rewarded patience and depth more than it rewarded agility.

That status quo is shifting quickly. Not because the moats have disappeared, they haven't, but because the pace of change in the tools and methods available to both challengers and incumbents has accelerated enough that standing still is no longer a neutral act. A vertical SaaS business whose leadership team has decided that AI is mostly hype, or that their customers aren't asking for it, or that they'll get to it eventually, is not holding its position. It's losing ground, quietly, to the competitor whose leadership team made a different call.

The businesses best positioned for the next decade are the ones where the founder or CEO is genuinely engaged with what AI means for their specific domain, not at the level of press releases and marketing copy, but at the level of product roadmap, customer conversations, and honest internal reckoning with what needs to change. That engagement has to come from the top, because the organisation will take its cues from whoever is running it. If the leader is curious, the team will be curious. If the leader is defensive, the team will be defensive, even if individual members privately know better.

The middle management problem

There's a subtler version of this that I think gets underweighted in most analysis, including my own until fairly recently. In a lot of the businesses I look at, the founder is genuinely open to change. They've seen enough business cycles to know that adaptability matters, and they're intellectually honest enough to engage with the question of what AI means for what they've built. The problem isn't at the top. It's in the layer underneath.

Middle management in a successful vertical SaaS business is often populated by people who built their careers around the current way of doing things. The head of implementation who designed the onboarding process eight years ago. The sales director whose relationships and methodology have delivered consistent results for a decade. The product manager who owns the roadmap and has a well-developed view of what customers want, based on what customers have asked for historically. These are good people doing good work. They're also people with a structural interest in things not changing too fast, because change means their accumulated expertise is worth less than it was.

This is not a cynical observation. It's a human one. But it matters enormously for whether a leadership team's stated openness to change actually results in change. A founder who wants to move fast on AI but has a senior team that's quietly resistant will find the organisation moving much slower than intended. The resistance won't be explicit. It will take the form of competing priorities, implementation complexity, customer readiness concerns, and a steady supply of reasonable-sounding reasons why now isn't quite the right moment.

The founders who navigate this well tend to be the ones who recognise the dynamic and address it directly, not by steamrolling their senior team, but by creating enough genuine urgency and enough psychological safety that the people who are privately excited about change feel empowered to say so.

What this looks like in practice

I've started paying more attention to this in how I evaluate businesses. The management meeting questions that reveal the most aren't the ones about product roadmap or customer metrics. They're the ones about process. How did the business decide to approach AI? Who drove that conversation? What did they change as a result, and what did they decide not to change? How do they think about the gap between where the product is today and where it needs to be in three years?

The answers to these questions are revealing, not because there's a single right answer, but because the way a leadership team engages with them tells you a great deal about the cultural posture of the business. A team that's genuinely grappling with these questions, that has a view, that has made some bets and is honest about the uncertainty, is a team you can work with. A team that gives you polished non-answers, or that treats the question as slightly beside the point, is telling you something important.

For investors and acquirors, this is increasingly a first-order variable. A vertical SaaS business with strong fundamentals and leadership that's genuinely change-oriented is a compounding asset. The same business with leadership that's dug in, that's mistaking past success for future strategy, is a much harder bet, regardless of what the retention numbers say today.

The pride paradox

I want to end on something that I think is genuinely underappreciated. The founders most at risk of getting this wrong are often the ones who have built the most impressive businesses. The strength of what they've built, the depth of the customer relationships, the durability of the retention numbers, all of it creates a very reasonable basis for confidence. And confidence, in the right measure, is what allowed them to build something great in the first place.

The paradox is that the same confidence that built the business can become the thing that prevents it from evolving. A founder who has been right about their market for fifteen years has a lot of evidence that their instincts are good. The instinct that AI is mostly noise, or that their customers don't really want it, or that the product is strong enough to compete without it: these feel like the same kind of contrarian conviction that served them well when everyone said the market was too small or too niche or too boring. Sometimes that conviction will be right. Sometimes it will be the most expensive mistake they ever make.

The businesses that come out of this period in the strongest position will be the ones where the person at the top held both things simultaneously: genuine pride in what they built, and genuine openness to the possibility that building the next version requires something different. That's not an easy balance to strike. But in a world that's changing as fast as this one, it's the most important leadership quality there is.

The product matters. The moat matters. The data matters. But the view from the top determines whether any of it compounds.

Author: Yousif Hanna