Bad Tech Is Expensive9 min read

Bad Tech Is Expensive. Bad Advice Costs Even More.

The most expensive technology mistake might happen before you ever sign the contract.

Jacquelyn Mosier
Jacquelyn “Jackie” Mosier

Founder & Principal Consultant, Jack-IT Consulting

There’s something happening in the technology industry that we need to talk about.

Businesses are being sold solutions faster than they’re being taught how to evaluate them.

AI agents. Automation platforms. CRMs. New operating systems. Another subscription promising to save time, increase revenue, eliminate inefficiencies, and transform the way your business operates.

And somewhere in all those demonstrations, proposals, and promises, one very important question gets overlooked.

Who determined that technology was actually the problem?

I’ve spent years in sales. Inbound, outbound, B2B, residential, and door-to-door. I’ve ranked #1 nationally multiple times, trained and developed sales teams across the country, and learned from some of the most successful sales leaders in the industry.

And one thing I’ve learned is that there’s an enormous difference between someone who knows how to sell and someone who understands how to help.

That distinction matters more than ever when businesses are making technology investments.

You can smell commission breath a mile away.

I wrote about this recently when discussing sales and leadership.

When someone becomes so focused on closing a deal that they stop listening to the person sitting across from them, it shows.

The questions become leading. The recommendations become predictable. Every problem conveniently points back to whatever product they’re selling.

And suddenly, the conversation isn’t about what’s best for the customer. It’s about getting the signature.

Now apply that mentality to technology consulting.

A business owner says they’re struggling with customer follow-up. They’re sold a CRM.

A company says employees are overwhelmed by manual processes. They’re sold automation.

Leadership wants to improve productivity. Someone immediately recommends AI.

But what happens when the CRM isn’t the problem? When the automation simply accelerates a broken process? Or when AI introduces complexity and risk the organization isn’t prepared to manage?

Just because you can sell someone a solution doesn’t mean you’ve solved their problem.

And when the wrong solution is implemented, the business is the one left dealing with the consequences.

Good salespeople aren’t afraid of the word no. Good consultants shouldn’t be either.

One of the biggest lessons I’ve carried throughout my sales career is that your job isn’t to convince everyone to say yes.

Your job is to help someone reach an informed decision. Yes or no. That’s it.

When you remove the desperation to close, something interesting happens.

You listen differently. You ask better questions. You’re willing to acknowledge when something isn’t the right fit. And you stop treating every objection as something that needs to be overcome.

That same mentality should exist in consulting.

If someone comes to Jack-IT convinced they need an AI agent, I’m not going to agree simply because there’s a budget attached to it.

I want to know what they’re trying to accomplish.

What systems are already in place? Where is the actual breakdown? What information would the proposed solution need access to? Who is responsible for maintaining it? How will employees use it? And what happens if it doesn’t work as expected?

Sometimes the recommendation will be to move forward. Sometimes it will be to take a different approach. And sometimes it will be to stop before spending another dollar.

A consultant who can’t tell you no isn’t necessarily advising you. They may just be selling to you.

A software demonstration is not a business assessment.

A great demonstration can make almost any platform look impressive.

But showing what technology can do isn’t the same as determining what a business needs it to do.

I’ve worked with businesses where the challenges extended far beyond the software they were using.

Customer information moving between disconnected systems. Employees repeating administrative tasks. Departments operating with different information. Leadership lacking visibility into the work happening throughout the organization.

These aren’t problems you solve by immediately purchasing another platform.

You have to understand the operation.

Where does information originate? Who touches it? Where does it get stuck? What decisions depend on it? And how do the people responsible for the work actually perform their jobs?

In one commercial installation engagement, we evaluated how customer inquiries, estimates, scheduling, project information, field reporting, purchasing, and financial activities moved across the business.

Instead of immediately recommending an entirely new platform, we developed a phased strategy using existing Microsoft 365 capabilities and targeted integrations.

The objective wasn’t to automate everything. It was to identify where better processes, connected systems, and appropriate automation could make a meaningful difference.

That’s the distinction between selling technology and understanding operations. See How We Solve Operational Problems Before Recommending Technology →

The hidden cost isn’t always on the invoice.

A $20,000 implementation doesn’t necessarily cost $20,000.

What happens when employees don’t adopt the system? When departments continue maintaining separate spreadsheets? When information has to be entered three different times? When leadership can’t trust the reporting? When the person who originally configured everything leaves? Or when a company discovers that its shiny new AI solution has access to sensitive information nobody properly evaluated?

The original proposal might not account for those costs. But the business will.

And here’s where leadership becomes part of the conversation.

