Skip to content

Don’t Buy Software. Solve a Problem.

By Tomasz Lewandowski · 23 Jun 2026 · 5 min read

Don’t Buy Software. Solve a Problem.
Digitalising Your Business — Technology Strategy

When businesses decide to modernise, the first conversation often revolves around technology. Should we buy a CRM? Do we need an ERP system? Which project management platform is the best? Would artificial intelligence help? These are sensible questions, but they are rarely the right place to start. The better question is this:

What problem are we actually trying to solve?

Because software, no matter how sophisticated, cannot compensate for unclear objectives or poorly designed processes.

Technology Is a Tool, Not a Strategy

Imagine buying a van because deliveries take too long. If the real issue is that orders are being packed incorrectly, the new vehicle will not solve anything. It may even allow mistakes to reach customers more quickly. Business software works in much the same way. Installing a CRM will not automatically improve customer relationships. An accounting package will not fix inconsistent invoicing procedures. A workflow platform will not eliminate unnecessary approvals if those approvals remain part of the process. Technology amplifies the way your business already operates. If the foundations are weak, the weaknesses become more visible rather than disappearing.

Start With Frustration

One of the easiest ways to identify worthwhile digital projects is to ask your team a simple question:

What wastes your time every week?

The answers are often remarkably consistent.

  • “I have to type the same information three times.”
  • “We can never find the latest version of the document.”
  • “Customers keep asking for updates because they cannot track progress.”
  • “Nobody knows who approved the order.”
  • “Everything stops when one person is away.”

These are not software requirements. They are business problems. Only once you understand them should you begin evaluating technology.

Avoid Buying Features You Will Never Use

Modern business platforms are extraordinarily capable. Many offer hundreds of features covering sales, marketing, reporting, automation and analytics. Yet most organisations use only a small proportion of what they purchase. Why? Because they bought software based on demonstrations rather than operational needs. It is rather like purchasing a Swiss Army knife when all you required was a screwdriver. Complexity can become a burden rather than an advantage.

Define Success Before Spending Money

Before signing any contract, write down exactly what success would look like. For example:

  • Reduce order processing time from 30 minutes to 10 minutes.
  • Eliminate duplicate customer records.
  • Shorten invoice approval from three days to one.
  • Cut manual data entry by 80 per cent.
  • Enable new employees to complete training within one week.

These are measurable business outcomes. If you cannot explain what improvement you expect, it will be difficult to judge whether the investment has delivered value.

Practical Steps You Can Take Before Buying Anything

  • Map the current process. Draw each step from beginning to end. Many inefficiencies become obvious once they are visible on paper.
  • Measure reality. Do not rely on assumptions. Time how long routine tasks actually take and count how many manual handovers occur.
  • Speak to the people doing the work. Frontline staff usually understand operational problems better than anyone else. Listen carefully before designing solutions.
  • Remove unnecessary steps first. Deleting a redundant approval may save more time than automating it.
  • Standardise your data. Ensure names, addresses, product codes and customer records follow consistent formats. Clean data improves every future technology project.
  • Prioritise one problem at a time. Trying to transform the entire organisation in a single project often creates unnecessary risk. Solve one important problem well before moving to the next.
  • Write a one-page problem brief. Before comparing products, summarise the problem, affected users, current cost, desired outcome and success measure on a single page.
  • Decide what you will not do. A clear project scope is valuable, but a clear list of exclusions may be even more useful. It protects the project from becoming everything to everyone.

The Best Software Is Sometimes Invisible

Successful digital transformation often goes unnoticed by customers. Orders arrive on time. Invoices are accurate. Support requests are answered promptly. Employees spend less time searching for information. Managers trust their reports. Nobody congratulates the plumbing when clean water comes out of the tap. Likewise, the best business systems quietly enable work rather than demanding constant attention.

Think in Outcomes, Not Applications

It is easy to become excited by product demonstrations and marketing claims. Resist the temptation. Instead of asking:

  • Which CRM should we buy?
  • Which AI platform is the most advanced?
  • Which software has the longest list of features?

Ask:

  • How can we reduce unnecessary work?
  • How can we improve the customer experience?
  • How can we make better decisions using our existing information?
  • How can we help our staff focus on valuable work instead of administration?

The answers may involve technology. But they begin with understanding your business.

Digital Transformation Is About Better Business

