Field notes
We are too small for this. Are we?
Size is not how many locations you have. It is whether somebody does the same task by hand every week. A simple test for whether it is worth your time, the cases where you genuinely are too small, and the arithmetic to check.
"We are just one store." It is said as a reason to stop reading, and most of the time it is the wrong reason.
Size matters less than people think. Repetition matters more.
The actual test
If somebody in your restaurant does the same task by hand every week, you are big enough.
One location still has invoices to key in. It still has a schedule to build, a prep list to write, reviews to answer and a food order to place. Those tasks do not get smaller because there is only one of you. If anything they land harder, because the owner is usually the one doing them at eleven at night.
What a single store does not have is a district manager, an IT department or anyone whose job is to figure this out. That is a real constraint, but it is a time constraint, not a size one.
Do the arithmetic before you decide
Here is the calculation worth doing on a napkin.
Take one task. Say building next week's schedule takes an extra thirty minutes it does not need to. That is thirty minutes a week, which is twenty-six hours a year.
Now guess how long it would take to set up a better way. Be pessimistic. Call it ten hours, including the frustrating parts.
Ten hours of setup against half an hour a week saved pays for itself in about twenty weeks, a little under five months. After that it is free time for as long as you keep doing it.
If the setup is longer than a year's worth of savings, skip it. That is a legitimate answer and nobody should talk you out of it.
When you really are too small
There are honest cases.
The task happens twice a year. Anything seasonal and rare is not worth automating. Do it by hand and put a reminder on the calendar.
The data does not exist. If sales are mostly cash and never reach a system, there is nothing for a tool to read. Fix how the numbers get recorded first, or leave it alone.
The only person who would set it up has no hours at all. If you are the owner, the chef and the closer, even ten hours is a lot. Start with something that takes one evening rather than a project.
None of those are about location count. They are about frequency, data and time.
Small has an advantage
A group has to roll anything out across stores, get every general manager to agree, and live with the store that quietly keeps doing it the old way.
A single operator decides on Tuesday and it is how things work on Wednesday. No rollout, no committee, no consistency problem. That makes a small operation the easiest place in the industry to try something and see if it earns its keep.
Do not buy anything first
The most common mistake small operators make is reaching for a new subscription to solve a problem the software they already pay for can handle. Your POS, your scheduling tool and your accounting software almost certainly do more than you use.
Look there first. Buying a second tool to do what the first one already does is how a small operation ends up paying enterprise prices for nothing.
Pick one task
Not a transformation. One weekly task, the one you most resent.
For a lot of single-location kitchens that is the prep list, because it happens every day, it is cheap to get wrong, and you know by lunch whether the new version worked.
Do that one for a month. If it earns its keep, pick the next.
Not sure which task is costing you the most? Take the free check — eight questions, no email, and it names the two worth starting with in your building.