Letter 06

What Comes Next

Five letters ago, I told you I'd been on every side of this business — including the side that sold to you. Since then I've tried to be honest about all of it: how the software got built for someone else, why the companies best positioned to fix it can't, what it's actually like to try to build it yourself, and the three roads you're left choosing between — each one carrying the same permanent tax.

I saved the reason for all of it for last. Here's what we've been building.

The fourth path

Go back to the question I left you with. What if you could get the thing you actually want — technology shaped to your practice, that you own — without becoming a builder, without managing a developer, and without spending your career holding a pile of tools together?

That's the fourth path. It's what my team and I have spent the last two years building, and we call it AdvisorCRM Studio.

The idea is simple to say, even though it was hard to build. You describe what your practice needs in plain language — the way you'd explain it to a new hire. It assembles a working tool from real building blocks we host and maintain, shows you the result, and waits. You shape it until it fits the way you actually work. What you build is yours from the first day. You never touch code. You never manage a server.

Own the ground. We run the utilities.

I've said all series that you shouldn't be a renter in your own practice. Let me be precise about what I mean, because it's the whole heart of this.

Think about a property you own. You own the land, and you own everything you put on it — the house, the improvements, thirty years of work. You do not own the power lines, the water main, or the road out front. You never wanted to. Somebody runs those so you can get on with living there.

Your practice works the same way. The difference is that nobody has ever handed you the deed.

The ground is your book and the record underneath it — the people, everything they hold, every document, and the process you built around all of it. That's yours. So is the shape you give it. When you tell the system how your practice actually works, that shaping belongs to you too — not a setting we're holding on your behalf. It's portable. It comes with you if you ever leave, and what you build on it doesn't convey back to us when you go.

The utilities are the servers, the updates, the security, the compliance archive. We run those. You never wanted them, and you shouldn't have to.

That's the deal, and it's the one you'd actually want. You own the ground and everything you build on it. We keep the lights on. And it answers the question that ran through the last letter — *who does the upkeep when it breaks or the world changes?* We do. Without you handing over the one thing you'd want to keep.

Where it starts: the gap in your day

Here's how we think about your practice, and it has nothing to do with software.

Ask yourself what your day is *supposed* to look like. Now look at what it *actually* looks like. The distance between those two is where everything lives — the follow-up you meant to make, the client you meant to call, the thing that slipped because you were busy being the thing that holds your own tools together. The whole job is to close that gap: surface what matters, draft what's routine, and hand your team back the hours they now spend feeding software — so they can spend them on the relationships instead.

It drafts. You decide.

And because I've spent this whole series being honest with you about AI, I'm not going to stop at the finish line.

It drafts. It prepares. It surfaces things for your review. It does not act on its own. A human — you, or someone on your team — is always the one who approves and sends. That isn't something we bolted on to sound safe. It's how we built it from the first line of code, because you are the one who is liable for the advice you give. The AI should make you faster. It should never make a decision you didn't see.

This is real, and it's early

I want to be careful here, because I've asked you to trust me for five letters.

This isn't a slide. Real pieces are live today — the client system, the AI you can actually talk to, the enrichment that fills in a prospect before your first call. A handful of offices are using it right now, in beta. The full picture I've painted for you isn't finished, and I will always tell you the difference between what's working today and what's still the bet. My team and I are building it the honest way: I prototype, our engineers turn it into something real, and we ship a piece when it's ready — not before. The hard part was never the demo. It was the unglamorous foundation underneath — the guardrails, the human-in-the-loop review, the compliance built in from the start. That's what we spent two years on, because it's what makes AI something you can actually hand a client.

It's also priced the way your practice actually works — for the team, not for every seat. But that's a detail. The point is the path.

Come see it

If any of this sounds like the thing you've been wanting and couldn't quite name, I'd like to show you.

I'll be at Future Proof in September. We're opening early access to a small number of firms who want to help shape what this becomes. Come find me there, or get on the list — I'd rather have a real conversation than sell you anything.

That's the whole reason I wrote these letters. Not to talk you out of your tools, and not to talk you into mine. To make the case that you shouldn't be a renter in your own practice — and to show you there's finally another way to run one.

Let's build the thing you own.

Talk soon,

Ryan Borer Founder & CEO, AdvisorCRM