The Warm Call Script for Financial Services: Turning a Peer Referral Into a Booked Second Meeting

1. 1

   Pre-call: write the provenance line out loud

   One sentence, small and checkable, before you dial: "[Referrer] mentioned you because [specific reason]." Good: "Marta Vance pulled down our quarter-end cycle-time benchmark last month and said you'd taken the ops seat at [Firm] right before the custodian conversion started." Dead: "Marta thought you'd be interested in what we do." Also pre-decide three things. One: exactly what Marta said, word for word — if she said "you should talk to Dani," you say that, never "Marta said you'd be really interested." These people sit on the same custodian advisory councils; they compare notes. Two: your relevance hypothesis about *their* firm — dually-registered vs. pure RIA, one custodian vs. two, 90 households per advisor vs. 140, new CCO, an ADV amendment, a job ad for a performance reporting analyst. Three: assume the intro email was never read and have the 15-second re-brief ready in ops language, not product language.

2. 2

   The open — name, referrer, provenance, permission (25 seconds)

   "Ray — Dani Okafor, from Meridian. Marta Vance suggested I call. She picked up our thing on quarter-end reporting cycle time and said you'd inherited the ops seat at [Firm] just as the custodian conversion kicked off. She may have been overselling my usefulness. Have you got four minutes for me to find out whether that's true, or should I come back after quarter-end?" If they say "yes, Marta said you'd call" — that is the entire warmth budget being handed over. Spend five words on it, not three minutes: "Good, she said she'd flag it. Then I'll be quick." Do not ask how they know Marta. It costs you the call.

3. 3

   If they can't place the referrer

   "No reason you would — it was a two-line intro on a Friday. Short version: we work with wealth ops teams on the gap between period close and client delivery — the part where performance comes out of portfolio accounting and then someone hand-marks held-away assets and alts in a spreadsheet before it goes into the client deck. That's the whole thing. Worth four minutes, or not really?" No company history. No funding round. No "we're an AI-powered platform." The re-brief is described in the work they do, so they can decide in one breath whether it's their world.

4. 4

   The relevance bridge — the move the call lives or dies on

   "What Marta was dealing with is a pure RIA, 40 advisors, one custodian, and three ops people rebuilding the same performance pack by hand every quarter — she was at fifteen business days from period close to client delivery and her board wanted single digits. That's her shop, not yours. You're dually registered, you're across two custodians mid-conversion, and you've got a compliance function she doesn't. So I honestly don't know if this lands. Where does the quarter-end client pack actually get assembled at your place — who physically touches it?" Naming the reason you might be irrelevant is the fastest credibility move available on a warm call in this industry, because every one of these buyers has been on the other end of a vendor who assumed an RIA workflow drops cleanly into a broker-dealer.

5. 5

   Discovery — three questions, maximum four

   1. Mechanical current state: "Walk me through it — performance comes out of portfolio accounting, then what? Who's stitching the held-away and the alternatives marks?" 2. Cost in their numbers: "How many business days from period close to when the last household has their statement? And what happens when a return number is wrong — is that a corrected statement, or does it hit your exception log?" 3. Priority test: "Is that a this-quarter problem or a live-with-it problem?" Optional fourth: "Besides you, who'd care about this — is that your Head of Client Reporting, or does it go straight to the CCO?" That's it. Four questions. Not eleven. An interrogation on a referred call reads as an abuse of Marta's name, and you'll get shut down with "can you just send me something." Listen for the correction. When they say "it's less the cycle time, it's that the advisors are doing the chasing" — write down their exact phrasing. That sentence is the subject line of your follow-up and the agenda of the second meeting.

6. 6

   When they lead with compliance before you've said anything

   They will. Half the time the first full sentence out of a COO or an ops director is about vendor risk. Don't defend — agree and narrow. "That's the right instinct and I'd rather deal with it now than at week eight. I'm not asking you to shortcut anything. What I'd want is to send your third-party risk team a complete package — SOC 2 Type II, the completed DDQ, pen-test summary, data-flow diagram, sub-processor list — before you commit to a single thing. Most firms tell me the six months is really four months of waiting on the vendor to answer questions. If your TPRM team has everything in week one, you know by week three whether this is even reviewable. And I'd rather be told no in week three." Then return to the operational question. Do not let the call become a compliance Q&A on the first contact.

