aaron@mccarthy:~/posts/when-to-replace-excel-with-real-app.md
← cd ../blog.md

When Should You Replace Excel With a Real Application?

Excel is one of the most powerful tools ever created for business. It’s also one of the most overused.

Every spreadsheet starts innocently. Track a bit of data, run a few calculations, share it with a teammate. No problem at all. But give it six months and that same file has quietly turned into a system, a process, and a dependency. At that point the question stops being “should we keep using Excel?” and becomes “when does this need to be a real application?”

After years of being called in to untangle these situations, I’ve seen a pattern. Here’s how to spot it early.

## The Core Problem: Excel Was Never Meant to Be a System

Excel is brilliant at calculations, analysis, and one-person workflows. It’s a poor fit for multi-user collaboration, complex business logic, structured workflows, and long-term scalability. Most businesses push it into those roles anyway, and it works—right up until the day it doesn’t.

The move to a real application isn’t about Excel being bad. It’s about recognizing when the tool has quietly been asked to do something it was never built for.

## 7 Signs It’s Time to Move Beyond Excel

1. Multiple people are editing the same file

This is usually the first warning sign. You start seeing files named Final_v3_REAL_FINAL.xlsx, people asking who has the latest version, and edits getting overwritten in the middle of the day. Even with cloud versions you run into conflicts, accidental changes, and a general lack of control over who did what. When collaboration becomes a coordination problem, your process has outgrown a single-file system.

2. The logic is too complex for anyone to understand

At some point the spreadsheet becomes a black box. Nested formulas point at hidden sheets. Circular references hide in cells nobody remembers naming. There’s a column everyone knows not to touch because it breaks everything. If only one person understands how it works, you don’t have a tool—you have a risk with a retirement date attached to it. Business logic this important needs to be structured and documented, not buried inside formulas.

3. You’re using Excel to manage a workflow

This is the big one. If your spreadsheet tracks status (Pending, Approved, Completed), assignments, approvals, or process steps, it’s not a spreadsheet anymore. It’s a workflow system wearing a spreadsheet costume, and Excel was never designed for that job. You’ll see it in the symptoms: manual status updates, missed steps, constant email follow-ups to figure out whose turn it is to act. You need a system that enforces process, not one that depends on people remembering it.

4. You’re copying data between multiple files

This usually shows up as monthly reports being rebuilt from source files, data exported from one system and pasted into another, or the same dataset living in three different workbooks. Every copy introduces errors, inconsistencies, and wasted time. If your people spend more hours shuffling data than using it, you don’t have a reporting problem—you have a missing source of truth.

5. Reporting is slow or unreliable

When getting answers means manual filtering, pivot table gymnastics, or rebuilding the same report every month, you’re losing time and introducing risk. Worse, different people run the same numbers and get different results, and before long nobody fully trusts the data. That’s a signal your underlying structure no longer supports the questions the business is asking.

6. You’re adding “just one more column” every week

This is how spreadsheets quietly spiral out of control. New columns for edge cases. Workarounds for missing structure. Logic layered on top of logic until nobody can see the original design through all the patches. Eventually the sheet becomes unmanageable, changes become risky, and even opening the file takes longer than it should. What you’re really doing is patching a system that needs to be redesigned.

7. You’re afraid to make changes

This is the biggest red flag of them all. When people say “don’t touch it, it might break something,” you’ve already outgrown Excel. A system that can’t be safely changed is a system that will eventually fail—usually at the worst possible moment. You need something stable, testable, and maintainable, and a fragile workbook is none of those things.

## So… What Replaces Excel?

Not everything needs a massive enterprise platform. In most cases what you actually need is a simple web-based application backed by a centralized database, with clear workflows and controlled user access. Nothing exotic.

A typical modern setup for this kind of internal tool looks like Next.js for the application, Prisma for data modeling, SQLite or PostgreSQL for storage, and role-based access with straightforward workflow logic on top. That’s it. The stack isn’t complicated—it’s just structured in a way a spreadsheet never could be.

## What You Gain by Making the Shift

Moving beyond Excel gives you a single source of truth, reliable structured data, enforced workflows with real accountability, faster reporting, and fewer errors—all wrapped in something that can actually grow with the business. Maybe most importantly, you stop relying on fragile files and start relying on a real system. The conversation shifts from “who broke the spreadsheet” to “what do we want to build next,” and that’s a meaningfully different kind of work.

## When You Shouldn’t Replace Excel

To be fair, Excel is still the right tool in plenty of cases. Stick with it when one person owns the data, the logic is simple, there’s no real workflow involved, and it’s used primarily for analysis rather than operations. Excel is excellent at what it was designed for. The problem is using it for what it wasn’t.

## A Simple Rule of Thumb

If your spreadsheet is shared by multiple people, driving a business process, hard to understand, and critical to operations—it’s no longer a spreadsheet. It’s an application pretending to be one.

## Final Thought

Most businesses don’t make this transition early enough. They wait until errors pile up, processes slow down, or something breaks badly enough that the cost of doing nothing finally outweighs the cost of change. You don’t have to wait for that moment. Recognizing the signs early gives you a chance to fix the problem before it becomes painful, and to do it on your own timeline instead of in a crisis.

Excel got you this far. It’s just not built to take you further.