Mind the (Feature) Gap

Consider what’s likely shipped in the last twelve months across your stack. New AI assistants embedded in tools you already pay for. Reworked reporting modules. Integrations that used to require custom development and now simply need enabling. Automations for tasks a team member still does by hand every Monday morning. It’s happening across portfolio monitoring, CRM, data rooms, treasury systems, HR platforms, and everything in between.

If your firm hasn’t taken a proper look at what’s changed in its tooling over the last eighteen months, you are running last year’s software. That’s the feature gap, and at almost every firm we speak to, it’s quietly leaking digital alpha: the firm is not capturing operational performance from software it has already paid for.

What the gap looks like in practice

The SaaS tools most firms rely on aren’t bad tools. If anything, that’s what makes the underutilisation so frustrating. You picked the right platform, and then left a meaningful portion of its value unrealised. These are the patterns we see again and again:

• Core workflows running alongside the tool, not through it. A vendor ships a guided workflow for a process the team still manages in email, Excel, or a secondary system. A migration path usually exists. Someone has to run it, and most firms haven’t done this.
• Manual work and reporting that features have already replaced. Data extraction, report generation, approval routing, custom dashboards: the platform handles these natively now. Teams still doing them by hand or budgeting for a separate BI tool are solving a problem the vendor has already solved.
• AI features sitting untouched. Almost every enterprise SaaS vendor has shipped AI capabilities in the last year. Copilots, in-platform assistants, natural-language querying, MCP integrations with external AI tools. Most firms haven’t adopted them yet because they didn’t exist six months ago. That is the point.

Why this keeps happening

The cause is structural. Most firms are still operating their SaaS platforms the way they operated on-premise software fifteen years ago: implement, train, move on.

That approach suited the software of its era. Enterprise applications in 2005 were capital projects. Implementation ran for twelve to eighteen months, major upgrades came every three or four years, and in between the software did not change. Training once was sufficient. IT owned the platform because the binding constraint was infrastructure. A project-and-done operating model was appropriate to the product.

SaaS has inverted these assumptions, but most firms have not adjusted. The result is what we call the operating model gap: the distance between what a platform can do and what the firm is currently utilising it for. It shows up in three patterns:

• Implementation is still treated as the finish line. The project team disbands at go-live. No ongoing ownership exists to absorb the continuous stream of new features, deprecations and behaviour changes. The platform on day 365 is materially different from the platform on day 1, and nobody is tracking the delta.
• Training remains a one-time event. Users were trained on the version that existed at go-live. They have received no subsequent training. They are, in effect, operating a different tool from the one they were taught to use.
• IT retains ownership of the platform. This made sense when the constraint was servers and uptime. The vendor now manages both. The constraint has shifted to adoption and configuration, which is a business capability question, but the organisational model has not caught up.

What’s required is a continuous operating model: named business ownership of platform value, a quarterly review rhythm matched to the vendor’s release cadence, and training treated as an ongoing operational cost rather than a one-off implementation expense. The shift is not expensive. Very few firms have made it.

A secondary reason these gaps persist is that the existing setup functions well enough. Reports are produced, investors receive their packs, and in the absence of acute failure there is little internal pressure to examine whether things could be substantially better.

Why now

Clients, investors and regulators are more operationally astute than they used to be. Self-service analytics, faster reporting cycles, cleaner data: these are increasingly read as indicators of how well a business is run. The firms that are fully using their software stack are reporting faster, spotting risk earlier, and presenting their stakeholders with a more sophisticated view. That translates into a commercial advantage, and it doesn’t require a new budget line or additional headcount. It simply requires extracting more from what has already been paid for.

Bridge the gap with a Health Check

This is the gap our Health Check service is designed to close. Over four weeks, a specialist team does the work your internal team doesn’t have the time or the benchmarks to do, on whichever platform you want assessed:

• Consultation: Stakeholder interviews, discovery workshops and scope alignment. We establish how the tool is actually being used in your firm versus how it’s designed to be used.
• Review: Data quality assessment through BI and API analysis. Workflow and integration review. Audit of legacy configurations against the current version of the platform. Gap analysis against industry best practice and features you aren’t yet using.
• Recommendations: An executive-level report and a prioritised roadmap showing which changes are worth making, and in what order.

You receive a data quality assessment, a best practice gap analysis, and a prioritised recommendations roadmap. What follows is closing the gap and keeping it closed. For some firms that means building the operating model internally: named ownership, a quarterly review rhythm, ongoing training. For firms who want the function without adding headcount, we provide it as a retained service.

What to do this week

If a full assessment isn’t on the cards yet, start smaller. Pick your most-used SaaS platform and ask the team one question: “What are you doing manually that this platform was supposed to automate?” The answers tend to amount to a shortlist of features already sitting in the platform, unused.

If that list is longer than you’d like, or if you’d prefer someone to benchmark it against what best practice looks like elsewhere in the market, that is what the Alpha Alternatives Health Check is for.