7. 7

   Reading the cool-off and naming it

   Signals: the answers shorten to "yeah, makes sense." They ask what it costs before you've established a problem. They start narrating logistics — "can you send something over." They mention the referrer as an exit: "well, if Marta rates you." Stop and name it: "I'm getting the sense this isn't the live thing for you right now, which is completely fine — Marta was guessing. Is it not the problem, or not the moment?" A clean "not the problem" is a good outcome. It protects the referral relationship and stops you burning a quarter chasing a firm that already solved reporting on their TAMP.

8. 8

   The close — a date, a length, their words, and a name

   "Then here's what I'd suggest. You said the issue isn't the cycle time itself, it's that two of your senior advisors are personally chasing ACAT paperwork and rebuilding decks the week before reviews — and you're carrying that against an AUM-per-advisor number that's supposed to go up without headcount. Give me thirty minutes and I'll walk you through what the same quarter looked like at a hybrid your size once the pack came off a pre-approved template. I'd want two people on it: whoever owns client reporting and performance, and I'd rather have your CCO in the room from the start than have her review it cold in month three. Thursday morning, or Monday afternoon?"

9. 9

   If they genuinely can't book — take the smaller real commitment

   "Fine. Then here's the smaller version. Tomorrow I'll send two things to you and your CCO: the DDQ package so third-party risk can start the clock, and one page showing a sample output with the version stamp and reviewer log on it. Nothing else, no deck. I'll call you Thursday at 8:15 — before your conversion standup — and you tell me in three minutes whether it's worth thirty. If it isn't, I'll close the file and tell Marta it wasn't a fit." The date goes in your diary, not as a request in theirs. Then actually call on Thursday at 8:15.

10. 10

    Same-day loop back to the referrer

    Two lines, the same afternoon. Skipping this is why most reps get one referral from a source and never a second. "Marta — spoke to Ray, thanks for that. Their issue is a bit different to yours: less the reporting build, more that advisors are doing the ACAT chasing themselves. Meeting him and their CCO Thursday. Appreciate the intro — is there anyone else on the ops council I should be talking to?"

11. 11

    If it goes to voicemail

    "Ray, Dani Okafor at Meridian — Marta Vance suggested I call you. She said you'd taken the ops seat right before the custodian conversion. I'm not calling to pitch you mid-conversion; I've got one question about how your quarter-end pack gets built and I'll be off in four minutes. I'll try you Thursday morning. Number's [number]." Name the referrer in the first six words or it's a cold voicemail.

1. Rep

   Ray — Dani Okafor, from Meridian. Marta Vance suggested I call. She pulled down our quarter-end cycle-time piece and said you'd taken the ops seat at [Firm] right as the custodian conversion started. She may have been overselling my usefulness. Four minutes to find out whether that's true, or should I come back after quarter-end?

2. Buyer

   Marta, yeah. She emailed. I'll be honest, I skimmed it in the car park. We're eleven weeks into the conversion and I've got two hundred accounts that haven't repapered, so — four minutes, and I'll tell you now, I don't buy anything that touches client data. That's not my call and it never will be.

3. Rep

   Understood, and I'd be worried if you did. Then let me be useful about the four minutes. What Marta's dealing with is a pure RIA, 40 advisors, one custodian, three ops people rebuilding the performance pack by hand — she was at fifteen business days from period close to client delivery. That's her shop, not yours. You're dually registered, two custodians, mid-conversion. So I don't know if this lands at all. Where does your quarter-end pack actually get assembled — who touches it?

4. Buyer

   Portfolio accounting spits out time-weighted returns, that's clean enough. Then it falls apart. Held-away assets come off a spreadsheet the advisors maintain themselves, the alternatives marks arrive whenever the sponsor feels like sending them, and my reporting team re-keys the whole thing into deck templates. Last quarter we were nineteen business days. During a conversion, that's — look, it's not sustainable, but neither is anything else right now.

5. Rep

   Nineteen days. And when a return number comes out wrong in that stitching — what actually happens? Is that a corrected statement, or does it land somewhere your CCO has to report?

