Most operations teams start on spreadsheets, and that is a sensible choice. A shared sheet is quick to set up, everyone knows how to use it, and it bends as the process takes shape.

The trouble starts when one file quietly becomes the system your whole team runs on, without anyone having designed it that way. If several of these signs sound familiar, your team has probably outgrown it.

Nobody is sure which version is the real one

There is a "final" copy, a "final v2" and another one saved on someone's laptop. Meetings start with a debate about whose numbers are right, and decisions wait until that is settled.

A related sign: only one person really understands the formulas. When they are on leave, the process slows down or stops.

The same information gets captured twice

An order, booking or job comes in by email or WhatsApp. Someone types it into one sheet, then someone else re-types it into another before the work can start. Every copy is another chance for a typo, and another argument about which entry to trust.

This is often the first thing a proper system fixes. Our build for by Rhay, an online bakery store, included a dedicated production and order-management workspace, so orders and production have their own home instead of sitting in separate lists.

Approvals happen in chat and email

Sign-offs, status changes and "is this done yet?" questions live in WhatsApp groups and inboxes, not next to the record they refer to. When something goes wrong, working out who approved what means scrolling back through weeks of messages.

Approvals work better inside the workflow they belong to. The moderated e-commerce marketplace we built for Terrain Tactics included seller onboarding, product approvals, feedback and administration, all inside the platform.

Everyone can see, and change, everything

The sheet holds client or staff details, and anyone with the link can view, copy or overwrite it. There is no record of who changed what, or when.

For South African businesses this goes beyond tidiness. Section 19 of POPIA asks a responsible party to secure personal information "by taking appropriate, reasonable technical and organisational measures". It is worth asking whether an open shared link meets that standard for your team.

A purpose-built system can limit each person to what their role needs, with proper user management behind it.

Reports take days to pull together

Weekly or month-end reporting means someone spends a day merging tabs and checking totals. By the time the report lands, the numbers are out of date, and next month it starts again from scratch.

When information is captured once, in one place, reports can come from that record instead of being rebuilt by hand each time.

The file keeps hitting its limits

The file takes ages to open, breaks when someone adds rows, or runs into a limit nobody planned for. Workarounds pile up: split files, hidden tabs, macros nobody wants to touch.

The best-known example comes from England in 2020. The BBC reported that "the badly thought-out use of Microsoft's Excel software was the reason nearly 16,000 coronavirus cases went unreported in England". Once the template reached its limit, "further cases were simply left off".

The lesson is not that spreadsheets are bad. It is that a critical process was running through a tool it had outgrown. As Prof Jon Crowcroft of the University of Cambridge told the BBC, "when you need to do something more serious, you build something bespoke that works".

Where Hardcode fits

If several of these signs apply, write down which ones and which workflows they affect. That list is the start of a brief.

Hardcode Studios builds ERP and business systems around the way a business already works, connecting teams, workflows, data, approvals and reporting, with role-based access. Our portfolio includes Tinpac, a customer-facing website and internal business system for a metal packaging operation, and Pygmalion Services, a corporate website for accounting and financial consulting with managed enquiries and administration.

For the practical side of scoping and building one, read build the ops system around the work. Our process starts by learning how your business works.