What 28 Years in Real Estate Taught Me About Technology That Flows

Host: Welcome to Real Stories with Buddy Blake. Today we're getting into what twenty-eight years in real estate taught Buddy about technology that actually flows. Buddy, welcome back. And I have to say, I love that you start this one with the old Mac versus Windows argument.

Buddy Blake: Thanks for having me. Yeah, so look, I'm not here to pick a side. People have argued about that for decades. But there's a lesson in it. Apple designs its computers and its operating system together, around a fairly small number of configurations. Windows has to work with hardware from a whole lot of manufacturers. So a Mac often feels simpler, and a Windows machine gives you a ton of choices.

Host: Okay, but that's not you saying one is better, right?

Buddy Blake: Right, exactly. Plenty of Windows computers perform beautifully. And Apple doesn't build every component itself. The point isn't that one never fails. It's about coordinated design, compatibility, and who's accountable when something doesn't work.

Host: Okay, so how do you get from computers to real estate? Because I know you've got a house analogy coming.

Buddy Blake: I do, because real estate people understand houses better than computers. You can keep adding rooms. That doesn't mean the house flows. A well-planned home starts with a coordinated design. The foundation, the framing, the plumbing, the electrical capacity, heating and cooling, the layout. All of it has to support what the house is meant to do.

Host: And then there's the other kind of house. The one that grew one afterthought at a time.

Buddy Blake: Yep. Another room, another bathroom, another floor, another electrical panel, another connection run through the wall. And every addition solved a problem that was real when somebody built it. But over time the house gets harder to operate and harder to maintain. Now to be fair, well-planned additions work fine. Different specialists and outside components can work together beautifully. The question is whether somebody took responsibility for the whole design.

Host: I love that. So the experience you see on the surface depends on the planning underneath.

Buddy Blake: That's it. That's the whole thing.

Host: Okay so let's bring it home. How do agents end up with a house that doesn't flow?

Buddy Blake: Look at how most of us build our businesses. We add a website, then a CRM. Then texting, email marketing, lead routing, content tools, AI tools, automation, reporting. And each purchase made sense on the day we bought it. But then we become the plumbing. We're the ones moving information from one system to another, fixing the connections that break, reconciling records that don't match, and trying to remember where everything lives.

Host: Oh wow, yeah. We become the plumbing. That's painfully accurate. And I'm guessing the cost isn't just the monthly subscriptions.

Buddy Blake: Not even close. It shows up as duplicate entry, customer details scattered across tools, training time, troubleshooting, missed follow-up. And honestly, the mental strain of carrying all of it in your head. That one's real. And one vendor or one login doesn't automatically mean a coordinated system. Separate products can work great together when somebody thoughtfully integrated them. So the test I use is simple: does this make it easier to serve people, or does it give me another thing to manage?

Host: That's a good gut check. Can you give us an example of what that looks like for a customer?

Buddy Blake: Sure, and I want to be clear, this is a hypothetical, not a real client. Say someone browses a few homes online and asks a question by text. Weeks later they call the office about selling. In a fragmented setup, the person who answers may have no idea about the text, the searches, or the timing. So the customer ends up repeating everything. In a coordinated setup, whoever picks up has the context and can focus on what the person actually needs. And nobody had to become a software expert for that to happen.

Host: Right. The customer just feels taken care of. Now you've also seen this stuff from the inside, haven't you? With the developers?

Buddy Blake: I have, and I've been lucky that way. I was involved early in BoomTown's development, when people from the company would come to my office and watch agents use the system. I have experience with Guaranteed Sale System. And I've spent a good amount of time working with Sierra Interactive's development team. Watching working agents matters, because something that looks logical in a demo can be cumbersome in a real day. And real days have appointments, interruptions, follow-up, and a client who needs something right now.

Host: Ha, so what do the developers get out of having you around?

Buddy Blake: I think they appreciate people like me because I can break things. But I can also explain what happened, suggest how to fix it, and tell them why it matters to an agent trying to get through a real workday.

