Nothing has crashed. No formula is broken. Yet three people have stopped working to answer one ordinary question.
That is a useful point to start asking whether you have outgrown your spreadsheet.
When should a business replace its spreadsheet? When running the work depends on repeated copying, chasing updates or one person remembering the rules. First check whether clearer ownership or your existing software can solve the problem. A replacement earns its place when it can handle the handovers and exceptions more reliably.
The test is what happens between the cells
A spreadsheet can be an excellent place to calculate a price, compare options or explore a forecast. A large workbook doing those jobs well may need no replacement.
The difficulty starts when the sheet becomes the place everyone goes to find out what to do next. It holds the bookings, tells the workshop which job is ready, or decides whether stock can be promised. At that point, changing a cell can affect somebody else’s work.
Ask what happens after an update. Does the right person see it? Can somebody tell who changed it and why? Does a cancelled order release its stock? If those answers live in phone calls and memory, the spreadsheet is only part of the system. Your team is doing the rest.
Five signs you have outgrown your spreadsheet
1. The same details get typed in twice
A quote is accepted, so somebody copies it into a job sheet. Later, somebody copies it into an invoice. Each copy takes time and creates another place to correct when the customer changes their mind.
Follow one changed order. If the price, quantity or delivery address must be corrected in several places, that is a better clue than the number of rows in the file.
2. People ring round for the latest position
“Is it ready?” “Has it come back?” “Can we promise two for tomorrow?” These questions interrupt the people doing the work because the record does not hold an answer everyone trusts.
Stock is a good example. Ten on the shelf does not mean ten available if seven are reserved and one is damaged. We explored that distinction in why stock answers need reliable business records.
3. One person knows how it all works
They know which tab is current, what the colours mean and which customer always needs a different price. Their knowledge is valuable. Having to ask them every time makes it difficult for the business to cope when they are away.
A useful first step is to write those rules down. Buying software before understanding them simply moves the uncertainty into a new screen.
4. Work waits to be typed up
The engineer finished the visit this morning. The office will find out when the paper sheet comes back tomorrow. Until then, nobody can confidently update the customer or prepare the invoice.
A phone or tablet job record may close that gap while leaving the accounts package alone. Where signal is unreliable, offline capture and a clear sync status need to be part of the design.
5. Customers find the mistakes first
A double booking, an old price or an order that never reached production becomes a customer-service problem before anyone spots it internally.
Look at the last mistake and ask which check would have caught it. A system needs to enforce that check or make the exception visible. A tidier dashboard on its own will not do it.
Follow one order before you buy anything
Imagine a small workshop quoting for twelve items. The customer accepts, then changes the quantity to ten. The office updates the quote, but production still has the original job sheet. Invoicing starts from a copy made before either change.
This is an illustrative example, not a reported customer result. It shows why “put it all in a database” is an incomplete brief.
The useful requirement is more specific: keep the accepted revision, show the change to production, identify work already started and prepare the invoice from the agreed record. Decide who can approve changes and what happens if the order is cancelled halfway through.
Those are the rules that make a business system useful. The screens come afterwards.
What should replace the spreadsheet? Four possible answers
Improve what you already have
If the problem is unclear ownership, inconsistent entry or people using different copies, begin there. An agreed location, clearer responsibilities and a few checks may be enough. Keep a spreadsheet that still does its job well.
Use a ready-made product
If your process is common, an existing job-management, stock or booking product may fit. Take a real example into the demonstration, including a changed order and a cancellation. Check the awkward bits before being persuaded by the overview screen.
Connect the missing step
Your accounts package may be fine. Your field team may only need a better way to send completed job details to the office. A form, an integration or a small app can be the right-sized answer. Confirm that the existing software supports the connection before committing.
Build around your process
Bespoke software becomes worth comparing with off-the-shelf options when your pricing, booking rules or handovers repeatedly force people outside standard products. Start with one process and agree how you will judge whether the change worked.
Put a number on the repeated work
Ten minutes spent thirty times a week is five hours. Across 52 weeks, that is 260 hours. Across 46 working weeks, it is 230. Use the number of weeks your business actually does the task.
That measures time spent. The saving depends on what changes. Someone may still need to check exceptions, approve changes and correct missing information. Count the work that remains, along with setup, data transfer, training, hosting and support.
Try your figures in the spreadsheet campaign’s checklist and time calculator. The question is whether the change would remove enough avoidable work to justify its whole cost.
What to do this week
Choose one recent job. Follow it from start to finish.
- Write down every place its details were entered.
- Mark each point where someone waited, chased or checked another record.
- Include a change, a mistake or a cancellation.
- Ask the people doing the work which handover they would fix first.
- Describe the result you need in one sentence: “The office can see completed visits without waiting for paper”, for example.
You now have a useful starting brief. It tells a supplier what the business needs to achieve and gives you something concrete to test their answer against.
Bring us the spreadsheet that causes the trouble
Our commercial interest is straightforward: Inferred builds business systems, field apps and customer portals. A Sussex sign maker still uses the quote, job sheet and invoice system we built in 2005. We also know that a new build is not the answer to every awkward workbook.
The Outgrown Check is a free fifteen-minute conversation about what your spreadsheet manages, who uses it and what goes wrong. We will help identify which options are worth investigating and what needs to be understood before anything is priced. No technical brief or spreadsheet upload is needed.
Request your free Outgrown Check →
About this guide
This is Inferred’s practical guidance, accompanying our Have you outgrown your spreadsheet? booklet. The workshop example is fictional and the time calculation is illustrative. Related reading: bespoke versus off-the-shelf software and our published sign-making system story.