Spreadsheet or custom tool? A simple way to decide

Use a spreadsheet. That's the short answer, and it's right more often than people want to admit.

Spreadsheets have a reputation as the thing you use before you get "real" software. In small businesses, they're often the real software. Your staff already know how to open one. It costs little or nothing. Anyone can see how it works, and when it breaks, someone can fix it.

A custom tool is worth building only when a spreadsheet has actually stopped working. Not when it looks messy, and not when it feels unprofessional.

Signs a spreadsheet is still fine

Fewer than a few thousand rows
A handful of people edit it, and not at the exact same moment
It's mostly lists, totals, and filtered views
Nobody needs to be blocked from seeing certain parts
It doesn't have to send anything anywhere on its own

If that sounds like your situation, stay put. Spend your effort on a cleaner layout, cleaning up the data, and a rule for who edits what.

Signs you've outgrown it

Two people overwrite each other's work, and it's costing you
The file takes a long time to open, or crashes
You have to hide parts of it from some staff, and a hidden tab isn't good enough
People have started making copies, and now there are four versions of "the real one"
Someone does the same copy-and-paste into another system every day

That last one may not mean you need a custom tool. Often it means you need a connection between two tools you already have. That's the middle option.

The middle option

Between a plain spreadsheet and a custom-built tool there's a lot of useful ground. A form that feeds a sheet. A booking tool that adds rows when someone books. An automation service that copies new entries from one place to another when they appear, so nobody retypes them.

Google Forms into Google Sheets is a good example. Customers or staff fill in a short form on their phone. Every answer lands as a new row. No logins to manage, no software to buy, and you can still sort and filter the sheet like normal. That handles a surprising number of "we need a system" problems.

Tools such as Zapier and Make can do the next step: when a row appears, send a text, add a calendar event, or email someone. Check current pricing and limits before you commit. They change, and the free versions have caps that surprise people.

Questions to ask before building anything custom

Could a form plus a sheet do 80% of this? If yes, start there and see what's left.
Does a product already exist for this exact job? Twenty minutes of searching can save weeks.
How many people will use it, and how often? A tool used by two people twice a week doesn't need to be a tool.
What happens when it breaks? If the answer is "we call the person who built it," that's a risk. Ask how you'll feel if they move away.
Who will maintain it in two years? Be specific. A name, not a role.

The last two matter most. Custom work has a hidden cost: somebody has to keep it running. APIs change, passwords expire, services shut down. A spreadsheet doesn't have these problems. Custom tools do.

When custom is the right call

It happens. Some good reasons:

You need something customers use, with their own logins, and no product matches
You've got a process that spans three systems, and the connections are too fiddly for off-the-shelf tools
You've already outgrown the middle option and the cost of staying is clear and large

If you're here, write down what it does in plain words before anything gets built. Then ask the builder to document it as they go, and to leave it in tools you can move away from. See the handoff document.

A rule of thumb

Build the spreadsheet version first, even if you're sure you'll need something bigger. Run it for a month. You'll learn what you actually need, which is usually less than you thought, and different from what you guessed. If you still need the custom tool, you'll be able to describe it precisely. That's worth more than any spec you could write on day one.