Internal business apps: when Excel stops being enough

Excel is enough while one or two people work in a file and the data doesn't need strict rules. It stops being enough when several people edit the same rows, when each of them should see something different, when the team works from phones out in the field, or when you need to know who changed what. That's when an internal app, built around how you actually work, starts to pay off.

The limit isn't the number of rows

An Excel worksheet holds 1,048,576 rows. Few small businesses ever get there. The real problems show up much sooner, and they're of a different kind:

• Multiple copies. "Orders_final_v3_good.xlsx" emailed around, then edited in parallel. Nobody knows which version is right anymore.
• Working at the same time. Microsoft does support co-authoring, with conditions: a Microsoft 365 subscription, the file stored in OneDrive or SharePoint, and the .xlsx, .xlsm or .xlsb format. When two people change the same cell, the last saved change generally wins, and whatever someone types offline is only merged once they're back online.
• Broken formulas. Someone deletes a row or pastes over a column, and the totals are wrong for days before anyone notices.

Sheet protection isn't security

Many people "hide" sensitive data with a password on the sheet. Microsoft says plainly that worksheet-level protection isn't intended as a security feature: it only stops people from editing locked cells. Anyone who has the file can see everything in it.

That matters when the spreadsheet holds personal data: customer phone numbers, addresses, national ID numbers, salaries. The GDPR requires security measures appropriate to the risk, including the ability to restore access to data after an incident and making sure the people who handle the data only use it as instructed. A file copied onto five laptops and sent by email makes both hard to meet.

Signs it's time

If three or more of these sound familiar, an app is worth discussing:

1. More than three people edit the same file every day.
2. Different people need to see different things (a driver only their own trips, the accountant only invoices).
3. Part of the team works from a phone, in the field or in a warehouse.
4. You need a history: who changed the price, when the order was closed.
5. The same data gets retyped by hand somewhere else (an invoice, an email, another sheet).
6. You lose time every month reconciling two files that should say the same thing.

What an internal app adds

Role-based access is the part most people underestimate. It has to be checked on the server, on every request. A button hidden from the menu stops no one. We explained why in our post on admin panels.

When you don't need an app

If it's two of you, the data isn't personal and the file has never broken, stay with Excel. A good middle step: turn your data into proper Excel tables, with validation on columns, and keep them in one shared place. Sometimes that buys you another year.

And don't start with "everything." The first version of an internal app covers the workflow that hurts most (orders, appointments, timesheets) and replaces a single sheet. The rest comes once people are using it. It's the same thinking as an MVP.

What to bring to the first conversation

• your current Excel file (test data in place of the real data is fine);
• who works with it and what each person does;
• where the work happens: office, field, phone;
• which reports you pull every month, and for whom.

The cost depends on how many roles there are, how many screens the workflow needs, connections to other systems (invoicing, courier, accounting) and whether it has to work offline. The price comes in the quote, after we've seen the file.

See the kind of apps we build on our App Dev services page.