What Small Businesses Actually Need From Software (Lessons From Building for Auto Shops)

Most small businesses are drowning in software that was never built for them. They've got a generic CRM they use 10% of, three spreadsheets, a notebook by the register, and a tool the last office manager set up and nobody understands anymore.

When I built GreaseGoose, software for small auto repair shops, the biggest lesson wasn't technical. It was this: a tool built for one specific trade beats a flexible tool built for everyone. Every time.

Here's what small businesses actually need - and what they don't.

They need it to match how they already work

The fastest way to get a tool rejected is to ask a shop to change how they run to fit your software. The owner has a system, even if that system is messy. Good software paves the cow path - it speeds up what they already do, in the order they already do it.

Before writing a line of code, I sat with how a shop actually moves a car through: phone rings, car comes in, work gets written up, parts get ordered, customer gets called, invoice goes out. The software just made each of those steps faster. No retraining, no "new process."

They need fewer features, not more

Enterprise software competes on feature lists. Small-business software competes on not making the owner feel stupid. Every extra button, setting, and tab is a tax on someone who has nine other things on fire.

The discipline is brutal: for every feature, the question isn't "would this be useful?" - almost everything is useful. It's "will this still be used in week three, by a tired person, without a tutorial?" Most features fail that test.

They need it to just work, unattended

A small business does not have an IT person. There's no one to restart the server, rotate a key, or notice the backups stopped running. So the software has to:

• Run on managed infrastructure that heals itself.
• Back itself up without anyone thinking about it.
• Fail safely and visibly, not silently.
• Survive the owner ignoring it for months at a time.

This is exactly why the "it works on my laptop" prototype never makes it into a real shop. Working isn't the bar. Unattended reliability is the bar.

They don't need cutting edge - they need trustworthy

Nobody running a repair shop cares what framework you used. They care whether their customer data is safe, whether the thing is up when they open at 7am, and whether a real person answers when something breaks. Trust is the entire product. The tech is just how you deliver it.

What this means if you're choosing or building software

• Niche beats general. A tool built for your trade will fit better than a flexible platform you have to bend.
• Simple beats powerful. If your team needs a manual, it's too complex.
• Boring infrastructure is a feature. "It just runs" is worth more than any flashy capability.
• Support is part of the software. A human you can reach matters more than a roadmap.

This is the whole thesis behind how I build: pick a real, specific problem a small business has, build exactly the software that solves it, ship it on infrastructure that runs itself, and stick around to keep it alive.

If that sounds like what your business is missing, start a project and tell me about the messy spreadsheet you're trying to kill.