Most insurance agencies make technology decisions the wrong way: they start with the solution. There’s a better framework.

Key takeaways

• Define the problem before you evaluate the solution. The first question in any technology decision isn’t “should we buy this?” It’s “what friction are we eliminating, and how will we measure success?” Skipping that step is how agencies end up with a bigger expense line and nothing to show for it.
• A proven solution that covers 80% of your needs is better than a perfect one that never ships. Waiting for complete alignment is its own form of risk. Run what works, learn from it, and close the gaps as you go.
• Clean data and functional workflows have to come first. No technology decision makes sense on a broken foundation. Before you build, buy, or partner, know exactly how your current processes run and where the time goes.
• Unless you can measure productivity, you’re chasing dreams. A baseline, built from real-time studies and operational analysis, is what separates a genuine investment from an expensive experiment.
• Architecture is the question most agencies aren’t asking. A collection of tools that each do their job but don’t talk to each other is a 1980 software problem, not a platform. Every build-buy-partner decision should be evaluated against a clear map of how your systems connect.
• Strategic differentiation outweighs ROI at the top of the scorecard. An investment that cuts costs but does nothing for client experience or competitive positioning isn’t a strategic investment. Build what only you can build.
• Platform investment requires patience. Spend goes up before it comes down. The goal is for productivity gains to materialize and bring costs back in line, not for technology to keep adding to the expense structure indefinitely.

Build-buy-partner framework for insurance agency technology

Every few months, something lands inside my inbox that promises to transform the way we run our agency. A new AI tool. A workflow automation platform. A co-development opportunity with a vendor who swears their product is exactly what independent agencies have been waiting for. And every time, my first instinct is the same: slow down.

Not because I’m skeptical of technology. I’m not. We’ve been on a digitization journey since 2017, and the investments we’ve made in building a technology architecture have been among the most consequential decisions this company has made.

But I’ve also watched good agencies spend real money on the wrong things at the wrong time, only to walk away with nothing but a bigger expense line to explain to their shareholders.

That’s why we built what we call a “Build-Buy-Partner Decision Tree.” It isn’t a purchasing checklist. It’s a governance discipline. And it’s a way of forcing clarity on decisions that, left unchecked, tend to be based on excitement rather than evidence.

Start with the opportunity, not the solution

The first thing the build buy partner framework asks isn’t “should we buy this?” It’s “what problem are we actually solving?” We then break this down into four more specific questions: What business friction are we eliminating? What is the expected value? Who owns the outcome? How will we measure success?

Those questions sound obvious, but they’re not. When something new and useful appears in front of an entrepreneurial person, the pull toward action is immediate. We see the upside and we want to move. It takes discipline to pause long enough to engage the decision tree: begin by defining the opportunity, in fine detail, before anyone looks at a vendor demo.

The second gate in our framework asks whether we already have an established solution that delivers roughly 80% or more of what we need. For most agencies, the honest answer is “yes.” And that’s good news. If a proven market solution covers the core workflow, there’s no strategic reason to reinvent it. Improve it, instead. Build what differentiates you. Buy only what doesn’t.

The mistake I see is holding out for 100%. Waiting for perfect alignment before committing to a good solution is its own form of risk. In most cases, if you’re at 80%, you’re closer to 100% than you think; you just need to run it, learn from it, and close the gaps as you go.

Your data and your workflow come first

Here’s what most agencies skip, and it costs them: before any technology decision makes sense, your underlying data has to be clean, and your workflows have to be functional. That’s not a technology problem you can fix with new technology. It’s a housekeeping problem, one that has to be addressed from the beginning. Legacy clutter is a barrier to efficiency, and the worst impediment to technological growth.

We learned this the hard way. When we brought in an outside operations partner to conduct a workflow analysis, they did time studies across our key processes. How long does a given task take today? What would it take with automation? That analysis gave us something most agencies don’t have: a baseline. A way to say, with specificity, if we make this change, here’s what the productivity impact looks like in hours, headcount, and dollars.

That baseline is everything. Because unless you can measure productivity, you’re just chasing dreams — and you’re not facilitating profit. I’ve been guilty of this myself. The shiny object appears, we get excited, we hit the spend button — and when it’s all said and done, that spend is twice what we planned — and we can’t even point to a clear outcome. The decision tree exists precisely to prevent that.

The architecture question no one is asking

Most agencies have some form of technology architecture, whether they know it or not. Their agency management system is the nucleus. Accounting plugs in. Maybe there’s a CRM. Data flows. The infrastructure exists.

What most agencies don’t have is a clear articulation of that architecture. You need a map of how the pieces connect and where the gaps are. And that articulation turns out to be the difference between a platform and what I’d call a 1980 software problem: a collection of tools that do their separate jobs but don’t talk to each other in any meaningful way.

The architecture question matters because it’s the lens through which every build-buy-partner decision should be evaluated. We ask specifically: Does this fit our technology architecture? Will it integrate with our systems without creating a disconnected silo? A tool that solves one problem but doesn’t connect to the broader platform is often more trouble than it’s worth. You fix something, but you can’t fix it all.

The goal of a platform is connectivity. Data flows in, flows through, and flows back out to the people who need it, in real time. When an agency achieves connectivity that smooth, the downstream effects are significant: faster service, better client insights, more informed advisors. But you can’t get there by stacking point solutions on top of each other.

The scorecard that keeps us honest

When a technology decision makes it through the early gates, we run it through a weighted scorecard. Strategic differentiation carries the most weight. Then financial ROI. Then productivity and capacity impact, data readiness, architectural fit, client and employee experience, security, and scalability.

That hierarchy is important. Strategic differentiation sits at the top because the purpose of this investment is to make us better at what we already do best: serve clients, retain relationships, and grow the book. An investment that scores well on ROI but does nothing for our competitive position or client experience isn’t a strategic investment. It’s a cost reduction. Those have their place, but they shouldn’t drive the roadmap.

Investments that score in the top tier proceed and scale. Mid-range scores go to pilot, where you validate the economics before you commit. Low scores mean stop, redesign, or find a partner who can supply a bridge.

Patience is a technology strategy

I tell my board the same thing every time we review our technology spend: this is a journey, and journeys require patience. We have increased our technology investment meaningfully over the past several years, and our goal is to bring it back down as the productivity gains materialize. That’s how platform investment works. It should pay off, not mushroom into new expenses.

The pressure on independent agencies right now is dramatic. Rates are moving, competition is intensifying, and every vendor in the market is telling you their AI solution is the one you can’t afford to miss. The agencies that navigate this well will be the ones who use the build buy partner framework. They will be the ones who asked the right questions first. They defined the opportunity, confirmed the foundation, assessed the fit, and measured the outcome.

Build what only you can build. Buy what the market has already solved. Partner where the expertise isn’t yours to develop. And before any of it, make sure your data is clean and your workflows are sound.

Everything else follows from that.