The hidden cost of a business that has outgrown its spreadsheets

Monday, 8:47 am. An enquiry arrives. A colleague adds it to a shared spreadsheet, forwards an email and separately tells the person responsible for quotes. That afternoon, the owner asks what happened. Answering requires searching three places. This is a fictional working day, but the pattern may feel familiar.

The cost seldom appears as one dramatic failure. It accumulates through interruptions: a copied phone number, a status check, a reply held up because someone is unavailable. Each looks manageable. Together they absorb time that could go into customers and developing the business.

The limit appears when a spreadsheet becomes a workflow

Excel is valuable for calculations, modelling, reports and quick analysis. A small team can run a simple, stable register in it successfully. Friction appears when one case moves between several people, stages and deadlines. Permissions, the next action and the ability to detect a delay become part of the job.

A well-designed shared sheet, a form and a few automations may be enough. Custom software becomes worth considering when your process repeatedly exceeds those arrangements. The development decision should respond to a real constraint. A spreadsheet is not, by itself, evidence of a problem.

One of the most expensive pieces of information is the detail someone has already recorded and another colleague asks for again.

Watch three signals for a week

• The same information is entered more than once: a customer record becomes a quote, a calendar entry and an internal list. Each transfer adds coordination.
• The process relies on one person’s memory. When that person is away, others struggle to understand what happened and what comes next.
• Management reporting requires a separate collection exercise. Someone merges lists and reconciles conflicting statuses before the meeting.

Record how often these events occur, how many minutes they take and where corrections become necessary. Involve the people doing the work. They know both the expensive manual steps and the exceptions that a seemingly unnecessary workaround currently handles.

Start at the handovers

The enquiry in our example can have one case identifier. The proposal belongs to that case. The owner of the task sees its deadline. Acceptance creates the next action. Management reporting draws from the same recorded states. Each change then has an understood place, and less information travels by hand.

Eurostat’s 2025 data show ERP use by 46.45% and CRM use by 28.51% of surveyed-scope EU enterprises. The survey covers specified sectors and businesses with at least ten employed people. These are adoption figures, not evidence of an individual implementation’s return. Eurostat

Make the first project narrow enough to finish

Choose a process with a clear beginning and end, such as enquiry to accepted proposal. Name the people involved, the information required and the definition of completion. If the team cannot agree on these, development is premature.

Then choose the appropriate scale. Could better configuration solve the issue? Is there a suitable existing product? Would a small custom module or integration be enough? Bespoke development can make sense where the process justifies it. Data migration, training, export and ongoing support also belong in the scope.

Decide who owns the process after launch. A system needs someone to resolve new exceptions, maintain sensible fields and keep responsibilities current. Without that ownership, a tidy first version can gradually become another place where information is left incomplete.

Growth should not require another round of copying

Digitalisation can create value by helping the team handle more work consistently. First decide what you want to improve: response times, lost enquiries, internal coordination or management visibility. Each can become a measurable operational objective.

At the next management meeting, start with one question: which detail do we copy again and again, and what would change if it belonged to one shared case? That is specific enough to begin a useful development conversation.