I build apps, websites and automation for small businesses and founders, and most of the internal tools I build replace something that started as a perfectly sensible file. This is the same guide that lives on my site.

Spreadsheets are not the problem. The problem is the moment one becomes the only record of what your business did, and nobody dares to edit it. Keep the file while one person reads it and the numbers still match reality. Replace it when two people edit the same file, or when a total is wrong and nobody can say why.

Short answer:

  • Keep the spreadsheet while one person reads it and the numbers still match reality.
  • Replace it when two people edit the same file, or when a total is wrong and nobody can say why.
  • A dashboard is trusted only when every figure traces back to the rows behind it.
  • The usual first step is not a big system. It is one screen and one source of truth.

What are the signs it has outgrown the spreadsheet?

These are the ones I see, in roughly the order they arrive.

  • Two people edit the same file, and one of them overwrites the other.
  • There is a copy on someone's phone that is more up to date than the shared one.
  • A formula broke and nobody noticed for a week.
  • You cannot tell who changed a number, or when.
  • Adding a column means rebuilding three tabs and the summary.
  • The person who understands it is the person you cannot afford to lose.
  • A manager asks a question and the answer takes someone an hour to build.

None of those is about the size of the file. A small spreadsheet with three editors is already past the point where a file is the right tool, and a large one with a single careful owner can be fine for years.

The last two are the expensive ones. When answering a question costs an hour of somebody's time, the file is charging you a salary to do what a screen would do in a second. When only one person understands it, you are carrying a risk that has nothing to do with software.

What does a dashboard give you that a file does not?

Three things: one source of truth, roles, and a screen that loads on a phone in a warehouse or a cab.

What you need Spreadsheet A built dashboard
One number everyone agrees on Only if one person owns the file Yes, from one source
Two people editing at once Conflicts and overwrites Handled properly
Who changed what, and when Rarely, and never reliably Every change is recorded
Different views for different roles Tabs, and trust Real access control
Readable on a phone on site Poorly Designed for it
Feeds itself from your shop, bank or jobs By hand, or by a fragile link By a connection that can be monitored
Cost to start Nothing A build, then very little to run

The row that decides most projects is the last one before cost. A file gets its numbers from a person remembering to paste them. A built screen gets them from a connection, and a connection can be monitored, so you find out it stopped sending on the day it stopped rather than at the end of the month.

The row about roles is the one people underestimate. Tabs and trust are not access control. If a number should only be visible to the owner, that has to be enforced where the data is read, not by asking people to stay off a tab.

When the spreadsheet is the right answer

If one person maintains it, the numbers still match reality and nobody is waiting on it, leave it alone. Software should remove work, and a dashboard nobody opens is just a new thing to maintain.

The same goes for the tool you already pay for. If your shop platform or accounts package can produce the report, I would rather connect the two than build a screen that duplicates it.

  • One person owns the file, and it is part of their job.
  • The numbers still match the bank and the warehouse.
  • Nobody waits on it to answer a question.
  • A tool you already pay for can produce the same report.

A screen that duplicates a report your platform already produces is a bill without a benefit, and saying so is part of the first call.

How do I start, so the cost stays low?

I write down the six questions the owner asks every week, and build the screen that answers those. Nothing else. Small jobs start at $49, so a single report is a cheap way to find out whether this is worth doing.

After that first screen, the next ones are usually quick, because the data is already in one place and already trusted. That is the real saving: the second screen is not a second project.

The reason to start with the questions rather than with the data is that it fixes the scope. "Everything about the business" is not a screen anybody opens. "What sold yesterday, what is late, and what is owed" is.

Does a dashboard need AI?

Usually no. A dashboard is arithmetic and access control. AI earns its place on a separate job, like recommending a price or summarising what changed this week.

That distinction matters when you are getting quotes. If a proposal puts a model in front of a sum, ask what the model decides that arithmetic could not. Often the answer is nothing, and you are paying for a word.

What does it cost to run afterwards?

Very little for a small business: hosting and a database, often a few dollars a month at first. The real question is who fixes it when a feed stops sending, which is what a support plan covers.

I quote one fixed price after a free call and a written plan, so you know the number before I start. After launch I stay on as your engineer on a monthly plan from $149 a month, for as long as it is useful. The code and the accounts are in your name, so the plan is a choice rather than a lock-in.

Takeaways:

  • Replace the file when it stops being one person's job.
  • Start with the questions the owner asks every week.
  • Every figure on the screen should trace back to the rows behind it.
  • If an existing tool can produce the report, connect it instead.

Q: Can you move my spreadsheet into a database?
A: Yes, and that is usually the first step. The old file keeps working while the new one is checked against it, so nobody has to trust a number they cannot verify.

Q: Will my team actually use it?
A: They use it when it is quicker than the alternative and works on the phone in their pocket. That is why I build around the process they already follow instead of asking them to change it.

Q: Can it show my ecommerce numbers from more than one shop?
A: Yes, and that is the most common reason people come to me. One screen for every shop, with the numbers that matter to you rather than the ones a platform chose to show.

Sources:

The full guide, with its sources, is at https://najam.dev/guides/dashboard-or-spreadsheet/. If you want the short version of how I work: one engineer, one fixed price agreed in writing before anything starts, and the code and the accounts stay in your name. More at https://najam.dev