SaaS stack audit

Builds one inventory of the SaaS tools the organisation pays for and proposes a decision per tool. The inventory joins three views: what is billed (invoices, card and expense exports), what is connected (the SSO app list), and what is used (sign-ins and admin exports). Each tool gets an owner, seats paid and used, its overlaps with other tools, and a proposal: keep, cut or replace. For replace, the page lists open-source and agent-built options next to other vendors, each with its switching cost and risk.

The skill cancels nothing, changes no seat count and signs into no vendor console. The owner of each tool acts after the user agrees the decision.

Inputs

• Billing sources (required): invoices, card statements, expense exports, accounts payable exports. Default the last 12 months, so annual plans show up.
• SSO app list: the export of connected apps from the identity provider, with the number of assigned users per app.
• Usage: sign-in counts per app from the identity provider, or active-user exports from each tool's admin page, with the export date.
• Owners: who answers for each tool. Ask the user for a first list.
• Page: default docs/fin/saas-inventory.md.

Steps

1. Set up. Copy the templates without overwriting: