Business software

Your software works, but your teams still work in Excel: why?

Quentin Debray
Written by Quentin Debray
Published 23 September 2026 · 9 min read

In brief

Your teams export everything to a spreadsheet even though the software is paid for and works. It is not a discipline problem: it is the free, precise map of the gaps between your tool and your real business.

You invested in a management tool. It runs, it is paid for, it is supposed to cover the business. And yet, every week, someone clicks "export". If your teams use Excel instead of the software you gave them, it is neither a whim nor a discipline problem. It is a signal, and a valuable one: it shows exactly where the tool departs from the way you really work.

The good news is that this signal is readable. The less good news is that the reflex reaction (calling people to order, banning parallel files, relaunching a replacement project) misses the point in most cases.

The symptom: the Friday export and the parallel table

Before looking for causes, look at the facts. In an SME of 10 to 80 employees, the scene almost always repeats in the same forms.

  • The salesperson keeps their own deal-tracking table, because the software does not show follow-ups in the order they make them.
  • The workshop prints a schedule redone by hand on Monday morning, because the workload screen ignores absences and the machines actually available.
  • The administrator exports the invoicing lines into a workbook to cross-check them against delivery notes, because the two are not in the same place.
  • The owner receives a consolidated file on Friday, built in three hours, because no screen gives the view they ask for.

These four examples have one thing in common: nobody is working against the tool. Each person fills a gap, in a hurry, with the only universally available instrument. The spreadsheet is not the problem. It is the plaster.

The cost, though, is very real. It is counted in hours of re-keying, in diverging versions of the same figure, in information that lives on one workstation and disappears when a person leaves. And it is invisible in the accounts: nobody bills "three hours rebuilding a table".

Why your teams use Excel instead of the software: the five usual causes

1. The software imposes a process that is not yours

An off-the-shelf package encodes one way of working, the one that suits the largest number of its customers. If your company approves a quote in two stages, if you invoice by progress under house rules, if a project can change customer along the way, the tool will ask you to fit into its boxes. The teams then find a workaround, and the workaround is almost always a workbook.

This is the most structural case, and also the hardest to fix with configuration. The underlying subject is covered in our comparison off-the-shelf package vs software: a package saves you time where you are standard, and costs you time where you are specific.

2. A field, a step or a view is missing

Sometimes the gap is tiny. A piece of information everyone needs to note and that has no box: the contact's name on site, the serial number, the reason for a postponement. With no field, the information goes into a free comment, then into a file on the side, because you cannot sort or filter a comment.

The same logic applies to views. The software displays files by creation date, the team thinks by deadline. A sort that does not exist means one export a week.

3. The tools do not talk to each other, so people re-key

An SME of this size commonly handles a sales management tool, an accounting solution, a planning spreadsheet, a mailbox and sometimes a production tracking tool. When these blocks ignore each other's existence, someone makes the junction by hand. The spreadsheet becomes the transit zone: export on one side, rework, re-import on the other.

This symptom is the easiest to put a figure on: count how many times the same information is entered twice in the week, multiply by the unit time. The result is often surprising.

4. It is too slow or too heavy for daily use

A screen that takes eight seconds to open, an entry that needs eleven clicks, a search that forces you to know the exact reference: for occasional use, people put up with it. Forty times a day, they run. Ergonomics is not a comfort matter, it is a volume matter. Teams arbitrate with their time, and they arbitrate fast.

Add mobile. Many management tools are designed for a fixed workstation. If your teams are travelling, in the workshop or at the customer's, they will note things on paper or in a shared file, and the "clean" entry will happen in the evening, or never.

5. Nobody has really configured the tool, or trained the teams

This is the most frequent cause and the least spectacular. The software was installed, a demonstration was given, two people were trained, and the rest managed. The functions exist, but nobody knows they exist. The default settings were never adjusted to your nomenclature, your statuses, your access rights.

This is then an adoption problem, not a tool problem. And it is fixed with days of tuning and support, not with a development budget.

What the spreadsheet tells you about your organisation

Each parallel file documents a gap between the official process and the real one. It is free information that few companies exploit.

A workbook maintained by a single person for two years is a business need that never found its place in the tool. It tells the story of a step in your value chain that the software ignores. Before deleting it, you have to read it.

Conversely, a file created six months ago for a one-off need and never reused does not deserve a place in a specification. The whole point of the diagnosis is to tell the two apart.

Diagnosing in a week: the map of gaps

The exercise is simple and costs only time. It is done internally.

Step 1. Ask each department to list the files they keep outside the software. Without judgement, explicitly. As long as the teams fear a reprimand, they will say nothing, and you will be diagnosing blind.

Step 2. For each file, ask four questions.

QuestionWhat it reveals
What information is missing in the software?A field, a view, a calculation, a link between two files
Who maintains it and how much time a week?The hidden cost and the risk of depending on one person
Who else uses it?Whether it is an isolated use or a de facto process
What happens if the file disappears tomorrow?The real criticality

Step 3. Sort. Gaps that come up in three departments belong to the process. Those that appear only once often belong to individual habit or a training gap.

Step 4. Put the list to the vendor or integrator of your tool. Some of the gaps may already be covered by a function nobody has switched on. This happens more often than you would think.

At the end of the exercise, you have a map: on one side what the tool can do, on the other what you really do. The space between the two is exactly the zone occupied by spreadsheets.

The four possible outcomes, in the order to consider them

OutcomeWhen it appliesOrder of magnitude of effort
Configure and trainThe functions exist but are neither set up nor knownA few days
Connect the toolsThe data exists twice and is re-keyed by handA few days to a few weeks
Add a custom building block alongsideA precise, lasting need, not covered, on a limited perimeterA few weeks
Replace or buildThe gap is structural: your business does not fit the toolSeveral months

The order is not decorative. Starting from the bottom of this table means risking rebuilding, at great expense, a tool that will fail on the same point, because the cause was not there.

The counter-intuitive reflex: often, there is nothing to develop

A significant share of the situations we see are settled by tuning and support. No project, no development, no five-figure budget. One configuration session, two hours of training per department, a clear instruction on who enters what and when.

It is rarely what you expect from a software builder. Yet it is the honest answer when the diagnosis points to it. Building on top of an adoption problem means paying twice.

When custom building becomes the right answer

It becomes so when three conditions are met: the gap is structural (your process does not fit the tool and never will), it affects several people every day, and it concerns what makes you different commercially. A generic job tracker does not need to be reinvented. A pricing logic specific to your sector does.

To decide between buying a market solution and having one built, the detailed grid is here: build or buy software. And if you are still unsure about the exact perimeter of a management tool, the overview of tool families is in what is management software.

Three mistakes to avoid

Banning parallel files. You will not remove the need, you will remove its visibility. The workbooks will migrate to personal workstations and you will lose your best sensor.

Launching a replacement project out of irritation. The feeling that "the tool does not fit" is almost always partly true. The useful question is: on what percentage of use? Software that covers 80% of the need and leaves you two spreadsheets is not a failure, it is a tool to complement.

Confusing the tool and the rule. Some gaps come not from the software but from the absence of a decision: who enters the quote, at what moment a file changes status, who has the right to change a price. No solution settles that for you.

Where to start on Monday morning

Take an hour with three people who use the tool every day. Ask them to open, in front of you, the files they keep on the side. Note for each one the missing information and the time spent each week. In an hour, you will have a first version of the map of gaps, and you will already know whether you are facing a configuration problem, a link between tools, or something deeper.

This is precisely the exercise we run in our diagnosis: mapping the tools in place, the parallel files and the re-keying points, then saying which of the four paths is the right one. Sometimes the conclusion is that there is nothing to build. That is a useful conclusion too.

If your tool is an application already developed for you and it no longer keeps pace with how the business has evolved, the subject is a little different: it is covered in taking over a business application that no longer keeps up.

Also read: Build or buy software: how to decide · Off-the-shelf package vs software: differences, uses, choices and trade-offs in 2026 · What is management software? · Taking over an existing custom business application

Also read: What is custom business software?

Also read: CRM pricing: how much does CRM software cost in 2026? (SaaS, custom and full comparison)

A question about your situation?

Ask Quentin, he replies personally.

Your details are used only to reply to you. Learn more

We use audience-measurement cookies to improve the site. Learn more.