60-Min Sales Training: Cross-Sell to Existing Customers
Direct Answer
Run a 60-minute cross-sell training that locks AEs and CSMs onto a three-trigger framework (usage signal, stakeholder change, support pattern), a CSM-led intro script, and a joint go-to-market motion with a written RACI. The session ends with every AE having three named accounts, a CSM intro request drafted in Slack, and a 14-day calendar invite on the books for the joint discovery call.
1. Setup (5 min)
Open with the 2027 expansion math, not a hype reel. Top-quartile B2B SaaS in 2027 runs NRR above 130%, while the median enterprise NRR sits at 118%, mid-market at 108%, and SMB at 97%. The single biggest gap between those quartiles is cross-sell motion discipline, not pricing or product.
If your NRR-to-GRR gap is under 10 percentage points, your cross-sell motion is broken; healthy 2027 benchmarks sit at 15-25 points of gap.
Put two numbers on the whiteboard:
- Your trailing 90-day cross-sell ARR
- Your installed-base ACV times 20% (the realistic 12-month opportunity ceiling if you ran a clean motion)
The delta is the meeting. Tell the room: "We are not pitching today. We are building the trigger list, the intro script, and the joint motion. By 4 PM Friday every AE has three named accounts moving."
Set the three ground rules:
- CSM owns the trust, AE owns the close. No AE cold-emails an active CSM-owned account.
- Every cross-sell starts with a logged trigger in the CRM. No trigger, no pursuit.
- CSM gets credit on the comp plan — surface the CSQL bounty (Customer Success Qualified Lead) so the room hears it from leadership, not from rumor.
Drop the agenda on screen and start the timer.
2. Framework Teach (15 min)
Teach the Trigger-Trust-Transfer (TTT) framework. It is the only model the team will use after today.
Trigger is the entry gate. The three trigger families that convert in 2027:
- Usage signals. Account hits 80% of seat license, blows through storage or API call limits, or shows power-user adoption of a feature that gates the next product tier. Marketing-automation operators reported expansion ARR jumping from 20% to 45% of new ARR after instrumenting an 80%-of-send-capacity trigger paired with a webhook-adoption upsell trigger.
- Stakeholder change. New VP of Sales, new CRO, M&A close, or a department reorg. Sales Navigator and Champify both surface these inside 48 hours; the trigger window is short.
- Support pattern. Three or more tickets on an adjacent use-case in 60 days is the cleanest signal you have — the customer is already trying to solve a problem your second product solves.
Trust is the second gate. The CSM owns it. A cross-sell pitched by an AE who hasn't earned the customer's time burns the relationship and the renewal. CSQLs convert at roughly 3-5x outbound conversion rates because they ride on proven adoption.
Transfer is the joint go-to-market. The CSM does not hand the customer over. They stay on the deal as the Expansion Champion, opening the call, vouching for the AE, and closing with a 60-second adoption story.
Hand out the printed TTT one-pager (front: framework diagram, back: RACI). Make it the cover of every 1:1 deck for the next quarter.
3. Verbatim Scripts (15 min)
Three scripts. Read them out loud as a room. Then the manager picks two AEs and two CSMs and reads them again in pairs.
Script 1 — CSM Intro Email (sent by CSM, AE on cc, never the other direction).
"Hi Priya, quick note while it's fresh. On our QBR Tuesday you flagged that the new sales-ops team Marcus hired is hitting the seat ceiling on the Growth plan and that forecasting in spreadsheets is eating your Mondays. We have a piece of the platform — Pulse Forecasting — that eight of your peers in industrial distribution are running today, including [Customer A] and [Customer B].
I'd like to put Jordan, our AE who covers your region, on a 25-minute call next Wednesday so you can see what it looks like in your data. I'll be on the call, and I'll only stay if it's useful to you. Two options: Wed 10 AM or Thu 2 PM Central.
Which is easier?"
The four moves inside that script: named pain from a real meeting, named peers (social proof, not generic logos), named AE with a region anchor, and CSM offering to leave — which signals the customer is not being handed off.
Script 2 — AE Discovery Opener (first 90 seconds of the joint call).
"Priya, thanks for the time. Before I touch any slide, I want to know what changed. Sam mentioned the new ops team and the Monday forecasting pain — what happened in the last 30 days that made this a priority over the other twelve things on your plate?
I'm going to ask three questions, then Sam will share what she's seen across your account, and we will decide together if there's a next step. If there isn't, we will give you the 25 minutes back."
The three moves: change-event question (what triggered now?), explicit ownership of the joint motion (Sam will share), earned-right-to-the-deck posture.
Script 3 — CSM Close-of-Call Vouch (last 60 seconds, CSM speaks).
"Priya, you've heard what Jordan can do on the forecasting side. Here's what I've seen in your account that matters for this decision: your team's adoption on the core platform is at 87%, which is the eighth-highest in our book of business; you've logged 14 successful forecast cycles; and the three peers Jordan mentioned all started with exactly the team-size and data-volume profile you're at today.
If you decide to move forward, I stay on your account, I stay on every implementation call, and the Monday forecasting pain is on me too — not just on Jordan."
The vouch is the close. The CSM is staking their relationship on the second product working. That is the trust transfer.
4. Role-Plays (15 min)
Break into trios: one AE, one CSM, one observer with a scorecard. Three rounds, four minutes each + one minute of feedback.
Round 1 — Usage-Signal trigger. Scenario: Customer hit 92% of their seat license three weeks ago. CSM runs Script 1 live, AE responds as the customer (objection: "We are slammed, send a deck"). CSM holds the call, books the 25-minute slot.
Observer scores named pain (1pt), named peers (1pt), CSM-offers-to-leave (1pt), specific time options (1pt).
Round 2 — Stakeholder-Change trigger. Scenario: New VP of RevOps started 11 days ago at a customer with 18 months on the platform. AE runs Script 2 live with CSM in the room. The "customer" is coached to push back: "I haven't even unpacked my boxes." AE must land the change-event question and the three-questions-then-decide-together posture.
Observer scores change-event question used (1pt), CSM ownership stated explicitly (1pt), earned-right-to-deck posture (1pt), gave-time-back option offered (1pt).
Round 3 — Support-Pattern trigger. Scenario: Customer logged four tickets in 60 days asking how to pull data into BI tools — the cross-sell product is your reporting module. CSM runs Script 3 vouch at the end of a simulated discovery. Observer scores specific adoption number used (1pt), peer profile match called out (1pt), staked CSM ownership of outcome (1pt), no hand-off language (1pt).
Rotate so every person runs all three roles. Manager floats and interrupts any AE who slips into a generic pitch — full stop, restart the round.
5. Common Pitfalls (5 min)
Five failure modes the room will recognize.
Pitfall 1 — The AE cold-emails the customer the day after the QBR. Kills the CSM's trust capital in one move. Rule: no AE outreach inside seven days of a CSM-touched conversation without CSM written approval in Slack.
Pitfall 2 — "Just put me in touch" with no trigger logged. AE asks CSM for intros to "any account that might want product two." Result: shotgun emails to non-ICP accounts and a CSM who stops responding. Rule: every intro request includes a logged trigger ID from CRM.
Pitfall 3 — CSM disappears after the intro email. The deal stalls in week three because the AE is alone and the buying committee doesn't trust them yet. Rule: CSM is on every customer-facing call until close-won, full stop.
Pitfall 4 — Comp plan punishes the CSM. If the CSM's renewal number drops because the customer used the renewal budget on the cross-sell product, the CSM will quietly stop sourcing CSQLs within 60 days. The fix is a CSQL bonus of $500-$2,000 per sourced+closed deal plus carve-out language in the renewal target.
Surface this in the meeting; do not leave it to comp memos.
Pitfall 5 — Generic "value prop" pitch. Customer hears the same deck they saw two years ago. Rule: every cross-sell deck rebuilt around the specific trigger — usage screenshot, named stakeholder change, or ticket thread — in the first three slides.
6. Action Items + Drill (5 min)
Every AE leaves the room with three named accounts on a 14-day clock. Every CSM leaves with a triage list and a Slack DM template. Manager owns the scoreboard.
The drill: manager DMs every AE at 9 AM Day 1 asking for the three account names and trigger IDs. Any AE who is late gets a 15-minute clinic, not a lecture. Any CSM who pushes back on a non-ICP intro request gets backed publicly. The scoreboard goes on the team channel Day 14 and stays up for the quarter.
Close the meeting with the two numbers from minute one, and the room's commitment to close the delta. No deck recap. Adjourn.
FAQ
Q1: My CSMs are already maxed on renewals — how do I add cross-sell sourcing without breaking them? Cap CSQL sourcing at three named accounts per CSM per quarter for the first two quarters. That is enough to build the motion without burning the team. Once the comp plan lands and the bonus pays out twice, capacity expands on its own — CSMs prioritize what gets paid.
Q2: What if the AE doesn't have a relationship with the CSM yet? Run a CSM-AE pairing kickoff in week one — 30-minute coffee, account-by-account walkthrough of the top 10 ICP-fit installed accounts per AE. No selling, no roleplay, just context exchange. The relationship is a prerequisite, not an output.
Q3: How do we handle the customer who feels "sold to" by their CSM? The CSM-offers-to-leave move in Script 1 is the antibody. If the customer says no, the CSM honors it on the spot and goes back to renewal mode, no soft re-pitch in the next QBR. One "no" buys six months of trust; one ignored "no" burns the renewal.
Q4: Should the SDR team be involved at all? Not on CSM-sourced motions. SDRs add friction to a warm CSQL and the customer reads it as "I just got handed off to a junior person." SDRs run cold cross-sell on accounts the CSM doesn't actively own (dormant logos, low-touch tier) — that is a separate motion with a separate playbook.
Q5: My CRM doesn't have a CSQL stage. Do I need to wait for ops? No. Add a custom field called trigger_id (free text) and a lead source value called CSQL today. The full CSQL pipeline stage can come in 30 days. The motion does not wait on Salesforce admin queue depth.
Sources
- ChurnZero — Customer Expansion, Upselling, and Cross-Selling for CS Teams
- ChurnZero — Sales and Customer Success Alignment Expansion RACI
- Gainsight — Customer Expansion Software for Cross-sell & Upsell
- ZoomInfo Pipeline — Signals That Indicate Cross-Selling Opportunities
- Stackmatix — Expansion Revenue Marketing: Upsell and Cross-Sell Without Being Pushy
- MatrixFlows — CS to Sales Handoff: Why Expansion Stalls and How to Fix It
- Growthspree — B2B SaaS NRR and GRR Benchmarks 2026 by ARR Stage, Vertical, and GTM Motion
- SaaS Mag — Why Net Revenue Retention Is the Defining SaaS Metric of 2026
- Levera Partners — NRR in SaaS: 2026 Benchmarks and How to Improve
- Bridge Partners — The Five Cardinal Rules of Joint Go-to-Market