Selling Into Financial Services: The COO Who's Really Buying Protection From the Regulator

A wealth management COO does not lie awake thinking about your integration roadmap. I want to open with that because almost every rep I have watched sell into financial services builds their entire call around the thing the buyer thinks about least.

Here is the actual ranking inside that person's head. First, a regulator finds something. Second, a producing advisor team walks out the door and takes their book with them. Third, a client complaint escalates into something a journalist can write about. Your product features are fourth, and fourth is a long way down.

If you sell software to wealth management firms and you cannot speak fluently to the first three, you are going to get polite calls that go nowhere. The COO will nod, say it looks interesting, and ask you to send information. That is not an objection. That is a person deciding you are not relevant to the things they are actually paid to prevent.

The three fears, in order

One: the regulator finds something

Examiners show up. They ask for records. The firm produces them, or the firm explains why it cannot, and the second answer is the one that turns a routine exam into a deficiency letter, and a deficiency letter into a remediation project that eats the COO's year.

What matters here is not that the firm is doing something wrong. Most of them are not. What matters is whether they can demonstrate they are doing it right, on demand, with a timestamp. Supervision that happened but was not documented did not happen. A communication that was archived in three places but cannot be retrieved by a single search is, functionally, not archived.

So when you hear a COO say "we need better visibility," translate it. They mean: when someone asks me to prove it, I want to be able to prove it in an afternoon instead of a month.

Two: the advisor team walks

In an advisor-led firm, the producers have leverage. They brought the assets. Many of them could take those assets somewhere else, and every competitor in the region is already calling them. The COO's job is to give advisors reasons to stay that are not just money — better support, less administrative drag, faster onboarding for their new clients, technology that does not embarrass them in front of a prospect.

This is where advisor productivity actually lives as a buying motive. It is not a cost-savings story. It is a retention story. A COO who tells you "our advisors hate the current onboarding process" is not complaining about efficiency. They are telling you a recruiter is going to use that against them.

Three: the complaint that becomes a headline

Every firm has complaints. The fear is the one that gets amplified — a vulnerable client, a bad outcome, a paper trail that looks worse than the facts, and suddenly the firm's name is attached to a story that follows it into every prospect meeting for two years.

This fear is quieter than the other two and rarely stated out loud. But it is why COOs care disproportionately about anything touching client communications, suitability documentation, and how quickly the firm can reconstruct what happened.

Your features rank fourth, and that is fine

I am not telling you features do not matter. They matter in the demo, they matter in diligence, and they matter to the person who will administer the thing. They just do not open the door.

The mistake is leading with capability and hoping the buyer does the translation work for you. They will not. They are busy, they have seen a lot of vendors, and the ones who make them do the translating get filed under "send me something."

Your job is to arrive with the translation already done.

Translating a generic pitch into their language

Take whatever you sell and run it through four filters. If it does not survive at least one of them, you have a positioning problem, not a prospecting problem.

Supervision. Who reviews what, how often, and how is that review evidenced? If your product creates a record of a review that previously lived in someone's inbox, that is a supervision story and you should say the word supervision out loud.

Books and records. Can the firm produce it, search it, retain it for the required period, and hand it to an examiner without a fire drill? Anything that reduces the number of systems a record has to be assembled from is a books-and-records story.

Advisor productivity. Not "saves time." Specifically: does it remove administrative work from the person who generates revenue and hand it to a system or to support staff? A COO will trade a lot for that, because it directly addresses fear number two.

Client onboarding cycle time. How long from "the client says yes" to "the account is funded and the advisor can trade"? Every firm I have encountered has a number in mind here and hates it. Onboarding is where compliance friction and client experience collide, which means it touches all three fears at once. If your product does anything to that timeline, lead with it.

Here is the difference in practice. Generic version: "We help teams centralize their client data and automate manual workflows." That could be sold to a dentist.

Translated version: "When an examiner asks you to show the supervisory review on a specific account opening from fourteen months ago, how long does that take you today? I ask because that reconstruction is usually the thing that eats a compliance team's week, and it is the piece we take off the table."

Same product. One of them earns a second call.

The single best first-call question

Ask about last year's audit findings.

Not "what are your priorities this year." Not "what keeps you up at night," which is a question that has been asked so many times it now functions as a signal that you have nothing to say. Ask: what came up in your last exam or internal audit that you are still cleaning up?

Three things happen when you ask this well.

The first is that you find the funded problem. Remediation work has a budget attached and a deadline that somebody external set. That is the most purchasable pain in the entire firm, because the COO does not have to build a business case for it. The case was built by the examiner.

The second is that you learn where the firm is thin. If the finding was about documentation of supervisory review, the firm has a supervision gap and probably a records gap behind it. If the finding was about marketing materials or client communications, there is an archiving and approval story. The finding tells you which of the three fears is currently loudest.

The third is that you separate yourself from every other vendor who called that week. Asking about findings signals that you understand the firm operates under examination and that you are not going to waste their time with a discovery script built for a SaaS company selling to marketing.

