Outgrown the spreadsheet? When a custom web or desktop app makes sense
Plenty of small businesses in New Zealand run on a shared spreadsheet, and that's fine. Spreadsheets are flexible, familiar to many people, and often inexpensive to start with. I'd never tell someone to replace a spreadsheet that's working.
The question is what happens when it stops working, and how to tell the difference between "this is a bit annoying" and "this is costing us real time and mistakes".
Signs you've outgrown it
- Several people edit it at once and you regularly find overwritten rows or "final_v3_REAL" copies.
- The same data is typed in twice: into the spreadsheet, then into the accounting system, then into an email to a customer.
- Only one person really understands the formulas. If they're on holiday, things stall.
- You need different people to see different things. Staff shouldn't see margins; customers should only see their own jobs.
- Mistakes are expensive. A wrong quantity or a missed booking costs money or a customer.
- You're doing the same steps every day that could clearly follow a rule.
If only one of these applies, try fixing the spreadsheet first: lock cells, split tabs, add data validation, or try an existing tool built for your industry. Off-the-shelf software is usually cheaper than custom, and you should look properly before commissioning anything.
When custom actually makes sense
Custom software earns its place when your process is genuinely specific to your business, existing products would force you to change how you work for the worse, and the time saved is significant and ongoing. It's not about being fancy. A good small custom app often looks plain: a few screens, a clear form, a list, and an export.
Web app or desktop app?
A web app (for example built with React or Next.js and a Node backend) runs in the browser. It suits you when:
- people work from different places, or on phones and tablets;
- you want one up-to-date copy of the data;
- customers or contractors also need access.
The tradeoffs: it needs hosting, logins if the data is private, and ongoing security care. It usually depends on an internet connection unless offline use is deliberately designed in.
A desktop app (I use Electron, which builds apps for macOS and Windows from web technologies) installs on a computer. It suits you when:
- the work happens on one or a few machines in a shop, workshop or office;
- it needs to work with local files, printers, scanners or other hardware;
- it should keep working when the internet doesn't (which still has to be designed deliberately, along with how data syncs later).
The tradeoffs: it still needs security care and, where data is private, access control; updates have to reach each machine, the app has to be packaged and, for a smooth install, code-signed for each operating system, and sharing data between machines needs a plan.
Sometimes the honest answer is "both, later": start with whichever solves today's problem and keep the data in a form that can move.
How to start small
- Write down the process as it is now, including the workarounds. A page of bullet points is plenty.
- Pick the single most painful step. Not the whole business, just one step.
- Build the smallest thing that removes that step, then use it for a few weeks.
- Keep an export. Your data should always be able to come back out as a CSV or spreadsheet. That protects you if the app or the developer goes away.
- Agree who owns the code and where it lives before work starts.
Questions to ask any developer, including me
- Can I get my data out at any time, in a standard format?
- Will I own the source code?
- What does it cost to keep running each month (hosting, accounts, certificates)?
- What happens when the operating system or browser updates?
- Is there an existing product I should try first?
If the answer to that last one is "yes", a good developer will tell you.
Where I fit in
I build React/Next.js/Node web apps and Electron desktop apps for macOS and Windows, and I try to keep them simple to run. If you have a spreadsheet or manual process that's started to creak, tell me about it. Sometimes the useful answer is a small app; sometimes it's a better spreadsheet.