Internal platforms: when one app replaces three spreadsheets

An internal platform pays off when the same information lives in three spreadsheets and nobody knows which one is right anymore. Not when the spreadsheet gets too big. Excel handles over a million rows. What it handles badly is five people typing into different copies, from their phones, each with different access rights.

What "three spreadsheets" looks like

The story is almost always the same. One sheet for orders or jobs. Another for the team's hours. A third for clients and what was promised to them. Each started out fine, on one computer.

Then the business grows. The hours sheet gets passed around on WhatsApp at the end of the week. Someone works on Monday's version, someone else on Wednesday's. The client's name is spelled differently in every file, so you can't see at a glance what's been done for them.

Signs you've outgrown spreadsheets

• The same data gets typed twice. The client goes into the orders sheet, then by hand into the billing one.
• You don't know who changed what. A number changed and nobody remembers when.
• Everyone sees everything. The person in the field can see salaries, because it's one file.
• Field work, no computer. The team should check things off from their phones, but the sheet is miserable on a small screen.
• Reports happen on Sunday. Someone pulls data from three places by hand to find out how the month went.

If two or three of these sound familiar, the problem isn't Excel anymore. It's that your business has a workflow no spreadsheet knows about.

What a platform gets you

An internal platform is a web app built around your workflow: one database, different screens for different people, and a history of changes. A client is entered once and shows up everywhere. The person in the field sees only their own jobs, on their phone. The monthly report builds itself from the same data.

There's another gain you notice later: personal data. The EU's data protection regulation (GDPR, Article 32) calls for measures that keep data confidential and intact on an ongoing basis, regular testing of those measures, and people with access handling data only on the company's instructions. A spreadsheet with ID numbers and salaries posted to the team group chat is hard to defend.

Access rights are checked on the server

This is where things go wrong most often, in small and large apps alike. In the 2021 OWASP Top 10, broken access control ranks first, found in some form in 94% of the applications tested. The classic examples: someone changes a number in the page address and sees another person's account, or opens a page directly that the menu never showed them.

The practical takeaway: hiding the "Salaries" button from a menu isn't protection. Every request to the server checks who the person is and what they're allowed to see. And you test it exactly that way: log in with an employee account and request the forbidden address directly.

When it isn't worth it

Not every spreadsheet needs replacing. If one person uses it on one computer and it works, leave it alone. A platform makes sense when several people work on the same data, from different places, with different rights.

How to start without much risk:

1. Pick one workflow, the one that hurts most (usually hours or orders).
2. Import your existing spreadsheets so you don't start from scratch.
3. Keep an export back to Excel, for your accountant and your own peace of mind.
4. Add the rest step by step, after the team has used the first part for a few weeks.

The cost depends on how many workflows and roles the business has, how much data moves over, and what other software the platform has to talk to. The price comes in the quote, after we've seen your spreadsheets. See what our App Dev studio does.