Selling Into Wealth Management: The COO, the Compliance Shadow and the Advisor Who Won't Change Tools

13 min read

In wealth management deals the COO signs, compliance vetoes, and advisors quietly refuse to adopt — here is how to sell to all three before procurement shows up.

Three people, one deal, and only one of them will tell you the truth

Here is the pattern I have watched play out over and over when reps go after wealth management firms. You get a good first call with the COO. Genuinely good. She takes notes, she pulls up her calendar without being asked, she says something like "this is exactly the kind of thing we've been talking about internally." You send the recap. You get a second meeting. Somewhere in week three a name you have never heard appears on the invite, the meeting gets rescheduled twice, and then the whole thing goes quiet in a way that feels less like a no and more like a building that stopped answering the door.

What happened is that the deal hit the other two people. Selling into wealth management firms means selling into a structure where the person who signs, the person who can veto, and the people who have to actually use the thing are three different constituencies with three different incentives, and only one of them is on your calls.

The COO signs. Compliance can kill it without ever attending a demo. And the advisors — who produce the revenue, who own the client relationships, and who in most firms have more real leverage than anyone with an operations title — can simply decline to log in, and there is very little anyone can do about it. If you do not build a plan for all three before procurement gets involved, you are running a deal that looks alive right up until the moment it isn't.

What the COO is actually buying

The COO is the one who will take your call, and it is worth understanding why. Operations leadership at an advisory firm sits at the intersection of every complaint in the building. Advisors complain that onboarding a new household takes too long and makes them look amateurish in front of a client who just moved money. The founder complains that the firm can't absorb the next acquisition without hiring. The CCO complains that nobody documents anything. The custodian changed a form. The CRM and the planning tool disagree about a client's address.

So the COO is not buying software. She is buying the removal of a specific recurring failure that has her name on it. That is a much narrower purchase than the one on your slide.

The mistake I see reps make is pitching the COO on the whole platform because the COO has the broadest view. Wrong direction. The broad view is exactly why she cannot get anything approved — a wide pitch gives her a wide problem to socialize, and wide problems die in committee. Narrow it. "When a new client comes over from another firm, how many people touch that account before it's fully open, and where does it usually stall?" That question gets you a story. The story gets you a champion, because now she has one thing to fight for instead of a category.

And she does have to fight for it. In most firms of this size the COO controls process, not the P&L. She can spend within a line item and she can recommend, but a new platform means going to a founder or a managing partner who has been doing this since before the tools existed and has a working theory that most software is a tax. I have had more of these deals stall at the "she has to ask her partner" step than at any technical objection. Ask her early, directly, and without apology: who else signs, and what do they usually say no to? A good COO will tell you. She has been through this before.

The compliance shadow

The Chief Compliance Officer is the strangest stakeholder in this deal because in a lot of firms the role is worn part-time by someone who already has another job. It might be the COO herself. It might be a partner. It might be an outsourced firm that shows up on a quarterly cadence and has no idea who you are.

What you need to internalize is that compliance is almost never a buyer and almost always a veto. Nobody in that seat gets promoted for approving your vendor. They get fired for approving the one that caused a data incident or a books-and-records problem in an examination. That asymmetry explains every behavior you will find frustrating: the sixty-question security questionnaire for a tool that touches no client data, the insistence on knowing where your sub-processors are, the refusal to move faster because you have a quarter to close.

Stop treating this as an obstacle to route around and start treating it as an approval you can pre-earn. The single highest-leverage thing a rep can do in this segment is assemble the compliance packet before anyone asks for it — your SOC 2 report, your data flow diagram, your retention and deletion policy, your sub-processor list, your business continuity summary, your cyber insurance certificate, your standard DPA — and hand it to the COO in week one with a line like: "Before you spend political capital on this, here's everything your CCO is going to ask for. If there's a dealbreaker in here I'd rather we find it now than in month two."

That one move does three things. It makes you the easiest vendor in the pipeline to say yes to. It surfaces the actual dealbreaker early, which is worth more than a month of optimism. And it tells the COO you have done this before, which in financial services is most of what credibility is.

The other thing to understand is scope creep in reverse. Compliance rarely says no outright. They say "we'd need to be able to archive that," or "can advisors send that to a client without review?" Every one of those is a feature question wearing a risk costume. Answer it as a risk question. "Everything sent through the system is captured and exportable in the format your archiving vendor takes" lands. "Yes, we have an export feature" does not.

The advisor who won't change tools

Now the part most reps get wrong entirely.

