Skip to main content
Israr Ahmed Labs

Business Automation

When a small business should build its own management dashboard (and when it should not)

A custom system is not always the answer. Six signs that spreadsheets have stopped working, four reasons to wait, and how to start without a large project.

Israr Ahmed · · 3 min read

A spreadsheet is a good tool and often the right first answer. It is cheap, everyone understands it, and it can be changed in minutes. Many businesses should stay on spreadsheets for a long time. But there is a point where they begin to cost more than they save, and the honest question is whether you have reached it.

Six signs the spreadsheet has been outgrown

  1. The same information is typed in more than one place. Every copy is a chance for them to disagree, and sooner or later they will.
  2. Only one person understands it. If the business stops when that person is on leave, the sheet has become a single point of failure.
  3. Who can see or change what really matters. Salaries, patient or client records, prices and approvals should not be open to everyone with the file.
  4. You need approvals and a history. "Who approved this, and when?" is hard to answer from a spreadsheet and easy from a system that records every step.
  5. Several people edit at once and overwrite each other, or versions of the file are emailed around.
  6. Someone assembles the same report by hand every week. Work done the same way every time is work a system can do.

If three or more of these describe you, it is worth looking at something better.

Four reasons to wait

  • The process is still changing every week. Software hardens a process. Let the process settle first.
  • An existing product already does most of it. Buying is usually cheaper than building. A custom system earns its cost where your way of working is genuinely different.
  • Only one person would use it. The overhead of a system is rarely worth it for a single user.
  • Nobody will own it afterwards. A system needs someone who decides what it should do, and someone who looks after it. Without both, it decays.

If you do build, start small

The projects that go well begin with one workflow, not the whole business. Pick the process that hurts most, write down in plain words what it must do and how you will know it works, build it in working steps that you review on a test copy, and release it before starting the next. Real use will teach you more than a long specification.

Insist on these from any supplier

  • Your data is yours and can be exported at any time.
  • Permissions are enforced on the server, with roles that match how your business is organised, and an audit trail for sensitive actions.
  • You receive the source code and the documentation, so you are never locked in.
  • It runs where you choose and has a written backup and restore procedure.
  • Maintenance is priced openly, because a system that is not looked after stops working.

The right-sized answer

Sometimes the best advice is to tidy the spreadsheet, add a simple form, or adopt an existing tool. Sometimes it is a small custom dashboard for one workflow. Either way, the goal is the same: the people in the business spend their time on the work, not on keeping the information straight. If you would like a second opinion on where you stand, tell us about your process and we will say plainly whether building anything is worth it.

  • business automation
  • dashboards
  • spreadsheets
  • custom software

Updated . Need help with something like this? Get in touch.

Let’s talk

Have a project or a problem to solve?

Tell us what you are trying to achieve. We will reply by email with questions or a suggested next step.