This Is For B2B service firms who are slammed, sitting on too many tools, and still feel like everything is harder than it should be....or who are about to make a tech decision and want to get it right the first time.

This newsletter was inspired by a fascinating DM conversation I had recently with someone else in the tech implementation space. We were discussing why so many tech investments fail, and we landed on something that most people miss: the problem isn't the tools. It's the mental model people bring into the room before any of it gets touched.

​Two businesses can buy the exact same software, ask two different questions before implementation, and get completely different outcomes. One asks, "How can this save me money?" The other asks, "How can this help my team move faster?" Same desired outcome. Completely different results.

I had a DM conversation recently with someone else who works in the operational side of tech implementation. We were going back and forth about why so many tech projects fail, and we kept landing on the same conclusion:

The problem is rarely the tools.

The problem is the mental model people bring into the room before any of it gets touched.

She said something that stuck with me: "Speed without structure just accelerates fragmentation." - Heather Ioerger

And that's exactly what I see happening in businesses every day. They buy tech hoping it will solve problems, but because they approached it with the wrong mindset, they just accelerate their existing chaos.

So let's talk about the two mindsets, and why one consistently outperforms the other.

 When the starting question is, 'How can this save me money?' the system is designed to replace effort. When the question is, 'How can this help my team move with less friction?' the system is designed to support behavior.

Most people approach tech through the lens of cost reduction.

"How can I save money on this task, process, or workflow?"

When you come at a situation thinking about how to save money, you're looking for reduction. You're trying to take tech and replace humans with it. Cut headcount. Eliminate roles. Reduce expenses.

And look, there are absolutely things that tech should be doing instead of people. Repetitive tasks. Data entry. Automated follow-ups. Things that don't require human judgment or connection.

But there's also the inverse...there's a lot of stuff that humans should absolutely be doing that tech should not touch. Relationship building. Complex problem-solving. Nuanced communication. The stuff that actually moves the needle.

The Alternative Question is,  "How can I make my team's life easier?"

When you come at tech from this angle, you're not looking for reduction. You're looking for multiplication.

If you free up 10 hours in a salesperson's weekly schedule, they can make more calls. More calls means more sales. More sales means more revenue.

One additional sale from that freed-up time could cover the entire cost of the tech implementation. Two sales? You're profitable in month one.

​Both questions lead to tech implementation. Both aim for better business outcomes. But one is designed around cutting, and the other is designed around growing.

 Not sure which processes in your business are candidates for multiplication? Take the free Tech Health Scorecard...10 minutes to identify where you're losing time that could be converted into revenue-generating activities.

Here's something that came up in that DM conversation that I think is critical: Tech decisions fail far earlier than people realize. Not because the tools are wrong, but because the humans were never brought along with intention.

Companies will invest heavily in the tech and completely underestimate the operational scaffolding needed to hold the human side steady once things go live.

Think about it: the price might be right, the tech might be right, but if the humans don't actually use it, what have you accomplished?

Unused tech is equally as valuable as tech you don't have.

​Actually, it's less valuable. Because you're paying for:

Before you invest in any tech, ask yourself this:

Am I asking "How can this save me money?" OR "How can this help my team move faster?"

If it's the first question, pause. Reframe. (BTW you are not wrong to think that way, but there is a better question to ask to get those results.)

Think about who uses the tech. What do they struggle with today? What would make their work easier? What outcome would they actually be excited adopt and use?

Then ask: if this freed up 5 hours per week for them, what could they do with that time that would generate value?

That's the question that leads to multiplication.

The irony is that both questions are trying to get the same result. But one approaches it through the lens of tech, and the other approaches it through the lens of business requirements and people.

One limits. The other scales.

How you approach your tech, specifically your mental approach, changes everything.

Every business now has to deal with the reality that their tech stack is a huge factor in whether they're optimized or not for success. It's not optional anymore.

But Here's the Pattern I Have Witnessed After Nearly a Decade:

If you come at technology through the lens of "How do I cut costs?" you're looking for reduction. You'll get reduction. And you'll limit your ability to scale.

If you come at technology through the lens of "How do I make my business and the people who work in it more efficient and effective?" you're looking for multiplication. And that's what you'll get.

Both thoughts lead to tech implementation. Both lead to saving time and money in some form. But in one case, you're looking through the lens of your P&L first. In the other, you're looking through the lens of business requirements and people first.

Same tools. Different questions. Different outcomes.

​Your Next Steps:

What if I genuinely need to cut costs right now?

Cost reduction is sometimes necessary. But even then, reframe the question: "How do I cut costs in a way that doesn't limit our ability to grow later?" This keeps you thinking about the future, not just the immediate expense. Cut the things that don't contribute to growth. Protect the things that do.

How do I know if my current tech was implemented with the wrong mindset?

Look at adoption. If people aren't using it, or they're working around it, or they complain about it constantly, that's a sign the humans weren't considered in the design. The tech might be fine. The approach was wrong.

Can I fix a cost-first implementation without starting over?

Often, yes. The fix usually involves going back to the humans. What do they actually need? What would make them want to use this? Sometimes small adjustments to the workflow or interface can dramatically improve adoption. Sometimes you need bigger changes. But you rarely need to scrap everything.

How much should I budget for change management?

At minimum, plan for it to take as much effort as the technical implementation itself. If you're spending 40 hours on setup and integration, plan for 40 hours on training, communication, and adoption support. Most companies budget 5-10% for this. The successful ones budget 40-50%.

Where can I learn more about the 5-part framework you mentioned?

The Tech Debt Detox is a free 6-part system that breaks down how to audit your tech stack, identify where things are failing, and implement fixes that actually stick. Step 5 specifically covers change management in depth.