Nearly every system we have built replaced a spreadsheet. Not a bad spreadsheet either. Usually a good one, built by someone competent, that held the business together for years and then stopped. Spreadsheets do not degrade gradually. They work, and then one Tuesday two people need the same row at the same time and you lose an afternoon of orders.
If none of these is happening, keep the spreadsheet. We will tell you that on the call and it will not have cost you anything.
Concurrent edits, overwritten rows, someone working from a copy that was current an hour ago. The most common trigger, and the hardest to fix in place.
Nested formulas, hidden columns and a macro nobody can read. The business now depends on a document only one former employee understood.
Answering what is happening right now takes three phone calls, because the file records what happened rather than what is happening.
A number changed and nobody can say who changed it, when, or what it was before. That gets serious the first time it involves an invoice.
Not a bigger spreadsheet, and not a database with a form on top. A system shaped like the work: a live view of what is happening today, records that cannot be edited into an invalid state, permissions so people see the parts that concern them, and the exports your finance team will ask for in week two.
Jobs, orders, stock or cases as they stand right now, rather than as they were last saved.
Your pricing, your approvals, your statuses, applied rather than remembered.
Staff see what they need, managers see the team, finance sees the money.
Who changed what, when, and what the value was before they changed it.
Because the spreadsheet is not the enemy. Being the only copy of the truth is.
Including the formulas, the hidden columns and the conventions nobody wrote down.
The gap between how a process is described and how it is done is where projects go wrong.
Something your team can run a real week on, rather than a finished system you meet at the end.
Historical records come across, so the new system is not day one of your history.
Documentation, a deployment runbook, and the code sitting in your own repository.
The clearest signal is concurrency. If two people need the same file at once and you have started coordinating that by message, the spreadsheet has stopped being the right tool. The second is dependence on one person. If only one member of staff can safely change the formulas, you are one resignation away.
One price for the build, agreed at discovery before anything starts, with a first production version typically four to eight weeks out. A single focused replacement, one process rather than a whole operation, sits well below both. The cost tracks how many roles need separate permissions.
Often yes, and if that fits we will say so. Those tools are strong at structured records and weak at unusual rules, hardware and deep permissions. The honest test is whether your process is standard. If it is, buy something. If your process is the business, building costs less over a few years.
No. Migrating the existing rows is part of the work rather than an extra. We map the spreadsheet's columns onto the new schema, run the import against a copy, and reconcile the totals with you before anything goes live. Nothing gets thrown away.
We aim to get a usable first version in front of the people doing the work within weeks, then extend it while they use it. A system that arrives complete after six months is a system nobody has tested against a real Tuesday, which is when it will break.
Then you should. Every build ships with CSV and Excel export, because operations and finance teams always need the data out. The goal is to stop the spreadsheet being the only record of what happened, not to take Excel away from people who are fast in it.
Describe what you’re building, what it has to do and when it needs to be live. You’ll get back the architecture we’d use, the trade-offs, and a realistic timeline, before anything is signed.