Every Technology Purchase Should Answer These Five Questions

← Back to Insights

Every business reaches the same moment.

Someone schedules a meeting. A presentation is shared. The software looks impressive. The demonstrations are polished. The features seem endless.

By the end of the meeting, everyone is asking the same question.

How much does it cost?

I think that's the wrong question.

Not because cost doesn't matter.

Because by the time you're discussing price, you've already decided the software is the answer.

You just haven't proven the problem.

Over the years, I've watched organizations purchase software with the best intentions.

Some of those investments transformed the business.

Others became expensive applications employees reluctantly opened because they had to.

The difference was rarely the software.

It was the questions leadership asked before making the investment.

Instead of beginning with features, I encourage leadership teams to walk through five questions.

Every single time. Regardless of the vendor. Regardless of the budget. Regardless of the technology.

Those questions have prevented far more poor technology decisions than any product demonstration ever has.

Question One — What business problem are we actually solving?

This sounds obvious.

It isn't.

I've seen organizations purchase reporting platforms because leadership wanted better visibility.

After a few conversations, it turned out reporting wasn't the issue.

The data itself wasn't reliable.

No dashboard could solve that.

I've seen companies invest in collaboration software because communication felt fragmented.

The real problem was that every department followed a different process.

The software wasn't going to fix that either.

A technology investment should solve a clearly defined business problem.

If the problem can't be explained in a sentence or two, keep asking questions.

Technology should solve a business problem—not create a new monthly subscription.

Question Two — Can we improve the process before we buy another tool?

One of my favorite questions is surprisingly simple.

If we had no budget, how would we improve this process?

That question changes the conversation immediately.

People stop talking about products.

They start talking about work.

How information flows. Who approves requests. Where delays occur. Who owns each step.

Sometimes improving the process removes the need for new software altogether.

Other times, it makes the software implementation dramatically more successful.

Either way, the process should come first.

Question Three — How will we know this investment was successful?

This is where many projects quietly fail.

Nobody defines success.

The project finishes. Everyone celebrates. Six months later... nobody can explain whether anything actually improved.

Every technology investment should have measurable outcomes.

Examples might include: Reduce employee onboarding from one hour to fifteen minutes. Reduce software deployment time by 80%. Eliminate manual reporting every Friday. Improve first-day readiness for new employees. Reduce recurring support requests.

Notice none of those measurements mention software.

They're measuring business outcomes.

That's intentional.

Before approving any project, complete this sentence: "Six months from now, we'll know this investment was successful because..."

If leadership struggles to finish that sentence, the project probably isn't ready yet.

Question Four — Who owns this after implementation?

Technology projects often receive tremendous attention during implementation.

Then everyone moves on.

Ownership becomes unclear. Documentation stops. Processes drift. Configurations change.

Eventually the business wonders why the investment isn't delivering the expected value.

Technology doesn't manage itself.

Every solution needs a business owner.

Not necessarily someone in IT.

Someone responsible for making sure the technology continues supporting the business long after the implementation team leaves.

Ownership creates accountability.

Accountability creates long-term value.

Buying technology is an event. Owning technology is a responsibility.

Question Five — Will this still support the business three years from now?

This is my favorite question.

Not because anyone can predict the future.

Because it forces leadership to think beyond today's frustrations.

Imagine your company doubles in size.

Will the solution still work? What if you acquire another business? What if half your workforce becomes remote? What if regulations change? What if you expand into another market?

Good technology decisions aren't made for today's business.

They're made for tomorrow's business.

That's strategy.

According to McKinsey & Company, organizations that consistently generate value from digital investments focus on long-term business capability rather than individual technology implementations. The greatest returns come when technology decisions support broader organizational goals instead of isolated departmental needs.

That's exactly why these five questions matter.

They shift the conversation away from software features and toward business outcomes.

The Apex Decision Framework

Every technology investment should be able to answer these five questions.

1. What business problem are we solving?
2. Can we improve the process first?
3. How will success be measured?
4. Who owns this after implementation?
5. Will this support where the business is going—not just where it is today?

If leadership can't answer those questions confidently, don't schedule another product demonstration.

Schedule another business conversation.

The technology can wait.

Clarity can't.

Leadership Challenge

At your next budget meeting, resist the urge to ask, "What does this software do?"

Instead ask, "What business outcome are we buying?"

That single question changes the entire conversation.

You'll spend less time comparing feature lists and more time discussing operational improvements, measurable outcomes, and long-term business value.

In my experience, those are the conversations that lead to the best technology decisions.

Ready to Make Better Technology Decisions?

Every technology investment is really a business investment.

The question isn't whether the software is impressive.

The question is whether it will help your organization operate better, grow more effectively, and create measurable value.

If you're evaluating a major technology initiative, start with the five questions in this article.

If you'd like an outside perspective, I'd be happy to help facilitate that conversation with your leadership team.

Sometimes the most valuable thing you can do before buying technology is make sure you're solving the right problem.