How much can a typical mid-market team recover in 90 days?

Modeled across the GTM stack patterns we track: 25-40% of total annual GTM stack spend, mostly through duplicate-capability cuts (Outreach + HubSpot sequencing, Gong + Kaia, Apollo + ZoomInfo) and dormant-seat de-provisioning. The exact figure depends on stack composition — teams with heavy SEP + CI overlap see the biggest recovery; teams already running lean see less but still recover 5-15% through year-2 uplift refusal and tier audits.

Do we need executive buy-in to run this playbook?

For Days 1-30 (dormant assets, departed-employee seats, no-conversation cuts): no executive sign-off needed. Recovery is direct savings, not strategic. For Days 31-60 (renewals): finance approval helps but most renewals are within RevOps/CRO authority. For Days 61-90 (strategic consolidations): executive sponsorship is required because it touches sales motion. The right cadence is: run Days 1-30, document the recovery, then bring the larger plan to leadership with proof of execution.

What if our renewal isn't for 6 months?

Run Days 1-30 immediately — dormant seats, departed-employee de-provisioning, and add-on cuts don't require a renewal. Add-on cuts (Outreach Kaia, Salesloft Drift CI, Apollo Buyer Intent) are usually month-to-month or have separate contract terms — most can be cancelled mid-cycle. Then time Days 31-90 to land 90 days before each major renewal, in waves.

How do we know which capability overlap to cut?

Three-question test: (1) which tool is the source of truth — where reps actually do the work? (2) which tool has the deeper integration with the rest of the stack? (3) which contract is harder to exit (longer term, larger penalty)? Cut the tool that fails 2-of-3. The hardest case is when both tools score equally — those are usually post-acquisition stack patterns where neither team wants to migrate, and the right call is forcing the decision via a renewal-deadline hard date.

What about migration risk during consolidation?

Real but usually overstated. The big risks are: (1) data loss (sequence templates, recordings, enrichment history) — mitigate by exporting before cutover, (2) rep adoption (workflow change burden) — plan 4-6 weeks of side-by-side, (3) integration breakage (CRM sync, data flows) — test in sandbox first. Most consolidation projects underestimate the operational lift by 30-50%; budget accordingly. The savings still pencil out, but plan for 8-10 weeks of sustained operational effort, not 4-6.

When should we re-audit?

90 days post-consolidation: run StackScan again to validate the cuts and surface new overlaps. Quarterly thereafter: quick tier + dormant-seat review (~30 minutes). Annually: full audit before the largest renewal of the year. The stack re-bloats over time — new tools get adopted by departments, add-ons creep back via QBR upsells, dormant seats drift up as teams change. Quarterly cadence is the only structural defense.

Can StackSwap run this playbook for us?

StackScan produces the input — the ranked overlap and consolidation map. The 90-day execution is operational and lives with your RevOps/CRO. We can scope a deeper engagement (audit + consolidation roadmap + vendor negotiation prep) for teams that want hands-on support. Start with the free StackScan to see the cut list, then decide if you need help operating it.

StackSwap · Operational playbook

GTM Stack Consolidation Runbook

What to do once you have the cut list. A week-by-week 90-day plan that moves from zero-conversation quick wins, into vendor negotiations with leverage, and ends with the strategic consolidations that produce the biggest single-decision recovery. Built for RevOps and CROs running the work.

Pre-work (Week 0)

Before Day 1, you need: (1) the StackScan output (or equivalent self-built overlap map), (2) a one-page sponsor brief showing the 90-day plan and target recovery, (3) scheduled time on the calendar for the first 4 weeks. The execution doesn't need executive sponsorship for Days 1-30 — but Days 31-90 will.

One-page sponsor brief structure: current annual GTM stack spend, top 3 overlap patterns by recovery, upcoming renewals in the next 90 days, ask: 90 days of operational time, no committed cuts yet, audit-only mandate. Most CROs approve this if the framing is "reduce risk before renewal" instead of "cut tools."

Days 1-30

Quick wins

Cut what nobody operates. No vendor conversations yet. Pure inventory + dormant-asset pruning + license-count truth. Target: lock in 25-40% of total recovery before talking to a single AE.

Expected recovery: 15-30% of total annual GTM stack spend

Week 1 · Inventory truth

Pull every active GTM contract from Finance/Procurement. Print to one spreadsheet: tool, owner, seats, price, renewal date, year-2 uplift clause.
If StackScan output exists, line it up against the contract list. Mark every tool flagged as overlap or low-utilization in the scan — those are your work queue.
Send a 1-question Slack to each tool's primary department: 'When did you last open <tool> for actual work?' Anything that comes back vague is a red flag.

Week 2 · Seat-level audit

Pull a 90-day usage report from every per-seat-priced tool (Outreach, Salesloft, Apollo, Gong, Clay, Salesforce, HubSpot Sales Hub).
Mark every seat with <30% activity over 90 days. These are dormant-paid-for seats. Don't cut yet — just identify.
Cross-reference: which dormant seats belong to people who left the company 3+ months ago? Those are no-conversation cuts. Pull a list.

