Many small businesses have one Excel file everybody knows. It is called "Tracking 2026 v4 FINAL", it has twelve tabs, color-coded columns, a few macros, and one person who knows why column P must never be sorted. That file runs the business. It is software, without any of the safeguards.
I have nothing against Excel. It is a remarkable tool, and most of these files have served their companies well. But there comes a point where the file costs more than it gives back. This article helps you spot that point, compare your options, and understand how a move to custom business software works when it is the right answer. Sometimes it is not, and I will say so too.
In short. A spreadsheet is built to calculate, not to have several people work through the same process. If your file shows three of the seven signs below, it at least needs rethinking. Always start with the lightest option: rebuild the spreadsheet, automate around it, or adopt off-the-shelf software. Custom software comes in when those options are no longer enough.
Why does Excel end up getting in the way?
Excel is not the problem. The way it gets used is. A spreadsheet is designed to hold numbers and calculate them. Over time, a business asks it to do something else: track cases, manage teams, decide who sees what, keep a record of who changed what.
For all of that, a spreadsheet lacks the right building blocks. It has no concept of a user with row-level permissions. It does not know a quote must be "sent" before it can be "accepted". It does not stop you from overwriting a formula. It does not alert anyone when a deadline passes. People compensate with colors, comments and discipline. It holds, until someone is away or in a hurry.
Technical limits exist too, but they rarely come first. An Excel worksheet holds at most 1,048,576 rows and 16,384 columns, according to Microsoft's specifications page. Google Sheets allows up to 20 million cells or 100 MB per file, according to Google's help center. Few small businesses ever reach those ceilings. The seven signs below show up long before.
What are the 7 signs an Excel file has become software?
- 01
Several people edit it, and versions multiply
"Tracking_v3_JM", "Tracking_v3_JM_fixed", a copy on the sales rep's desktop. Nobody knows which one is current, and time goes into merging them.
- 02
Only one person knows how it works
The macros, the nested formulas, the order in which tabs must be filled in: it all lives in one person's head. When they are on vacation, the file freezes.
- 03
The same data is copied elsewhere
The customer is entered in the file, then in the invoicing software, then in the schedule. Every copy is a chance for error and an hour lost each week.
- 04
You need to control who sees what
Margins should not be visible to everyone, a subcontractor should only see their jobs, a client would like to follow their case. A shared spreadsheet shows everything or nothing.
- 05
The file is used to track stages
A "status" column someone has to update, then check every morning to see who needs chasing. The file records the process, but it does not move it forward.
- 06
People open it in the field, and it is painful
Zooming in on a phone to find the right row, on a job site, wearing gloves. Or writing on paper and retyping in the evening.
- 07
A mistake costs money
A row deleted by accident, a price copied from the wrong cell, a forgotten order. If you have already lost a sale or a margin because of the file, this sign counts double.
My rule of thumb: one or two signs, the spreadsheet can be improved. Three or more, it is time to look at alternatives. If signs 03 and 05 apply, automation may be enough. If signs 04 and 06 apply, you probably need a real app.
What are the alternatives to Excel?
Replacing Excel does not necessarily mean having software built. Here are the five options, from lightest to heaviest.
| Option | When to choose it | Its limit |
|---|---|---|
| Rebuild the spreadsheet | One or two signs, a small team | Still fragile, no fine-grained permissions |
| Automate around the spreadsheet | Data copied by hand, manual follow-ups (signs 03 and 05) | The spreadsheet stays the foundation, weaknesses included |
| Off-the-shelf software | Your need is common (CRM, invoicing, scheduling) | You adapt to the tool, per-user subscription |
| No-code tool | Online database or app builder, set up in-house | Depends on one vendor, gets complicated with permissions and integrations |
| Custom app | Specific process, several signs, several tools to bring together | Several weeks of building, an upfront investment |
To rebuild a spreadsheet, two habits change everything: one row per tracked item (a job, a visit, an order), and dropdown lists instead of free text. I show an example in the article on scheduling software for a cleaning business. Automating around the spreadsheet is what my automation projects do: the file stays, but reminders, copies and summaries happen on their own.
What does a custom app actually look like?
The term sounds intimidating, but the reality is simple. For a small business, a custom business app usually means:
- A web app, opened in the browser, on a computer or a phone, with nothing to install.
- A database that replaces the tabs: one table for customers, one for jobs, one for site visits, linked together.
- Screens designed for each use: the list of open cases, the detail page of a case, the form filled in on site.
- Roles: the owner sees everything, the technician sees their jobs, the client sees their case.
- Integrations with your existing tools (invoicing, calendar, email), so you stop retyping.
Take a fictional example: a renovation company tracks its jobs in an eight-tab file. The equivalent app would have an "open jobs" screen with each job's stage, a page per job with photos and documents, and a button that turns an accepted quote into a scheduled job. The rest of the file (statistics, old tabs) can wait for version two.
If your teams mostly work in the field, offline or with the camera, an installed mobile app may fit better than a web app. That is what my mobile apps page covers.
How does the switch from Excel to an app work?
- 01
Take stock of the file
Every tab, every column, every formula: what is it for, who fills it in, who reads it. You often find tabs nobody uses anymore. The existing file is the best requirements document there is.
- 02
Pick the most used screen
You do not replace everything at once. Start from daily use: the list of cases, this week's schedule. The rest comes later.
- 03
See the screens before building
A mockup of the main screens, built from your own data, checks that the app fits the way you work before a line of code is written.
- 04
Build in small steps
Two-week sprints, each ending with a demo you test on real cases. Someone on your team needs to be named as the tester.
- 05
Migrate the data
Spreadsheet rows are imported into the database after cleanup: duplicates, names spelled three ways, dates in the wrong format. It is often the most underestimated step.
- 06
Run both side by side, briefly
One or two weeks where the file stays open read-only, to reassure people and compare. Then you archive it. Running two tools in parallel for too long means double data entry.
If you want to put this in writing first, a requirements document has the same structure for a web or mobile app: I go through it in mobile app requirements document: template and example.
What drives the cost of a custom app?
I will not give a price here: it depends entirely on what the app needs to do, and a number out of context would not help you. Here is what makes it vary instead, so you can read a quote.
| Item | What pushes it up | How to keep it down |
|---|---|---|
| Screens | Number of screens and their complexity | Start with the two or three daily screens |
| Roles and permissions | Many different profiles, detailed rules | Two or three roles to begin with |
| Integrations | Tools without an API, two-way syncing | Check APIs before the quote, start with a simple export |
| Data migration | An old, messy file with lots of exceptions | Clean the spreadsheet first, only migrate what is useful |
| Mobile and offline | An installed app that works without network | A web app usable on a phone, if coverage is good enough |
| Running costs | Hosting, maintenance, new features | Standard services, maintenance sized to your needs |
The right comparison is not "Excel is free". It is the time spent around the file every week, multiplied by the hourly cost of the people involved, plus the cost of mistakes. For the mobile side, I break down the costs in how much a mobile app costs in 2026.
What mistakes should you avoid when replacing a spreadsheet?
- Copying the file exactly. The file holds workarounds piled up over years. The app should follow the process, not the workarounds.
- Wanting everything in version one. A small first version used every day beats a complete version delivered in six months.
- Leaving users out. If the people who filled in the file are not part of the demos, they will keep their own Excel copy "just in case".
- Not planning the exit. Check that the code, the database and the access will be handed over. With me, you own the code once the invoice is paid, along with the access, files and documentation.
- Picking a rare technology. Prefer widely used tools, so another developer can take over if needed.
When is it better to keep Excel?
In many cases, keeping the spreadsheet is the right call:
- The file is for analysis, not for running a process. A dashboard, a simulation, a budget forecast: that is what Excel is for.
- Only one person uses it. With no shared work and no permissions to manage, most of the seven signs disappear.
- The process changes every month. Until the way you work settles down, locking a process into an app is premature.
- Off-the-shelf software already does almost everything. Take it, and connect it to your other tools rather than rebuilding it all.
The simplest step is often to show me the file. In 30 minutes, we can see whether it needs restructuring, automating or replacing. Book a 30-minute call: it is free, with no commitment.
Sources checked on October 17, 2026
- Microsoft, Excel specifications and limits
- Google Drive Help, files you can store in Google Drive (spreadsheet limit)
Frequently asked questions
What can replace Excel in a business?
Depending on the need: a better-built spreadsheet, automations around it, off-the-shelf software (CRM, invoicing, scheduling), a no-code tool or a custom app. Start with the lightest option that solves your problem.
When should a business stop using Excel?
When the file is edited by several people, data is copied into other tools, you need to control who sees what, or a mistake in the file costs money. If three of these signs apply, it is time to look at alternatives.
How much does a custom app to replace an Excel file cost?
The price depends on the number of screens, user roles, integrations with your tools and data migration. A first version limited to the daily screens costs less and goes live sooner.
Can Excel data be moved into an app?
Yes. Spreadsheet rows are imported into the app's database after cleaning up duplicates and formats. The more structured the file, with one row per item, the easier the migration.
Custom app or no-code tool?
A no-code tool fits a simple need set up in-house. A custom app makes sense when permissions, integrations or volume make no-code complicated, or when you want to own the code and the data.
How long does it take to replace an Excel file with an app?
Usually several two-week sprints, depending on the number of screens and integrations. A first version limited to the most used screen can be live well before the whole file is replaced.