Why spreadsheets don't scale (and what to actually use instead)

Excel is probably the most underrated and most overrated business tool in the world at the same time. It's underrated because it has let millions of small businesses start and grow without spending a euro on management software. It's overrated because it gets used in places it shouldn't be — out of pure inertia — until one day it creates more problems than it solves.

This article isn't an attack on Excel. Excel is extraordinary at what it was designed for: analysis, calculation, simulation, quick prototyping. The problem starts when it becomes the operating system of a company. Then the limit arrives — always.

Let's see how to recognise it, why it happens, and what to do before throwing money at the wrong software.

The signs that Excel has stopped scaling

You rarely notice it on a single day. The problem grows over months, then surfaces all at once:

• Multiple versions floating around: the most up-to-date file is in three different folders, everyone uses their own copy, and nobody is really sure they're working on the right one.
• Silent errors: someone changes a formula three months ago, the error propagates, and you only notice when a customer points out a wrong number.
• Real collaboration is impossible: Excel online helps, but if two people touch the same range at the same time, something gets lost.
• Macros have become a second job: every new requirement means calling "the one who's good at Excel," who's often a single person in the company.
• Tracking changes is impossible: who deleted client Y's row? When? Why? Nobody knows.
• Access controls don't really exist: either everyone sees everything (including pay, margins, sensitive data), or you make different copies of the file and you're back to square one.
• Reports require hours of copy-paste every month, always with small errors to fix by hand.
• Real-time updates: absent. The status seen this morning may already be wrong before lunch.

If you recognise three or more, Excel is no longer your ally. It's your bottleneck.

Why it happens: Excel is a sheet, not a system

To understand the root, you need a distinction that sounds trivial but changes everything: Excel lets you manage data. A management system lets you manage processes.

Data is rows and columns. Processes are rules, sequences, dependencies, people passing information to each other. Excel gives you a place to lay out numbers and text. It doesn't know what they mean, doesn't know when a piece of data should turn into an action, doesn't know who can do what.

That's why, when Excel starts being used as "the company's ERP," the people using it are actually hand-writing an operating system inside a spreadsheet. It works while the system is simple. It stops working as the system grows, because complexity doesn't live in single cells: it lives in the relationships between things.

Three technical limits no macro can overcome:

1. Excel is single-source by definition. Even with cloud collaboration, the mental model stays "one file for one purpose." More people, more parallel purposes = more files. More files = inevitable divergences.
2. Excel has no real integrity constraints. You can't truly stop someone from entering a customer with an invalid tax code, a date in the wrong format, a numeric value in a column meant to be text. You can mitigate with rules, but they're fragile.
3. Excel doesn't separate operational data from historical data. When a project closes, it stays in the file. After two years the file has 4,000 rows, of which 200 are active. Finding them takes filtering every time.

These aren't defects, they're characteristics. Excel wasn't designed to be a management system. It works perfectly as what it is: a personal calculation tool.

The most common mistakes when leaving Excel

Recognising the problem is the first step. The second is not replacing it the wrong way. Four mistakes I see again and again:

1. Buying the first CRM "because everyone has one"

CRMs are great if your problem is sales management. They're poor if your problem is admin, production, or logistics. Buying a CRM and then continuing to do admin in Excel solves half the problem and creates a new one: synchronising two sources of truth.

2. Adopting a "no-code" tool without designing the process

Tools like Notion, Airtable, Coda solve many cases and are cheap. But if you start using them without defining the process, you reproduce Excel with a different interface — and now you're paying a monthly subscription too. The tool alone doesn't add order.

3. Jumping straight to enterprise software

The big enterprise systems solve many problems but bring others: rigid, expensive, hard to change when your process evolves. For many SMBs they're overdimensioned. For others they're under-dimensioned in the parts specific to the sector.

4. Building custom from scratch without experience

The opposite mistake: getting fully custom software built from zero, with the first available developer. Without a serious design of the domain and without practice on real systems, you risk creating an MVP that has to be rewritten after six months. It happens, and it's the most painful spend.

The real alternatives: an honest map

There's no single right answer to "what to use instead of Excel." It depends on the size of the problem. A practical map:

Level 1 — Shared no-code tools (Notion, Airtable, ClickUp)

When they work: project management, simple records, processes for small teams (3–10 people), linear workflows.

When they're not enough: complex integrations, specific business rules, fine-grained access control, large data volumes, invoicing, accounting.

Typical cost: 10–30 euros per user per month. Implementation: weeks, not months. They're often the smart first step for those leaving Excel while still small.

Level 2 — Vertical off-the-shelf software (industry systems)

When they work: your sector is standard enough to have dedicated solutions (shops, restaurants, gyms, travel agencies, professional firms).

When they're not enough: your business model has specifics the software forces you to work around with free-text fields, notes, workarounds. If the first thing they tell you is "we'll customise it with custom fields," that's often a warning bell.

Cost: 50–500 euros a month depending on modules. Implementation: 1–6 months. They work well when your company is "average" inside its sector.

Level 3 — Custom-built business software

When it makes sense: your process is specific, you have employees spending hours on it daily, and off-the-shelf products can't bend to how you work. Typically above a certain operational size: 10–15 people using the system every day, or processes that generate direct value (logistics, production, B2B services with SLAs).

When it doesn't: you're below 5 operational people, your process is still evolving weekly, you don't have clarity on what's truly needed. In those cases, stabilise the process first with lighter tools.

Cost: an initial investment that typically starts from a few tens of thousands of euros for serious projects, up to hundreds for extensive platforms. Important: the real cost isn't the build, it's the maintenance and evolution over the next three to five years.

Level 4 — Custom + off-the-shelf mix (the option that actually works)

The most mature option in most real cases is hybrid: use off-the-shelf software for standard functions (accounting, e-invoicing, payroll), build custom only where it's truly needed (the company's specific operational core), and connect everything through APIs.

This approach keeps the custom cost low (focused only on unique value) and leverages mature tools where there's nothing to reinvent.

How to figure out where you are: five honest questions

To decide well, it's worth stopping and answering without romanticising:

1. How many hours a week do you (or whoever helps you) spend manually updating spreadsheets that should update themselves?
2. In the last six months, have you had a concrete problem caused by wrong or stale Excel data?
3. To collaborate on a piece of data, do you still send attachments by email?
4. Do you have real-time visibility on margins per client, project status, critical deadlines — or do you reconstruct them at month-end?
5. Does every new client or new employee require an amount of admin work that grows, instead of staying constant?

Three or more "yes" answers mean Excel is costing more than the software you'd need. The question is no longer if, it's what to adopt and in which order.

In summary

Excel isn't the problem. The problem is using a personal calculation tool as the backbone of a company that has stopped being personal. The smart question isn't "Excel yes or no": it's where Excel still helps you (analysis, simulations, prototypes) and where it's making you lose time, money and quality (daily operations, shared data, processes that should be automated).

Moving to a structured system — whatever the right level for you — isn't a cost. It's the decision that gives you back hours a week, reliable data, and the ability to grow without every new client slowing the whole machine.