An advisor's book is the asset. Their compensation is tied to production. Their calendar is full of client meetings that generate revenue and empty of anything that doesn't. When you introduce a new system, you are asking a revenue producer to spend billable attention learning something in exchange for a benefit that mostly accrues to the firm. From their chair, that is a bad trade, and they are correct.

Advisors also have leverage that operations staff do not. In a lot of firms they can leave and take clients with them. Nobody in the building is going to force a top producer onto a platform they have publicly grumbled about. So the veto is quiet. There is no meeting where the advisors reject you. There is just an adoption number that never moves, a renewal that doesn't happen, and a reference call in eighteen months where the COO says "the product was fine, we just never got the team on it."

The implication for how you sell: you have to make at least one advisor visibly better off, in their own economics, and you have to do it before the contract is signed.

Advisors care about three things you can actually affect. Whether they look good in front of a client. Whether they get time back that they can put into prospecting or servicing. And whether the thing that currently makes them look bad — the paperwork that bounces, the transfer that takes weeks, the plan that has to be rebuilt because the data didn't sync — stops happening. Notice that none of those is "efficiency." All of them are status and revenue.

So ask the COO for a name. "Who's your most skeptical senior advisor?" Then ask to meet them, and do not demo. Ask what part of their week they would pay out of their own pocket to never do again. In my experience, when you put that question to a producer who has been ignored by every vendor that came through the door, you get a very specific answer and a very unexpected ally.

Why "efficiency" is a weak pitch here

Efficiency pitches assume the buyer converts saved hours into avoided cost. That works in a business with a large hourly workforce and a hiring plan you can freeze. It does not work here, because the cost base of an advisory firm is people the firm has no intention of firing. Advisors are the product. Client service associates are scarce and painful to replace. Nobody is going to buy your platform, cut a headcount, and hand you the delta.

When you say "we'll save your team hours a week," the COO hears an unfalsifiable claim about time that will be reabsorbed by other work the moment it appears. She has heard it from every vendor. It does not survive contact with a founder who wants to know what the firm gets.

What travels instead is capacity, speed, and exposure. Same hours, more households. Same team, faster onboarding. Same operations, less audit surface. Those map to things the firm's leadership already measures and already argues about, which means your champion can carry them into a partner meeting without translating.

The business case in the three currencies that matter

AUM growth. This is the only number the whole firm agrees on. Revenue is a function of assets under management, and assets grow through market performance, additional deposits from existing clients, referrals, and new households. You cannot influence markets. You can influence how many new households a given advisor can bring on without the firm's operations breaking, and how quickly a referral turns into funded accounts. Frame your business case as capacity for growth the firm has already decided it wants — most of these firms have an explicit growth plan, and most of them are quietly worried that ops cannot absorb it. Ask the COO what the firm's growth target is and what breaks first if they hit it. That conversation is worth more than any ROI calculator.

Client onboarding time. The window between a client saying yes and the assets actually landing is the most dangerous period in the relationship. The client is comparing you to the firm they just left. Every form that bounces back is a small withdrawal from the trust account. Advisors feel this personally, which is what makes onboarding one of the few business cases that gets the COO, the founder, and the producers nodding at the same time. Do not claim a number you cannot support. Ask them to walk you through their last three onboardings, in detail, and let their own story be the evidence.

Audit exposure. This is the one reps skip because it feels like compliance's problem. It is not — it is a real cost with a real owner. Examination prep pulls senior people off client work for weeks. A deficiency letter means remediation on someone's calendar. Anything that makes the firm's records easier to produce and its supervision easier to demonstrate is money, it just shows up as avoided chaos rather than a line item. When you frame your product as reducing what the firm has to reconstruct under deadline, the CCO stops being a veto and starts being a co-sponsor.

If you want the actual question sequence for pulling these out in a first conversation, I laid out how I run the twenty-five minute discovery call with a wealth management buyer in a separate playbook, because the ordering matters more than the questions do.

The diligence gauntlet

Assume the process. Vendor questionnaire, security review, sometimes a call with an outsourced compliance consultant who bills by the hour and will not be rushed. Legal redlines around data ownership, breach notification, and right-to-audit. If the firm is part of a broker-dealer or has an institutional custodian relationship, add another layer.

The way to survive this is not to be clever, it is to be boring and prepared. Three habits:

Give the timeline to your champion in writing, with the steps named, before she asks. COOs live in dependency chains. Handing her a sequence she can forward is a gift.

Never let a diligence item travel through more than one person. If the CCO has a question about encryption, get the CCO on a call with someone technical from your side for fifteen minutes. Email relay through a champion adds a week and loses fidelity every hop.

