The Upsell Script for Financial Services Customers: Expanding an Account Without Restarting Vendor Diligence

1. 1

   0. Pre-call usage audit — do not dial without these six

   Fill these in from your own systems, in their language, before you touch the phone: 1. **Adoption split.** Licensed seats vs. weekly active, separated by ops and advisor. "Ops has 22 seats and 19 weekly actives. The advisor side has 90 seats and 24." Name the dark corners — which office, which pod, which region never onboarded. 2. **Depth.** Which modules they touch. Have they ever used the alternatives-marks workflow? The held-away reconciliation? Last login of the exec sponsor — the COO, Wealth Management, or the Head of Client Reporting & Performance. 3. **Their outcome number, not your benchmark.** Business days from period close to client delivery, before and now. Compliance exceptions or 2210 kickbacks per cycle, before and now. Sourced from their instance or their own QBR words. 4. **Commercials.** ACV, renewal date, who signed, whether that person is still in the seat, discount level, co-term implications. 5. **Support history.** Any open P1, any escalation in the last 90 days, any missed cycle during their custodian conversion. A stale custodial feed that broke their December close changes this entire call. 6. **Champion status.** Promoted, sidelined, or gone? If your champion moved from ops to the platform team, that's good news you need to know before you dial. The test: can you say one thing about their account they'd be mildly surprised you knew? If not, don't dial.

2. 2

   1. Frame the call in the first thirty seconds

   "Thanks for the time. Two things, and I'll be straight about both. First, I pulled your last two quarter-end cycles and there's a pattern in the advisor-side usage I want to check with you, because I think it means something and I might be reading it wrong. Second — depending on what you say — there's a piece of our platform I think is relevant to it, and if the conversation tells me it isn't, I'll say so and we'll skip it. Fair?" Do not sandbag. Do not open with "we've just launched." You are pre-committing to walking away, which lowers their guard faster than any rapport-building.

3. 3

   2. Anchor on the result they already own — in their numbers

   "When we started, you were at [17] business days from period close to client delivery, and your ops lead described it to me as a two-and-a-half week fire drill. Last quarter you closed in [9], and the reconciliation breaks that used to eat the first three days are down to [two]. Does that match how it feels on your side, or am I reading the dashboard optimistically?" Then shut up. Their correction is worth more than your number — it tells you which metric they actually defend in front of the COO. Write it down verbatim; it becomes the first line of the business case they take upstairs. **If they can't confirm a result, stop the upsell.** "Then let's not talk about anything new today. If you can't point at a number, we've got a value problem and I'd rather spend this call on that." That's not a lost call. That's the only version that protects the renewal.

4. 4

   3. Say the underuse out loud before they do

   "Here's the thing I'd push back on if I were sitting in your chair. You've got [90] advisor-side seats and about [24] people in there in any given week. So why would you buy anything else before you've used what you've already licensed? That's the right question. Let me tell you what I think those other [66] are doing — because from my side they're not idle. They're building client review decks in PowerPoint on a Thursday night, pulling numbers off the custodian portal by hand, and sending them into advertising review as one-off attachments. The seats aren't wasted. The work is just happening outside the system where you can't see it or supervise it." Reframe unused capacity as **unrouted work**, not wasted spend. Then be honest about whether the module fixes it. Sometimes the answer is "it doesn't — you've got an onboarding gap in the Northeast office, not a product gap," and saying that buys you the right to come back next quarter.

5. 5

   4. Find the seam — diagnostic questions that open the gap

   Ask three or four, not all of them. Let them talk. - "Once the quarterly book goes out, what does an advisor build on top of it before a review meeting? Who touches that?" - "What's the Monday-morning fire drill that still happens — the one that isn't quarter-end?" - "When an advisor makes a one-off client-facing piece, how does it get into 2210 review, and what's your kickback rate on those?" - "Who's asking you for reporting you can't produce today? Is the CCO asking for exception counts by advisor?" - "During the custodian conversion, what did your team hand-build that should never have been hand-built?" - **The highest-yield question on this call:** "When we scoped the original deal, what did you deliberately cut because it was too big a bite at the time?" Most upsells were already scoped and cut in the first negotiation. You're not selling something new — you're reopening a decision they already made once, with eighteen months of evidence they didn't have then.

