martech-stack-auditlisted

# Martech Stack Audit Inventory, price, and rule on every tool. Stack sprawl is an accumulation of individually defensible decisions, so only a portfolio-level review catches it. ## When to use - Budget pressure, or a CFO asking questions - Any renewal above a threshold worth caring about - Annual planning - Before adding a tool, to test whether the gap is real ## Inputs - Needs from user: every tool with its annual cost and renewal date, seat counts against seats used, ARR, and who owns each contract - Reads: `workspace/audit/systems-audit.md` Ask for all of it in one batch. Finance usually has a cleaner list than marketing does, and the gap between the two lists is itself a finding. ## Workflow ### 1. Build the true inventory Include the things nobody counts: tools on a credit card, tools inside another tool's bill, per-seat tools with unused seats, and anything auto-renewing that nobody owns. ``` Tool | Category | Annual cost | Renewal date | Seats bought | Seats used | Owner | What it does that nothing else does ``` The last column is the one that produces the verdict. If it cannot be filled in with a specific capability, that is the answer. ### 2. Compute the ratio ``` Stack spend to revenue = total annual martech spend ÷ ARR ``` | Ratio | Reading | |---|---| | Under 4% | Possibly under-tooled, check for manual work that should be automated | | 4 to 8% | Healthy band at growth stage | | 8 to 12% | Elevated. There is usually real redundancy | | Over 12% | Need