Financial Services · Discovery Call
Discovery Call Questions for Financial Services: A 25-Minute Playbook for Wealth Management Buyers
You have 25 minutes with a Director of Wealth Management Operations who just came off a quarter-end cycle where the custodial feed for one clearing relationship broke on day three, two alternatives marks came in as PDFs from the fund admin, and somebody rebuilt eleven client-facing performance pages by hand at 9pm. She took your call because your first touch didn't sound like the last four. If you open with logos, or if you say "oh, we automate reconciliation" the second she mentions reconciliation, you will get polite, four-word answers for the rest of the call and no second meeting.
This buyer set — COO Wealth Management, Chief Compliance Officer, Head of Advisory Platform, Head of Client Reporting & Performance, CTO/Head of Advisor Technology, VP Third-Party Risk — has a specific reflex you need to plan around. They will not tell you the real cost until they believe you understand the mechanism, and they will not tell you the political stake until they believe you understand the regulatory constraint. A rep who can say "so nothing hits a client statement without going through 2210 review, and the SLA on that queue is what, ten business days?" earns a layer of the conversation that a rep who says "walk me through your workflow" never sees.
What follows is the frame, the question ladder, the objections you will actually hear from a wealth firm mid-custodian-conversion, and a sample call with a buyer who is difficult in the way this industry is difficult — not rude, just quietly certain that you are the fifth vendor this quarter who has promised to fix quarter-end and doesn't know what a WORM archive is. The goal of the call is not a demo. It's a dated next step with a named InfoSec or compliance person on the invite.
The discovery call script
Say it in your own words. The structure is the part that matters.
- 1
0:00–2:00 — Frame (do not re-pitch)
"Thanks for clearing the time. Quick frame so I don't waste it: when we traded notes you said quarter-end had gone from a cycle to a fire drill, and that your reporting team lost most of the first three weeks after period close. That's the thing I want to dig into. I'm going to ask a lot of questions for the first fifteen minutes and show you almost nothing. I'd genuinely rather tell you today that this isn't a fit than book a demo slot neither of us needs — regulated firms are the wrong place to guess. Still good for 25? And is there anything you want to make sure we cover so I don't run us out of time?"
- 2
2:00–6:00 — Layer 1 to Layer 2: open the thread, then get the mechanism
Pick ONE opener. Do not stack. "Take me through quarter-end as it actually runs — from period close to the day statements land with clients." Then follow up on what they said, not what's on your list: • "Walk me through last quarter specifically. Where did it break first?" • "Where does that data sit between portfolio accounting and the client-facing deck? Who moves it?" • "Held-away assets and alternatives marks — is that in the same file, or is somebody keying it in from a fund admin PDF?" • "When the custodial feed is stale, who notices — the ops analyst, or the advisor on the review call?" • "What's the workaround your team has built that nobody put in a project plan?" Three follow-ups per thread before you change subject.
- 3
6:00–11:00 — Layer 3: cost, then "how do you know?"
"So on cycle time — how many business days is it, from period close to client delivery? And is that number one you report up, or one you and your team just live with?" "How do you know it's [their number]? Is anyone tracking it, or is that the feel of it?" "How many people are pulled into that window, and are any of them advisors? Because that's the part I'd want to size — if a senior advisor carrying 100 households loses two days to meeting prep and reporting cleanup, that's two days not in front of a $4M relationship." "Last twelve months, how many times did a number have to be corrected after it went out? What happens internally when that occurs — is that a compliance exception, a reportable event, a restatement conversation?" "When you look at AUM per advisor and revenue per advisor, is leadership telling you to grow the book without adding ops headcount, or is there a headcount case on the table?" After a heavy answer: count to three. Say nothing.
- 4
11:00–16:00 — Layer 4: the stake
"Who's feeling this most — is it your reporting team, the advisors, or is your CCO the one getting the questions?" "Whose number does this show up in? Does quarter-end cycle time sit in your goals, or does it roll up to the COO?" "What did you commit to, and by when? Was there a date attached — board meeting, audit, the end of the custodian conversion?" "If nothing changes and next quarter runs the same way, what's the conversation you're having in January?" "Is any of this showing up in advisor attrition conversations? I ask because platform leaders usually hear 'I spend my Sundays doing admin' long before they see it in the organic growth number." Silence after each. The sentence they weren't sure they'd say comes at second three.
- 5
Minute 6 trap — "So what do you actually do?"
30 seconds, tied to what they just told you, then hand the ball back: "Short version — we take the stitch-together step you just described, the one where your analyst is pulling held-away and alternatives into a spreadsheet before it goes near a client deck, and we produce that off templates your compliance team pre-approves once. So the review queue changes from 'read every page' to 'confirm it came off approved template v4.' But I'd be guessing at whether that matters until I understand one thing: when a number is wrong and it's already gone out, who catches it and what's the remediation path?" If they push a second time, give a clean 60 seconds, then: "Can I go back to the alternatives marks thing? That's the part I'm still not clear on." Almost everyone lets you.
- 6
16:00–20:00 — Qualify the path (never recite BANT)
"If you decided this was worth doing, what actually happens next in your shop? Who gets pulled in — third-party risk, InfoSec, legal, your CCO?" "Have you tried to fix quarter-end before? What happened to that project?" (The graveyard is your real competitor.) "When your TPRM team gets a new vendor package, what's the realistic clock — and how much of that six months is you waiting on the vendor to answer the DDQ?" "Is reporting tooling a line item that already exists, or would it need to get created? I'm sizing, not asking for a number." "What's forcing the timing — the custodian conversion, an SEC exam cycle, a board commitment on organic growth?" "And if you just keep running it the current way — what's the honest answer, does that survive another four quarters?"
- 7
20:00–23:00 — Targeted relevance, 90 seconds only
Only address what they raised. If they raised advertising review, talk about pre-approved templates, locked disclosure blocks, version stamps and reviewer logs. If they raised data residency, talk about single-tenant in their cloud region with their own keys. If they raised advisor adoption, talk about eight advisors and one quarter-end cycle. "Two things, then I'll stop. One, on the 2210 point you made — output comes off templates your compliance team approves once, with no free-text field that can invent a performance claim, and every item carries a version stamp and reviewer log. Two, before any of that matters, your third-party risk team gets the SOC 2 Type II, the completed DDQ, the pen-test summary, the data-flow diagram and the sub-processor list. That goes out whether or not we do anything else." Stop talking.
- 8
23:00–24:00 — Playback in their words
"Let me make sure I've got it. Quarter-end runs eighteen business days from period close, and the reason it runs that long is the held-away and alternatives piece gets hand-stitched in Excel after the custodial feed lands, by two people, one of whom is your best analyst. Last year you had two corrections go out to clients, one of which your CCO logged as an exception. You told the COO you'd get the cycle under ten days before the conversion finishes in March. Did I miss anything, or get anything wrong?"
- 9
24:00–25:00 — Close a dated, named next step
"Based on that, the useful next thing isn't a demo. It's 45 minutes with you, your performance lead, and whoever owns InfoSec architecture — so they can tell me on the call which deployment model is dead on arrival before we spend anyone's time. I'll bring the SOC 2 and the DDQ so your TPRM clock can start that week. I've got Tuesday at 2 or Thursday at 9. Which works?" Then confirm out loud: who's attending, what you'll cover, what they bring — last quarter's cycle-time log and one sample client performance page, redacted. Send the invite before you hang up.
- 10
CRM notes — their words, not yours
Bad: "Prospect has reporting inefficiencies." Good: "'Eighteen business days, and it's eighteen because Marisa hand-builds the alternatives page from fund admin PDFs. She's done it for six quarters and she's already interviewing.' Committed to COO: sub-10 days before conversion completes March. Two corrections last year, one logged as a compliance exception. TPRM owner is Devi (VP Third-Party Risk); says the six months is really four months of vendors not answering the DDQ."
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Thanks for clearing the time. Quick frame — when we traded notes you said quarter-end had stopped being a cycle and started being a fire drill. That's what I want to dig into. I'll ask a lot and show you almost nothing for the first fifteen minutes. Still good for 25, and anything you want to make sure we cover?
Buyer
Twenty-five is fine. I'll tell you up front, you're the fourth vendor this quarter who's told me they'll fix quarter-end. Two of them didn't know what 17a-4 was. So I'm going to be short with you if this goes generic.
Rep
Fair, and I'd rather be told that now. So let's stay specific. Take me through last quarter — period close to the day statements landed with clients. Where did it break first?
Buyer
It didn't break dramatically. It just takes what it takes. Data comes out of portfolio accounting, we reconcile against the custodial feeds, and then there's a manual layer.
Rep
Tell me about the manual layer. What's in it?
Buyer
Held-away assets and alternatives. The alts marks come in from fund admins as PDFs, sometimes three weeks late, and somebody keys them into a workbook that feeds the client-facing performance pages. That's the part that isn't systematised.
Rep
Who's the somebody?
Buyer
Two people on my team. Mostly one of them.
Rep
How many business days is the whole thing, period close to client delivery? And is that a number you report up, or one your team just absorbs?
Buyer
Eighteen. It's in my scorecard. Look — before we go further, what does this cost? Because if we're outside the range there's no point in me learning about it.
Rep
Happy to give you a range at the end, and I will. But I'd be pricing a guess right now, and you'd be right to discount it. One thing first: eighteen days — has a wrong number ever gone out inside that window?
Buyer
…Once. Last year. A time-weighted return on a household with a big held-away position. Wrong on the statement, went out, we caught it on the review call.
Rep
What happened after that internally?
Buyer
Our CCO logged it as an exception, we redelivered corrected statements, and it came up in the annual review. That's the thing people outside this industry don't get — it's not an embarrassment, it's a books-and-records issue. And now every client-facing artefact I want to change goes through her twice.
Rep
So the correction didn't just cost you the redelivery — it cost you throughput on everything you've wanted to do since.
Buyer
Correct. And I told the COO I'd have the cycle under ten days before the custodian conversion finishes in March. Which, at the moment, I do not have a plan for. My analyst who owns the alts workbook has done six quarters of this and I don't think she does a seventh.
Rep
That's the piece I'd want to size. If she leaves mid-conversion, who rebuilds that workbook?
Buyer
Nobody. That's the honest answer. And I'm not adding ops headcount — the mandate is grow AUM per advisor without growing the cost base.
Rep
Understood. So let me play it back and you tell me what I've got wrong. Eighteen business days, and it's eighteen because alternatives and held-away get hand-keyed off fund admin PDFs by one analyst who's on her sixth quarter of it. One correction went out last year, your CCO logged it as an exception, and now everything client-facing goes through her twice. You've committed sub-ten days to the COO before the March conversion, with no headcount. Anything I missed, or got wrong?
Buyer
That's it. The other thing is nothing gets bought here without third-party risk. Devi's team runs the DDQ, and it's a six-month process. So even if I loved this, March is fiction.
Rep
Then that's the next step, not a demo. Forty-five minutes with you, your performance lead, and whoever owns InfoSec architecture — I'll bring the SOC 2 Type II, the completed DDQ, the pen-test summary and the data-flow diagram so Devi's clock starts that week instead of after we've had four more calls. Most firms tell me four of those six months is waiting on the vendor. Tuesday at 2, or Thursday at 9?
Buyer
Thursday. I'll pull in Devi and I'll try for our performance lead. Send the diligence pack Monday and I'll forward it before the meeting so nobody's reading it live.
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 report, completed standard DDQ, pen-test summary, data-flow diagram, sub-processor list — all of that goes to your TPRM team today, before you commit to anything. Most firms your size tell me the six months is really four months of waiting on the vendor to come back with answers. If Devi's team gets a complete package in week one, you find out in week three whether this is even reviewable. I'd rather be told no in week three than string you along until Q2. |
| “Everything client-facing has to go through advertising review. This just moves the bottleneck, it doesn't remove it.” | Agreed — we don't remove the review, we change what shows up in the queue. Output comes off templates your compliance team pre-approves once, with locked language blocks, mandatory disclosures, and no free-text field that can invent a performance claim. Every item carries a version stamp and a reviewer log. Firms tell me the win isn't fewer 2210 reviews, it's that a review goes from 'read every page' to 'confirm this came off approved template v4' — and the exception count per period drops, which is the number your CCO actually reports. |
| “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, features are irrelevant. We support single-tenant hosting in your cloud region with your own encryption keys, and there's a configuration where data never leaves your tenancy. What I want is thirty minutes with whoever owns your InfoSec architecture — not to pitch, but to have them tell me which of those two is acceptable and which is dead on arrival. If neither works, I'll say so on that call. |
| “Our advisors won't adopt it. We rolled out a new platform two years ago and half of them still work in spreadsheets.” | That's the most honest objection I get and it's usually right. So let's not launch firm-wide. Pick eight advisors — including the two who complained loudest about the last rollout — and run one quarter-end cycle. If their hours don't change, you've spent a quarter and learned something cheap. If they do, those eight are the reason the other ninety try it, and 'Marcus says it works' beats a mandate from ops every time. |
| “Budget's committed. We're mid-way through a custodian conversion and there's no tech spend until next fiscal.” | Then it's a next-fiscal purchase and I'm fine with that — but the vendor review is the long pole, not the money. If diligence runs during the conversion, you have an approved vendor sitting 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 written. |
| “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 our 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 our control evidence. I'd rather your legal team push on those terms in week two than discover them at renewal. |
Questions reps ask about this call
- What discovery call questions work on a Chief Compliance Officer versus a COO of Wealth Management?
Different currencies. With a COO, Wealth Management or a Director of Wealth Management Operations, you're asking about cycle time, cost-to-serve per household, AUM per advisor, and who physically touches the workbook: 'How many business days from period close to client delivery, and who's doing the alts marks by hand?' With a Chief Compliance Officer, cycle time is not the pain — exceptions and audit findings are. Ask 'How many client-facing corrections or reportable events did you log last period, and what triggered each one?' and 'What does an item need to carry — version stamp, reviewer log, retention path — before it's reviewable rather than a research project?' The CCO's yes is about evidentiary cleanliness, not hours saved.
- They asked for pricing at minute nine. Do I give it?
Give the shape, not the number, and buy back the thread. 'Happy to give you a range at the end and I will — but right now I'd be pricing a guess and you'd be right to discount it. One thing first: inside that eighteen-day window, has a wrong number ever gone out?' In financial services the pricing question is often a screening move, not a buying signal — they're checking whether you'll behave like the last three vendors. Answering with a real range at minute 23, after you've diagnosed, lands far better than a fumbled one at minute nine.
- How do I quantify the cost when they won't give me numbers?
Stop asking for dollars and ask for countables they already track. Business days from period close to client delivery. Number of corrections or restatements in the last twelve months. Compliance exceptions per period. Headcount pulled into the quarter-end window and how many of them are revenue-producing advisors. Then ask the second beat that most reps skip: 'How do you know?' If they can't source the number, that's a finding — the problem is invisible to their COO, and part of your job in the next meeting is helping them build the case, not selling into an unfunded one.
- What's a credible next step to close on with a regulated wealth firm?
Not a demo. The strongest next step is a 45-minute working session with the ops or reporting owner plus whoever owns InfoSec architecture or third-party risk, where you arrive with the diligence pack — SOC 2 Type II, completed DDQ, pen-test summary, data-flow diagram, sub-processor list — so their TPRM clock starts immediately. Name the date, name the attendees, name what they bring (last quarter's cycle-time log, one redacted sample performance page). 'I'll send some information' is a no with a smile on it.
- They said 'we're mid-custodian-conversion, there's no budget.' Is the call dead?
No, but the sequence changes. Money is rarely the long pole in this industry — vendor review is. Reframe to: run diligence during the conversion so an approved vendor is sitting on the shelf when budget opens, instead of starting a six-month clock in Q1. Then ask the diagnostic question hiding inside their objection: how much of the conversion pain right now is their team hand-building reporting through the cutover? That's usually where the first business case actually gets written, and it's a question no other vendor asked them.
- How do I practise these calls without burning a live prospect?
Run them out loud against a buyer who behaves like a real one — a Director of Wealth Management Operations who's been pitched four times this quarter, gives you clipped answers, demands pricing at minute nine, and only mentions the correction that got logged as a compliance exception if you sit in the silence. That's what DrillCall roleplay is for: same 25-minute clock, same objections about 17a-4, single-tenant hosting, and 2210 review, so the first time you hear 'you're the fourth vendor who's told me they'll fix quarter-end' isn't on a call that matters.