Audit your full sales tool stack for overlap, gaps, and waste
Turns your tool list into a capability matrix that exposes overlaps, gaps, and zombie subscriptions, then delivers cut/keep/consolidate verdicts with savings math and safe migration notes. Teams typically find 20-35% of GTM tool spend is redundant — this makes the case with a matrix, not a hunch.
You are a GTM stack auditor who has reviewed the tooling of over 150 B2B companies, and you've never once found a stack without waste. The pattern is always the same: tools bought for one feature, overlapping capabilities nobody mapped, and at least one subscription that survives purely on autorenewal. You are ruthless about cost and equally ruthless about not cutting things that quietly hold the operation together. Audit my stack. Output: 1. CAPABILITY MATRIX — rows are capabilities (data sourcing, enrichment, sequencing, dialing, CRM, reporting, automation, deliverability), columns are my tools, cells show which tool covers what — making overlaps visible at a glance. 2. OVERLAP CALLS — for each overlap: which tool should own that capability and why, and what the loser's remaining unique value is, if any. 3. GAP LIST — capabilities I'm missing or handling manually that the stack should cover, ranked by pain. 4. CUT / KEEP / CONSOLIDATE — a verdict per tool with one-line reasoning and estimated monthly savings from cuts. 5. MIGRATION NOTES — for anything cut or consolidated: what must move first (data, sequences, integrations) so nothing breaks. 6. TOTAL — current monthly spend versus post-audit spend. Rules: never recommend cutting a tool that is load-bearing for an integration without naming the replacement path. 'We might use it someday' is not a keep reason. If two tools tie, the one the team actually opens wins. Before you audit, interview me. Ask ONE AT A TIME, waiting for my answer each time: 1. List every sales and GTM tool you pay for, with monthly cost (estimates fine). 2. For each, who on the team uses it, and how often, honestly? 3. What does each tool integrate with in your stack today? 4. What work still happens manually or in spreadsheets? 5. Any contracts with renewal dates or lock-ins I should know about? Then produce the audit. Be direct — I'd rather hear that a tool everyone likes is redundant than keep paying for sentiment.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Pull your actual billing before answering question 1 — remembered costs run 30% under real costs.
- 3
Answer usage honestly (question 2); the audit is only as good as your candor about what nobody opens.
- 4
Execute cuts in migration-note order, and calendar the renewal dates it flags so autorenewals stop deciding for you.
Best practices
Run this quarterly or before any renewal over a few hundred dollars a month — leverage peaks before renewal, not after.
Ask the team what they'd fight to keep before cutting; the answers sometimes reveal integrations the matrix missed.
Watch for the reverse failure too: a gap in deliverability tooling costs more than most redundant subscriptions save.
Use the matrix in vendor negotiations — 'this overlaps 80% with a tool we keep' is a strong discount argument.
Example: what this looks like in practice
A founder at a 20-person consultancy lists eleven tools totaling $3,900 a month: two sequencers (one from a defunct experiment), Apollo plus Clay plus a niche enrichment tool, a dialer with three seats and one active caller, and an unused intent-data platform on autorenewal in five weeks. The matrix shows sequencing covered twice and reporting covered nowhere — pipeline reviews run on exported spreadsheets. Verdicts: cut the old sequencer and intent platform, drop two dialer seats, keep Apollo only for its database seat while Clay owns enrichment, and fill the reporting gap with the CRM tier they already pay for but never configured. Post-audit spend lands at $2,450 with one genuine gap closed, and the migration notes sequence the sequencer sunset so no live campaign breaks.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Rules of thumb vary, but the more useful lens is redundancy: most stacks audit out at 20-35% waste regardless of total size. Spend correlates poorly with results once core capabilities are covered — a $2,500 stack with clear capability ownership routinely outperforms a $6,000 stack with three tools fighting over enrichment.
More automation & workflow design prompts
Build a system prompt for an AI cold email reply agent
Interviews you about your offer, booking flow, and voice, then generates a complete production system prompt for an AI reply agent — classification taxonomy, response rules, escalation conditions, and a strict JSON output contract an n8n or Zapier workflow can parse. You get the artifact teams pay thousands to have written, tuned to how you actually talk.
Turn a manual sales process into an automation blueprint
Converts a fuzzy 'we do this by hand every week' description into a structured blueprint with a detectable trigger, labeled steps, edge cases, human checkpoints, and failure alerts. It forces the design decisions people usually discover mid-build, so what you hand to n8n, Zapier, or an ops hire is assembly work, not archaeology.
Architect a Clay table before you burn the credits
Designs the Clay table before you build it: sources, column order, run conditions, waterfalls, outputs, and a credit estimate. Column ordering and gating are where most teams silently overspend, so the prompt enforces filter-first architecture and makes every paid column defend its run condition — typically cutting credit burn 40-70% versus enrich-everything builds.