6. Buyer

   Both, and that's the part that keeps me up. We sent a corrected statement to about sixty households in Q2. Wrong money-weighted figure on a household with three entities. That's a books-and-records issue, it's in the exception log, and Priya — my CCO — had to explain it. So yes, I feel this. That doesn't mean I'm buying software in the middle of a conversion.

7. Rep

   Fair. So is this a this-quarter problem or a live-with-it problem?

8. Buyer

   Live-with-it until next fiscal. Budget's fully committed to the conversion. And frankly even if I had money, Priya won't look at a new vendor right now. Anything that generates client-facing output goes through 2210 review, and after the off-channel sweeps she's not entertaining anything that produces communications without a WORM archive and a pre-review workflow. You'd be dead in vendor risk before you got to her anyway. Six months, minimum.

9. Rep

   Then let's treat those as two separate clocks, because they are. The money is next fiscal, fine. The vendor review is the long pole, and it doesn't need budget to start. If your third-party risk team gets a complete package in week one — SOC 2 Type II, completed DDQ, pen-test summary, data-flow diagram, sub-processor list — you find out by week three whether this is even reviewable. Do that during the conversion and you've got an approved vendor sitting on the shelf when budget opens, instead of starting a six-month clock in Q1.

10. Buyer

    You're not hearing me on the communications piece. It's not just vendor risk. If your thing produces a client-facing performance page, it's advertising under the Marketing Rule and it goes in Priya's queue with everything else. So you've moved my bottleneck from my reporting team to my compliance team. That's not a win, that's a transfer.

11. Rep

    Agreed, and I'm not going to claim we remove the review. What changes is what shows up in her queue. Output comes off templates your compliance team approves once — locked language blocks, mandatory disclosures, no free-text field where anyone can invent a performance claim. Every item carries a version stamp and a reviewer log. What firms tell me is the win isn't fewer reviews, it's that a review goes from reading every page to confirming it came off approved template v4 — and the exception rate drops. Exceptions per period is the number Priya reports on, not the page count.

12. Buyer

    Hm. And you'd expect me to run a trial on live client data to prove that?

13. Rep

    No — a trial with live client data would be the wrong thing for you to say yes to and I'd tell Priya the same. It's a sandbox, synthetic or anonymised data, no PII, outside your production environment, so nothing in scope for supervision or books-and-records moves. Your reporting lead and one compliance reviewer look at the output and the audit trail. That's an evaluation, not a deployment. And on hosting — if the answer is client data never leaves your tenancy, say so now, because there's a single-tenant configuration in your own cloud region with your keys, and if that's still dead on arrival I'd rather find out today.

14. Buyer

    Priya would want that in writing before she'd give you twenty minutes. And she'd want the indemnity language, because if you get breached it's our name in the enforcement action, not yours.

15. Rep

    That's the correct way to think about it, and it's exactly what I'd send her — cyber cover, indemnity that survives termination, and 24-hour breach notification to your named incident contact, not 72. So here's what I'd suggest, and it's built on what you told me, not what Marta told me: nineteen business days, sixty corrected statements, and an exception you had to explain. Thirty minutes with you, Priya, and whoever owns client reporting and performance — I'll walk through what one quarter-end looked like at a hybrid your size once the pack came off pre-approved templates. Thursday morning or Monday afternoon?

16. Buyer

    Thursday, eight o'clock, before the conversion standup. Thirty minutes, hard stop. And if the diligence package isn't in Priya's inbox by tomorrow morning she won't show up, so don't waste my slot.

17. Rep

    Tomorrow morning, to Priya and your third-party risk lead — give me the name and I'll copy them. Thursday at eight, thirty minutes, agenda is the nineteen days and the exception log, nothing else. And I'll let Marta know I got hold of you.

How is a warm call script for Financial Services different from a cold script?

The referral buys you three things: the pickup, roughly ninety seconds where they won't hang up, and permission to ask a direct question without earning it. It does not buy interest, budget, or a problem. So the cold-call habits — a value proposition, a company overview, a two-sentence credibility build — actively hurt you here. In wealth, the specific risk is that your ninety seconds gets spent on 'so how do you know Marta' and then on a platform overview, and by the time you ask about quarter-end cycle time they've mentally filed you with the last four vendors who couldn't answer an InfoSec question.

