Almost every business has an Excel file that has become essential: case tracking, the schedule, quotes, the customer list. It started small, it grew, and today several people depend on it. The question always comes up eventually: keep it, or replace it with an application built for your business?

This article does not put Excel on trial. It is an excellent tool, often the best one to start with. It simply helps you spot the moment it costs more than it brings in, and decide with figures rather than gut feeling.

When is Excel still the right choice?

Keep Excel when:

  • only one or two people edit the file;
  • it is mainly used to calculate, analyse or simulate, not to pass work between several people;
  • the process still changes often, and you are looking for the right way to do things;
  • a mistake in a cell has no serious consequence for a customer.

In these situations, an application would freeze a process that has not settled yet. It is better to keep learning with the spreadsheet.

What are the five signs it is time to change?

1. Several people edit the same file. Crossed versions, a file “locked by another user”, a copy named “final-v3-ok”: when a spreadsheet becomes a shared work tool, it loses what made it strong, its simplicity.

2. The same tasks come back every week. Copying rows from one tab to another, chasing the same customers, rebuilding the same table for the Monday meeting: every task repeated by hand is a candidate for automation.

3. Mistakes are costly. An overwritten formula, a half-sorted row, a shifted column. Spreadsheets check almost nothing by default. In 2020, Public Health England lost track of nearly 16,000 positive Covid cases because an old Excel file format limited the number of rows, as reported by the BBC. Your file does not carry those stakes, but the mechanism is the same: nothing warns you when the data is incomplete.

4. Customers or partners need access to the data. Sending an extract by email, hiding columns before sharing, retyping the answers you get back: as soon as outside people need to view or complete your data, an online space with permissions per user type becomes safer and simpler.

5. The file becomes slow or fragile. Excel accepts up to 1,048,576 rows and 16,384 columns per sheet, according to the specifications published by Microsoft. Long before those limits, a file loaded with formulas, links and formatting becomes slow to open, and only one person still knows how to fix it.

How do you put a figure on the benefit of an application?

A simple calculation is enough to know whether the question deserves a closer look. For two weeks, note the time spent on tasks the tool would remove: retyping, searching, chasing, consolidating, fixing mistakes.

  • 1. Time lost per week: the total hours noted, divided by two
  • 2. Annual cost: that time multiplied by 47 working weeks and by the loaded hourly cost of the people involved
  • 3. Cost of mistakes: last year’s mistakes and what they cost: a discount granted, a late file, a lost customer
  • 4. Comparison: the sum of both, compared with the price of the application and its maintenance over three years

A fictional example: three people each lose two hours a week retyping and consolidating, at a loaded hourly cost of €35. That makes 6 hours, or €210 a week and nearly €10,000 a year, before counting mistakes. A module from €2,250 excl. VAT, or a business application between €11,250 and €27,000 excl. VAT, can then be compared very concretely with that cost.

What about online spreadsheets or no-code?

Between the Excel file and the custom application, there are intermediate steps. A shared online spreadsheet solves the problem of crossed versions, but not unchecked data or repeated tasks. No-code tools, online databases and automations, go further: forms, filtered views, automatic emails.

They suit a small team with simple rules. They show their limits when calculation rules get complicated, when customers need access to part of the data with precise permissions, or when the per-user subscription grows with the team. That is often when the custom question comes back, with one advantage: the process has been tested and settled in the meantime.

A custom application or off-the-shelf software?

Before going custom, always check whether some software already does what you need. An off-the-shelf CRM, scheduling or project management tool may be enough, and will cost less upfront.

  • Getting started: immediate with off-the-shelf software, usually 6 to 12 weeks for a custom application.
  • Your process: with off-the-shelf software, you adapt to the tool; with a custom build, the tool follows the way you work.
  • Cost: a monthly subscription per user for off-the-shelf software; an initial budget, then maintenance, for a custom build.
  • Data: with the vendor for off-the-shelf software; yours, hosted in France, for a custom build.

Custom makes sense when your process is what sets you apart, when no software follows it without workarounds, or when per-user licences become expensive as the team grows.

What does an application that replaces a spreadsheet look like?

In practice, each row of the file becomes a record, with a status, an owner and a history. Columns become validated fields: a date is a date, an amount is an amount. Repeated tasks become automations: a reminder sent after 7 days, an alert before a deadline, a monthly report generated on its own.

A few examples by trade:

  • An accounting firm replaces the busy-season tracking spreadsheet with case tracking, deadline alerts and a document upload portal.
  • A communication agency replaces the production and time tracking file with a tool that calculates profitability per client.
  • A franchisor replaces the candidate file with a kanban recruitment CRM, with scoring and reminders.

How do you migrate without breaking everything?

  1. Start from the existing file. It holds your real rules, even the ones nobody ever wrote down. We go through it column by column.
  2. Keep the scope short. The first version replaces the heart of the file, not all its tabs.
  3. Import the history. Data is cleaned of duplicates and imported at launch: nobody starts again from an empty tool.
  4. Plan a parallel period. A few days when the file can still be consulted, while the team finds its bearings.
  5. Keep the export. An Excel export stays available for one-off analyses. The spreadsheet goes back to what it does best: analysis.

Who should lead the project on your side?

Choose the person who knows the file best, not necessarily the most senior. They know the hidden rules, the exceptions and the workarounds. Give them a few hours a week during the project to answer questions and test each delivery. Their involvement is the best guarantee that the application will be adopted by the rest of the team, rather than seen as one more tool imposed from above.

What should you do next?

Run the two-week test and note the time lost. If the annual figure exceeds a few thousand euros, or if a mistake has already cost you a customer, the question deserves a video call. Our Replace Excel page covers the cases we handle most often.

For an opinion on your file, describe your situation in two minutes: we will tell you whether an application is worth it, or whether off-the-shelf software is enough.