Selling Into Wealth Management: Compliance, Advisor Time, and the COO Who's Sat Through Forty Demos

A wealth management COO can sit through your entire demo, nod in the right places, ask two thoughtful questions, and then never respond to another email. Nothing went wrong on the call. The deal died somewhere you never had visibility into — a hallway conversation with the head of compliance, a lead advisor who said "I'm not learning another system," or a note in the custodian relationship that made your integration story a problem instead of a feature.

I have sold into enterprise and I have watched a lot of reps run at financial services accounts with the same demo they use everywhere else. It does not work, and the reason it does not work is not that wealth management buyers are slower or more risk averse in some vague cultural way. It is that the decision has more parties in it than your CRM has fields for, and most of those parties never take your call.

Here is how I would map it.

The room is bigger than the room

When a rep tells me "the COO is the decision maker," what they usually mean is "the COO is the only person who answered." Those are different statements. In a wealth management firm the COO is often the person who owns the outcome and controls the budget line, but the number of people who can stop the deal is larger, and several of them have veto power without ever needing to justify it.

The COO owns the problem, not always the decision

The COO is your best entry point because operational drag is the thing that keeps them up at night. Advisors complaining about double entry. Onboarding a household taking too long. Quarterly reporting turning into a fire drill. The COO has a felt sense of where the time goes, and they can usually name the three worst parts of the workflow without preparation.

What the COO cannot do is unilaterally approve a system that touches client data. They can champion it. They can fund it. They cannot clear it. If you treat the COO as a single-threaded close, you will get a verbal yes and then a six-week silence while the actual gates open behind the scenes. I wrote a whole breakdown of how to earn that first conversation in the financial services cold call script for getting a wealth management COO to give you 25 minutes, and the core of it is the same idea: you are not selling the COO, you are recruiting them.

The head of compliance can kill it without a meeting

This is the one that surprises reps. The head of compliance — sometimes a CCO, sometimes a dual-hat COO/CCO at smaller shops, sometimes an outsourced compliance consultant on retainer — can end your deal in a two-sentence email to the COO. They do not need to see your product. They do not need to take a call with you. They need one unresolved question about where data lives, who can see it, whether communications are captured, and whether the firm can produce a record if a regulator asks for it.

The mistake is treating compliance as a late-stage checkbox. By the time you are formally "in compliance review," the opinion has usually already formed. Someone forwarded your website. Someone looked at your trust page, or noticed you did not have one. Someone asked a peer at another firm whether they had heard of you.

So the move is to give the COO something to forward on day one. Not a security questionnaire response — a short, plain description of what data your product touches, where it is stored, who at your company can access it, what your audit logging looks like, and whether you have a SOC 2 report available under NDA. If you do not have that document, build it before your next call. It is the single highest-leverage asset in this segment and most vendors do not have one ready.

The lead advisor with political weight

Every firm has one. Sometimes it is a founding partner, sometimes it is the advisor with the largest book, sometimes it is just the person everyone else defers to in a meeting. This person does not care about your admin console. They care about whether their day gets worse.

Advisors have a reasonable and hard-earned skepticism about new software, because they have been through implementations that promised to save them time and instead added a login. If your buying process does not include a plan for how this advisor experiences the product, you are relying on the COO to win an internal argument you have given them no ammunition for.

Ask for them by name. "Who's the advisor most likely to push back on this? I'd rather hear their objection now than in month three." COOs respond well to that question because it signals you have done this before. And when you get that advisor on a call, do not demo. Ask what they do on a Monday morning and where the friction is.

The custodian relationship you did not know existed

Wealth management firms sit on top of custodians, and the custodian relationship shapes the technology stack more than most outside vendors realize. Data flows in a particular way. Certain integrations are pre-approved, certain ones require a conversation, and certain ones create a data-sharing question the firm does not want to open. There may also be preferred-vendor arrangements or platform tooling the firm already pays for indirectly.

You will not discover this by asking "what's your tech stack?" You discover it by asking how client data gets from the custodian into the systems the advisors actually use, and then listening for the words "we have to check" or "that goes through." Those phrases are your map.

"We're fiduciary" is a constraint, not a brush-off

When a rep hears "we have fiduciary obligations," they usually hear "no." It is not no. It is a specification, and it is one of the more useful things a prospect can tell you.

A fiduciary duty means the firm is legally obligated to act in the client's interest, and that obligation extends to how the firm handles client information and how it documents its own decisions. Practically, this shows up in three places that matter to you.

First, anything that touches client-facing recommendations has to be defensible after the fact. If your product surfaces a suggestion, generates a summary, or drafts a communication, someone at that firm has to be able to explain how it worked and show that a human reviewed it. "The model decided" is not an answer they can give.

Second, client communications generally need to be captured and retrievable. If your product creates a new channel where an advisor might say something to a client, and that channel is not captured, you have created a problem rather than solved one.

Third, the firm has to be able to justify the expense in terms that survive scrutiny. This is subtler, but it is why "it makes advisors more productive" lands better than "it increases AUM growth." Efficiency claims are safe. Performance claims invite questions the firm does not want to answer.