What do I say if the prospect doesn't remember the referrer or the intro email?

Don't argue them into remembering — it happens constantly, because a COO of Wealth Management reads intro emails on a phone between meetings. Say: 'No reason you would — it was a two-line intro on a Friday.' Then give a 15-second re-brief in operations language, not product language: the gap between period close and client delivery, the held-away spreadsheet, the deck someone reformats by hand. If they recognise the work, they'll give you four minutes. If they don't, they weren't a fit anyway.

Should I raise SOC 2, DDQ and vendor risk on the first warm call, or wait?

Raise it only if they raise it, but be ready to answer in one breath when they do — and in Financial Services they will, often in their first full sentence. The move is to agree, narrow, and offer the complete package proactively: SOC 2 Type II, completed DDQ, pen-test summary, data-flow diagram, sub-processor list. Then get back to the operational question. Turning a four-minute warm call into a compliance Q&A means you never learn what their quarter-end actually looks like, and you'll book a second meeting with no agenda worth attending.

Which metrics should I put in the call itself?

Use the numbers these buyers are personally measured on, and use them as questions rather than claims. Quarter-end reporting cycle time in business days from period close to client delivery is the sharpest one for a Director of Wealth Management Operations or a Head of Client Reporting & Performance. For a COO of Wealth Management, AUM per advisor and organic growth as a percentage of beginning AUM. For a Chief Compliance Officer, compliance exceptions and reportable events per period. For a Head of Advisory Platform, advisor attrition and time-to-productivity. Ask what their number is; never assert what the industry average is.

Who should I ask to be in the second meeting?

Name people, not functions, and name them on the call. If your entry point is ops, ask for the Chief Compliance Officer and whoever owns client reporting and performance — getting the CCO in the room at meeting two rather than reviewing you cold in month three is the single biggest thing that shortens a Financial Services deal cycle. If your entry point is the Chief Technology Officer or Head of Advisor Technology, ask for the VP of Third-Party / Vendor Risk Management. Warm calls have an unusually high hit rate on 'who else would care about this,' because you're already a known quantity by association.

What counts as a successful warm call here if they won't book?

A clean 'not the problem' is a genuine win — it protects the referral relationship and stops you burning a quarter on a firm whose TAMP already handles reporting. Short of that, take a smaller real commitment with a date on your side: you send the diligence package and one page of sample output to them and their CCO, and you call at a specific time on a specific day for a three-minute yes or no. What is not a success is 'send me some info,' however pleasantly it was said. And either way, close the loop with the referrer the same day — sources who never hear back stop referring.

How do I practise this without burning a real referral?

Run the call out loud before you dial, with someone playing a mid-conversion ops director who leads with 17a-4 and the off-channel sweeps. The specific things worth rehearsing are the 25-second open without a single generic sentence, the relevance bridge where you name the reason you might be irrelevant, and the close that repeats their words back with a date and two names attached. DrillCall exists for exactly this — voice roleplay against a buyer who pushes on Marketing Rule review and single-tenant hosting rather than nodding along.

• 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
• Upsell CallThe Upsell Script for Financial Services Customers: Expanding an Account Without Restarting Vendor Diligence

The same call in a neighbouring market

• Warm Call for SaaSWarm Call Script for SaaS: Cashing a Referral With a CRO in Four Minutes
• Warm Call for InsuranceWarm Call Script for Insurance: Cashing a Peer Referral with a Claims Leader in 90 Seconds
• Warm Call for HealthcareWarm Call Script for Healthcare: Cashing a Peer Referral with a CMIO in Ninety Seconds

Related reading

• Selling Into Wealth Management: What a COO at a $4B Firm Is Actually ProtectingWealth management operations leaders buy defensively. Here is what a COO is protecting, why efficiency pitches bounce, and how RIA, broker-dealer and bank buyers differ.
• Your Champion Just Left. Here's the Call You Make on Day Two.Every rep eventually sees their champion at a new logo. Here is the tactical 48-hour play: the intro ask, the interim owner call, and the honest forecast decision.