When a spreadsheet is enough, and when you need your own system

Spreadsheets are underrated

We have talked plenty of Toronto businesses out of building software. A spreadsheet is free, everyone can read one, it changes in seconds, and it never has an outage. For a lot of businesses it is the correct answer for years.

A spreadsheet is still the right tool when:

• One or two people touch it, rarely at the same time
• You are under a few hundred rows that matter
• Nothing terrible happens if a cell is wrong for a day
• You are still working out what the process even is

That last point matters most. If your process is changing every month, software will freeze a bad version of it. Keep it in a spreadsheet until it stops changing.

The middle option most people skip

Between the spreadsheet and the custom build there is a layer that solves most problems: existing tools, connected properly.

Your booking tool talking to your calendar. Your form feeding your invoicing app. Your enquiries landing in one shared inbox with tags. A shared database tool where a spreadsheet has become dangerous.

This costs a fraction of a build and it fails safely. Try it before anything else. If you still hit a wall, the wall itself tells you what to build.

The five signs you have outgrown both

Not one of these on its own. Two or three together, and building becomes the cheaper path.

1. The same data is typed in more than twice

A customer's details go into a form, then a spreadsheet, then an invoice, then a job sheet. Every retype is a chance to be wrong, and the versions drift until nobody knows which is true.

2. Only one person can do it

When a process lives in someone's head and their private spreadsheet, you cannot delegate it, and you cannot take a holiday. That is not a software problem yet — but it is the most common reason a business stops growing.

3. You are paying per user for features you don't use

Five staff on a $60-a-month platform is $3,600 a year, forever, and you use a tenth of it. Three years of that funds a tool that does exactly your job and nothing else.

4. Customers feel the mess

Double bookings. Quotes sent twice. Someone asked for their address three times. When the internal chaos reaches the customer, it costs revenue and not just patience.

5. You can't answer a simple question

How many jobs did we do in Scarborough last quarter? Which service makes the most margin? Which quotes never got followed up? If answering takes an afternoon of copying and pasting, you are running blind on decisions that matter.

What building actually looks like when it goes well

Small. The projects that succeed do one job, for the people who already do that job by hand.

• A job board: enquiry in, quoted, scheduled, done, invoiced. One screen, five states.
• A client portal where customers see their documents and don't email you for them.
• An internal dashboard that answers the three questions you ask every Monday.

The ones that fail try to replace the whole business at once, take nine months, and land on a team that has already invented workarounds.

Our rule: the first version ships in weeks, replaces one spreadsheet, and is used daily before anything else gets added.

Questions to ask any supplier

• Do I own the code and the data, in writing?
• What is the fixed price of a first working version?
• What does it cost to host and maintain per month, honestly?
• What happens if you disappear — can another developer pick this up?
• What are you not building in version one?

If the answers are vague, the project will be too.

The honest order of operations

• Keep it in a spreadsheet while the process is still moving.
• Connect the tools you already pay for.
• Build only the piece that is still broken after that.

Most businesses never need step three, and that is a good outcome, not a failure.

If you're not sure which step you're on, book 30 minutes and describe how the work moves through your week. We'll tell you whether it's a spreadsheet, a connection, or a build — and we say spreadsheet more often than you'd expect.