BlogLocal Business
Local Business

Do You Need Custom Software, or Just a Better Spreadsheet?

Paul EvansPaul Evans
6 min read
A person working on a laptop at a desk with snacks, emphasizing productivity and technology.

Most businesses do not need custom software. Some are losing real money every week without it. Here is how to tell which one you are, in about ten minutes.

Every business we work with has a spreadsheet that runs some part of the company. The orders board. The schedule. The list of who owes what. It started as a quick fix and it has been the system for six years.

The question I get asked, usually a bit sheepishly, is whether that is a problem. The honest answer is: sometimes. Here is how to tell.

You probably do not need custom software if

  • One person maintains the spreadsheet, and it takes them under an hour a week.
  • Nothing has gone badly wrong because of it. No double-booked crew, no order that shipped twice, no invoice that never went out.
  • An off-the-shelf product covers most of what you do. Scheduling, invoicing, a simple CRM and inventory are all solved problems with good software you can rent for the price of lunch.
  • The business is not growing in a way that multiplies the manual work.

If that is you, buy the subscription, tidy up the spreadsheet, and stop worrying. We will tell you the same thing on a call, and we would rather do that than sell you a project you resent.

You probably do need it if

The same information gets typed in twice

An order arrives by email, gets keyed into accounting, then keyed again into the schedule. Every retype is a chance for an error and ten minutes nobody gets back. Across a year, a single double-entry step is often a part-time salary. This is usually the cheapest thing to fix, and it is frequently where we start.

Growth means hiring a coordinator

If handling twenty percent more volume means another person doing manual coordination, the process is the bottleneck, not the people. Software should absorb that growth. Payroll should not.

Only one person understands the system

The workbook has forty tabs and formulas nobody else dares touch. That person goes on vacation and the business slows down. That is not a spreadsheet problem, it is a database and an interface waiting to be built, and it is a risk you are carrying every day.

You pay for three tools that almost fit

Three subscriptions, none of which quite match how you work, plus a manual step to bridge them. Sometimes the answer is keep them and connect them. Sometimes one purpose-built tool replaces all three and the subscriptions pay for the build inside two years.

Customers have to call to do simple things

Reorder, check a status, download an invoice, book a slot. If your customers phone for those, a portal that lets them do it themselves is not a luxury. It is the thing that lets you grow without adding a phone line. We built exactly this for a wholesale distributor and their stores now order without a call.

What it costs to find out for certain

We will not quote a software build from a phone call, because anyone who does is guessing. What we do is a paid discovery phase: we sit with the people doing the work, map what actually happens, prototype the risky part, and hand you a written scope with a fixed price. If the numbers say do not build it, you keep the document and you have lost a small amount rather than a large one.

The spreadsheet is not the problem. The spreadsheet becoming the system, with one person holding it together, is the problem.

The ten-minute test

  1. Write down every place the same piece of information gets entered more than once.
  2. Estimate the hours per week spent on those retypes and on chasing things through the spreadsheet.
  3. Multiply by what those hours cost, and by fifty.
  4. If the number is under a few thousand dollars, buy better tools. If it has a comma in it, talk to someone about building the thing that removes it.

We are happy to be that someone, and equally happy to tell you to keep the spreadsheet. Either way, you will know.

Paul Evans

Paul Evans

Founder & Engineer, Phaseable

I've been building software for 30+ years. I run Phaseable, a small engineering studio in Birmingham that designs websites, builds custom software and practical AI for businesses, and builds products with founders.

See a Problem Worth Building?

If this resonated — let's talk. We partner with founders who have niche industry problems and need a team to build the product.