Host: I love that. So after all that, what's the standard you hold technology to?

Buddy Blake: I've got a list. Customer context is there when I need it. Fewer repeated entries and unnecessary handoffs. Useful priorities instead of endless notifications. Communication that reflects the actual relationship. Clear permissions, consent, and accountability. Workflows intuitive enough to reduce training and management. And growth that the underlying architecture can support. And a shared foundation doesn't mean every component has to be built from scratch. It means somebody designed how the parts work together.

Host: Okay, I have to ask about AI, because everybody's saying the word agentic right now. What does that mean to you?

Buddy Blake: In everyday terms, I take it to mean software that takes appropriate steps toward a goal within defined permissions. I like the idea. But the judgment stays with a person, and the information has to be accurate. And customers shouldn't have to learn a new app, repeat their circumstances, or understand any of this to get good service.

Host: Totally. So here's something I think a lot of people listening have felt. Business slows down, and suddenly you're eyeing the next shiny thing.

Buddy Blake: Oh, I know that feeling. I've felt that pull myself. You start thinking maybe a new CRM, another website, or another lead source will get everything moving. But sometimes the tools do need improvement. Sometimes the habits do. And sometimes the market simply delays the results. A slow month doesn't automatically mean you're a bad agent, and another subscription doesn't automatically fix it. It really helps to understand what's actually happening in the market, which is why we put together market insights on what really happens to listed homes. That link's in the show notes.

Host: So what should somebody do before they pull the trigger on something new?

Buddy Blake: Name the actual operational problem first. Is it that leads aren't getting followed up? That information is stored in three places? That you can't see what happened last week? Then look at the practical side. The total cost, not just the sticker price. The time and effort implementation will take. Cancellation provisions and renewal terms. And whether you can take your data with you if you leave. And none of that means stop running your business while you wait for something better. Keep working. Fix what you can fix today.

Host: Now I know you've been testing something new yourself. Can you tell us about that?

Buddy Blake: I'll keep this part short, because this is an opinion piece, not a product pitch. I've been fortunate to be invited in early, as Alpha One, on something that hasn't been publicly unveiled. I'm grateful to the people behind it for listening and letting me challenge things. I'm not going to say who they are or how it works. What excites me is seeing familiar industry problems treated as parts of one coordinated experience. It brings together a breadth of capability, thoughtful automation, and an approach to affordability that I find genuinely exciting. But that's my early assessment, nothing more. It's not a promise of results for anyone, and I'm still testing it.

Host: I respect that you're not overselling it. So what do you actually want from technology, at the end of the day?

Buddy Blake: Simple. I want it to help me spot opportunities, pursue listings, serve buyers and sellers, follow through, and strengthen the relationships that earn referrals. I focus on sellers now, and my team's agents help buyers. In both cases, being valuable is different from sending more messages. If you want to see how we approach selling a home, or what that looks like specifically for selling in Wilmington, those links are in the show notes.

Host: And you talk about winning the day. What does that mean to you?

Buddy Blake: To me, winning the day means completing the meaningful actions within your control while staying accountable for your business results. At the end of the day, I want to know I followed through. That I paid attention to the people who needed me. That I took the steps I could take and did the work I should have done. I can't begin to tell you how freeing that feels. The results may not show up on the leaderboard yet. Relationships and good work don't always turn into closings on our schedule. But knowing you showed up and served people well matters.

Host: Man, I love that. Okay, any last thoughts before we wrap up?

Buddy Blake: After twenty-eight years, I don't need more rooms added to a house that already doesn't flow. I need the work to flow around the people I'm here to serve. If you're thinking about selling and want an honest conversation, or you're an agent who just wants to compare notes, call or text me at nine one zero, three nine five, one thousand. The full article is linked in the show notes, along with a look at homes for sale in Wilmington. Serve the customer. Serve the agent. Win the day.

Host: Love it. Buddy, thanks so much for being here. That was a good one. And to everybody listening, go check the show notes for the full article. We'll catch you next time on Real Stories with Buddy Blake.