Operations platform: build, buy or keep the spreadsheet

An operations platform is the system a business runs its day-to-day work in. Each job, order or client moves through set stages, every stage has its tasks, documents and an owner, and everyone works from the same record instead of their own copy.

Most businesses already have one. It is made of spreadsheets, a shared inbox and a chat group, held together by the people who know where everything is. So the real question is not whether to have an operations platform, but what yours should be made of: the spreadsheet you have, a product you buy, or a system built around your process.

A spreadsheet is quick to change, everyone can open it and nobody needs training. It is often the right tool, as long as:

• one or two people maintain it and understand every formula in it
• the process has few steps and few handovers between people
• a mistake is cheap and easy to spot
• nobody outside the business needs to see or update it
• it holds little personal information about customers or staff.

If all of that is true, put your effort elsewhere. A tidy spreadsheet with a clear owner beats software nobody uses.

Spreadsheets fail quietly. In 2020, 15,841 positive COVID-19 test results in England were left out of the daily figures because some of the files carrying them exceeded the maximum file size (opens in a new tab). Few businesses ever hit a limit like that, but the warning signs usually show long before something breaks:

• the same data is typed into two or three places, and the copies disagree
• only one person understands how it works, and work slows down when they are away
• people overwrite each other's changes or keep their own copies
• customers and suppliers chase you by email for updates you already have
• approvals happen in chat, and nobody can show who approved what
• month-end means days of exports and reconciling
• customer or staff details sit in files that get emailed around.

The last one matters more than it looks. Human error caused 37% of the data breaches notified to the Office of the Australian Information Commissioner (opens in a new tab) in the first half of 2025, and in the report before that, the most common human error was personal information emailed to the wrong person (opens in a new tab). A shared system with logins and permissions keeps those files out of inboxes.

Buy when a product fits the way you already work. Job management, field service, CRM, practice management and accounting software are mature categories, and for many businesses one of them covers most of the process out of the box. You start sooner, and the vendor looks after the software.

Buying is usually right when:

• the process is standard in your industry and is not what sets you apart
• a product covers most of what you need without heavy customisation
• your team is willing to adjust the way it works to match the product
• the product lets you export all of your data and has an API, so it can be connected to your other systems later.

Before you commit, check three things: where the data is hosted, how you get all of it out if you leave, and how licences scale as the team grows.

Build when the process is part of what you sell, or when you already run several tools and still join them up by hand. A custom platform follows your stages and rules, keeps the records in one place and connects to the systems you keep.

Building is usually right when:

• every product you have tried needs a workaround at the core of the process
• the work crosses several tools, and people copy data between them every day
• customers or suppliers need their own view of the work, through a portal
• you need rules a product cannot express, such as approvals that depend on the amount or stages that depend on the type of job.

Building has trade-offs too. Someone has to look after the system after launch, and a custom platform needs a written scope, or it keeps growing. Start with the part that hurts most, keep everything else where it is, and connect the two.

It is rarely all or nothing. Many businesses keep their accounting software and CRM and build only the part that is specific to them: the operations platform in the middle, connected to both through their APIs. A signed deal in the CRM becomes work for the team, and everyone stays on the same record.

The same idea applies inside tools you already pay for. If the team works in Lark, Microsoft 365 or Google Workspace, simple approvals, forms and shared databases can often live there before anything custom is built.

1. Which steps does the work go through today, and who owns each one?
2. Where does each piece of data start, and where is it copied to?
3. What does a mistake cost, and how would you notice it?
4. Who outside the business needs to see or update the work?
5. Which tools are you keeping, and do they have APIs?
6. Who will look after the system once it is live, and in whose accounts will the hosting, domains and data sit?

Write the answers down. Whichever way you go, they are the start of a good scope.

Vetrox is an Australian IT company that designs and builds custom systems for businesses across Australia: operations platforms, internal tools, portals and the integrations between them. If keeping the spreadsheet or buying a product is the better answer for you, we will say so on the first call.