Excel, ERP, no-code or custom software: which one should you pick?

Keep Excel while it stays a personal tool

A budget, a simulation, an export to clean up once a month: Excel is great for that. It is flexible, everyone knows it and it needs no project.

Trouble starts when several people work in it, when the same figure is copied somewhere else, or when a forgotten formula can send out the wrong amount. At that point the file is no longer a spreadsheet. It is your management tool, without the safeguards of a management tool.

Off-the-shelf software fits when your business looks like many others

For standard accounting, a simple CRM or ordinary appointment booking, start by looking at existing software. It costs less up front and it has already solved the most common problems.

The warning sign: your team starts working around the tool in the first few weeks. Excel exports, side notes, double entry, steps done outside the system. It is not necessarily a lack of discipline. Often your way of working simply does not fit the software.

No-code holds up on a simple need, less so when everything depends on it

Airtable, Notion or Make can be very good shortcuts. To test a process, build a small internal directory or connect two tools without complicated rules, they save a huge amount of time.

But as soon as there are precise permissions, business calculations, large volumes of data, clients who log in or a slightly twisted rule, the setup becomes fragile. Someone has to understand and maintain it. No-code does not remove technical debt; it just makes it less visible at the start.

Custom software becomes reasonable when the cost of patching is already there

Business software is worth it when your team loses time every week checking, retyping, hunting for the right version or fixing a mistake. Not because custom is nobler. Because you are already paying for the problem, in hours and in fatigue.

At Celaé, assessments, documents and invoicing went through Excel, Drive, email and paper. A single application replaced that whole route. The starting point was not modernising for its own sake: the same information had to stop travelling through four places.

• You have a business rule that existing software cannot apply.
• The same data is retyped into several tools.
• A mistake costs more than the tool would cost to build.
• Your team has already tried to adapt, and it did not stick.