How to turn spreadsheets into a system: when and where to start

Almost every company starts on a spreadsheet. It's free, everyone knows how to open it and it solves today's problem. Order tracking, team schedules, finances, inventory: it all fits into tabs and formulas. For a while, it works really well.

The problem shows up slowly. One person becomes the only one who understands the formulas. Three versions of the same file circulate on WhatsApp. Closing the month takes two days and nobody trusts the final number. In this guide I show when the spreadsheet stopped helping, how to turn it into a system without halting operations and what to ask of whoever builds it.

Spreadsheets fail more than you think

This isn't a software vendor's grudge. In 2024, a research review led by Professor Pak-Lok Poon, with researchers from Central Queensland University, Swinburne University of Technology and City University of Hong Kong, concluded that 94% of spreadsheets used in business decisions have errors. The work pulled together studies published over more than 35 years and appeared in the journal Frontiers of Computer Science.

The reason the authors give is simple: more and more people build spreadsheets with no software development training. A formula dragged one row short, a cell typed over a calculation, a filter left on by mistake. None of it raises a warning. The number just comes out wrong.

And mistakes are expensive. A 2024 survey by Datarails, done with input from Simon Thorne, program chair of the European group that studies spreadsheet risk (EuSpRIG), found 12 lawsuits in the United States and the United Kingdom, over two years, in which spreadsheet disputes led to US$210 million in company losses.

6 signs your spreadsheet became a bottleneck

Spreadsheets aren't the enemy. They're great for testing an idea, running a one-off calculation or tracking something only one person uses. They become a problem when they turn into the company's system without being built for it. See if you recognize these signs:

1. More than one person edits the same file. Someone overwrites someone else's work, and nobody knows who changed what.
2. There's one indispensable person. When they go on vacation, the month-end close stops.
3. Data is copied by hand from one place to another. From the online store to the spreadsheet, from the spreadsheet to finance, from finance to the report.
4. A customer asks and you have to dig. Order status, balance, next visit: the answer means opening three tabs.
5. The file got slow or heavy. It takes ages to open, freezes on your phone and already has a “do not touch” tab.
6. You can't give partial access. Either a person sees everything, including margins and salaries, or nothing at all.

If three or more of these describe your operation, the spreadsheet already costs more than a system would. That cost just doesn't show up on an invoice. It shows up in hours of rework, wrong orders and decisions made on bad numbers.

What a system solves that a spreadsheet can't

A web system built for your process trades the spreadsheet's total freedom for rules. And that's exactly what you want:

• Each person sees and edits only what they need. Sales enters the order, finance approves it, the manager sees the dashboard. Nobody deletes anyone else's formula.
• The rule lives in the code, not in a cell. Maximum discount, delivery time, commission: the system calculates them the same way every time.
• Everything has a history. Who changed it, when and what the value was before.
• Data goes in only once. Integrating with the payment gateway, the invoicing tool or WhatsApp ends double entry.
• Customers can serve themselves. A simple portal shows status, invoices and schedule without anyone on the team having to reply.

A custom system isn't always the answer. If your process is the same as any other company in your industry, off-the-shelf software may do the job. The criteria for choosing between them are in custom system or off-the-shelf software. A spreadsheet usually calls for a custom system when it holds a rule only your company has.

How to turn spreadsheets into a system, step by step

1. Map what the spreadsheet really does

Before designing any screen, list who fills in each tab, who only reads it, where the data comes from and which decision depends on it. Old spreadsheets hide business rules in formulas nobody remembers writing. Those rules have to be found and confirmed with the people who use them, one by one.

2. Pick the most painful workflow

Don't try to migrate everything at once. Pick the workflow where errors cost the most: orders, billing, scheduling or inventory. That workflow becomes the first version of the system. The rest stays in the spreadsheet for now. Cutting scope to fit a date is what gets the project off the ground, as the article on cutting scope to hit the date shows.

3. Design the screens with the people who'll use them

The person who fills in the spreadsheet every day knows where the shortcuts and workarounds are. Show them the prototype before writing code. A screen that takes one more click than the spreadsheet will be abandoned.

4. Migrate and clean the data

Spreadsheets pile up duplicates, names spelled three ways and dates in different formats. Migration is the time to clean up. Decide which historical data comes in, standardize it and check the totals: the year's revenue in the system has to match the spreadsheet.

5. Run in parallel, then switch off

For a short period, the team uses the system and someone checks it against the spreadsheet. Once the numbers match, that workflow's spreadsheet becomes read-only. Then it gets archived. If it stays open for editing, people go back to it.

6. Measure and move to the next workflow

With the first workflow live, measure what changed: hours of data entry cut, errors gone, time to close. Those numbers decide which spreadsheet goes next.

How much it costs and how long it takes

It depends on how many workflows, access roles and integrations go into the first version. An order tracking spreadsheet with two roles is one project. A set of spreadsheets handling sales, inventory, finance and commissions for ten branches is another. What drives the price is covered in how much a custom web system costs.

What doesn't change: be wary of anyone who quotes a price without looking at your spreadsheets. That's where the rules that will become code live. Without that discovery, the quote is a guess, and the guess comes back later as a change order.

How we do it at the Studio

At the Studio, the price is fixed after discovery and the deadline is written into the contract. Discovery is exactly the reading of the spreadsheets, the rules hidden in the formulas and who uses each part.

One case study shows the logic: LCX, a travel company operating in more than 10 South American countries, had one system per country. We merged everything into a single system, live in 29 days. The principle is the same as replacing scattered spreadsheets with one place and one rule.

The code, files and access are in the client's name, and the dev team is the Studio's own. Every system ships with an AI agent that runs daily, flags failures, suggests improvements and checks whether the data makes sense. It's the kind of check a spreadsheet never did: a wrong number gets flagged before it becomes a decision.

If your company already runs on spreadsheets only one person understands, see how we launch custom systems and SaaS, starting with the workflow that costs you the most today.