Financial Services · Cold Call
Financial Services Cold Call Script: Getting a Wealth Management COO to Give You 25 Minutes
It is business day 14 after quarter close. Somebody on the operations team is stitching a stale custodial feed to a spreadsheet of held-away assets and two alternatives marks that came in as a PDF, and somebody else is hand-reformatting a client-facing performance deck that still has last quarter's disclosure block on page nine. The Director of Wealth Management Operations is not thinking about your category. She is thinking about whether the delivery date slips past business day 20 again, and whether the return number on page three is a books-and-records problem.
That is who answers your cold call. She has been pitched by a dozen reporting vendors, three TAMPs, and a data-aggregation platform this quarter alone, and every one of them opened with "we help wealth management firms streamline...". Her reflex is not rudeness — it's triage. She knows that even if she loves you, you are six months of DDQ, SOC 2 Type II review, InfoSec pen-test evidence, legal redlines on the data-processing addendum, and then advertising review under FINRA 2210 or the SEC Marketing Rule before a single client sees output. So the bar for the first thirty seconds is high: say something so specific about her quarter-end that she stops sorting you into the pile.
This is a Financial Services cold call script built for that call. It assumes you are dialling a Chief Operating Officer of Wealth Management, a Director of Wealth Management Operations, a Head of Client Reporting & Performance, or a Head of Advisory Platform — people whose numbers are cycle time from period close to client delivery, AUM per advisor, household attrition, and compliance exceptions per period. The goal is not to sell. It is not even to qualify. It is a 25-minute calendar hold, confirmed while you are still on the line.
The cold call script
Say it in your own words. The structure is the part that matters.
- 1
The 90-second prep (do not dial without this)
Answer each of these out loud in one sentence before you touch the phone: **Who is this?** Exact title and registration model. "Priya Raman, Director of Wealth Management Operations, dually-registered hybrid, roughly $4.2B, 38 advisors, Pershing and Schwab." A pure RIA and a dually-registered hybrid have different supervision burdens and you will be caught inside sixty seconds if you get it wrong. **Where did the numbers come from?** Form ADV Part 1: regulatory AUM, number of advisory accounts, number of IARs. Divide. Now you can say "about 110 households per advisor" instead of "a lot of households." Part 2A tells you fee schedule and whether they hold themselves out as fiduciary-only. **What's the trigger?** New CCO in seat under a year. A custodian conversion announced in the trade press. Job postings for "Performance Analyst" or "Client Reporting Associate" — that's a firm buying humans to shorten a cycle. A recent acquisition of a $500M book that has to be onboarded onto the reporting platform. If there's no trigger, the segment is the trigger. **The one problem I lead with.** One. Written on a sticky note. Not three. **The ask.** "Twenty-five minutes, Thursday 8:15 or Friday 7:45." Ops people are at their desks before the market opens and unreachable after 9:30. **Timing note:** do not dial a client reporting lead in the first two weeks after quarter close. Dial in week four, when the cycle just finished and the wound is fresh, or in the last three weeks of the quarter when they can see the next one coming.
- 2
The opener
**Name → honest frame → permission → pause.** > "Priya — Sam Cutler, Northrail. You don't know me, this is a cold call. Give me thirty seconds and you can tell me to get lost?" Downward inflection on "get lost." Then stop talking. Two full seconds. Do not fill it. **Trigger-led variant:** > "Priya, Sam Cutler at Northrail. I saw you've had a client reporting associate role open since January — that's actually why I rang. Bad time?" **Pattern interrupt for the flat, clipped answerer:** > "Priya — Sam, Northrail. You don't know me. Bad time?" Never open with "How are you today," "Did I catch you at a bad time," or "I'll be brief." And never open with what your company is. Nobody in wealth ops has ever cared that you closed a Series B.
- 3
The reason — for a COO or Director of Wealth Management Operations
> "We work with about fifteen dually-registered hybrids in the two-to-eight billion range. The thing that keeps coming up with ops directors is quarter-end — performance comes out of portfolio accounting clean enough, then somebody's stitching held-away assets and alternatives marks in Excel, then somebody else is hand-reformatting the client deck. Firms that started the quarter saying day ten are delivering on business day eighteen or nineteen, and the number that actually hurts isn't the cycle time, it's the one wrong return that turns into a restatement. Is that anywhere near your world, or have you got that cycle clean?" Note the structure: **who else → what they deal with → the operational consequence → an exit-friendly check-in question.** No product name. None.
- 4
The reason — for a Head of Advisory Platform or Practice Management
> "The pattern I keep hearing from platform leads is that a senior advisor carrying 110 households is spending a day and a half a week on ACAT chasing, CRM notes, and building meeting prep decks. So AUM per advisor is the number the board is pushing on, but the advisor's constraint isn't capacity for more assets — it's that Sunday night is admin night, and that's the sentence that shows up in exit interviews when a team breaks away. Does that track with what your top quintile is telling you, or is that not the complaint you're getting?"
- 5
The reason — for a Head of Client Reporting & Performance
> "Most performance leads I speak to have the same three-week problem: reconciliation breaks on maybe two percent of accounts, the custodial feed for one custodian lands stale, and then the alternatives marks come in on a PDF eleven days late — so the whole cycle is hostage to the slowest input. And every time you shorten it by pulling people in on a weekend, you're trading cycle time for review quality. Which one are you protecting right now?"
- 6
Two questions, maximum
You are not running discovery. You are getting just enough to make the meeting relevant. Narrow and factual only. - "Where are you landing today — business days from period close to client delivery?" - "Is the stitching the bottleneck, or is it the 2210 review queue at the back end?" - "Is that on the roadmap this year, or is it just living with it?" - "How many advisors are on the old process?" Do **not** ask: what are your priorities this year, walk me through your process, what would fixing it be worth. You haven't earned those and you'll burn the reason to hold the next meeting. Listen for the admission — "yeah, day eighteen is about right," "honestly it's a mess in Q4," "we've been meaning to look at that." The moment you hear it, stop asking and close.
- 7
The ask
> "Here's what I'd suggest. Twenty-five minutes, and it's not a demo. I'll bring the SOC 2 Type II, the completed standard DDQ and the data-flow diagram so your third-party risk team isn't the reason the meeting was pointless, and I'll walk you through what business day eight looks like at a firm your size. If it's not relevant you tell me on the call and I'll leave you alone. Thursday 8:15, or Friday 7:45 — which is less bad?" Why this works on this buyer specifically: naming the diligence artifacts in the ask signals you know their actual gating factor is TPRM, not budget. Most vendors find that out in month two. The second they say a day: **"Sending the invite now — can you tell me it landed?"** A meeting confirmed on the phone shows up. One calendared afterwards does not.
- 8
Gatekeeper / EA screen
> "It's about their quarter-end reporting cycle — Sam Cutler at Northrail, she won't know me. If she's not the right person for that, whoever owns client reporting is fine too." Short, calm, specific. Don't be cute, don't imply a prior relationship, don't say "it's regarding a partnership." If the EA asks you to email, ask for the calendar instead: "Happy to. Is there a fifteen-minute slot before the open on Thursday I could hold, and I'll send the material to fill it?"
- 9
Voicemail — under 20 seconds, no ask
> "Priya, Sam Cutler at Northrail — you don't know me. Calling about the quarter-end reporting cycle, specifically the gap between period close and client delivery at hybrid firms your size. It's a thing we see a lot. I'll try you again Thursday morning. 415-555-0148." The voicemail's job is name recognition for attempt two and the email that follows it. Do not ask for a callback. Do not describe your product.
- 10
The soft no and the recycle
If they won't book, you are now hunting one dated reason to call back and one named priority. > "No problem. Last thing and I'll let you go — is this a timing thing or a not-a-priority thing? … Got it, so the conversion wraps in October. When does tech budget get set for next fiscal? … Perfect. I'll come back to you the second week of September. I'll send one email today so you've got my name in the system." A call that ends with "conversion completes October, budget set November, cycle time is the metric she owns" is a good call. A call that ends with "send me an email" and nothing else is a polite hang-up you agreed to.
- 11
The follow-up email (drafted before you dial, sent within five minutes)
**Subject:** Our call just now — business day 18 > Priya, > > Thanks for the four minutes. Three things, as promised: > > 1. SOC 2 Type II report and completed standard DDQ — attached. > 2. Data-flow diagram and sub-processor list — attached. Nothing in the sandbox uses live client data; it's synthetic, outside your production environment, so nothing in scope for 17a-4 moves. > 3. Thursday 8:15, 25 minutes, invite already accepted. > > You said the bottleneck is the review queue, not the stitching. I'll build the walkthrough around that. > > Sam Log the exact words she used. "Business day eighteen" and "the review queue" go into the discovery call verbatim.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Priya — Sam Cutler, Northrail. You don't know me, this is a cold call. Thirty seconds and you can tell me to get lost?
Buyer
Who gave you my number? We're mid-conversion to Pershing and I've got a call in four minutes, so.
Rep
Your direct's on your ADV cover page. I dial ops leaders at dually-registered hybrids between two and eight billion — that's the whole story. Four minutes is more than I need. Reason I rang: we work with about fifteen firms in your band, and with ops directors the thing that keeps coming up is quarter-end. Performance comes out of portfolio accounting fine, then someone's stitching held-away assets and alts marks in a spreadsheet, then someone else is hand-reformatting the client deck. Firms that plan for business day ten deliver on eighteen. Is that near your world, or have you got that cycle clean?
Buyer
Every vendor who calls me in January says they'll fix quarter-end. Then it turns out they mean a dashboard.
Rep
Fair. Let me be specific instead. The firms that call me back usually have the same three inputs holding the whole cycle hostage — one custodial feed that lands stale, reconciliation breaks on one or two percent of accounts, and alternatives marks arriving on a PDF on day eleven. Which of those three is yours?
Buyer
…The marks, and the feed. But honestly that's not where the time goes. We're at business day eighteen, nineteen, and most of the back half is review. Everything client-facing goes through 2210, and we just closed out a deficiency letter on marketing rule material. So I'm not putting anything new in front of a client this year.
Rep
Then I'd be careful telling you we shorten the review, because we don't. What changes is what shows up in the queue. Output comes off templates your compliance team pre-approves once — locked language blocks, mandatory disclosures, no free-text field where anyone can invent a performance claim — and every item carries a version stamp and reviewer log. The firms I work with say the win isn't fewer reviews, it's that a review goes from reading every page to confirming it came off approved template v4. Their exception rate per period drops. That's the number your CCO reports, not mine.
Buyer
Even if all of that's true, anything that touches client data is a six-month vendor review here. Our VP of third-party risk would eat you alive, and she'd be right to.
Rep
I'd like to meet her, genuinely. I'm not asking you to shortcut TPRM. I'm asking you to start it on something that's already been through it — SOC 2 Type II, completed standard DDQ, pen-test summary, data-flow diagram, sub-processor list, all of it goes to her in week one before you commit to anything. Most of that six months is four months of waiting on the vendor. If she has a complete package on day one, you find out by week three whether this is even reviewable, and I'd rather be told no in week three than string you along until Q3.
Buyer
And then my advisors won't use it. We rolled out planning software two years ago. Half of them still build the review deck in PowerPoint the night before.
Rep
That's the most honest objection I get and it's usually right. Which is why I'd never launch you firm-wide. Eight advisors, ideally including the two who complained loudest about the planning rollout, one quarter-end cycle. If their hours don't move, you've spent a quarter and learned something. If they do move, those eight are a much better internal story than a mandate from ops.
Buyer
Look — send me something and I'll look at it after the conversion.
Rep
I will, but if I send the standard deck you'll bin it and we'll both have wasted the effort. Give me twenty-five minutes instead, before the open. Not a demo. I bring the SOC 2 and the DDQ so your risk team isn't the reason the meeting was pointless, and I show you what business day eight looks like at a firm running your household count per advisor. If it's not relevant, say so on the call and I'll go away. Thursday 8:15, or Friday 7:45?
Buyer
Thursday 8:15. But bring the actual reports, not slides about the reports. And if you can't tell me what happens to data at rest and whether anything sits outside our tenancy, don't bother coming.
Rep
Understood — single-tenant in your cloud region with your own keys is one option, and there's a configuration where nothing leaves your tenancy at all. I'll bring both and let your InfoSec architect tell me which one's dead on arrival. Sending the invite now, twenty-five minutes. Can you tell me it landed?
Buyer
It's here. And you were right, that was under four minutes.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “"Anything that touches client data goes through a six-month compliance and vendor-risk review. I can't shortcut that."” | "I'm not asking you to shortcut it — I'm asking you to start it on something that's already been through it. SOC 2 Type II, completed standard DDQ, pen-test summary, data-flow diagram and sub-processor list go over today, before you commit to anything. Firms your size tell me the six months is really four months of waiting on the vendor to answer questions. If your TPRM team gets a complete package in week one, you know by week three whether this is even reviewable — and I'd rather be told no in week three than string you along." |
| “"We're regulated. I can't just try a new vendor because it looks good."” | "Agreed, and a free trial on live client data would be the wrong thing for you to say yes to. What we do instead is a sandbox on synthetic or anonymised data, no PII, sitting outside your production environment — so nothing in scope for supervision or 17a-4 moves. Your ops lead and one compliance reviewer see exactly what output looks like and what the audit trail looks like. That's an evaluation, not a deployment, and it's the artifact your CCO needs to make a real decision instead of a hypothetical one." |
| “"Everything client-facing goes through advertising review anyway. You're moving the bottleneck, not removing it."” | "Right, and I won't claim we remove it. We change what lands in the queue. Output comes off templates your compliance team pre-approves once — locked language, mandatory disclosures, no free-text field that can invent a performance claim — with a version stamp and reviewer log on every item. The review goes from reading every page to confirming it came off approved template v4. The number that moves is compliance exceptions per period, which is what gets reported, not review volume." |
| “"Our client data can't leave our environment. Full stop."” | "Then let's settle deployment before we talk about anything else, because if we can't satisfy that, nothing else matters. Single-tenant in your cloud region with your own encryption keys is one option; there's a configuration where the data never leaves your tenancy at all. What I want is thirty minutes with whoever owns your InfoSec architecture — not to pitch, but to have them tell me which of those is acceptable and which is dead on arrival. If neither works, I'll say so and stop calling." |
| “"If you get breached, my firm's name is in the enforcement action, not yours."” | "That's the correct way to think about it, and it's why the contract carries cyber liability cover and an indemnity that survives termination, plus breach notification inside 24 hours to your named incident contact — not 72. We'll sit for your annual vendor attestation and give internal audit read access to control evidence. I'd rather your legal team push on those terms in month one than discover them at renewal." |
| “"Our advisors won't adopt it. We rolled out a new platform two years ago and half of them are still in spreadsheets."” | "Most honest objection I get, and usually accurate. So don't launch firm-wide. Eight advisors, including two who complained loudest last time, one quarter-end cycle. If it doesn't change their hours, you've spent a quarter and learned something. If it does, those eight become the reason the other ninety try it — and that's a far better internal story than a mandate out of ops." |
| “"Budget's committed. We're mid-custodian conversion, there's no tech spend until next fiscal."” | "Then it's a next-fiscal conversation and I'm fine with that — but the vendor review is the long pole, not the money. Run diligence during the conversion and you have an approved vendor on the shelf when budget opens, instead of starting a six-month clock in Q1. Worth asking too: how much of the conversion pain right now is your team hand-building reporting through the cutover? That's usually where the first case gets made." |
| “"Just send me an email."” | "Happy to, but the generic deck will get binned and we'll both have wasted it. Give me two things — where you're landing on business days from period close to delivery, and whether the bottleneck is the data stitching or the 2210 queue — and I'll send you something that's actually about you. Or give me twenty-five minutes Thursday before the open and I'll bring the diligence pack with it." |
Questions reps ask about this call
- What's the best opener for a cold call into a wealth management firm?
Name, company, and an explicit admission that it's a cold call, then ask permission and stop talking. "Priya — Sam Cutler, Northrail. You don't know me, this is a cold call. Thirty seconds and you can tell me to get lost?" Ops and compliance leaders at RIAs and broker-dealers are pitched constantly; naming the call for what it is collapses the suspicion loop faster than any clever hook. Skip "how are you today" and never lead with your company's story — a Director of Wealth Management Operations does not care who you are until you've proven you understand what business day eighteen feels like.
- Should I cold call the Chief Compliance Officer directly?
Usually not first. A CCO's default answer to an unknown vendor is no, and that no is expensive to reverse. Lead with the person who owns the operational metric — COO of Wealth Management, Director of Wealth Management Operations, or Head of Client Reporting & Performance — and treat the CCO and VP of Third-Party / Vendor Risk Management as people you volunteer to meet early rather than route around. Saying "I'd like your compliance and vendor risk people in the room in week one, with the SOC 2 and DDQ already sent" is one of the strongest trust signals available on a first call, because most vendors do the opposite.
- How do I answer "everything goes through a six-month vendor review" without sounding like I'm dismissing it?
Agree with the constraint and attack the timeline's real cause. Most of that six months is the vendor being slow to answer, not the reviewer being slow to read. Offer the complete package — SOC 2 Type II, completed standard DDQ, pen-test summary, data-flow diagram, sub-processor list — before any commitment, and frame the goal as a fast no: "If your third-party risk 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." That reframes you as someone who respects the process rather than someone trying to slip past it.
- When is the best time to cold call wealth management operations leaders?
Before the market opens. 7:45 to 8:45 in their local time is the window where ops and reporting leaders are at their desks and not yet in back-to-back meetings. Avoid the first two weeks after quarter close entirely — that's the reporting fire drill and nobody will pick up. Week four of the quarter is ideal: the cycle just finished, the pain is fresh, and there's still runway before the next close. Also avoid a firm mid-custodian conversion cutover for the meeting itself, though it's a perfectly good time to run the vendor review so an approved vendor is waiting when budget opens.
- What metrics should I put in a financial services cold call script?
Use the numbers these buyers are actually measured on, and use them as things you've heard from peer firms, never as market claims. The strongest for wealth ops are quarter-end reporting cycle time in business days from period close to client delivery, compliance exceptions and audit findings per period, AUM per advisor and households per advisor, and organic growth measured as net new assets as a percentage of beginning AUM. Saying "firms that plan for day ten deliver on eighteen" and "a senior advisor carrying 110 households" lands because those are the exact figures on their monthly ops report.
- What counts as a successful cold call here if they won't book a meeting?
A dated reason to call back plus one named priority in their own words. "Conversion wraps in October, budget gets set in November, and the metric she owns is cycle time" is a real outcome. "Send me an email" with nothing traded for it is a polite hang-up. Before you let go, ask whether it's a timing thing or a not-a-priority thing, get the budget cycle date, and log the exact phrasing they used about the problem — those words go straight into the follow-up email and the eventual discovery call.