The Sales Tech Stack Reboot — 60-Min Training

Direct Answer

Section 1 — Frame the Reboot (5 min)

Open the room with the cost of the status quo. Sales Hacker's 2025 Tech Stack Report (Max Altschuler, Scott Barker) puts the median B2B SaaS sales tool count at 17 with annual spend between $4,200 and $9,800 per rep. OpenView Partners (Kyle Poyar) tracks a tighter top-quartile band of 9-11 tools at higher productivity.

Then state the goal of the hour out loud:

• Outcome 1: A single page that maps every tool to one of 5 layers.
• Outcome 2: A keep / cut / consolidate decision for every tool the team can name in 60 seconds.
• Outcome 3: A named owner for each of the 5 layers and a deprecation cadence on the calendar.

Ground rule: nothing is "sacred." If a tool cannot defend its layer with usage data and a buyer-visible outcome, it goes on the cut list.

Section 2 — The 5-Layer Architecture (15 min)

Whiteboard the five layers in this order. Every tool in the company must land in exactly one. If it lands in two, you have a consolidation candidate.

1. CRM Core — system of record, account/contact/opportunity object, forecasting. Examples: Salesforce, HubSpot, Pipedrive. Rule: exactly one, never two.
2. Engagement — outbound cadences, email/phone/LinkedIn sequencing, meeting booking. Examples: Salesloft, Outreach, Apollo, Chili Piper. Rule: one primary; second tolerated only for outbound vs. Inbound split.
3. Intelligence — contact data, intent signals, conversation intelligence, ICP fit scoring. Examples: ZoomInfo, Clearbit, Gong, Chorus, 6sense, Bombora. Rule: one data layer, one conversation layer — not three of each.
4. Enablement — content management, training, deal rooms, digital sales rooms. Examples: Highspot, Seismic, Mindtickle, DocSend. Rule: one platform; do not let "content lives in five places" survive the meeting.
5. Analytics — pipeline analytics, forecasting, revenue intelligence, deal inspection. Examples: Clari, BoostUp, InsightSquared, Looker/Tableau on top of warehouse. Rule: the layer the CRO actually opens daily wins.

Bowery Capital's "SaaS Sales Stack" map (revised 2025) is the canonical reference here — print it and tape it to the wall. Trish Bertuzzi's *The Sales Development Playbook* makes the same architectural point for the SDR org specifically.

Section 3 — Consolidation Framework: Keep / Cut / Consolidate (10 min)

For every tool on the wall, the team votes one of three buckets in under 90 seconds per tool. Use these tests verbatim:

• KEEP if: the tool is the *only* one in its layer AND 70%+ weekly active users among reps AND a renewal in the next 6 months would cause a measurable outcome regression.
• CUT if: under 40% weekly active, OR duplicates a feature already covered by a Keep tool, OR no rep can name the outcome it produces in one sentence.
• CONSOLIDATE if: two tools overlap >50% on use case, OR a Keep tool has a module that covers the function at <30% incremental cost.

Vendr (Ryan Neu) and Tropic publish median consolidation savings of 18-31% of stack spend when this framework is applied cleanly — most of that comes from collapsing Intelligence (data + conversation) and Engagement (sequencer + booker) overlaps.

Section 4 — The "No Shadow Stack" Rule (10 min)

Shadow stack = any tool a rep, manager, or marketing team paid for with a personal card, a department card, or a "free trial we never turned off" that touches a prospect. It is the single biggest source of data leakage, compliance risk, and forecast distortion in B2B SaaS.

Run this audit live in the meeting:

• Pull the AmEx/Brex feed for the last 90 days, filter SaaS merchants, surface anything not in the official stack.
• Pull Chrome extension inventory from IT (Google Workspace admin → Apps → Chrome).
• Pull the OAuth grants from Google Workspace and Microsoft 365 — every "Sign in with Google" to a sales tool is a shadow-stack candidate.
• Pull email subdomains (mailgun, sendgrid, etc.) sending on your behalf — unauthorized senders are deliverability landmines.