6. 6

   5. Introduce the module as the gap-closer — and lead with the audit trail, not the features

   "So the piece I'd put in front of you isn't a reporting tool — you've already got that from us and it works. It's the advisor-generated material layer. Same locked template library your compliance team already approved for the quarterly book, extended to the ad-hoc pieces: review meeting decks, held-away summaries, proposal comparisons. Mandatory disclosure blocks, no free-text field where someone can type a performance claim, every piece version-stamped with a reviewer log. The reason I think it's relevant to you specifically is that your 2210 kickback rate on the automated book is down at [4%], and on advisor-built one-offs it's still [22%]. Those are the same reviewers reading the same kind of document. The difference is one comes off approved template v4 and one doesn't." For a Chief Compliance Officer in the room, the sentence that matters is: "This doesn't remove the review. It changes what shows up in the queue — from 'read every page' to 'confirm the template version.'"

7. 7

   6. Build the case in their arithmetic — and say the price in the same breath

   Four steps. Unit, volume, capture rate, net. "Let's do the arithmetic with your numbers and you tell me where I'm being generous. **The unit.** A kicked-back piece costs you about three and a half hours all in — advisor rebuilds it, reviewer re-reads it, someone chases the right version. Is that low? **The volume.** Across the eight advisors in the [Northeast] pod, you logged [26] kickbacks last quarter. **The capture rate.** I'd assume it catches half. Not all of it — half. That's [45] hours a quarter back for eight advisors, and it takes your exception count on that pod from [26] to about [13]. **The net.** It's [$95] per advisor per month. For the eight-person pod that's [$760] a month — call it [$2,300] for the quarter. If you think half is optimistic, give me the number you believe and I'll rerun it in front of you." Hand them the pencil on the assumptions. That's the difference between a business case and a pitch deck. And name the firm-wide number too, unprompted: "At all [96] advisors it's [$9,120] a month. I don't want you signing that today. I want the pod number first."

8. 8

   7. Cost the implementation in hours and names — including the vendor-risk hours

   Bandwidth is the real objection; budget is the costume. So quantify the ask honestly, and include the part your competitors pretend doesn't exist. "Here's the full cost to your team. One 90-minute session with whoever owns the template library — probably your Head of Client Reporting — to load the existing approved blocks. Then two hours a week from that person for three weeks. My CSM runs the advisor enablement, not you. On the diligence side: this sits inside the same tenancy, same data flow, same sub-processors as what you already run. Nothing new leaves your environment. I'll send your VP of Third-Party Risk a delta memo — what changed and what didn't — plus the current SOC 2 Type II and updated data-flow diagram, so they can scope whether this is a full re-review or an amendment to the existing approval. I'd rather they tell me it's a full DDQ in week one than find out in week ten." If you can absorb work — template migration, the config, the enablement session — put it on the table here, not later as a concession.

9. 9

   8. Check the buying committee — it may have changed since the conversion

   "Last time this went through [name] on the platform side and finance signed off above [$50k]. Is that still the path, or did the threshold move after the conversion? And who owns third-party risk now — is it still [name], or did that get pulled under InfoSec?" If a new CCO, a new procurement policy, or a three-bid rule has landed since the original deal, you are running a fresh evaluation, not an expansion. You need to know that on this call, not in week six when your forecast has it closing.

10. 10

    9. The ask — small, specific, reversible, co-termed

    "Give me the eight advisors in the [Northeast] pod for one quarter-end cycle. Include the two who complained loudest about the last rollout — if it works for them it works for anyone. Success criteria you write, not me. My suggestion: kickback rate on that pod's client-facing material under [10%], and no increase in your days-to-delivery. If we miss it, we pull it out at the end of the quarter and there's nothing further owed. If we hit it, we roll it to the rest of the advisors at your March renewal and co-term it, so you're amending one contract instead of negotiating a second one. That's one procurement cycle instead of two, and it lands as a line item on a paper you're already signing." Co-terming is the most underused unlock on this call. It turns a new purchase into an amendment — which is exactly what a firm mid-conversion wants to hear.

