Financial Services · Demo Call
The Financial Services Product Demo Script for Wealth Management Buyers
You have a demo booked with a Director of Wealth Management Operations who told you last time that quarter-end takes her team fifteen business days from period close to client delivery, that three of those days are someone hand-keying alternatives marks and held-away balances into a deck, and that the last time a wrong time-weighted return went out on a statement it became a books-and-records conversation with the CCO. She said yes to the demo. She also invited the Chief Compliance Officer and the Head of Advisor Technology, and neither of them asked to be there.
That's the room. The COO or ops director wants the fifteen days to become eight. The CCO is there to find the sentence that makes this a FINRA 2210 problem or a 17a-4 problem, and she will find it in the first twenty minutes if you show a free-text field on a client-facing page. The CTO wants to know whether this reads from Orion or Addepar or Tamarac, whether it writes anything back, and who gets paged at 11pm on the second business day after quarter close. Three demos, one hour, and the only thing that gets you a second call is answering all three in their environment instead of yours.
This Financial Services product demo script is built for that call. It assumes you've done the pitch, you know their custodian and their portfolio accounting system, and you're now being tested rather than educated. Every interruption you get is either a buying question or a disqualification test. Run the standard tour — dashboard first, admin screens, feature parade — and you'll hear typing, then "this is really helpful, let us digest it," and the deal is dead without anyone telling you.
The demo call script
Say it in your own words. The structure is the part that matters.
- 1
Before the call — confirm the stack in writing
Send this in the confirmation email, three days out, not the morning of: "So I don't waste an hour showing you things that don't apply — three quick ones: 1. What are you running for portfolio accounting and performance? (Orion, Addepar, Tamarac, Black Diamond, in-house?) 2. Which CRM, and which instance — Salesforce Financial Services Cloud, Redtail, Practifi? Who administers it internally? 3. Which custodians are you on, and are you mid-conversion on any of them? And one more: who owns your communications archive — Smarsh, Global Relay, Proofpoint, something else? That determines about half of what I show your compliance lead." If they answer, build the demo around those names. If they don't answer, ask again on the call in the first ninety seconds. Demoing a wealth platform without knowing whether the firm is a dually-registered hybrid or a pure RIA is like demoing without knowing what industry they're in — the supervision story is completely different.
- 2
Before the call — map the room to three different demos
Write these down before you dial: - **Chief Operating Officer, Wealth Management / Director of WM Operations** — wants the cycle-time number to move and cost-to-serve per household to come down. Show them the quarter-end pack build, start to finish, with their household count. - **Chief Compliance Officer** — wants to know what lands in the 2210 review queue, whether output is archivable in WORM storage, whether anything creates a new communication channel, and what the exception rate looks like. Show them the template lock, the version stamp, and the reviewer log. Nothing else. - **CTO / Head of Advisor Technology** — wants the integration method, the direction of data flow, and what breaks at their next Orion release. Show them the data-flow diagram, not a screen. - **VP, Third-Party / Vendor Risk Management** — if they're on the call, the demo is secondary. Their outcome is a complete DDQ package in their inbox before you hang up. Decide what you will not show. Every extra module is another line on the CCO's risk assessment.
- 3
Opening — 90 seconds, set the contract
"Before I share anything — last time, [Name], you said quarter-end is fifteen business days from period close to client delivery, and three of those are someone stitching alternatives marks and held-away balances into a deck by hand. And you said the thing that scares you isn't the fifteen days, it's a wrong return number going out. Still accurate? [Let them answer.] Anything shift since we spoke? Budget, priorities, custodian conversion timeline? [Let them answer.] Two things about how I'd like to run this. First, please interrupt me. If you're thinking 'that won't work here,' say it in the moment — that's the useful part of the hour, not the part where I click through screens. Second, [CCO name], you're the one who can kill this fastest, so let's start there: what's the one thing that, if this can't do it, we don't need to keep talking?" Then shut up. Whatever they name is the first thing you demo. If the CCO says "it has to be archivable," you do not open with the reporting workflow, no matter what you rehearsed.
- 4
Core loop 1 — quarter-end, the moment not the feature
**Problem:** "So it's the third business day after period close. Your performance analyst has the data out of [Orion/Addepar], but the alternatives marks aren't in yet, two custodial feeds broke over the weekend, and the client-facing deck for the [Firm] households still gets reformatted by hand." **Screen:** "This is the reconciliation exception view. It's not showing you everything — it's showing you the twelve accounts where the custodial position doesn't tie to portfolio accounting, sorted by household AUM, so the $4M household gets looked at before the $40k IRA. Your analyst works this list, not the whole book." **Consequence:** "What stops happening is the spreadsheet stitch. The marks and the held-away balances land in the same place as the custodial data, and the deck is generated from that, not retyped from it. The number in the client's statement and the number in your books came from the same row." **Check:** "Is that how your team actually works the breaks, or does someone own it account-by-account? I want to know if I'm making that up."
- 5
Core loop 2 — the advisor hour, told from the advisor's chair
**Problem:** "Your senior advisors are carrying — what did you say, 110 households? So Thursday afternoon, an advisor has three reviews Monday. Right now that's pulling performance, pulling the plan from eMoney, checking whether the RMD went out, and building three decks." **Screen:** "This is what he opens Monday at 7am. One household. Performance off the same approved template your compliance team signed off on, the plan progress, the open items — ACAT still in flight, beneficiary form unsigned, held-away 401(k) balance he entered last quarter and hasn't updated. He's reading, not building." **Consequence:** "The thing you're measured on is AUM per advisor and organic growth. Nobody grows a book on a Sunday spent in CRM. This isn't a productivity story, it's a 'the advisor is in the review meeting instead of prepping for it' story." **Check:** "When your top quintile complains about admin — is it prep, is it paperwork, or is it CRM notes? Because those are three different screens and I only want to show you the one that matters."
- 6
Core loop 3 — the compliance screen (run this for the CCO, alone if you have to)
"[CCO name], this next part is for you and it'll take four minutes. This is a client-facing output. Notice what isn't here: there is no free-text box. The language blocks are locked. The disclosure footer is mandatory and can't be deleted at the item level — it's set at the template. The advisor can select from approved commentary; he cannot write a performance claim. Up here: template v4, approved by [reviewer], date stamped. Every item carries that stamp. Down here is the reviewer log — who opened it, who approved it, when, and whether it was exception-routed. What changes in your 2210 queue is not the volume. It's that your reviewer goes from reading every page to confirming it came off approved template v4. And the number you actually report on — compliance exceptions per period — is the one that should move. What this does not do: it does not send anything to a client. It generates the item; delivery happens through your existing channel, which means it stays inside your supervision and archiving perimeter. We are not creating a new communication channel. If you thought we were, that's the most important thing I've said today." Then: "What's the question I should have anticipated and didn't?"
- 7
Pressure line 1 — Integration, named not gestured at
Never say "we integrate with everything." Say: "Read-only against [Orion] via their API, on a schedule — nightly by default, we can run it after your custodial files land instead. We read positions, transactions, and performance. We do not write back. Ever. Your book of record stays your book of record. CRM is a two-way connector for [Salesforce FSC] — we read household and contact data, we write meeting notes and completed tasks back into the activity record, and every write is attributed to the advisor's user, not a service account, so your supervision picks it up normally. Custodial data we take from the feed you already have, not from a separate connection to [Schwab / Fidelity / Pershing]. If your feed is stale, we surface it as stale — we don't average around it. Archive: every generated item goes to [Smarsh/Global Relay] through your existing capture path, in your retention policy, WORM. We are not the archive of record. We hand it to yours. What that means for your team: no gateway inside your network, no agent on advisor desktops. If you're on a heavily customised [Orion/Salesforce] instance, the thing I'd want to check before we go further is your custom object model — that's a thirty-minute call with your admin, and I'd rather do it before your vendor risk team spends a day on us."
- 8
Pressure line 2 — Who owns it once you're gone
"Honest answer: this is not IT work after week four. Ongoing it's roughly two to three hours a month, and it's admin — adding advisors, changing which reviewer an exception routes to, updating a template when disclosure language changes. Your ops coordinator does it. It should not sit with your CTO. One exception: template changes that alter client-facing language have to go through your 2210 review before they go live, same as any other advertising change. We build the template; your compliance team approves it. We don't approve our own output. On our side: [name] runs implementation, and [name] is your ongoing contact — different people, and I'll be straight that the handoff happens at week six. If your admin leaves, the handover is a two-hour session and a runbook; there's no tribal knowledge in the config."
- 9
Pressure line 3 — What actually happens when it breaks
Do not lead with an uptime percentage. Lead with the failure mode, and lead with the worst week of their year. "If we go down on the second business day after quarter close — which is the only outage that matters to you — here's what happens. Your portfolio accounting system is untouched; it's your book of record and we're read-only. Nothing already generated is lost; approved items are already in your archive. What you lose is the ability to generate new items until we're back. You do not lose data and you do not have a books-and-records gap. Support: P1 is a phone number, twenty-four hours, and a person answers — during quarter close we staff it heavier and I'll give you the direct line. P3 is email, next business day, and I'm not going to pretend otherwise. Breach notification is twenty-four hours to your named incident contact, not seventy-two, and that's contractual. If you want, I'll walk your team through our last incident and what we changed. Firms that can describe an outage clearly are easier to trust than firms that claim they've never had one."
- 10
Pressure line 4 — Time to value, in three dates against their calendar
"Three dates, not one. **Live** — connections up, data flowing, one pod of eight advisors seeing their households. Four to five weeks, and we would not cut over during your quarter-end window. If period close is the 1st through the 10th, we're doing this mid-quarter. **Useful** — one full quarter-end cycle run through it with those eight advisors, and your ops team stops rebuilding those decks by hand. That's the first quarter after go-live. That's when you'll know whether fifteen business days becomes eleven or doesn't move at all. **Fully rolled out** — all ninety-odd advisors, two quarters. What you have to do, and I'd rather over-state it: a household and advisor list, a data extract from [Orion] for the sandbox, your existing disclosure language, one compliance reviewer for roughly six hours across the template approvals, and two ninety-minute sessions with the pilot advisors. That's the workload. Projects stall in week three when nobody warned the ops director about the template approvals. Comparable: [Firm], [X]B, three custodians, dually-registered — live in five weeks, ran one quarter-end on it, and they'll take a reference call."
- 11
Handling 'will it handle X?'
Slow down. Get the actual case before you answer. "Will it handle held-away assets?" is unanswerable. Ask: "Held-away meaning an old 401(k) the advisor keys in manually once a quarter, or aggregated via [Plaid/ByAllAccounts] and included in the performance calculation? Those are two very different answers." Then pick one of three, honestly: - **Yes, and here it is.** Show it live. Strongest thing that happens on a demo. - **Yes, but not how you'd expect.** "You don't do it on this screen. You do it here, and it's two extra clicks and one approval. Buyers forgive ugly; they don't forgive discovering ugly in month three." - **No.** Say it. "No. We don't produce GIPS-compliant composite reporting today, and it isn't on this year's roadmap." Then: "How often does that come up — is that every quarter for every client, or is it the two institutional relationships?" Half the time the deal-breaker is an edge case they mentioned because it occurred to them. Never say "we can build that." To a Head of Advisory Platform who lived through an eighteen-month platform migration, that phrase is the exact promise the last vendor broke. Write the open items down out loud: "Noting that — money-weighted returns for the accounts with big cashflows. Straight answer by Thursday." Then Thursday, not next week.
- 12
Recovering when the room goes quiet
Signs: short answers, "mm-hm," typing you can hear, a beat of delay before every response, the CCO's camera goes off. Stop. Do not add features and do not talk faster. In order of preference: 1. "I've been talking for a while. Is this the part you care about, or should I jump somewhere else?" 2. "Let me stop the tour. What's the thing you're worried about that I haven't touched?" 3. "Do you want to drive? Tell me what to click." (Almost nobody offers this. It works.) 4. "I think I'm showing you the wrong things. Can I stop, spend ten minutes understanding what actually matters, and come back Thursday with a demo built for that?" Giving up twenty minutes of a demo to save the deal is a good trade. Pushing through to the end of your deck to feel finished is not.
- 13
Closing — fit, gaps, temperature, calendar
"Let me summarise, including the parts that didn't land. Three things worked: the exception view against the custodial break, the template lock and reviewer log, and the fact that we're read-only against [Orion]. Two open: money-weighted returns for the cashflow-heavy accounts, and whether your Salesforce custom objects change the connector scope. I'll have both answered by Thursday. [CCO name] — where does this sit for you now? Worth pursuing, or is there something you've already seen that rules it out? I'd genuinely rather hear that today. [Then:] Who else needs to see this before it's real? If it's your VP of Third-Party Risk, I'd run twenty minutes that's only architecture, data flow, sub-processors and SOC 2 — no product. And I'll send the DDQ, the SOC 2 Type II, the pen-test summary and the data-flow diagram today, before you commit to anything, so your review clock starts now instead of after a procurement decision. Can we get the vendor-risk session on the calendar while we're all here? What does the week of the [date] look like?" Send within twenty-four hours: the two open items with real answers, the four screens that mattered (not the recording of the whole hour), the security package, and a one-line list of what you need from them.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before I share my screen — last time, Dana, you said quarter-end is fifteen business days from period close to client delivery, and three of those are someone hand-stitching alternatives marks and held-away balances into the deck. Marcus, you weren't on that call, so before I show anything: what's the one thing that, if this can't do it, we stop?
Buyer
Two things. One, if any client-facing output comes out of a large language model with a free-text field, I'm out — I'm not defending a hallucinated performance claim to an examiner. Two, if this creates a channel my advisors can communicate with clients through, it's in scope for 3110 and 17a-4 and I have to capture and surveil it. We just came out the other side of the off-channel sweeps. I'm not adding surface area.
Rep
Then I'll start there and skip the reporting workflow entirely for now. Screen's up. This is a client-facing quarterly item. Look at what's missing — there is no free-text field anywhere on this page. The commentary block is a pick-list your compliance team populates. The disclosure footer is set at the template level and cannot be deleted at the item level. An advisor cannot write a sentence that goes to a client.
Buyer
Who approves the pick-list? Because if your team writes the language and my team rubber-stamps it, that's not a control, that's a liability with a signature on it.
Rep
Your team writes it. We build the template shell; the language blocks are yours, entered by your reviewer, approved in your workflow, and locked. Here's the version stamp — template v4, approved by whoever your reviewer is, with the date. Every generated item carries it. And the reviewer log underneath shows who opened it, who approved, and whether it exception-routed. Your 2210 review goes from reading every page to confirming provenance.
Buyer
Fine. Second question. Where does the item live once it's generated, and don't tell me you archive it. I have Global Relay. I'm not running a second archive and I'm not explaining two retention policies to an examiner.
Rep
We're not the archive of record and I don't want to be. The item goes to Global Relay through the capture path you already have, under your existing retention policy, WORM. We hold a working copy for regeneration and it expires on a schedule you set. If your answer is 'zero working copy,' tell me now, because that's a configuration conversation and I'd rather have it today than in your DDQ in six weeks.
Buyer
And the model. Is our client data training anything? Because Dana's team is going to feed this household-level positions and I've read enough vendor terms to know what 'to improve our services' means.
Rep
No. Contractually no, and it's in the DPA, not in a marketing page — no training on your data, no retention beyond the working copy, sub-processor list attached and we notify you before it changes. And we're single-tenant in your cloud region with your own keys if that's what your InfoSec architecture requires. Which of those two is acceptable to you and which is dead on arrival? I'd like thirty minutes with whoever owns that.
Buyer
That's Priya, and she'll take that call. But I'll tell you what happens next regardless — this goes to third-party risk, and that's six months. I've got a queue. I can't shortcut it and I'm not going to for you.
Rep
I'm not asking you to. I'm asking you to start it on something that's already packaged. SOC 2 Type II, completed standard DDQ, pen-test summary, data-flow diagram, sub-processor list — I can send all five today, before anyone commits to anything. Most firms tell me the six months is really four months of waiting on the vendor to answer follow-ups. If Priya's team gets a complete package in week one, you know by week three whether this is even reviewable. I'd rather be told no in week three.
Buyer
Dana, does any of this actually move your fifteen days? Because I've now spent twenty minutes on controls for something that might save us three days on a report nobody reads.
Rep
That's the right question and I shouldn't answer it — Dana should. But let me show one screen and then she can tell you if I'm inventing it. Dana, this is the third business day after close. Twelve accounts where the custodial position doesn't tie to portfolio accounting, sorted by household AUM so the $4M household surfaces above the small IRA. Is that how Rachel's team works the breaks today, or is it account-by-account down a list?
Buyer
It's down a list, and it's Rachel plus two temps every quarter. But I'll push on one thing — a chunk of my fifteen days isn't reconciliation, it's the alternatives marks that don't arrive until day nine. You can't fix that. So don't tell me eleven days if the marks are the constraint.
Rep
Then I won't. If the marks land day nine, your floor is day nine plus whatever production takes, and we only touch the second half. Honest version: we compress production and reconciliation, not vendor timing. Whether that's fifteen to eleven or fifteen to thirteen, I don't know from here — and I'm not going to guess in front of your CCO. That's what one pilot quarter with eight advisors tells you.
Buyer
Eight advisors. Which eight? Because we rolled out a new planning tool two years ago and half the book still lives in spreadsheets. If you pick the eight who like technology, you've proven nothing.
Rep
Then pick two of the loudest complainers from that rollout on purpose. If it doesn't change their hours in one quarter-end cycle, you've spent a quarter and learned something real. If it does, those eight are a better internal story than a mandate from ops ever will be. Marcus — where does this sit for you now? Worth Priya's thirty minutes, or is there something you've already seen that rules it out?
Buyer
It's worth Priya's thirty minutes. Send the package today, and I want the DPA language on training in front of my legal team before we schedule anything else.
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 and sub-processor list, all ready to send 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 your third-party risk 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 Q3. |
| “We're regulated. I can't just try a new vendor because the demo looked 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 your supervision or books-and-records obligations moves. Your ops lead and one compliance reviewer see exactly what output it produces and exactly 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. This just moves the bottleneck, it doesn't remove it.” | We don't remove the review and I wouldn't claim to. We change 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 that can invent a performance claim. Every item carries a version stamp and a reviewer log. The win firms describe isn't fewer reviews, it's reviews going from 'read every page' to 'confirm it came off approved template v4' — and the exception rate drops, which is the number your CCO reports on, not the page count. |
| “Our client data can't leave our environment. Full stop.” | Then let's settle deployment before we talk about a single feature, because if we can't satisfy that, nothing else matters. 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 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 two is acceptable and which is dead on arrival. If neither works, I'll say so and we'll stop. |
| “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. Which is why I don't want to launch firm-wide. Pick eight advisors — including two who complained loudest about the last rollout — and run one quarter-end cycle. If their Sunday admin doesn't change, you've spent a quarter and learned something. If it does, those eight are why the other ninety try it, and that's a far better internal story than a mandate from operations. |
| “Budget's committed. We're mid-way through a custodian conversion and there's no tech spend until next fiscal.” | Then this is a next-fiscal conversation and I'm genuinely fine with that — but the vendor review is the long pole, not the money. If diligence runs during the conversion, you've got 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 is your team hand-building reporting during the cutover, when the feeds are half-on and half-off? That's usually where the first internal case gets written. |
Questions reps ask about this call
- How is a financial services product demo different from a standard SaaS demo?
The room is different. In most SaaS demos one buyer evaluates fit. In wealth management you're typically in front of three people with three incompatible agendas: a COO or Director of Wealth Management Operations who wants quarter-end cycle time and cost-to-serve per household to move, a Chief Compliance Officer who is looking for the reason to say no under FINRA 3110, 2210 or 17a-4, and a CTO or Head of Advisor Technology who wants to know what you read, what you write back, and who gets paged. The CCO can kill the deal alone; the others can only advance it. So you demo the compliance surface first and the productivity story second, even though the productivity story is what got you the meeting.
- What should I show first in a demo to a Chief Compliance Officer?
Show the absence of risk before you show capability. Open on a client-facing output and point at what isn't there: no free-text field, locked language blocks, disclosure set at template level and not deletable at item level. Then show the template version stamp and the reviewer log. Then say explicitly whether you create a new communication channel and where the item lands in their archive — Smarsh, Global Relay, Proofpoint, whatever they already run — under their retention policy, in WORM storage. Four minutes, then hand the mic back with 'what's the question I should have anticipated and didn't?' Skip the dashboard entirely; it reads as unserious.
- How do I answer 'will it handle held-away assets?' or 'does it do GIPS-compliant reporting?' without overpromising?
Get the actual case before you answer, because both questions have two very different versions. Held-away could mean an advisor keying an old 401(k) balance once a quarter, or full aggregation feeding the performance calculation. Ask which. Then answer one of three ways: yes and show it live, yes-but-ugly and show the workaround with the exact number of extra clicks, or no. If it's no, say no and then ask how often it comes up — a quarter-end need for two institutional relationships is not the same as a daily need across the book. Never say 'we can build that' to a Head of Advisory Platform who just survived an eighteen-month migration; they hear the promise their last vendor broke.
- What integration detail do wealth management buyers actually want in a demo?
Direction, frequency, and what you don't touch. Say 'read-only against Orion via API, nightly, or triggered after your custodial files land — positions, transactions, performance, and we never write back' rather than 'we integrate with Orion.' For CRM, say whether writes are attributed to the advisor's user or a service account, because that determines whether the firm's supervision picks it up. Then say what you don't touch: not the book of record, not the archive of record, no agent on advisor desktops. Naming what you refuse to write to calms a CTO faster than any capability claim.
- How do I set expectations on time-to-value when their quarter-end is the constraint?
Give three dates, not one, and tie them to their close calendar. Live — connections up, one pilot pod seeing their households, four to five weeks, and explicitly not during their period-close window. Useful — one full quarter-end cycle run through the platform, which is the first quarter after go-live and the only honest point at which they'll know whether fifteen business days becomes eleven. Fully rolled out — all advisors, two quarters. Then over-state their own workload: household and advisor lists, a data extract, their disclosure language, roughly six hours of a compliance reviewer's time for template approvals, and two sessions with pilot advisors. Projects stall in week three when nobody warned the ops director about the approval hours.
- The buyer went quiet halfway through the demo. What do I do?
Stop the demo immediately — do not talk faster or add a feature. In wealth management, silence usually means the CCO has mentally filed you under 'six-month review, not worth the sponsorship' or the ops lead has decided the constraint you're solving isn't their real constraint. Ask directly: 'I've been talking a while — is this the part you care about, or should I jump somewhere else?' If that doesn't land, hand over control: 'do you want to drive? Tell me what to click.' If it's truly the wrong demo, say so and rebuild it: 'I think I'm showing you the wrong things — can I stop, take ten minutes to understand what actually matters, and come back Thursday?' Losing twenty minutes to save the deal is a good trade.