Audit software subscriptions and duplicates

Maps recurring SaaS spend, flags potentially duplicate suppliers, and isolates AI tool spend to detect shadow IT.

ProcurementCFO๐Ÿ“† MonthlyIntermediateRead-only

Ask it like this

What are my biggest recurring SaaS subscriptions and are there any duplicates?

When to use it

Use it for a regular review of your software subscriptions: cost by supplier, possible duplicates and AI tools taken out without coordination.

What it produces

List of recurring SaaS suppliers, potential duplicates flagged, and AI tool spend concentration by cost center.

How it works

  1. 1Ranks recurring subscriptions by supplier, from most to least expensive
  2. 2Spots supplier names that look alike and checks whether they are separate records
  3. 3Identifies who holds each active subscription and on which cost centre
  4. 4Isolates spend on AI tools
  5. 5Presents three views: ranking, possible duplicates and AI tools with their owners

What protects you

  • This skill only reads: it changes nothing in Spendesk
  • It acts with your permissions and your role, never beyond
  • The assistant cannot approve or pay
โ–ธTechnical detail87/100 ยท 3 tools
Spend analysisSuppliersspendesk_analyze_spendget_supplierslist_cards

# Recurring SaaS, duplicate, and shadow IT audit

## Goal

Give a Procurement lead a periodic view of an organisation's SaaS fleet: which recurring expenses weigh the most, which suppliers are likely duplicates (the same vendor registered under several names), and where AI tool spend concentrates without central coordination (a shadow IT signal). Typical use case: quarterly SaaS fleet review, prep for a renewal negotiation, or a one-off audit before a budget close.

---

## MCP scope โ€” what's visible

> โš ๏ธ The Spendesk MCP has no built-in duplicate detection. Matching similar supplier names is Claude reasoning over the results of `spendesk_analyze_spend` / `get_suppliers` / `list_cards`, not a native capability of the tool. If a duplicate is confirmed, merging it stays a manual action in Spendesk โ€” no MCP write tool covers this today.

| Need | Accessible? | Via which tool |
|-------|:----------:|---------------|
| Recurring spend ranking by supplier | โœ… | `spendesk_analyze_spend` (groupBy=supplier, payableTypes=subscription) |
| Detail on a suspected duplicate supplier | โœ… | `get_suppliers` (`search` parameter) |
| Cardholder + cost center per active subscription | โœ… | `list_cards` (type=subscription, status=Active) |
| Automatic merge of two supplier records | โŒ | No write tool covers this need today |

## Instructions

1. Call `spendesk_analyze_spend` with `groupBy: ["supplier"]` and `filters.payableTypes: ["subscription"]` over the requested period (365-day max per call, split if longer) โ€” returns the recurring spend ranking by supplier, largest to smallest. Pass `limit: 50`: by default only 10 rows come back and the rest is rolled into an "Others" row.
2. In that ranking, spot supplier names that look alike (case variants, typos, different legal names for the same vendor). Confirm each suspicion with `get_suppliers` (`search` parameter) to check whether they are indeed separate supplier records.
3. Call `list_cards` with `type: "subscription"` and `status: "Active"` to see who holds each active subscription and on which cost center โ€” several different cardholders with equivalent subscriptions opened with no visible coordination is the shadow IT signal.
4. To isolate AI spend specifically, filter the suppliers from steps 1 and 3 whose name matches known AI tool vendors and group them separately.
5. Present three views: (a) recurring supplier spend ranking, (b) potentially duplicate suppliers with their respective cardholders and cost centers, (c) "AI tools" cluster with each owner and cost center.

**Example user prompts:**
"What are my biggest recurring SaaS subscriptions and are there any duplicates?"
"Give me a snapshot of AI tool spend across the company."

<!-- meta: score=87, date=2026-07-10, source=test-results/2026-07-10-audit-saas-recurrent-doublons-shadow-it.md -->

How to install this skill

/
  1. 1
    Download the file s64-audit-saas-recurrent-doublons-shadow-it.md using the button above.
  2. 2
    Place the file in the .claude/ directory of your project (or ~/.claude/ for a global install).
    cp s64-audit-saas-recurrent-doublons-shadow-it.md .claude/s64-audit-saas-recurrent-doublons-shadow-it.md
  3. 3
    Use in Claude Code โ€” the skill is automatically discovered. Describe your need in natural language and Claude will apply the skill instructions.
๐Ÿ’ก Make sure the Spendesk MCP is configured in your .claude/settings.json with the tools spendesk_analyze_spend, get_suppliers, list_cards.

Similar skills

โ˜… Top
95/100ยท๐Ÿ” Ad hocยทExpert

Audit what the MCP covers

Probes all available MCP tools, re-evaluates coverage of 50 persona use cases, detects new fields or tools, and regenerates the gap analysis report.

CFOControllerAP Manager
90/100ยท๐Ÿ” Ad hocยทIntermediate

Active vs archived cost centers

Distinguishes active cost centers from archived ones with correct use of get_cost_centers. Avoids the counter-intuitive isArchived vs isActive naming convention pitfall.

ControllerFinance Analyst
โ˜… Top
89/100ยท๐Ÿ” Ad hocยทIntermediate

Build a custom skill

Turns a precise business need into a brand-new tailored Claude skill, ready to use on the Spendesk MCP.

CFOControllerAP Manager

Interested in AI Agent services or Custom Integrations?