Week 3 · Dormant asset pruning

Archive dormant Outreach/Salesloft sequence templates (no sends in 60 days, no edits in 90 days). Cuts noise + drives rep adoption back up.
Clean HubSpot contact list — bulk-delete contacts with no engagement in 12+ months. Marketing Hub Pro contact-tier creep is the second-biggest HubSpot waste pattern.
Audit Clay tables — pause automations on tables not modified in 60+ days. Credits stop burning immediately.
Apollo: archive contacts in lists that are off-ICP or from pivoted campaigns. Stay under the next pricing tier.

Week 4 · No-conversation cuts

De-provision seats for departed employees from every per-seat tool. Most teams find 5-15% of total seats this way.
Cancel add-ons nobody operates: Outreach Kaia (if Gong exists), Apollo Buyer Intent (if no intent workflow), Salesloft Drift CI (if Gong exists), Clay AI columns (if no A/B test justified).
Document everything cut and the recovered annual amount. This is your case for the next 60 days of conversations.

Days 31-60

Renewal negotiations

Now you have data. Use it. Every conversation with a vendor renewals team should reference specific usage metrics, credible alternatives, and a willingness to walk. Goal: cut 8-15% off list price across the contracts you keep.

Expected recovery: 5-12% off list price on retained contracts

Week 5 · Renewal calendar

Map every renewal date for the next 6 months. Sort by dollar value. The top 3-5 renewals are where 60% of negotiation leverage sits.
For each top renewal: write a one-page brief — current cost, modeled cost if downgraded/cut/swapped, credible alternative threat, your walking point.
Schedule renewal calls 90 days before contract end (not 30). Vendors are trained to handle 30-day-out conversations; 90-day-out conversations are when you have leverage.

Week 6 · Tier downgrades

For tools where usage data shows tier overpayment: schedule the downgrade conversation. Outreach Engage → Standard, Salesloft Premier → Advanced, Apollo Pro → Basic for low-utilization users.
Anchor on usage data: 'Of our 30 reps, 22 don't use AI features. We're downgrading those seats at renewal. We'd rather stay on your platform than swap — if you can match the lower-tier-effective price for the higher-tier-actual-features for our power users, we'll commit to a longer term.'
Most vendors will match within 60-70% of the downgrade economics to keep tier. Net: you get power-user features for 30 reps at the price of 22 power-user seats + 8 basic.

Week 7 · Year-2 uplift refusal

For every renewal: refuse the year-2 list-price uplift. Trade it for: (a) longer commit, (b) larger seat count if you're growing, (c) paid-up-front terms.
Anchor: 'We renewed at X% increase last year. We can't justify another increase to the board. If the price holds flat, we'll commit to 2 years instead of 1.'
For HubSpot specifically: reference Standard Marketing Hub at $50/mo (their cheapest tier) as the floor. Every contact tier above that is negotiable.

Week 8 · Credible alternative leverage

Bring credible alternatives into every conversation: Apollo for ZoomInfo, Apollo for HubSpot Sales Hub, Fireflies for Gong (low-volume seats), Smartlead for Outreach (cold-email-only motions).
Don't bluff — actually price out the alternative and have the contract terms ready. Vendors can tell when the threat is real.
Document the discount achieved per renewal. If you're not getting at least 8% off list, the conversation isn't leveraged enough.

Days 61-90

Strategic consolidations

The hard cuts. Switching tools, eliminating overlap, changing motion. These take longer to operate but produce the biggest single-decision recovery. Goal: kill at least one duplicate-capability stack pattern.

Expected recovery: 15-25% of total annual GTM stack spend

Week 9 · Sequencing canonical decision

If you run HubSpot Sales Hub Pro AND a separate SEP (Outreach, Salesloft, Apollo): pick one. The math usually favors HubSpot bundled for sub-30 reps and dedicated SEP for 50+ reps with governance burden.
Migration prep: export sequence templates from the cut tool, import to the canonical. Plan 4-6 weeks for 25 reps to acclimate.
Inform the vendor of the cut at the next renewal cycle. Don't announce mid-cycle — they'll try to save the account with discount maneuvers.

Week 10 · Conversation intelligence canonical

If you have Gong AND (Outreach Kaia OR Salesloft Drift CI): keep one. Most teams keep Gong (deeper recording quality, better deal intelligence).
Downgrade the SEP to the tier without bundled CI: Outreach Engage → Standard saves $30/user/mo; Salesloft Premier → Advanced saves $40/user/mo.
For sub-50-rep teams without dedicated enablement: consider downgrading Gong itself to Fireflies/tl;dv. Recovery: $1,000+/seat/yr. Trade-off: lose AI flagging and forecasting.

Week 11 · Data canonical

If you pay for ZoomInfo AND Apollo on overlapping use cases: pick one. Apollo wins for SMB/mid-market on TCO ($30K-$50K/yr recovery at 30 reps). ZoomInfo wins for enterprise ABM with deep technographic research.
If Clay is in the stack alongside ZoomInfo and an SEP: the triple-stack is rarely justified below 50 reps with dedicated ops. Decide on a canonical pattern (Clay-led with native enrichment ecosystem, OR Apollo-led with bundled data + sequencing).
Migration prep: export contact lists, reproduce critical enrichment chains in the canonical tool, run 4-6 weeks of side-by-side validation before final cutover.

