Spreadsheet Purgatory for Small Teams: When You're Five People, Not Five Hundred

Right-sizing internal tooling advice for small businesses with no IT department: what to skip, what still matters, and how to start.

You run a five-person business. The owner does the books, one person handles customers, two do the actual work and someone part-time keeps the whole thing glued together. Your “systems” are a shared workbook, a calendar and a lot of memory. You read advice about governance boards and change management and wonder who on earth has time for that.

Fair question. Most internal tooling advice assumes a company with departments. This post translates it for a team where the “IT department” is whoever is least scared of the settings menu.

The problem is the same, just smaller

Small teams fall into spreadsheet purgatory for the same reasons big ones do. A sheet starts as a quick list, grows columns, gets copied, and slowly becomes the thing the business runs on. The 7 Signs Your Spreadsheet Has Become a Database apply whatever your headcount.

What changes is the risk profile. In a large company, a broken spreadsheet costs a team some time. In a five-person business, it can lose a customer, a payment or the only record of a job. And the knowledge problem is sharper: if the one person who understands the booking sheet is off sick, there is no one down the corridor to ask.

So the motivation to fix it is often stronger in a small team. The capacity to fix it is what is missing.

What you can safely skip

Plenty of advice in this series is written for larger organisations. At five people, you can usually drop or shrink:

Formal governance. You do not need a steering group. You need one person who decides and a quick weekly chat.
Elaborate permission schemes. If everyone does a bit of everything, two roles (owner and staff) are probably enough. Keep sensitive data like pay and personal details separate.
Long parallel running. With small data volumes, you can often move over in a week rather than a month.
Detailed documentation. A single page explaining what goes where, plus a short video, beats a manual nobody reads.
Custom builds. At this size, buying or configuring almost always wins. Buy, Configure, or Build? lays out the trade-offs, but you can probably skip straight to the first two.

What you still cannot skip

Some things matter more, not less, when you are small:

Writing the process down. Even a half-page of “when a job comes in, this happens, then this” will expose steps that only live in someone’s head. Process First, Tool Second has a simple template.
Unique IDs. Give every job, customer and invoice a reference number from day one. It costs nothing and saves you the first time two customers share a name.
Backups and exports. You have no IT team to rescue you. Know how to get your data out, and do it monthly. Backups, Exports and Exit Plans explains why.
One source of truth. If the new tool and the old sheet both hold job details, people will update one and not the other within a week. Pick a date and switch.

Choosing tools when there is no IT department

Small teams should choose tools that someone non-technical can set up and maintain. A few practical tests:

Question	Why it matters at five people
Can the least technical person add a record without help?	They will be the one doing it at 6pm on a Friday
Can you set it up without writing code?	Nobody on the team writes code
Does it work well on a phone?	Half your work probably happens away from a desk
What does it cost at 5 users and at 15?	You may grow, and per-seat pricing scales fast
Can you export everything in a standard format?	You need an exit if the vendor changes terms

Resist the urge to buy one platform for everything on day one. A no-code database platform for jobs and customers, plus your existing accounting software, is often all a small team needs. Avoiding Tool Sprawl is worth reading before you add a third.

Start with the process that hurts most

Do not try to migrate the whole business. Pick the one spreadsheet that causes the most pain. For a small trades business, it is usually the job tracker. For a small agency, it is often client projects. For a shop, it is stock.

Say your job sheet gets updated by three people, double-bookings happen about once a month, and the owner spends Sunday evenings checking it. That is the one. Move just that, live with it for a month, then decide what is next. Your First Internal Tool: A Weekend-Sized Starter Project walks through how to scope that first move.

Make one person the owner

In a small team, the risk is not a bureaucratic bottleneck. It is that nobody owns the tool and it slowly fills with half-finished records and fields nobody understands.

Pick one person to own it. Their job is small but real: add new users, make small changes, check data is tidy once a fortnight, and run the monthly export. Give them an hour a week for it, written into their week rather than squeezed in.

If the owner is also the business owner, that is fine, but make sure at least one other person knows how to do the basics. A five-person business with one person who understands the system has just rebuilt its old problem in a new tool.

Be realistic about time

Nobody in a small business has spare days. Budget the work in small blocks: two hours to write down the process, a half-day to set up the tool, an hour to move the data, an hour to show everyone. Spread over two or three weeks, that is manageable alongside normal work.

What you get back is usually obvious within a month. Fewer “has anyone called this customer?” messages, no more Sunday evening checks, and the ability to take a holiday without the business losing track of itself.

Where to start this week

List every spreadsheet the business relies on and circle the one that causes the most trouble.
Write a half-page description of the process that sheet supports, including who does what.
Try two no-code tools on a free trial, and ask your least technical teammate to add a record in each.
Decide who will own the new tool and agree an hour a week for it.