The companies that benefit most from digital transformation are not necessarily those that spend the most. They are the ones that remain disciplined. They identify a genuine operational problem. They simplify the process. They organise their data. They involve the people who perform the work. Only then do they introduce technology that supports those objectives. So before purchasing another application or subscribing to the latest AI service, pause for a moment. Do not ask, “What software should we buy?” Ask, “What problem are we trying to solve?” If you can answer that clearly, choosing the right technology becomes far easier.

And if you cannot, no software in the world will solve it for you.

How to define the problem before buying business software

  1. Map the current process. Draw each step of the process from beginning to end. Many inefficiencies become obvious once they are visible on paper.
  2. Measure reality. Do not rely on assumptions. Time how long routine tasks actually take and count how many manual handovers occur.
  3. Speak to the people doing the work. Frontline staff usually understand operational problems better than anyone else. Listen carefully before designing solutions.
  4. Remove unnecessary steps first. Deleting a redundant approval may save more time than automating it, so cut waste before adding technology.
  5. Standardise your data. Ensure names, addresses, product codes and customer records follow consistent formats. Clean data improves every future technology project.
  6. Prioritise one problem at a time. Trying to transform the entire organisation in a single project often creates unnecessary risk. Solve one important problem well before moving to the next.
  7. Write a one-page problem brief. Before comparing products, summarise the problem, affected users, current cost, desired outcome and success measure on a single page.
  8. Decide what you will not do. Set a clear list of exclusions alongside the scope. It protects the project from becoming everything to everyone.

Frequently asked questions

Should I buy software to fix a slow or inefficient business process?

Not before you understand the actual problem. Software amplifies the way your business already operates, so if the foundations are weak the weaknesses become more visible rather than disappearing. The article uses the example of buying a van because deliveries are slow, when the real issue is that orders are packed incorrectly - the new vehicle just lets mistakes reach customers faster. Define and fix the process first, then choose technology to support it.

How do I identify which digital projects are actually worth doing?

Ask your team a simple question: what wastes your time every week? The answers are usually consistent - typing the same information three times, never finding the latest version of a document, or everything stopping when one person is away. These are business problems, not software requirements. Only once you understand them should you begin evaluating technology.

Why do companies end up paying for software features they never use?

Because they buy software based on demonstrations rather than operational needs. Modern platforms offer hundreds of features across sales, marketing, reporting, automation and analytics, yet most organisations use only a small proportion. The article compares it to buying a Swiss Army knife when all you needed was a screwdriver - complexity can become a burden rather than an advantage.

How do I know if a software investment was worth the money?

Write down exactly what success would look like before signing any contract, expressed as measurable business outcomes. Examples from the article include reducing order processing time from 30 minutes to 10, eliminating duplicate customer records, shortening invoice approval from three days to one, and cutting manual data entry by 80 per cent. If you cannot explain what improvement you expect, it will be difficult to judge whether the investment delivered value.

What should I do before comparing or buying any software?

Map the current process on paper, measure how long routine tasks actually take instead of assuming, and speak to the frontline staff doing the work. Remove unnecessary steps first, standardise your data so names, addresses and product codes are consistent, and prioritise one problem at a time. Finally, write a one-page problem brief covering the problem, affected users, current cost, desired outcome and success measure, and decide what you will not do.

Is digital transformation about spending more on technology?

No. The companies that benefit most are not those that spend the most but those that stay disciplined. They identify a genuine operational problem, simplify the process, organise their data and involve the people who do the work, and only then introduce technology that supports those objectives. The best business systems quietly enable work rather than demanding constant attention - nobody congratulates the plumbing when clean water comes out of the tap.

Share Follow
Do Not Start With an App. Start With the Job It Must Do
Working With App Developers

Do Not Start With an App. Start With the Job It Must Do

Before briefing a developer, ask the harder question: what operational problem are you actually solving? A one-page problem brief prevents six months of expensive wandering.

6 Jul 2026 · 8 min read
Your Customers Don’t Care Which Software You Use
Digitalising Your Business

Your Customers Don’t Care Which Software You Use

Your customers don't care which CRM or accounting tool you use — they care whether you answer promptly, remember them, and get things right. Here's how internal systems shape that experience.

30 Jun 2026 · 5 min read
Stop Collecting Data You Will Never Use
Digitalising Your Business

Stop Collecting Data You Will Never Use

More data does not mean better decisions. Learn why collecting only what you will genuinely use leads to cleaner systems, faster workflows and smarter choices.

29 Jun 2026 · 4 min read