Account Expansion Conversation Script Pack
Five word-for-word scripts for the live expansion conversations that account managers actually face, from proactive success bridges to stalled-deal restarts. Each script includes context notes, named objections, and honest warnings about when not to use it.
How to use it
Pick the script that matches your current situation, read the context note first, then practise it aloud before using it live. Swap in the bracketed fill-ins before the call, not during it. After each conversation, note which objections surfaced and use the named objection responses to sharpen your next attempt.
What's inside
- Script 1: The proactive success-to-expansion bridge (moving from a positive check-in into a growth conversation)
- Script 2: The reactive inbound expansion request (handling a customer who comes to you asking for more)
- Script 3: The multi-stakeholder expansion pitch to a new budget holder (entering a room where you have no relationship yet)
- Script 4: The stalled expansion restart (reopening a deal that went quiet without burning goodwill)
- Script 5: The post-QBR expansion ask (converting QBR momentum into a concrete next step)
- Named failure modes for each script (pitching before value is established, leading with product, misreading a compliment as buying intent)
- Common objections specific to each conversation type, with word-for-word responses
- When NOT to use guidance for every script
How to read these scripts
Each script is written as a practitioner guide, not a rigid transcript. The structure is: context note, opening, transition, the expansion moment, likely objections with responses, and a "when NOT to use this" warning. Adapt the tone to your relationship, but keep the logical sequence intact. That sequence is what prevents the most common AM failure modes: pitching before value is established, leading with product rather than outcome, and misreading a warm conversation as buying intent.
Script 1: The Proactive Success-to-Expansion Bridge
Context: You are in a regular check-in or success call. Things are going well. You want to introduce a growth conversation without turning a positive moment into a sales ambush.
The failure mode this prevents: Hearing "we love it" and immediately saying "great, let me tell you about [Product X]."
Opening: "Before we finish today, I want to use the last few minutes well. You've mentioned [specific result or positive outcome] a couple of times, and I want to make sure we're not leaving anything on the table for your team. Can I ask you one or two questions?"
The expansion moment: "You said [result]. I'm curious: is that result contained to [current use case / team / region], or are there other parts of the business where something similar would matter?"
Listen. Do not fill the silence. If they name something, say:
"Tell me more about that. Who owns that area?"
If they do not name anything, say:
"That's fine. What I'd suggest is we give that some thought and I'll come back with a couple of ideas. No pressure on this call."
Common objections and responses:
| Objection | Response |
|---|---|
| "We're happy where we are." | "Completely understood. I'm not suggesting change for the sake of it. I just want to make sure that if there's a natural next step when the time is right, we've already had the conversation. I'll leave it there." |
| "I'd need to check with [other person]." | "Of course. Who should I be talking to alongside you? I can make it easy for them to get up to speed." |
When NOT to use this: Do not use this script if the customer raised a problem or complaint earlier in the same call. Deal with that fully first. Using this script over a live issue signals that you are focused on your number, not their outcome.
Script 2: The Reactive Inbound Expansion Request
Context: The customer contacts you asking about additional products, seats, features or services. The risk here is moving too fast and closing a small deal when a bigger one is available, or over-engineering a simple request.
The failure mode this prevents: Taking the request at face value without understanding the underlying need, then leaving scope on the table.
Opening: "Thanks for reaching out. I want to make sure I get this right for you rather than just send over a quote. Can I ask a couple of questions first?"
The expansion moment: "What's prompting this now? Has something changed, or is this more of a 'we've been meaning to do this for a while' situation?"
If they give a specific trigger: "That's useful context. So the real problem you're solving is [restate in their words]. Is that fair?"
Then: "Before I put anything together, I want to check whether what you're asking for is the right solution for that problem, or whether there's a better fit in what we have. Give me 24 hours and I'll come back with a recommendation, not just a price."
Common objections and responses:
| Objection | Response |
|---|---|
| "We just want a price, we don't need a full review." | "Completely fair. I can send you a number today. I just want to flag that in similar situations we've found [brief example of a better fit]. If you'd rather move straight to the quote, I'll do that now." |
| "We've already decided what we want." | "Understood. I'll put it together. I will include one alternative option with a short note on the difference, just so you have it to hand." |
When NOT to use this: Do not slow down a customer who has clear authority, clear budget and a simple, well-scoped request. Slowing down a decided buyer to ask probing questions reads as obstructive. Send the quote and ask one follow-up question at the end.
Script 3: The Multi-Stakeholder Expansion Pitch to a New Budget Holder
Context: You are being introduced to, or are requesting a meeting with, a budget holder or executive who does not know you. Your champion has opened the door. You have one shot at credibility.
The failure mode this prevents: Walking in as "the account manager who wants more money" rather than someone with a point of view.
Opening (after introductions): "Thanks for making time. [Champion's name] suggested this conversation because we've been working together on [current scope] and have seen [specific result]. I'm not here to pitch anything today. I want to understand whether what we've built with [champion's name]'s team is relevant to what you're responsible for, and if so, what that might look like."
The expansion moment: "Can I ask: when [champion's name] mentioned what we've been doing, what caught your attention, if anything?"
Listen carefully. If they engage, ask: "What would need to be true for that to be worth exploring further in your area?"
If they are cautious or non-committal: "That's fine. The most useful thing I can do is leave you with a short summary of what we've delivered and one or two examples from similar businesses in your position. Would that be useful?"
Common objections and responses:
| Objection | Response |
|---|---|
| "I'm not sure this is relevant to my team." | "Fair. What does your team focus on? I'd rather tell you now if there's no fit than waste your time." |
| "We'd need to go through procurement." | "Of course. When that time comes, I can give you everything you'd need to make that straightforward. For now, is the concept of interest?" |
| "What does this cost?" | "I don't want to give you a number before I understand your situation, because the number varies significantly depending on scope. What I can tell you is the range we typically work in for teams like yours is [£X to £Y]. Does that fit a conversation worth having?" |
When NOT to use this: Do not book this meeting without your champion's full support and a clear brief on the stakeholder's priorities. Going in blind on a warm introduction is still going in blind.
Script 4: The Stalled Expansion Restart
Context: An expansion conversation started, got positive signals, then went quiet. It has been 3-6 weeks. You need to re-open without guilt-tripping or desperation.
The failure mode this prevents: "Just checking in" emails that signal you have nothing new to say.
Opening: "[Name], I want to be straightforward with you. We spoke about [expansion topic] a while back and things went quiet, which usually means either the timing was off or something changed. I'm not following up to push, I'm following up because I'd rather know which it is."
The expansion moment: "Has the situation changed, or is this still something that's on the radar but hasn't had the right moment?"
If timing was wrong: "That makes sense. Is there a better moment I should come back? I'd rather put a date in the diary now and respect that, than keep checking in at the wrong time."
If priorities changed: "I appreciate you telling me. What's taken priority? I want to make sure I understand what's important to you right now."
Common objections and responses:
| Objection | Response |
|---|---|
| "We've put this on hold." | "Understood. What would need to change for it to come off hold? I want to know so I can be useful when that happens." |
| "We went a different direction." | "Thanks for being straight with me. Can I ask what drove that? I'm not trying to reverse the decision, I just want to understand it so I can be more useful in future." |
When NOT to use this: Do not use this script if the deal stalled because of an unresolved service issue, a billing dispute or a relationship problem. Fix the underlying issue first. Using a restart script on a broken relationship reads as tone-deaf.
Script 5: The Post-QBR Expansion Ask
Context: You have just run a QBR. The customer is engaged, the results are strong, the room is positive. This is the highest-intent moment in any account cycle. Most AMs waste it by ending the meeting without a next step on growth.
The failure mode this prevents: Leaving a QBR with nothing but a "great meeting, let's do this again in 90 days."
Opening (at the end of the QBR): "Before we close, I want to use the last five minutes on something forward-looking. We've covered what's worked over the last quarter. I want to make sure the next quarter is even more useful to you."
The expansion moment: "Looking at what we've shown today, is there anything here that made you think: we should be doing more of this, or: there's a gap we haven't solved yet?"
If they engage: "That's worth a proper conversation. Can we schedule 30 minutes in the next two weeks specifically on that? I'll come with a structured proposal, not just ideas."
If the room is positive but vague: "Here's what I'd suggest. I'll send a short note this week with two or three areas where I think there's a logical next step. If any of them resonate, we schedule time. If none of them do, that's useful feedback too."
Common objections and responses:
| Objection | Response |
|---|---|
| "Let's get through the current phase first." | "Completely fair. When would be the right time to have that conversation? I want to put a date in the diary so it doesn't get lost." |
| "I'd need to check budget." | "Of course. What I'd find useful is understanding whether it's a timing question or a priority question. That changes how I'd approach the proposal." |
When NOT to use this: Do not use this script if the QBR surfaced unresolved problems that dominated the conversation. A growth ask after a difficult QBR signals poor situational awareness. Close the meeting on a plan to resolve the issues. Save the expansion conversation for when those issues are behind you.
Common failure modes: quick reference
| Failure mode | Where it shows up | The fix |
|---|---|---|
| Pitching before value is established | Scripts 1 and 3 | Ask one more question before making any recommendation |
| Leading with product instead of outcome | Scripts 2 and 5 | Name the customer's problem before naming your solution |
| Misreading a compliment as buying intent | Scripts 1 and 5 | Test intent explicitly: "Is that something you'd want to explore?" |
| Reopening a deal without new information | Script 4 | Bring something: a relevant case study, a changed piece of data, a direct question |
| Rushing past an objection | All scripts | Repeat the objection back before responding. It slows you down and signals you heard them. |