When Excel stops being enough

Let’s say it out loud: spreadsheets are fantastic. They are free to start, everyone knows them and you can build a working tool in an evening without asking anyone for permission. Plenty of successful companies were run on a single file called “Orders_final_v3_REAL.xlsx” for years. This post isn’t here to bully your spreadsheet. It’s here to help you notice the day it quietly stops being a tool and becomes a risk.

Signs the spreadsheet is straining

The classic first sign is the version problem. There are three copies, nobody is sure which is current, and the phrase “wait, who changed this?” is part of your weekly vocabulary. Next comes the one-person dependency: only Maria understands the formulas in column R, and Maria has just announced her holidays. Then the file starts to groan: it takes a minute to open, formulas break when somebody inserts a row, and the macro that “always worked” now throws an error nobody can read.

There are quieter signs too. You copy the same data from one place into another every day, say from emails into the sheet and from the sheet into the invoice. Several people need to work at the same time and keep overwriting each other. Customers or suppliers need to see their own status, and you answer by sending screenshots. You need to control who may see what, but a spreadsheet is either shared or it isn’t. You can’t answer “what did this look like last Tuesday?” because history lives in someone’s memory. Any two or three of these together are a strong hint.

The hidden cost

The expensive part of a strained spreadsheet is rarely the file itself. It is the time people spend double-checking numbers they don’t trust, the order that shipped to the wrong address because a cell shifted, the quote sent with last month’s price, the afternoon lost hunting for a bug in a formula. None of that shows up as a line in your budget. It shows up as tiredness, small embarrassments and a quiet reluctance to change anything, because everyone is afraid the whole thing will fall over.

What “custom software” really means

It doesn’t have to be a giant system with a three-year plan. In most cases it starts as a small web application that does the job of your spreadsheet properly: one place for the data, logins with the right permissions, forms instead of free cells, automatic calculations, a history of changes, and simple reports on one screen. It can send an email when an order changes status, create the invoice for you, or let a customer log in and see where their job stands. It does exactly the steps your business does, and nothing you don’t need.

Off-the-shelf, ERP or custom?

Be honest about the options, because the best one is sometimes the boring one. If your process looks like most companies’ processes, such as standard invoicing or basic CRM, a ready-made tool is probably cheaper and faster, and you should buy it. A full ERP makes sense when many parts of the company, such as stock, purchasing, sales and accounting, must share one set of numbers, and is usually configured and adapted rather than built from nothing. Custom software earns its place when your way of working is your advantage, when ready tools force you into awkward workarounds, or when what you need is a connection between systems that don’t talk to each other.

Often the answer is a mix: keep the accounting program you trust, and build a small piece of software around it that handles the part nobody sells. Integrations are not a lesser kind of project. For many companies they are the most valuable one.

Start with a first version, not the whole dream

The way to avoid a painful project is to shrink it. Pick the one process that hurts the most, for example order handling or quotes, and build only that. Sit with the people who use the spreadsheet every day and watch them work, because the real process is always a bit different from the one in the manager’s head. Write the main steps and the awkward exceptions on one page. Then build a first version that covers the everyday path, let the team use it for a few weeks next to the old sheet, and improve it from real feedback.

Moving the data is its own small project and deserves attention. Old spreadsheets contain typos, duplicate customers and dates written seven different ways. Plan to clean it as you import it, and keep the old file as an archive until you’re sure nothing was lost. Think about training too: a tool that people hate will be quietly replaced by a new spreadsheet within a month. Involve the team early, listen to their complaints about the old file, and make the new thing easier than the old thing from day one.

Questions to ask before you build

Who will use it every day, and what do they hate about the current sheet? What happens if the system is down for a day? Who owns the data, and who may see which part? Which other tools must it talk to? Will the code and data be yours, hosted where you can move them, with a clear way to continue if you ever change developers? How will it grow when the business doubles? A good partner asks you these questions before quoting anything, and tells you when the answer is “you don’t need custom software yet”.

We build web applications, mobile apps, ERP systems and integrations, and we like to start small. If your business is held together by a spreadsheet and Maria’s goodwill, send us a screenshot with the sensitive numbers blurred. We’ll tell you whether it needs custom software, a ready tool or just a tidier sheet.

Rastezh DigitalThe studio team