And keep the deal warm while diligence runs, because the risk is not rejection, it is decay. Priorities change, a partner retires, an acquisition eats the quarter. Schedule the implementation kickoff conditionally while the paperwork is moving. It sounds presumptuous. It is actually the thing that keeps the deal on someone's calendar.

Build the adoption plan into the deal

Here is the move that separates reps who close this segment from reps who spend a year in it.

Before the contract goes to procurement, you and the COO write a one-page adoption plan together. Who goes first, and why them. What that first group has to see in the first two weeks to keep going. Who announces it internally and in what words. What the firm does if a senior advisor opts out. When you and the COO look at usage together, and what happens if it's flat.

Write it as a document you both sign, not a slide. You are not doing this to be thorough. You are doing it because the conversation itself is the qualification. A COO who engages seriously with "what do we do if Dave refuses" is a COO who has thought about internal politics and intends to spend capital on this. A COO who waves it off with "they'll be fine, we'll mandate it" is telling you she has never successfully mandated anything to a producer, and your renewal is already in trouble.

This is also why the demo has to be built around the advisor's day, not the operations team's dashboard. I go deeper on structuring that in the product demo script for wealth management buyers, but the short version is that if the first screen you show is an admin console, you have already lost the room you actually need.

The two questions that predict whether this firm ever buys anything

After enough of these calls you learn that the qualifying signal is not budget, timing, or enthusiasm. It is change history. Two questions get you there.

"What's the last tool your advisors changed how they work for — and what made them do it?"

Listen for whether an answer exists at all. If the COO can name a system, a date, and a reason, you are in a firm that is capable of adopting things, and she has just handed you the exact mechanism that works there. Maybe a founder made it personal. Maybe one advisor tried it, made more money, and the rest followed. Maybe the custodian forced it. Whatever it was, run your play the same way.

If the answer is a pause, or "honestly, not much has changed," or a story about a platform they bought and never rolled out, you have learned something worth more than a demo. That firm does not have a change mechanism. You can still sell them, but you are selling a change-management project with software attached, and you should price the effort accordingly and forecast it late.

"If nothing changes here for the next year, what breaks first?"

This is a cost-of-inaction question, and the reason it works is that it cannot be answered with enthusiasm. A firm with a real problem answers immediately and specifically — the ops lead is going to quit, the growth plan misses, the next exam is going to hurt, the acquisition won't integrate. A firm without one gives you an abstraction: "we'd just be less efficient, I guess." That answer means there is no forcing function, which means there is no deadline, which means your deal has no reason to close this quarter or any quarter.

Ask both. Ask them early, ideally on the first call, which is also why I spend so much of the cold call itself buying the right kind of twenty-five minutes rather than pitching. A firm that answers both well is worth six months of your attention. A firm that answers both badly is a pipeline decoration, and the kindest thing you can do for your own forecast is to say so out loud.

What I'd do next

If I were ramping into this segment tomorrow, I would not start by reading about RIAs. I would take those two questions, plus the compliance packet line and the "who's your most skeptical senior advisor" ask, and I would run them out loud until they stopped sounding like a script. That is the whole gap for most reps — they know the theory and they have never said the words at speed to someone who interrupts. Practicing that against a live objection is exactly what we built DrillCall for, and it is what I would do with my first week before I burned a single real COO conversation learning it.

The firms in this space are not hard to sell because they are sophisticated. They are hard to sell because the signature, the veto, and the adoption live in three different people, and only one of them will ever be on your calendar unless you go get the other two.

Practise these calls

The playbooks behind this post — a scripted opener, the objections you will actually hear, and an AI buyer to run it against.

About the author

Timothy Yang

Founder & CEO, DrillCall

I build products by getting on the phone. Four businesses built and exited, including a micro-task marketplace with 170,000+ users, and the common thread in every one was the same: nothing moved until I picked up the phone and sold. Cold outreach, discovery calls, closing. The unglamorous work that actually creates revenue. Right now I am building DrillCall, an AI-powered voice training platform where sales reps practice live calls against realistic AI buyer personas, 310 of them across 31 industries, and get a scorecard after every call. Think flight simulator, but for cold calls. I also run Vibe Coding Club, a community of over 3,500 builders shipping products with AI, and I have spent time inside AWS and Dell, so I have seen how enterprise sales machines work from the inside as well as from the founder seat. What I care about: expected value thinking, fast iteration, and talking to customers before writing a line of code.

← All posts