Selling Into Wealth Management: The COO Buys, Compliance Vetoes, Advisors Decide Whether It Lives

Wealth management looks like an easy enterprise sale from the outside. It isn't a hospital system. It isn't a bank with nineteen layers of governance. A registered investment advisor with a few dozen advisors and a couple of billion in assets has maybe five people in the room, and you can get all five on one Zoom.

That is exactly why so many deals die there. Five people, three centers of gravity, and every one of them can stop you for a different reason.

The chief operating officer holds the budget and signs the paper. The chief compliance officer holds a veto and almost never uses it in a meeting — they use it in a two-line email after the meeting. And the advisors, who are not in your deal at all, decide six months later whether the thing lives or gets quietly ignored until renewal.

Selling software to wealth management firms means running all three at once. Here is how I would map it.

The three-body problem

In most B2B sales you have an economic buyer, a technical buyer, and a set of users, and the org chart tells you how much power each one has. In a wealth firm the org chart lies.

The COO is the economic buyer and usually your champion. They are the one who feels operational pain daily and the one who has a line item for fixing it. Good news.

The CCO reports somewhere near the CEO or the managing partner, sometimes to the COO, sometimes not, and sometimes the CCO is the COO wearing a second hat at a smaller shop. Their power is asymmetric. They cannot buy anything. They can end anything. And the mechanism is not a debate — it is one sentence in an email thread you are not on: "I'm not comfortable with where the client data sits." That's it. That's the whole objection handling window, and you missed it.

The advisors are the strange part. Structurally they are employees or partners. Economically most of them behave like small business owners renting space, brand, compliance cover, and back office from the firm. They have their own book. They have their own client relationships that would follow them out the door. They have opinions about their CRM the way a chef has opinions about knives. The firm can buy them software. The firm cannot really make them use it, because the leverage a COO has over a producing advisor who controls client relationships is thinner than the leverage they have over an operations associate.

So: one signer, one vetoer, and a population of users who effectively vote with their behavior after the money is spent. Your job is to sell all three, in that order, without letting any of them find out later that you skipped them.

What a wealth COO is actually measured on

If you want a wealth management COO to give you real time, you have to talk about what shows up in their quarterly partner meeting. It is a shorter list than you think.

Advisor capacity

Every growing RIA hits the same wall: the advisors who are good at gathering assets are spending their week on things that are not gathering assets. Account paperwork. Rebalancing exceptions. Building a review deck for a client meeting from four different systems. Chasing a signature.

The COO's core job is to push that work off the advisor and onto operations or onto software, so the advisor can carry more households without the service quality falling apart. When you hear a COO say "capacity," they mean households per advisor. That is the number.

If your product touches anything in that list, lead with it. Not with features. With the sentence "which parts of a client review does an advisor still assemble by hand here?"

Onboarding and account-opening time

Ask a COO how long it takes from a signed engagement letter to funded accounts and you will get either a proud answer or a wince. Both are useful. This cycle is visible to the client at the worst possible moment — right after they decided to trust the firm with their money — and it is usually a mess of custodial forms, NIGO paperwork coming back for correction, ACAT transfers sitting in limbo, and someone re-keying the same household data into the CRM, the planning tool, and the portfolio system.

COOs remember the ugly cases by name. Get them talking about the last transfer that took months and you will learn more about their stack in five minutes than a discovery template would surface in thirty.

AUM per advisor and per operations head

The economics of an RIA are simple and brutal. Revenue is a fee on assets. Cost is mostly people. So the two ratios that decide margin are assets per advisor and assets per non-advisor employee. Every technology purchase is implicitly a bet on one of those ratios.

You do not need to know their numbers. You need to ask which ratio the purchase is supposed to move, because a COO who has not decided that has not really built the business case yet, and you are going to lose to "we'll revisit next year."

Audit exposure

This is the one salespeople underweight. An SEC-registered advisor lives under a compliance program rule that requires written policies, an annual review, and a designated CCO, plus books-and-records obligations that dictate what has to be retained and producible. A firm with a broker-dealer affiliate carries supervision and retention requirements on top of that. A deficiency letter after an exam is a real event with real remediation cost and real reputational drag when a large prospect asks about it in due diligence.

So when the COO is evaluating your product, one of the silent criteria is: does this create a new place where records live, a new channel where client communication happens, or a new surface where something can go wrong that nobody is supervising? If the answer is yes and you have not addressed it, you have handed the CCO the grenade yourself.

That is the frame I would use to earn the first meeting — capacity, onboarding, ratios, exposure — and it is the same frame behind the financial services cold call script for getting a wealth management COO to give you 25 minutes. Nobody opens the calendar for a platform. They open it for a bottleneck they already complain about.

Bring compliance in early or they end you late

The single biggest change I would make to how most reps run these deals: stop treating the CCO as a hurdle at the end and start treating them as a second champion at the beginning.

What the CCO is actually afraid of

Not your product. The CCO is afraid of an exam question they cannot answer.

They are thinking about where client personally identifiable information will be stored and who can see it. Whether anything your product generates counts as a record that must be retained and produced on request. Whether your product creates a communication channel with clients that now has to be captured and supervised. Whether anything you output could be construed as advertising under the marketing rule — performance displays, projections, testimonial-adjacent language. Whether you are a new vendor that has to go into their vendor due diligence program with a security review, a SOC 2 report, and a contract that survives a subpoena. And whether, if you disappear tomorrow, the firm can still produce its records.

Every one of those has a defensible answer or it doesn't. If it does, you want the CCO to hear it from you, in a scheduled fifteen minutes, before they hear a garbled version of it secondhand from the COO.