11. 11

    10. Close and document — write the email your champion will forward

    Same day, short, and structured for the person who wasn't on the call — the COO, Wealth Management, or the Chief Compliance Officer: 1. The result they confirmed, in their words: "You said the close went from seventeen days to nine and the December cycle didn't slip even during the conversion." 2. The gap they described, in their words. 3. The value math with **their** assumptions, including the capture rate they chose. 4. The price, both pod and firm-wide. 5. The implementation ask in hours and names. 6. The diligence path: what's going to third-party risk and when. 7. Pilot scope, success metric, decision date. This email is the artifact, not your CRM note. Write it for the reader who has to defend it in a governance meeting.

12. 12

    11. Park signals — walk away from these, don't push through

    Do not run the upsell if any of these are live: - An open P1 or an unresolved escalation — especially a missed quarter-end delivery. - A custodian conversion in its cutover window, where every hour of ops attention is spoken for. - A champion who changed roles in the last 60 days. - Renewal inside 60 days with unresolved value questions. - Flat or declining weekly actives you can't explain. - A regulatory exam, a deficiency letter, or an SEC/FINRA sweep response in flight. In any of those, say it out loud: "You've got a bigger fire than this. Let's do the account review, I'll park the rest, and I'll bring it back after the cutover." Pushing through converts a healthy account into a churn risk to book an incremental thirty grand.

1. Rep

   Thanks for making the time. Two things, and I'll be honest about both. First — I pulled your last two quarter-end cycles and there's a pattern in the advisor-side usage I want to check, because I might be reading it wrong. Second, depending on what you say, there's a piece of our platform I think is relevant, and if the conversation says it isn't, I'll tell you and we'll drop it. Fair?

2. Buyer

   That's more agenda than I usually get on a check-in. I'll give you twenty minutes — I'm two weeks out from the second tranche of the custodian conversion, so my head is not really here.

3. Rep

   Understood, and I'll be quick. Start with what I've got. When we signed, you were at seventeen business days from period close to client delivery, and your December cycle ran into the second week of February. Last quarter you closed in nine, and you did it during the conversion. Does that match how it feels, or am I reading the dashboard optimistically?

4. Buyer

   Nine is right, but I'd push back on the framing. It's nine because we finally cleaned up the alternatives marks, not because of your software. And honestly, my ops team still lost a week in November when a custodial feed went stale.

5. Rep

   That's fair and I'll take the correction — the marks cleanup was your team's work, not mine. Can I ask about the stale feed, though? When that happened, how did the exceptions get caught?

6. Buyer

   The reconciliation break flagged before anything went out the door. Which — fine, credit where it's due. That's the part I'd have been fired for ten years ago. A wrong return number in a client statement is a books-and-records problem, not a typo.

7. Rep

   That's the sentence I wanted. Here's what I'd push back on myself with, then. You've got ninety advisor-side seats and about twenty-four weekly actives. If I were you I'd be asking why I'd buy anything else before using what I've got. So let me tell you what I think the other sixty-six are doing — they're building review meeting decks in PowerPoint on a Sunday and sending them into 2210 review as one-off attachments. Your kickback rate on the automated quarterly book is four percent. On advisor-built one-offs it's twenty-two.

8. Buyer

   I don't need you to tell me that. My CCO reports exceptions per period to the risk committee and that number is the reason she's on my calendar every month. But I'll stop you there — if you're about to sell me something that generates more client-facing material, that's a harder conversation, not an easier one. After the off-channel sweeps, anything that produces output without a clean audit trail is dead before it reaches her desk.

9. Rep

   Then let's talk about the audit trail before we talk about anything else, because if that doesn't satisfy her, nothing else matters. It's the same locked template library your compliance team already approved for the quarterly book, extended to ad-hoc pieces. Pre-approved blocks, mandatory disclosures, no free-text field where someone can type a performance claim. Every piece version-stamped with a reviewer log. It doesn't remove the review. It changes what shows up in her queue from 'read every page' to 'confirm it came off template v4.'

10. Buyer

    Even if she likes it, you're adding a module. That's a new line in our TPRM inventory. Which means a fresh DDQ, another SOC 2 read, InfoSec wanting a new data-flow diagram, and legal reopening the DPA. Last time that took us five months. I am not spending five months of vendor-risk attention during a conversion.