A caution on delivery. This question can land as intrusive if you throw it out cold. Earn it with a sentence of context first: "Most of the COOs I talk to are still working through something from their last exam — is that true for you, or did you come out clean?" The escape hatch at the end matters. It gives them a graceful way to say no, and half the time the way they say no tells you what you needed anyway.

The whole opening sequence — getting past the gatekeeper, earning the first twenty seconds, and setting up this question so it does not feel like an interrogation — is worth rehearsing before you dial, and I have written out the exact structure I would use in the financial services cold call script for wealth management COOs.

Who actually owns budget in an advisor-led firm

This is where deals die quietly.

In an advisor-led firm, the org chart is a suggestion. The COO runs operations and often owns the technology decision on paper. But the producing advisors — especially the largest teams — have informal veto power over anything that touches their workflow. And in many independent and hybrid structures, some technology spend sits at the advisor or office level rather than the firm level.

So you have to qualify three separate things, and they are not the same person.

Who feels the pain. Usually operations or compliance. They are the ones doing the reconstruction work at eleven at night before an exam.

Who signs. Often the COO, sometimes a CFO, sometimes a managing partner who is also a producing advisor. In smaller firms these collapse into one person. In larger ones, they do not.

Who can kill it. The biggest advisor team. If your product changes how they work and they were not consulted, they will find a reason it will not work, and the COO will not spend political capital fighting them over a vendor.

The qualifying question I would ask, plainly: "When you have brought in something that changes how advisors work day to day, how has that decision usually gone? Who did you have to bring along?" You are not asking for the org chart. You are asking for the last real decision's history, which is far more predictive.

And ask about the advisor council or technology committee, because many firms have one. If it exists, it is your real buying committee, and the COO is your sponsor rather than your buyer. Sponsors need ammunition. Give them the language they will use in a room you are not in.

Most of this surfacing happens in discovery, and it is genuinely hard to do in one call without turning it into an interrogation, which is why I sequence the questions deliberately in the discovery playbook for wealth management buyers.

The gauntlet that starts the second they say yes

Here is the part nobody warns new reps about. "Yes" is not the finish line in financial services. It is the starting gun for a process that will test whether you actually understand this market.

Information security review

Expect a security questionnaire, and expect it to be long. Where is data hosted, who can access it, how is it encrypted at rest and in transit, what is your incident response process, do you have a current SOC 2 report, when was your last penetration test, who are your subprocessors. If you cannot answer these, you will burn weeks going back and forth with your own engineering team while the deal cools.

Get your security package assembled before you need it. Know what you have, know what you do not, and be honest about the gaps. A vendor who says "we do not have that yet, here is what we do instead and here is the timeline" survives. A vendor who bluffs and gets caught in the review does not.

Vendor risk and third-party oversight

Firms are responsible for the vendors they use. That means a due diligence file: financial stability, business continuity plan, insurance certificates, references, and an assessment of what happens to the firm if you go out of business or get acquired. Some firms will ask for your financials. If you are early-stage, that is an awkward conversation, and it is better to have it on your terms than to have it surface in month three.

Legal redlines

Your standard MSA will come back marked up. The recurring fights are around data ownership, the right to audit, breach notification timelines, limitation of liability, and what happens to the firm's data on termination. Regulated buyers push harder on all of these than a typical commercial buyer, and they are usually right to.

The practical advice: find out early which clauses your company will never move on, and surface them yourself rather than letting legal discover them. Nothing kills momentum like a sponsor who learns in week six that you were never going to accept unlimited liability.

The committee that meets monthly

Many firms route new vendors through a compliance or risk committee. If that committee meets monthly and you miss the agenda deadline by two days, you have lost a month. Ask about it early: "Is there a committee this has to go through, and when does it meet?" That single question will make your forecast dramatically more honest.

Build the timeline backwards from the committee date. Tell your sponsor what you need from them and when. Do the work of making it easy for them to get you on the agenda, because they have a day job and your deal is not it.

Run the demo against the fears, not the feature list

When you finally get to the demo, the temptation is to show everything, because diligence has made you paranoid about surprises. Resist it. Show the supervision trail. Show the record retrieval. Show the onboarding path an advisor would actually walk. Then stop, and spend the remaining time on the questions the committee is going to ask, because your sponsor needs to be able to answer those without you.

A demo in this market is not a product tour, it is a rehearsal for an internal conversation, and I lay out that structure in the demo script for wealth management buyers.

What I would do this week

Pick five wealth management firms in your patch. Look up their regulatory filings and disclosures, which are public. Find something specific — a recent change, a growth pattern, an entry in the disciplinary history if there is one. Then write one opening line per firm that connects what you sell to supervision, records, advisor retention, or onboarding time.

Then say them out loud until they stop sounding like a script. This is the part most reps skip, and it is why the first call goes badly and the confidence never builds. If you want to rehearse the audit-findings question and the budget-ownership sequence against a buyer who pushes back the way a real COO does, that is exactly what I built DrillCall for — you can run the financial services scenarios until the awkward questions come out clean, and then go spend your live calls on the conversation instead of on remembering your own lines.

The COO is not buying software. They are buying a slightly quieter year. Sell that.