So when you hear the fiduciary line, the correct response is curiosity, not concession. "That makes sense — help me understand what that means for a tool like this. Where does the review step have to sit?" You will get a specification. Build to it.

The three things that get you a second meeting

I have watched a lot of first meetings in this segment, and the ones that convert to a second meeting almost always land the same three points. Not a feature tour. Three points.

Advisor minutes returned per week

The COO's currency is advisor time. Advisors are the revenue-generating asset and the scarcest resource in the building, and every hour an advisor spends on data entry, report assembly, or CRM hygiene is an hour they are not in front of a household.

Your job is to express your value in advisor minutes per week, and to do it with the prospect's own numbers rather than yours. Not "we save time." Something closer to: "You said onboarding a new household takes your advisors about half a day of their own hands-on time across the whole process, and you're bringing on a handful of households a month per advisor. If we take a chunk of that out, what does that free up?"

Notice I did not supply the numbers. They did. That is the whole trick. A number the COO says out loud is a number they will defend internally; a number you say is a number they will discount. Getting those numbers out of a prospect is most of the work of discovery, and I laid out the sequence I would use in the discovery call questions for financial services playbook.

Audit trail

Say the words. Early. Unprompted.

The audit trail is what turns your product from a compliance risk into a compliance asset, and it is the thing that lets the COO win the hallway conversation with the CCO. If your system logs who did what, when, and what the state of the record was before and after, and if that log is exportable, you have handed the firm something they currently do not have for whatever manual process you are replacing.

Most of the workflows you are displacing live in spreadsheets, email threads, and someone's memory. None of those produce a defensible record. Yours does. That is not a footnote in your demo — for the compliance stakeholder, it may be the entire value proposition. I go deeper on how to sequence this inside a live demo in the financial services product demo script, but the short version is that the audit trail should appear in the first third of the demo, not as a closing feature.

A migration story that does not touch client data during Q4

Q4 in a wealth management firm is not a good time to change anything. Year-end reporting, tax preparation, rebalancing, client review meetings, and whatever the firm's own fiscal calendar demands all stack up in the same window. A COO who is even mildly interested in your product will still say no if the implementation lands in that window.

The answer is to bring the sequencing before they ask. Something like: "The way I'd run this, we'd do configuration and admin setup in a sandbox with no client data at all. Advisors don't touch it until that's done. If your Q4 is locked, we start the data piece in January and you have a working environment to look at before then."

This does two things. It removes the timing objection before it hardens, and it signals that you understand their calendar. Very few vendors do. The ones who do get remembered.

The security review started before you think it did

Here is the part reps get wrong most consistently. You think the security review is a stage in your pipeline that begins when someone sends you a questionnaire. In reality it began the first time anyone at that firm typed your company name into a search bar.

By the time the formal review starts, the informal one has already produced a verdict. Did you have a trust page? Did your privacy policy read like it was written for a consumer app? Was there a SOC 2 or an ISO certification mentioned anywhere, or a clear statement that one is in progress with a date? Did your pricing page suggest you are a company that will still exist in three years? Is your data hosted somewhere the firm recognizes?

This is where a lot of otherwise strong deals quietly stall, because the objection never gets voiced. Nobody emails you to say "your security posture looks thin." They just stop replying.

What I would do about it: get ahead of the questionnaire by offering it. On the first or second call, say "most firms your size want to run us through a security review — I can send you our standard package now so your compliance lead can start looking whenever they want." You have just converted a hidden gate into a visible one, and you have given the COO a reason to loop in compliance early, when the answer to a question is a conversation rather than a rejection.

Also, ask who does the review. Some firms have an internal IT or security function. Many outsource to a consultant or an MSP. If it is outsourced, that consultant is a stakeholder you have not met, and they get paid to find problems. Ask for a call with them. It is an unusual request and it almost always gets granted.

Why this changes how you hold price

When you win the technical evaluation in wealth management, you will often face a procurement or COO-led pricing conversation that comes late and comes hard. The firm has spent weeks on diligence, they know they want it, and they also know that a vendor who has invested that much time is motivated to close.

The defense is that everything above becomes your justification. If the value was framed in advisor minutes, using the prospect's own numbers, the discount conversation is a conversation about how much advisor time they are willing to buy back rather than a conversation about your list price. If the audit trail is part of the value, you are not just a productivity tool, you are part of their compliance posture, and that is not a line item people enjoy cutting. I put the specific language for that moment in the financial services pricing negotiation script, and most of it depends on work you did in discovery, not on anything clever you say at the end.

What I would do next

If you are running at wealth management accounts right now, pick one live deal and write down every person who could stop it. Not everyone on the call — everyone in the building with a veto. COO, compliance, the loud advisor, the outsourced IT consultant, whatever the custodian relationship implies. Then write down what each one needs to hear and whether you have said it to them.

Most reps find at least two names they have never spoken to.

The other half of this is repetition. Compliance objections and "we're fiduciary" and "our advisors won't adopt it" are the kinds of things you handle badly the first four times you hear them live, and beautifully the fifth. That is what we built DrillCall for — running these conversations against a buyer who pushes back the way a real COO does, so the fifth rep is the one who shows up on the actual call. If you would rather burn your reps on practice than on pipeline, that is where I would start.