What I Look At First When a Client Says They Need a New System

A client called me last spring convinced he needed to rip out his whole CRM and start over. He'd already priced three replacements. He'd already decided. He just wanted me to confirm which one to buy.

We never replaced it.

This happens more than you'd think. Someone tells me they need a new system, and they've already skipped past the only question that matters. "I need a new system" isn't a problem. It's a conclusion. And nine times out of ten, it's a conclusion reached at 11 p.m. on a Tuesday after the current setup did something maddening for the third time that week.

So before I look at a single piece of software, I look at the thing underneath the request. Here's the order I go in.

"New system" is a guess about the solution, not the problem

When you tell me you need a new system, you've handed me your answer and hidden your question. My job is to find the question.

The CRM guy from last spring didn't have a CRM problem. He had a follow-up problem. Leads were going cold because nobody was assigned to chase them, and the calendar reminders everyone relied on lived in someone's head. A brand-new CRM would have inherited the exact same hole on day one — except now he'd have paid for a migration, retrained his team, and spent three months in the productivity ditch that every system change digs.

The first thing I do is refuse to talk about the new system. I ask what specifically broke, the last three times it broke. Not "it's clunky." Not "it's old." What were you trying to do, and what stopped you? You learn more from three concrete failures than from an hour of general complaints.

How the work actually flows — not how it's described

The second thing I look at is the real path the work takes through the business, which is almost never the path the owner describes.

People describe their process the way it's supposed to work. The org chart version. The clean version. But the actual work flows through whoever picks up the phone, the spreadsheet nobody admits to maintaining, the one employee who "just knows" how to handle the weird orders. That shadow process is where the pain lives, and no software you buy off a shelf knows it exists.

I learned this the hard way years ago running product at Travelocity. You could not design a booking flow from a conference room. You had to watch what people actually did — where they hesitated, where they backed out, where they called support instead of clicking the button right in front of them. The map in everyone's head was always cleaner than the territory. Small businesses are no different. Before I recommend changing the tools, I map how the work really moves, because that's what any new system would have to absorb.

What you already own and aren't using

The third thing I check is almost insulting in how often it's the answer: you probably already own a tool that does most of what you need, and nobody ever turned it on.

I see this constantly. Businesses paying for software at the tier that includes the exact feature they're about to go buy somewhere else. QuickBooks doing 20 percent of what it can. A CRM with automation built in that nobody configured because the person who set it up left in 2022. Replacing a system you're using at 30 percent capacity doesn't get you to 100 — it gets you a new system you'll also use at 30 percent, plus a bill.

I worked with a wholesale distributor in the airfield lighting business that had been running projects out of three-ring binders, email threads, and spreadsheets since 1989. They were sure they needed something big and custom. What they actually needed was the right tool configured for how they work — we landed on Smartsheet, no AI, no custom build, no six-figure platform. Staff got back about 30 percent of the time they'd been burning. The "new system" they imagined would have cost five times as much and solved the same problem worse.

When a new system actually is the answer

Sometimes it is. I'm not in the business of talking everyone out of everything.

I helped one of the largest privately held electrical distributors in the country modernize a legacy ecommerce platform across more than 800 locations. That was a real rebuild — the old system genuinely couldn't carry where the business was going, and patching it would have cost more than replacing it. The difference is that we knew that before we started, because we'd done the diagnosis first. We weren't guessing. We'd traced the problem to the system itself, ruled out the cheaper fixes, and could say exactly why the rebuild was worth it.

That's the whole point. A new system is sometimes the right call. But it should be the conclusion of an investigation, not the opening assumption. When you start with the software, you spend money to find out whether you needed to. When you start with the problem, the software almost recommends itself — and sometimes it tells you to keep what you've got.

If you're staring down a "we need a new system" decision and you're not sure whether the system is actually the problem, [book a free conversation](https://outlook.office.com/owa/calendar/Brincore@brincore.com/bookings/). No pitch. I'll help you find the real question first — and if the honest answer is that you don't need a new system, I'll tell you that too.