Cut the GTM stack without breaking it.
Maps every tool to a job, finds overlap, unused seats, and gaps, and sequences cuts to the renewal calendar.
Inside: The capability map, the overlap and unused finds, and a consolidation plan.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads seat counts and last-login data automatically, so unused is a fact, not a hunch.
reconciles real spend against contracts and catches the tools nobody remembers paying for.
separates "licensed" from "actually used" seat by seat.
This was built for a B2B SaaS org auditing a mid-size GTM stack. Set these to your stack:
Define your capability map first. Overlap only means something against the list of jobs the stack is supposed to do. Two tools sharing a job is waste. Two tools doing different jobs that sound similar is not.
| Set this | What it is | Default / Example |
|---|---|---|
| INVENTORY source | where the tool list lives | a spreadsheeta spend/billing export |
| CAPABILITY map | the jobs a GTM stack must cover | CRMenrichmentsequencingroutinganalyticsCS |
| USAGE source | how you measure real use | seat countslast-loginadmin export |
| SPEND basis | the cost figure you audit | annual contract value per tool |
| RENEWAL field | when each contract comes up | renewal date and notice window |
| OWNER field | who owns each tool | the team or person accountable |
| KEEP criteria | what earns a tool its seat | usedunique jobpositive ROI |
Everything the skill does, in full.
Reads your list of GTM tools and returns a straight read on the stack: what each one is for, where two tools quietly do the same job, what is paid for and barely touched, and where a real capability is missing. Then it lays out a consolidation plan ordered by savings and risk, with renewal dates attached so the plan lands before the auto-renew does.
- 1Capability mapping
Place every tool on the map of jobs a GTM stack has to cover. A tool that maps to no job is a candidate to cut. A job with no tool is a gap. This is the frame everything else reads against.
- 2Overlap detection
Find the jobs covered by more than one tool and show the pair, the cost of each, and which one carries the usage. Two tools doing the same job is the most common and most defensible cut. Name the redundant one and the savings.
- 3Unused and underused
Flag tools with low or zero real usage against seats paid for. State the basis (last-login, seat activation) so nobody argues the call. An unused tool at renewal is the easiest dollar in the stack to save.
- 4Gap check
Name the capabilities with no tool or a tool too weak to count. A gap is as much a finding as an overlap. The plan is not only what to cut, it is what the cuts should fund.
- 5Consolidation plan
Order the moves by net savings and switching risk, and attach each to its renewal date. Cutting a redundant tool the month before it auto-renews is a clean win. Ripping out a load-bearing tool mid-contract is not. The renewal calendar sequences the plan.
- No tool called unused without stating the usage basis behind the call.
- Overlap always names both tools, both costs, and which one keeps the job.
- Every recommended cut carries its renewal date and notice window.
- Gaps are reported alongside cuts. The audit is not just a cost-cutting list.
TECH-STACK AUDIT · 18 tools · $412K annual Job Tools Finding Enrichment Tool A ($60K), Tool B ($28K) OVERLAP, B carries 12% of usage Sequencing Tool C ($75K) KEEP, core, high usage Sales analytics Tool D ($40K) UNDERUSED, 6 of 40 seats active in 90d Lead routing none GAP, routed by hand today Consolidation plan (by savings, sequenced to renewals): 1. Drop Tool B at its renewal next month. Saves $28K. Usage already on Tool A. 2. Right-size Tool D to 10 seats at renewal in Q3. Saves ~$30K. 3. Fill the routing gap. Fund it partly from the two cuts above.
The usage window (90-day last-login) and the keep criteria are defaults, not laws. They suited a mid-market SaaS stack review. If your tools are seasonal or your teams smaller, adjust the window. The capability map and the keep bar are yours.
Where an operator takes this next.
The audit runs once, by hand. Here is where an operator takes it once the manual version proves out.
The audit finds the waste once; the calendar is what stops it from creeping back.
Point the audit at a billing export (via a data warehouse like Snowflake) so contract cost and actual usage stay in sync without a quarterly manual pull.
A scheduled Claude task checks the renewal calendar monthly and flags any tool inside its notice window that is still marked underused.
Pull last-login data straight from each tool's admin API instead of asking IT for an export, so the "unused" call is defensible in the room.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.