Treat the owned platform as a substrate of capabilities rather than a bundle of products, then map those capabilities against the jobs that category software is bought to perform.
Capabilities, not products
Product lists are unhelpful here. What matters is the capability inventory: identity, email, calendar, appointments, booking, forms, documents, spreadsheets, structured data, shared storage, collaboration, chat, video, workflow, approvals, notifications, search, knowledge, intranet, lightweight applications, dashboards, automation, AI, security, permissions, and audit trails.
Most organizations already pay for all of that. Very few have an inventory of it, which is one reason the same capability gets purchased a second time under a category name.
Category is not the same as job
A software category is a marketing container for a set of jobs that were commonly bought together. It is a fact about the industry, not about the work.
The research discipline here is to keep the two apart. Write down the jobs first, in the language of the business, and only then look at what a product in the category provides. The difference between the two lists is the honest measure of what buying would actually add.