Engineering · Operations

When a spreadsheet becomes a liability

Spreadsheets run a remarkable share of Malaysian business operations, and most of the time that is fine. Seven signs that one of yours has quietly become critical infrastructure, and how to move off it without stopping work.

Pikabyte Engineering 3 min read

There is nothing wrong with a spreadsheet. It is the fastest way to get from an idea to a working process, and many good businesses run on them for years.

The trouble starts when a spreadsheet stops being a tool and becomes a system. Nobody decides this. It happens one tab at a time. Then one day the person who built it goes on leave, and a process stops.

Seven signs

1. One person understands it. If the answer to “how does this work” is a name, you have a single point of failure.

2. It is emailed around. “Final_v3_latest_USE THIS.xlsx” means there is no single version of the truth.

3. Two people cannot work in it at once without something breaking.

4. It feeds a document that leaves the building. A certificate, an invoice, a letter to a court. Copy and paste is now part of your compliance process.

5. It has formulas someone is afraid to touch. Especially a calculation involving money.

6. Nobody can say who changed a figure or when.

7. It is slow. Tens of thousands of rows, and people wait for it to open.

One or two of these is normal. Four or more and the spreadsheet is a liability.

What moving off it actually involves

The fear is a long, expensive project that disrupts everything. It does not need to be. The spreadsheet is, in effect, a complete specification written by the people who do the work. That is a large advantage.

Read the spreadsheet as a requirements document

Every column is a field. Every colour code is a status. Every formula is a business rule. Every tab that exists “because of that one customer” is an exception that must be preserved.

We sit with the person who maintains it and go through it line by line. The awkward rules are the valuable ones. They encode years of lessons.

Keep the spreadsheet as the way in

People do not need to stop using Excel on day one. In our banking litigation platform the bank still sends its monthly list as a workbook. The system accepts the upload, validates each row, and turns it into typed records. A row with a problem is reported with its row number and reason, not silently dropped.

Excel becomes the import format. It stops being the database.

Put the rules on the server

In a spreadsheet, a rule is a convention. In a system, it is enforced. In the quality control platform we built for a manufacturer, a product can only be added to a delivery order if its most recent pressure test passed. The interface hides the button otherwise, and the server refuses the request even if someone finds a way to send it.

Generate the documents

If the spreadsheet exists to produce a document, generate the document. Certificates in that system take under a second and carry a QR code for verification. Letters in the litigation platform render from the firm’s own Word templates, and a missing field is flagged instead of going out blank.

Run both for a while

For a few weeks the old and new run side by side and the outputs are compared. When they match, and the team trusts it, the spreadsheet is retired. Nobody is asked to take a leap.

What you get

  • A record of who did what. Every change has an author and a time.
  • Several people working at once.
  • Access by role. Workers see their screen, managers see the dashboard.
  • Live numbers. How many in progress, pass rate this month, what is overdue.
  • Mobile access. A factory worker scans a QR code with a phone. Nobody carries a laptop to the shop floor.

Both systems above went live within ten weeks of kickoff. The litigation firm cut filing and checking time by 95%. The manufacturer has traced more than 20,000 products and delivery orders.

Where AI comes in

Later, and more easily than you would expect. Once the data is in a real system, an AI model can read incoming documents into it, flag unusual entries and draft routine outputs. None of that is practical against a folder of spreadsheets.

Fix the foundation first. It is the cheaper project and it makes every later one possible.

A place to start

Pick the spreadsheet that would hurt most if it were lost tomorrow. Count the hours spent on it each week. Our automation readiness assessment helps you put a figure on it and decide whether it is worth replacing.

Written by

Pikabyte Engineering

Pikabyte builds custom business systems, applied AI and secure cloud infrastructure from Malaysia. Talk to us.

Start a conversation

Want this applied to your business?

Tell us what is slowing the business down. You will talk to an engineer, not a salesperson, and get a straight answer on whether software is the right fix.