The rule, written on the wall: "If it touches a prospect, it goes through RevOps or it gets shut off by Friday." No exceptions, no grandfathering, no "but my AE loves it." OpenView's 2025 RevOps benchmark found shadow-stack tools were responsible for 27% of duplicate-contact CRM pollution and a measurable lift in unsubscribe rates when discovered.

Section 5 — The 10-Point Vendor Evaluation Rubric (15 min)

Apply this rubric verbatim to any tool entering or surviving the stack. Score each criterion 0-1. Threshold: 7/10 to keep or buy. Below 7 is a cut or a no-buy.

1. Integrates natively with CRM Core (not Zapier-only). 0 or 1.
2. Has SOC 2 Type II and a current pen test report on file. 0 or 1.
3. Single sign-on (SAML/SCIM) included in the tier we pay for. 0 or 1.
4. Named CSM with quarterly business review committed in writing. 0 or 1.
5. Usage telemetry exposed via API or admin console (we can measure WAU). 0 or 1.
6. Contractual price protection — capped uplift at renewal (<=7%). 0 or 1.
7. Reference customer at our ACV band and company size will take a call. 0 or 1.
8. 30-day exit with data export in machine-readable format. 0 or 1.
9. No overlap >50% with an existing Keep tool's roadmap. 0 or 1.
10. A named internal owner willing to put their name on the renewal. 0 or 1.

Vendr's 2025 SaaS Buyer Report shows buyers who use a written rubric like this negotiate average discounts of 22-34% versus 8-12% for buyers without one. Procurement leverage is built before the call, not during it.

Section 6 — Deprecation Cadence + Named Owners (5 min)

Close the hour by writing two things on the board and then putting them on the company calendar:

• Quarterly Stack Review — same 60-minute format, every quarter, on the books for the next 4 quarters. Re-run the rubric on every tool. Tools that drop below 7/10 or below 60% WAU get a 60-day deprecation notice the same day.
• Named owners by layer — one human name per layer, full stop:
• CRM Core owner: ____________
• Engagement owner: ____________
• Intelligence owner: ____________
• Enablement owner: ____________
• Analytics owner: ____________

Owner accountability is the difference between a stack reboot that holds and one that drifts back to 17 tools in 9 months. Bertuzzi's playbook calls this "one throat to choke per layer" — uncomfortable language, correct principle.

FAQ

Q: What if our CRM Core is the wrong tool? Can we cut it in this meeting? A: No. CRM Core migration is a 6-9 month project with its own kickoff. Flag it on the wall, schedule the discovery, but do not let it derail the reboot. Every other layer can be cut in 60 days.

Q: How do we handle a tool that scores 6/10 but reps love it? A: Reps loving a tool is not on the rubric on purpose. "Love" is a lagging proxy for value and a leading indicator of switching cost. Cut it, give the 60-day notice, and measure the outcome regression. If something measurable breaks, you bring it back. Usually nothing breaks.

Q: Does this apply to a 5-person sales team? A: Yes, but the layers compress. A 5-person team should run 4-6 tools total, not 8-11. The framework is the same; the headcount per layer is zero or shared with RevOps.

Q: What's the ROI math we present to the CFO? A: Two lines. (1) Direct spend reduction — Vendr/Tropic median is 18-31% of stack spend on consolidation. (2) Selling-time recovery — every tool above 6.4 costs ~4% of rep selling time (Sales Hacker). Multiply by fully-loaded rep cost and quota attainment delta.

Q: How often do we re-run this meeting? A: Quarterly is the floor. The deprecation cadence is the meeting — same room, same wall, same rubric, every 90 days. Calendar it before everyone leaves the room.

Sources

1. Sales Hacker — *2025 B2B Sales Tech Stack Report* (Max Altschuler, Scott Barker)
2. Bowery Capital — *SaaS Sales Stack Map* (2025 revision)
3. OpenView Partners — *2025 RevOps Benchmark Report* (Kyle Poyar)
4. Trish Bertuzzi — *The Sales Development Playbook*, The Bridge Group
5. Vendr — *2025 SaaS Buyer Report* (Ryan Neu)
6. Tropic — *State of Software Procurement 2025*
7. Gong Labs — *Conversation Intelligence Adoption Benchmarks 2025*
8. Clari — *State of Revenue Operations Report 2025*