Week 12 · Motion-level reset

Document the new stack in one diagram: tool, role, owner, monthly cost, renewal date. This becomes the source of truth for the next renewal cycle.
Set quarterly renewal review cadence — not just at end-of-contract. Quarterly reviews catch tier creep, dormant seat drift, and add-on bloat before they compound.
Audit the StackScan output again. Re-run if needed. The post-consolidation stack should produce a cleaner overlap map and clearer 12-month roadmap.

Common pitfalls

Announcing cuts mid-cycle

Vendors will deploy retention discounts, account-team escalations, and "save offers" that look attractive in the moment but lock in 12+ more months at slightly-lower price. The right move is to inform vendors of cuts ONLY at renewal, not before.

Treating renewals as transactions, not negotiations

A renewal is a 90-day conversation, not a 30-day one. The vendor expects it to start at 30 days out and close at 5 days out. Starting at 90 days flips the leverage — you have time to develop credible alternatives, run usage audits, and walk if needed.

Cutting the wrong tool

Tools with high cost but high integration depth (HubSpot, Salesforce) are usually wrong cuts. Tools with low cost but low utilization (the $99/mo SaaS nobody opens) are wrong focus. The right cuts are duplicate capability — two tools doing the same job — where one can be eliminated without operational loss.

Skipping the post-cut audit

Consolidation isn't complete until you run StackScan again 90 days post-cut. New overlaps emerge, dormant seats drift back up, add-on creep returns. Quarterly cadence is the only thing that prevents the stack from re-bloating.

Outsourcing the decision to a SaaS management tool

Vendr, Zylo, Tropic, Torii, Zluri are useful for inventory, negotiation, and governance — but none of them tell you which tools to cut. The decision is operational: which capability is duplicate, which is dormant, which is unjustified at scale. SaaS management tools surface data; consolidation is a judgment.

FAQ

How much can a typical mid-market team recover in 90 days?: Modeled across the GTM stack patterns we track: 25-40% of total annual GTM stack spend, mostly through duplicate-capability cuts (Outreach + HubSpot sequencing, Gong + Kaia, Apollo + ZoomInfo) and dormant-seat de-provisioning. The exact figure depends on stack composition — teams with heavy SEP + CI overlap see the biggest recovery; teams already running lean see less but still recover 5-15% through year-2 uplift refusal and tier audits.
Do we need executive buy-in to run this playbook?: For Days 1-30 (dormant assets, departed-employee seats, no-conversation cuts): no executive sign-off needed. Recovery is direct savings, not strategic. For Days 31-60 (renewals): finance approval helps but most renewals are within RevOps/CRO authority. For Days 61-90 (strategic consolidations): executive sponsorship is required because it touches sales motion. The right cadence is: run Days 1-30, document the recovery, then bring the larger plan to leadership with proof of execution.
What if our renewal isn't for 6 months?: Run Days 1-30 immediately — dormant seats, departed-employee de-provisioning, and add-on cuts don't require a renewal. Add-on cuts (Outreach Kaia, Salesloft Drift CI, Apollo Buyer Intent) are usually month-to-month or have separate contract terms — most can be cancelled mid-cycle. Then time Days 31-90 to land 90 days before each major renewal, in waves.
How do we know which capability overlap to cut?: Three-question test: (1) which tool is the source of truth — where reps actually do the work? (2) which tool has the deeper integration with the rest of the stack? (3) which contract is harder to exit (longer term, larger penalty)? Cut the tool that fails 2-of-3. The hardest case is when both tools score equally — those are usually post-acquisition stack patterns where neither team wants to migrate, and the right call is forcing the decision via a renewal-deadline hard date.
What about migration risk during consolidation?: Real but usually overstated. The big risks are: (1) data loss (sequence templates, recordings, enrichment history) — mitigate by exporting before cutover, (2) rep adoption (workflow change burden) — plan 4-6 weeks of side-by-side, (3) integration breakage (CRM sync, data flows) — test in sandbox first. Most consolidation projects underestimate the operational lift by 30-50%; budget accordingly. The savings still pencil out, but plan for 8-10 weeks of sustained operational effort, not 4-6.
When should we re-audit?: 90 days post-consolidation: run StackScan again to validate the cuts and surface new overlaps. Quarterly thereafter: quick tier + dormant-seat review (~30 minutes). Annually: full audit before the largest renewal of the year. The stack re-bloats over time — new tools get adopted by departments, add-ons creep back via QBR upsells, dormant seats drift up as teams change. Quarterly cadence is the only structural defense.
Can StackSwap run this playbook for us?: StackScan produces the input — the ranked overlap and consolidation map. The 90-day execution is operational and lives with your RevOps/CRO. We can scope a deeper engagement (audit + consolidation roadmap + vendor negotiation prep) for teams that want hands-on support. Start with the free StackScan to see the cut list, then decide if you need help operating it.