Spreadsheet or app? 9 signs the spreadsheet is no longer enough

In short

A spreadsheet stops being enough when several people edit it at once, versions of it circulate, different permissions or a change history are needed, and data has to be entered in the field. Before you build an app, check the in-between solutions: data validation, a shared spreadsheet in the cloud or a database with a ready-made interface.

Key points
  • A spreadsheet is a great prototype of a process, but a weak system for several people at once.
  • The most expensive mistakes are the ones nobody notices: overwritten formulas and outdated copies.
  • Between a spreadsheet and a custom app there are in-between solutions.
  • Your spreadsheet is a ready specification for an app: columns are fields, tabs are screens.

9 signs the spreadsheet is no longer enough

  1. Files like “orders_final_v3_fixed.xlsx” circulate by email.
  2. Someone regularly asks: who changed this, and when?
  3. Two people edit the same file and one overwrites the other's changes.
  4. Some people should see only their own rows, or shouldn't see purchase prices.
  5. Formulas break now and then because someone pasted a value into the wrong cell.
  6. Data has to be entered in the field, on a phone, and a spreadsheet on a phone is torture.
  7. You retype the same data from the spreadsheet into another program, for example for invoices.
  8. The file takes longer and longer to open, and the filters can't keep up.
  9. All the knowledge of how the spreadsheet works is in one person's head.

One sign is not yet a reason to change. Three or more usually mean the company pays more for the spreadsheet in time and mistakes than it would pay for a simple app.

In-between solutions before you build an app

  1. Tidy up the spreadsheet

    Data validation (drop-down lists instead of typing), locked formulas, one data tab instead of copies in many places.

  2. Move it to a shared cloud

    One file in the browser instead of versions in emails solves the problem of copies and gives you a change history.

  3. A database with a ready-made interface

    Tools like Airtable or the open-source NocoDB and Baserow give you tables with permissions, forms and views, without programming.

  4. A simple custom app

    When the process has its own rules, integrations are needed or the data has to stay on your server.

When an app costs less than a spreadsheet

An app has an upfront cost, a spreadsheet has a cost spread over time: retyping, hunting for errors, calls asking for the current version. Count how many hours a week the team loses looking after the spreadsheet. If it's several hours every week, a simple app usually pays for itself sooner than it seems.

Tip

Don't throw the spreadsheet away. It's the best specification you can give a developer: it shows the fields, dependencies and exceptions that really occur in your company.

What a good app should have instead of a spreadsheet

Checklist0 of 8

Questions and answers

Can an app work alongside a spreadsheet?

Yes. Often, at first, the app exports data to a spreadsheet used by accounting or management, and over time the spreadsheet is no longer needed.

How long does moving a spreadsheet to an app take?

It depends on the number of tabs, rules and integrations. A simple register with permissions is a completely different scale from an order system connected to a warehouse.

What about the data already in the spreadsheet?

It's moved over when the app starts. It's a good moment to tidy up: duplicates and inconsistent entries come out during the import.

The service related to this guide

Custom software and internal tools

Describe the problem

Question 1 of 5

What would you most like to improve?

Pick the closest one. It doesn't have to fit perfectly.

First summary

This is a first suggestion based on a few answers, not a diagnosis. Nothing is saved until you send the message.