Workflow problems

When a spreadsheet should become an app

Spreadsheets are brilliant until they quietly become the system your business runs on. Six signs it’s time, and what to keep when you move.

3 min read

Spreadsheets are the most successful piece of software ever made, and for good reason. Anyone can start one, change it, and see every number at once. Plenty of good software started life as somebody’s spreadsheet, and that’s a compliment to the spreadsheet.

The trouble starts when a spreadsheet stops being a calculation and becomes a system: the place the business keeps its truth, edited by several people, with rules nobody wrote down. It gets the job without getting any of the protections a system needs.

Six signs it’s time

One person “owns” it. If there’s a colleague who has to be asked before anyone touches a tab, the rules live in their head. When they’re on holiday, the work waits.

There are copies. schedule_v7_FINAL(2).xlsx is a symptom. People keep their own copies when they can’t trust the shared one, and then nobody knows which copy is true.

Columns are colored by hand to mean something. Yellow means “waiting on the client”, red means “overdue”. That’s a status field and a rule, and a person is acting as both.

The same thing is typed twice. If information goes into the spreadsheet and then into another system (or an email, or an invoice), that’s a workflow with a person in the middle carrying it.

Something breaks when a row is added. Formulas that point at fixed ranges, lookups that stop at row 500, a pivot table nobody remembers how to refresh.

It sends nothing on its own. A spreadsheet can’t remind anyone. If the sheet says a client is due a follow-up, somebody has to notice.

Two or three of these is normal. Four or more and the spreadsheet is costing you more than it looks.

What changes when it becomes an app

The data gets a shape. Each customer, order or booking becomes one record with fields that can’t hold the wrong kind of thing. No more dates typed as text, or two spellings of the same client.

Rules move out of people’s heads and into the system, where they run every time. When we built CenterSuite, the reminders, missed-class alerts and follow-ups a learning center used to remember to send became rules with an on/off switch and a record of when each last ran.

Everyone sees the same truth, with permissions. The person who should change a price can; the person who shouldn’t, can’t. And every change has a history, so “who changed this?” has an answer.

What to keep from the spreadsheet

The best thing about a spreadsheet is that you can see everything and change it quickly. A good replacement keeps that feeling. Dense tables instead of one record per screen. Bulk edits. An export button, always, so your data never feels locked away.

And the import has to be painless. Nobody wants to retype years of history. CenterSuite’s spreadsheet import works out which column is which, because the first thing anyone does with a new system is try to get their old data into it.

Where to start

Don’t start by listing features. Start by watching the spreadsheet being used for a week: who opens it, what they change, what they copy out of it and where it goes. The app you need is usually smaller than you expect, and it’s hiding in those trips back and forth.

Next step

What’s the job you’d like to stop doing by hand?

Describe the problem in a few sentences. Within one working day you’ll hear whether software would fix it, roughly what it would take, and what we’d look at first.