Martech Stack Subscription Auditor

The problem this kills

Your marketing team's tool stack grew one urgent request at a time. A designer needed one app, a campaign manager swiped a card for another, somebody's trial quietly converted to an annual contract, and the person who owned that "essential" platform left eight months ago. Now you've got two email tools, three analytics dashboards, a video host nobody logs into, and a finance team asking why martech spend is up 40% with no plan to show for it.

The hard part isn't deciding to cut waste - it's seeing the waste. The subscriptions are scattered across credit-card statements, vendor portals, and a spreadsheet that's three months stale. You can't tell which tools overlap, which have ten paid seats and two active users, and which have no owner at all. By the time you've stitched it together by hand, the auto-renewal already hit.

What you'll build

A small private web app for your team that:

• Imports a subscriptions CSV (tool, category, cost, seats, last-used/usage note, owner) and a category map that says which tool types compete with each other.
• Categorizes every tool and computes its annualized cost (monthly contracts x 12, so you compare apples to apples).
• Flags the three big wastes: redundancy (two tools in the same category), low usage (seats far above active users, or a stale "last used" date), and unowned tools (no accountable owner).
• Estimates savings for each flagged tool and a total potential cut for the whole stack.
• Routes a keep / consolidate / cancel list to a manager who must review and approve each decision before anything is actioned.
• Produces an action plan and exports a clean stack + savings CSV in the columns your finance team expects.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook. It opens by interviewing you about your business - the systems your subscriptions live in today, how you name tools and categories, your renewal cadence, what "low usage" really means for you, and the messy edge cases like one tool billed under two accounts - so the auditor is tailored to your stack, not a generic template. The agent reads a short spec back to you and waits for your thumbs-up before it builds a thing.

From there it walks you, step by step, through standing up the database, the import screens, the categorization and flagging engine, the savings math, the approval gate, the email summary, and the CSV export - each step ending in a ready-to-copy prompt you paste into your AI coding agent.

The governance it includes (this is the point)

This is not a throwaway script. Every build includes:

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own subscriptions and spend.
• A full audit trail - who imported what, who flagged it, and who approved each keep/cancel decision, with timestamps.
• A hard human-in-the-loop approval gate - no tool is marked for cancellation until a manager reviews and approves it. The AI drafts the cut list; a person decides.
• Duplicate guards keyed on tool name + account so the same subscription can never be double-listed.

Who it's for

Marketing ops and RevOps people tasked with reducing tool sprawl and cost, who need to turn a messy pile of subscriptions into a defensible, auditable cut list - and who want a repeatable audit they can re-run every renewal season instead of rebuilding the spreadsheet from scratch.

You've got this - paste the first prompt and let the agent interview you.