11. Rep

    Then I'd want your VP of Third-Party Risk to make that call in week one, not week ten. Same tenancy, same data flow, same sub-processor list as what you already run — nothing new leaves your environment. I'll send a delta memo: what changed, what didn't, plus the current SOC 2 Type II and the updated data-flow diagram. Let them tell us whether this is a full re-review or an amendment to the existing approval. If they say full DDQ, I'd rather know that today and time it after your cutover.

12. Buyer

    That's the right sequence, I'll give you that. But there's no tech spend until next fiscal. The conversion ate the line item.

13. Rep

    Then the pilot is small enough that I don't think it's a budget conversation. Give me the eight advisors in the Northeast pod for one quarter-end cycle. It's ninety-five dollars per advisor per month — seven-sixty a month, about twenty-three hundred for the quarter. Firm-wide at ninety-six advisors it's nine thousand one twenty a month, and I don't want you signing that today. I want the pod number first.

14. Buyer

    And the value on twenty-three hundred is what, exactly? Don't quote me an industry average. I've heard the thirty-percent-reduction slide.

15. Rep

    Your numbers only. A kicked-back piece costs about three and a half hours all in — advisor rebuilds it, reviewer re-reads it, someone chases the right version. That pod logged twenty-six kickbacks last quarter. I'd assume you catch half, not all — that's forty-five hours back across eight advisors and it takes exceptions on that pod from twenty-six to about thirteen. If you think half is generous, give me your number and I'll rerun it right now.

16. Buyer

    Half is generous. Call it a third. And my advisors won't touch it — we rolled out a planning tool two years ago and a third of them still work off a spreadsheet they built in 2019.

17. Rep

    At a third it's thirty hours a quarter for eight people, and that's still fine at twenty-three hundred. On adoption — that's the most honest objection I get and it's usually right, which is exactly why I don't want a firm-wide launch. Pick the eight, and include the two who complained loudest about the planning tool. If it doesn't change their Sundays, we pull it out at quarter-end and you owe nothing further. If it does, those eight are a better internal story than a mandate from ops.

18. Buyer

    What does it actually cost my team? Because that's the real constraint. Nobody has a spare week.

19. Rep

    Ninety minutes with whoever owns the template library — I'd guess your Head of Client Reporting — to load the approved blocks. Then two hours a week from that one person for three weeks. My CSM runs the advisor sessions, not you. If it needs more than that, I've mis-scoped it and I'll say so. And I'd start it the week after your cutover, not before.

20. Buyer

    Fine. Send the delta memo to vendor risk this week and put a summary in front of my CCO. If she doesn't object and third-party risk says amendment rather than full DDQ, we'll do the pod after cutover. But I want it co-termed to March. I'm not managing two contracts.

21. Rep

    Co-termed to March, so it's an amendment on paper you're already signing. I'll write up today: the nine-day close in your words, the twenty-two percent kickback rate, the math at your one-third capture rate, the price both ways, the ninety-minute ask, and the success criterion — under ten percent on that pod, no slip in days-to-delivery. Decision date the Friday after your Q-end delivery. Anything you want in that email that your CCO will look for first?

22. Buyer

    Put the reviewer log and version-stamp language at the top. That's the only paragraph she'll read.

What should I have in front of me before running an upsell script for financial services customers?

Six things, all from your own systems: seat count versus weekly actives split between ops and advisor users; which modules they've never touched; one outcome number sourced from their instance (business days from period close to client delivery, or compliance exceptions per period, before and after); contract value, renewal date and whether the original signer is still in the role; any open escalation or missed quarter-end delivery in the last 90 days; and your champion's current status. If you can't say one thing about the account they'd be mildly surprised you knew, you're not ready to dial. "So how's everyone finding the platform?" is the single fastest way to get downgraded from partner to vendor with a Director of Wealth Management Operations.

How do I raise an expansion without triggering a whole new vendor due diligence cycle?

