At Amberg Team, we see more vertical SaaS in deal pipelines every year. Founders pitch a specialised vision. They present loyal users as evidence of a permanent moat. This story sells well but it can hide a deeper reality. A product can mimic an industry through design while lacking the actual logic to run that business.

The key question in diligence is simple. Are we looking at a real platform or a feature set that happened to find traction? The answer drives valuation, deal structure and the first years of ownership.

At Amberg Team, a platform is something customers build their business around. A feature set is something they can replace with planning and effort. Both can produce attractive numbers in the short term. Only one supports the kind of holding period most buyers need.

We start from the customer workflow. In a defensible vertical SaaS platform, the software sits close to the core of how the customer operates. It shapes daily routines. It holds records that matter for audit, regulation or revenue recognition. It links to other critical systems. You see this in interviews, not only in dashboards. Users talk about the product as “where we do our work”, not “a tool we add on top”.

By contrast, a feature set tends to live at the edges of the workflow. It helps, but it is not central. Customers describe it as helpful, and at best a “nice to have”. They can imagine moving away with clear steps. That story can still support a deal.

Retention and growth metrics sit at the centre of most investment cases. In vertical SaaS, those metrics need more context than a simple snapshot. We look at cohorts over several years. A platform often shows improving retention with customer maturity. A feature set often shows a flatter curve, with a visible drop when contracts renew and customers reassess their stack.

Expansion within accounts tells a similar story. In a genuine platform, customers deepen usage. They add new users. They connect more processes. They buy new modules that replace other tools. In a feature set, expansion often rests on price increases or bundles that customers do not fully adopt. Revenue grows faster than usage. That gap matters.

Competitive position in vertical SaaS also needs a sector lens. The most common threat to a niche product is not a direct clone. It is a horizontal vendor extending into the sector with templates and light configuration. In European markets, we see horizontal CRM, ERP and HCM tools doing exactly this.

At Amberg Team, we ask a direct question. What does this product do that a horizontal vendor cannot copy at reasonable cost? Clear answers tend to fall into three categories. One is proprietary data that compounds over time. Another is deep alignment with regulation and local practice that takes years to build. A third is credible integration with sector-specific legacy systems that general tools do not support well. If the main claim is that the product is faster to deploy and cheaper today, we treat that as a commercial edge, not structural defensibility.

In a defensible platform, the architecture can support the next stage of growth without a full rebuild. The roadmap focuses on deepening the core workflow and strengthening links to adjacent systems.

In a feature set, we often see scattered modules, custom builds for key accounts and a codebase that reflects short-term deals rather than a clear product vision. Technical debt in itself is not a reason to walk away. It becomes a problem when it blocks the change that the investment thesis depends on. For example, if the plan assumes international expansion, but core components are hard-coded to local rules and cannot adapt, the thesis and the product do not match.

Team composition is another strong signal. In vertical SaaS, sector knowledge often lives with a few people who shaped the product in its early years. A defensible platform usually has that knowledge distributed across a broader team.

A feature-heavy business can rely on one founder or a single domain expert. Roadmap choices sit in their head. Customer relationships are personal. That concentration adds risk, especially for international buyers or financial sponsors who plan to support further growth after a change of control. We flag this in our work and link it directly to forecast and integration risk.

For private equity and corporate buyers, these questions feed directly into valuation. If we see strong evidence of a defensible platform, with high switching costs, deep workflow integration and structural protection from horizontal vendors, then higher multiples can be justified. If we see a useful feature set with weaker lock-in and clear substitution risk, we say so. The deal may still make sense, but the price and capital plan should reflect that reality.

At Amberg Team, our role is to bring this distinction into focus before capital is committed. We combine customer research, product and architecture review and deep financial analysis to build a single view of where a vertical SaaS business truly sits on the spectrum from feature set to platform. We then translate that view into numbers, decision points and priorities for the first years of ownership.

For buyers looking at vertical SaaS, that clarity can be the difference between a strong asset that compounds and a product that looks attractive in year one, then stalls. Our work is built to help you tell the two apart.