Fee-For-Service Enterprise

The “We’ll Just Build It Internally” Trap: A Cautionary Tale

2 min read

Jun 17, 2026 11:45:01 PM

This is a fictional story. But it’s based on real patterns we’ve seen repeatedly working with large RIAs and broker-dealers.

Meet Evan

Evan runs operations at a large broker-dealer supporting thousands of advisor-client relationships. He’s backed by a talented internal engineering team, but he’s currently under pressure from three directions at once:

Growth wants fee-for-service models to attract top talent.
Compliance wants tighter, centralized supervisory controls
Leadership wants more efficiency

So when fee-for-service billing became a strategic priority, his conclusion was predictable: “We can just build this internally.”

It felt practical. Controlled. Cost-efficient.

And at first… it was.

Phase 1: The Internal Build

The team builds a basic fee-for-service billing and payment tool. It reduces some manual processes. It checks the box. And, for a while, no one questions it.

Phase 2: Complexity Starts to Accumulate

Then, enterprise reality shows up. Approval layers, ongoing product changes, and multiple fee schedules across advisors and teams.

Each request felt reasonable. “We’ll just extend the system for this scenario.”

Engineering accommodates. Compliance signs off. Operations adapts. But over time, this “system” becomes a set of exceptions held together by custom logic, historical knowledge, and spreadsheets.

Phase 3: The Exam

Then comes a routine regulatory examination. The request is simple: “Provide a complete, end-to-end audit trail for fee authorization and supervisory oversight.”

This is where internal systems often get tested. Not on functionality, but on defensibility, consistency, and retrievability under scrutiny.

When Evan’s team tries to pull the data, they don't find a single, enterprise-grade system of record. Instead, they have to stitch together a fragmented paper trail of:

Approval workflows
Billing engine outputs
Custom scripts and logic layers
Email-based authorizations
Spreadsheets
Disconnected logs across systems

Everything exists. But nothing is unified.

Phase 4: The Remediation Reality

In this fictional (but highly representative) scenario, the firm doesn’t fail the exam outright. But it does receive findings that require remediation. Suddenly, the internal build becomes expensive.

The true cost of ownership becomes painfully clear as resources are diverted into:

High-priced compliance consultants to reconstruct workflows.
Legal review of legacy fee authorization structures.
Engineering capacity diverted away from the revenue-generating product roadmap to build regulatory patches.
Heightened supervisory oversight and grueling documentation requirements until remediation is fully signed off.

Phase 5: The Infrastructure Shift

At this point, leadership stops talking about “build vs. buy” in terms of software costs.

They ask:

How much core engineering capacity is permanently tied up maintaining a billing system?
How often are shifting compliance rules dragging our developers away from core business goals?
Are we building infrastructure that supports revenue growth… or consuming it?

Phase 6: The Conversation with Evan

After remediation, Evan walks into a leadership meeting to evaluate options. The internal system is running. But it’s heavy, fragile, and expensive to defend.

Someone asks the obvious question, “Should we keep building this internally?”

And Evan, who once championed the build, doesn’t fight it this time. He looks at the executive team and says what most teams eventually say: “Knowing what we know now, we shouldn’t have built this.”

The Real Takeaway

This story is fictional. But the pattern is not. Internal billing systems can succeed early. They always struggle later. And in most firm environments, the real risk isn’t the initial build. It’s the moment someone asks, “Can you prove this is consistent, secure, and fully traceable?”

Why AdvicePay Enterprise

AdvicePay Enterprise is built for firms that reach the same conclusion Evan did. You can build internally. But at the scale of a large firm, it becomes a permanent obligation across compliance, engineering, and operations.