Get ahead of it and name it before they do. Prepare a delta memo for the VP, Third-Party / Vendor Risk Management that states plainly what changes and what doesn't — tenancy, data flow, sub-processor list, encryption keys, hosting region — attached to your current SOC 2 Type II, pen-test summary and data-flow diagram. Then ask them to scope it: full DDQ or amendment to the existing approval? The point is to get that verdict in week one rather than week ten. If it's a full re-review, you've learned that early enough to time the start date after their custodian conversion instead of forecasting a deal that dies in the queue.

Which metrics should appear inside the script itself?

Use the two that get reported upward. Quarter-end reporting cycle time — business days from period close to client delivery — is the number the COO, Wealth Management and the Head of Client Reporting & Performance defend. Compliance exceptions and audit findings per period is the number the Chief Compliance Officer takes to the risk committee. Both should appear as their figures, not your benchmark. Secondary numbers worth naming if the conversation opens up: AUM per advisor, households per advisor, and advisor attrition — which is what the Head of Advisory Platform is measured on and the reason "I spend my Sundays doing admin" is a business problem rather than a morale one.

The customer says they barely use what they've already bought. Do I keep going?

Only if you can show the unused capacity is doing the work somewhere else. If sixty-six advisor seats are dark but those advisors are producing client-facing decks in PowerPoint and pushing them into 2210 review as one-off attachments, that's unrouted work and it's a legitimate case. If the seats are dark because an office never onboarded, concede the point immediately and go fix adoption — free — before you sell anything. There is no third answer. Arguing with it turns a healthy account into a defensive one, and it's the fastest way to have your renewal reopened.

How big should the first ask be on an upsell call in wealth management?

One pod, one quarter-end cycle, success criteria written by them on the call, and a pre-agreed decision date. Eight advisors — including the two who complained loudest about the last platform rollout — is a better pilot than a region. Say both prices out loud: the pilot cost and the firm-wide cost, and then explicitly say you don't want them signing the firm-wide number today. Then co-term to the existing renewal. Co-terming turns the expansion into an amendment on paper they're already signing, which removes a second procurement cycle — and for a firm mid-conversion, that's often worth more than the discount you were about to offer instead.

When should I park the upsell entirely?

Park it if there's an open P1 or a missed quarter-end delivery, if they're inside the cutover window of a custodian conversion, if the champion changed roles in the last sixty days, if renewal is inside sixty days with unresolved value questions, if weekly actives are flat or declining and you can't explain why, or if they're responding to an exam, a deficiency letter or a regulatory sweep. Say it out loud on the call: "You've got a bigger fire than this — let's do the account review and I'll bring the rest back after cutover." Booking an incremental thirty thousand at the cost of a renewable account is a bad trade in an industry where the buying committee talks to its peers at every conference.

• All Financial Services playbooksEvery call type for Financial Services, in one place.

Other Financial Services calls

• Cold CallFinancial Services Cold Call Script: Getting a Wealth Management COO to Give You 25 Minutes
• Demo CallThe Financial Services Product Demo Script for Wealth Management Buyers
• Discovery CallDiscovery Call Questions for Financial Services: A 25-Minute Playbook for Wealth Management Buyers
• Manager Coaching CallSales Coaching Roleplay for Financial Services Teams: The Two-Quarter-Miss 1:1
• Pricing Negotiation CallFinancial Services Pricing Negotiation Script: Holding Your Number After the Wealth Management Technical Win
• Warm CallThe Warm Call Script for Financial Services: Turning a Peer Referral Into a Booked Second Meeting

The same call in a neighbouring market

• Upsell Call for SaaSThe Upsell Script for SaaS Customers That Survives a Seat Utilization Report
• Upsell Call for InsuranceUpsell Script for Insurance Customers: From Claims Account Review to a Recovery Module Expansion
• Upsell Call for HealthcareUpsell Script for Healthcare Customers: Expanding an Ambient Documentation Deal Without Burning the Account

Related reading

• "It Has to Go Through Security and Legal Review" — Keeping a Deal Warm Through Six Weeks of PaperworkThe technical win is done and the deal vanishes into InfoSec questionnaires and outside counsel redlines. Here is how to run that dead zone instead of waiting it out.
• "Legal Will Never Sign Your Paper" — Working the Redlines Stall Before It Eats Your QuarterHow to tell a genuine risk concern from a champion hiding behind counsel, and the concrete moves that unstick a contract before your quarter closes.