How I would actually do it

On the discovery call, once the COO has described the problem, I would say something close to this:

"Two things before we go further. First — who's your CCO, and would you rather I bring them in now or after we've scoped it? My honest preference is now. Every deal I've seen stall in this space stalled because compliance saw it for the first time at the contract stage and had to say no on principle. Second — is there a vendor due diligence packet you send out? Send it to me today and I'll have it back before our next call."

That does three things. It tells the COO you have done this before. It gets the security questionnaire started weeks earlier than it otherwise would. And it reframes the CCO from gatekeeper to co-designer, which is the only role in which a compliance officer will ever help you.

When you do get the CCO on the phone, do not demo. Ask what their last exam focused on. Ask what they had to remediate. Ask what their policy says about approving new vendors that touch client data. Then map your answers onto their language, not yours. "Records generated in our system are exportable in bulk in a format your archive can ingest, and here's the retention configuration" beats "we're enterprise-grade" every single time. The structure for that conversation — separating what the COO cares about from what the CCO cares about inside one 25-minute block — is what the discovery call playbook for financial services buyers is built around.

One more thing. Ask the CCO directly: "If you were going to block this, what would the reason be?" Most of them will tell you. Compliance officers are not coy; they are just usually not asked.

Advisor adoption is the entire renewal conversation

Here is the failure mode that costs the most money, and it happens after you have already been paid.

The COO buys. Implementation goes fine. Training happens on a Tuesday. Six months later, a third of the advisors are using it, the loudest producer at the firm is still doing it the old way and telling everyone the new system is slower, and when renewal comes around the COO cannot defend the line item because the ratios never moved.

You did not lose that renewal at renewal. You lost it in the sales cycle when you never talked to an advisor.

So talk to advisors. Ask the COO for two: the one who will try anything, and the one who hates change. The second one is more valuable. Get them on a call and do not sell — ask them to walk you through the first hour of their Monday and the last hour before a client meeting. You will find out where your product actually inserts itself and whether it adds a step or removes one.

Because that is the whole test. An advisor will adopt a tool that removes a step from something they already do. They will not adopt a tool that adds a step in exchange for organizational benefit they do not personally receive. Reporting dashboards for management are a step added. Pre-populated client review packets are a step removed. Same product, different pitch, completely different adoption curve.

This changes how you demo. A demo built for the COO shows oversight, consistency, and control. A demo built for an advisor shows their Tuesday getting shorter. If you only have one session, you have to do both and be explicit about the switch — "this next part is for the folks who'll be in it every day" — which is the part of the product demo script for wealth management buyers that most reps skip and then wonder why the room went quiet.

And get an adoption commitment written into the deal. Named pilot advisors, a date, a defined success measure the COO picks. Not because it protects you contractually — it barely does — but because it forces the COO to admit out loud whether they can actually get their advisors to change behavior. If they cannot, better to learn that before you discount.

Custodians and data integrations set your timeline

Your implementation date is not yours. It belongs to whoever holds the data.

Most RIAs custody with one of a handful of firms and run some combination of a portfolio accounting or performance system, a planning tool, a CRM, and possibly a rebalancer on top. Data flows between those on file drops and nightly reconciliation, and the reconciliation is the load-bearing wall. If your product needs positions, transactions, or household relationships, you are getting them from that stack, and you are getting them on that stack's schedule.

The practical consequences, which you should raise before the COO discovers them:

Integrations that require custodian-side enablement have their own approval and queue, and it is not a queue you can escalate. Data you get overnight is data that is stale intraday, so if your value proposition implies real-time, say so now. Household and account structures are modeled differently in every system, and mapping them is where implementations actually burn weeks. Somebody at the firm has to own the data cleanup, and if you do not name that person during the sales cycle, the answer is going to be "the operations associate who is already underwater."

Say all of it out loud. A COO who has been through a bad conversion — and most have — will trust you more for naming the risk than for promising a two-week go-live. It also protects your price. When the timeline is honest and the scope is understood, the late-stage "we need you to come down because implementation is bigger than we thought" move loses its footing, and you can hold your number the way the pricing negotiation script for wealth management deals lays out.

The diligence questions you should answer cold

You will be asked these. Know them without reaching for a slide.

Where does client data live, in what region, and who at your company can access it? Do you hold a current SOC 2 Type II, and can you send the report under NDA today? What is your incident notification commitment and is it in the contract or the marketing page? What happens to their data on termination — format, timeline, cost? Are you a subprocessor of anyone else, and can you name them? Do you have references at firms of similar size and custodial setup, and are those references advisors or just the COO who bought it? How does the firm supervise activity in your system, and can they export it for an exam? What is your uptime commitment and what is the remedy when you miss it?

If your answer to any of these is "I'll check with the team," you are fine — once. Twice and the CCO writes you off as a startup that has not thought about this, and the CCO's opinion of your seriousness travels straight to the COO.

What I would do next

If I were building a rep for this market, I would not start with product training. I would make them run the CCO conversation twenty times before they ever ran it live, because that is the call with the shortest window and the highest cost of a stumble, and it is the one nobody practices. Same for the advisor conversation, where the failure is subtler — you sound like a vendor instead of someone who understands that the person on the other end runs their own business. Reps get good at the COO call naturally because they have it constantly. They stay bad at the other two forever. That gap is the reason I built DrillCall: so a rep can go ten rounds with a skeptical compliance officer on a Wednesday afternoon and be ready for the real one on Thursday.

The firms are small enough that you can meet everyone who matters. Almost nobody does. Meet all three, in order, and the deal stops being a coin flip.