You cannot purchase your way out of poor leadership, undefined accountability, or broken processes.

Technology can support an organization. It cannot replace the responsibility to understand, lead, train, and develop the people responsible for making that organization function.

I’ve trained sales teams across the country, and one thing I’ve consistently seen is that performance doesn’t improve simply because leadership introduces another tool or increases pressure.

People need clarity. They need expectations they understand. They need training that actually prepares them to do their jobs. And they need leaders willing to examine whether the process itself is creating the problem.

The same principles apply when implementing technology.

If your employees don’t understand why something is changing, how it affects their responsibilities, or how to use it effectively, you’ve already created unnecessary resistance. That’s not necessarily a software failure. It’s an organizational one.

AI has made bad advice even more expensive.

AI has tremendous potential.

But potential and suitability are two very different things.

Right now, businesses are being encouraged to introduce AI into nearly every part of their operations. And some of the people making those recommendations aren’t asking fundamental questions about data security, permissions, liability, oversight, or the consequences of an automated system making the wrong decision.

Think about that.

Would you give an employee unrestricted access to your financial information, customer records, and internal systems without understanding their responsibilities and establishing appropriate controls?

Then why would you do it with an AI agent?

Before an AI system is given access to business information or permission to act on behalf of employees, someone should be evaluating what it can access, what actions it can perform, how those actions are monitored, and what happens when something goes wrong.

Being innovative doesn’t mean abandoning due diligence. And understanding AI means knowing when not to use it.

Sometimes traditional automation is more appropriate. Sometimes a better-defined process is enough. Sometimes the organization simply isn’t ready.

Those aren’t anti-technology recommendations. They’re responsible business decisions.

Leadership sets the standard. Consultants should be held to one, too.

Something else I’ve learned from developing sales teams is that leadership shapes behavior.

When an organization measures success exclusively by how many deals close, it shouldn’t be surprised when people prioritize closing.

When salespeople are pressured to push products regardless of fit, the customer experience suffers.

And when consultants are rewarded for recommending implementations rather than solving problems, businesses need to understand how those incentives may influence the advice they’re receiving.

That doesn’t mean every salesperson or technology provider is operating with bad intentions. There are exceptional professionals in this industry.

But businesses should feel comfortable asking difficult questions.

How did you determine this is the right solution? What alternatives did you evaluate? What are the risks? What happens after implementation? How will our employees be trained? How will we know whether this investment was worthwhile?

And perhaps most importantly:

What would make you recommend that we don’t move forward?

Pay attention to that answer. It may tell you more than the entire demonstration.

Strategy before software isn’t a slogan. It’s how we operate.

At Jack-IT Consulting, we don’t begin with a product catalog. We begin with the business.

We evaluate existing systems, understand operational challenges, challenge assumptions, and identify where technology can create meaningful value.

Sometimes that means building integrations, improving workflows, implementing automation, or developing a technology roadmap.

Sometimes it means helping leadership understand why the technology they’ve already purchased isn’t delivering.

And sometimes it means telling a business that the solution they’re considering isn’t the right investment.

We’re not interested in recommending technology simply because it’s available, trending, or profitable to implement. We’re interested in whether it makes sense for the business, its employees, and its long-term objectives.

Because I’ve spent enough time in sales to know that getting someone to say yes isn’t the hard part.

Earning their trust, delivering on what you promised, and being willing to tell them the truth even when it costs you a sale? That’s where the real work begins.

And it’s the standard I believe this industry needs to hold itself to.

Before you buy another solution, ask better questions.

If your business is considering AI, struggling with disconnected systems, evaluating a CRM, or trying to understand why your technology investments aren’t producing the results you expected, let’s have a different kind of conversation.

One that starts with your business, not a software demonstration.

Explore Our Consulting Services →

Jack-IT Consulting | Strategy Before Software. Always.

Jacquelyn Mosier — Founder and Principal Consultant, Jack-IT Consulting
Jacquelyn “Jackie” Mosier

Founder & Principal Consultant, Jack-IT Consulting

Technology Strategy  ·  AI Advisory  ·  Business Operations  ·  Executive Leadership

Jacquelyn Mosier is the Founder and Principal Consultant of Jack-IT Consulting. With a background in national sales leadership, team development, and business operations, she built Jack-IT on a straightforward premise: technology decisions should start with the business, not the software. She works directly with leadership teams to evaluate investments, identify operational gaps, and build strategies that connect people, processes, and systems before recommending what comes next.

Before you invest in another solution, make sure you’re solving the right problem.

Considering AI, struggling with disconnected systems, or wondering why your technology investments aren’t delivering? We’ll help you evaluate what’s happening before recommending what comes next.