# Upsell & Cross-Sell Email Swipe File > 15 proven, word-for-word email openers for surfacing expansion opportunities: organized by the trigger that makes them timely: so outreach reads as helpful, not like a sales pitch. Free script/swipe for sales reps. Topic: [Account Management, Retention & Expansion](https://www.peerlab.ai/library/topic/account-management-retention-expansion/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/upsell-cross-sell-email-swipe-file/ ## How to use it Match the trigger to what's actually happening on the account right now (a usage spike, a new hire, a milestone), copy the closest template, personalize the bracketed fields, and send, don't reuse the same opener twice on the same contact. ## What's inside - 3 usage-triggered openers (power users, limits, new use cases) - 3 milestone-triggered openers (ROI proof points, anniversaries) - 3 team-growth-triggered openers (new hires, new departments) - 3 feature-launch-triggered openers (new capability relevant to them) - 3 low-pressure check-in openers for quiet accounts with expansion potential - A subject line for every email - Guidance on when NOT to send 15 emails, grouped by the trigger that makes them timely. Match the trigger to what's actually happening on the account, don't fire these off cold. ## A. Usage-Triggered **A1: Approaching a plan limit** Subject: Looks like [Team] is close to your plan's limit Hi [Name], I noticed [Team]'s usage of [feature/workflow] has grown [X]% over the last [timeframe], you're now close to the limit on your current plan. That's usually a good sign, so before it becomes a blocker: want me to walk you through what the next tier unlocks? Should take 15 minutes. [Your name] **A2: New use case discovered organically** Subject: Saw your team using [Product] for [use case]: didn't expect that Hi [Name], I noticed your team has started using [feature] for [use case] we don't usually see, that's a smart application. A few of our customers doing something similar have also added [related feature/module], mostly to [specific benefit]. Worth a quick look together? [Your name] **A3: Strong pilot, worth extending** Subject: The [department] rollout is working, worth extending it? Hi [Name], [Department]'s adoption has been strong since go-live, usage and outcomes both ahead of where most rollouts land at this stage. I know [adjacent team] has a similar workflow. Want me to put together a quick view of what that would look like for them? [Your name] ## B. Milestone-Triggered **B1: ROI milestone hit** Subject: You've hit [X] in [outcome] since go-live Hi [Name], Wanted to flag a number: since go-live, [Team] has [quantified outcome, e.g. "saved roughly 400 hours" / "processed $2M through the workflow"]. That's ahead of where most accounts your size land at this point. Given that, I think there's a case for extending this into [adjacent area], want to put 20 minutes on the calendar to look at the numbers together? [Your name] **B2: Contract anniversary** Subject: One year in: here's what's changed, and what's next Hi [Name], Hard to believe it's been a year since we kicked off. Looking back at where things started vs. now, [specific outcome] stands out. Before we get into renewal conversations, I'd love to spend some time on where else this could go, a few ideas came out of looking at your usage data. Open to a call this week or next? [Your name] **B3, Case study / reference moment** Subject: [Team]'s results are genuinely one of our best, want to go further? Hi [Name], The results your team has gotten with [use case] are strong enough that I'd love to feature them (with your sign-off, of course). Separately, teams that hit this kind of result usually find [adjacent workflow] valuable next. Want me to send over what that would look like? [Your name] ## C. Team-Growth-Triggered **C1, New hires on the account** Subject: Saw the team's grown, worth revisiting seats? Hi [Name], Congrats on the growth, saw [Company] has added [X new roles/headcount] recently. Wanted to check whether your current seat count still fits, or if it's worth adjusting before anyone's stuck waiting on access. Happy to make this a 10-minute admin task, not a sales conversation. [Your name] **C2: New department/geo expansion (news trigger)** Subject: Congrats on the [new office/market] launch Hi [Name], Saw the news about [new office/market/product line], congratulations. Given how [current team] is using [Product] for [use case], I'd guess the same problem exists there. Want me to sketch out what standing that up would take? [Your name] **C3: New stakeholder identified** Subject: Introducing you and [new stakeholder] on the [Product] side Hi [Name], Noticed [new stakeholder]'s joined [team/role]: thought it might be useful to loop them in on what [current team] has built with [Product], especially if their group has a similar need. Open to a short three-way intro call? [Your name] ## D. Feature-Launch-Triggered **D1: New feature relevant to their use case** Subject: New: [feature name]: built for exactly what [Team] is doing Hi [Name], We just shipped [feature name], and it's a near-exact fit for [specific workflow] you've described before. Wanted you to hear about it directly rather than find it in a release note. Want a quick walkthrough? [Your name] **D2: Beta/early access invite** Subject: Early access to [feature] before it's generally available Hi [Name], Given how [Team] uses [Product], I think you'd get real value out of [feature], which isn't public yet. I can get you early access if you're interested: no cost to try it, and your feedback would help shape the general release. Want in? [Your name] **D3: Feature removes a known workaround** Subject: You won't need that workaround anymore Hi [Name], I remember your team built a workaround for [specific limitation] a while back. We just shipped [feature] specifically to close that gap. Worth 15 minutes to see if it replaces what you built? [Your name] ## E. Low-Pressure Check-Ins for Quiet Accounts **E1: No-agenda check-in** Subject: Not a sales email: just checking in on [use case] Hi [Name], Realized it's been a while since we've properly caught up. No agenda beyond hearing how things are going with [use case] and whether there's anything getting in the way. If there's nothing to discuss, no worries at all, just wanted to check in. [Your name] **E2: Sharing a peer insight, no ask** Subject: Thought of you when I saw this Hi [Name], [Peer company/similar team] just shared how they're using [feature/workflow] to solve [problem], reminded me of a conversation we had a while back. Sharing in case it's useful, no need to reply unless you want to dig in. [Your name] **E3: Direct, honest expansion-readiness check** Subject: Are we underusing [Product] on your end? Hi [Name], Genuine question, not a pitch: looking at how [Team] uses [Product] today, is there a workflow or team that's still doing [problem] manually that we haven't talked about? If so, I'd like to understand it before assuming what the fix looks like. [Your name] ## When NOT to Send - Any account currently flagged Orange or Red on the Customer Health Score Scorecard: fix health before pitching expansion - Within 30 days of a renewal decision still in progress: expansion asks compete with and can stall the renewal conversation - Immediately after an unresolved support escalation: lead with resolution, not upsell - To a contact who has explicitly said budget is frozen this cycle