When the Owner Is Also the Manager
A venue run by its owner is usually run well and is usually one person deep. What actually fails when that person is unavailable, and the order to fix it in — starting with the parts that cost nothing.
The owner opens, closes, does the rota, handles the suppliers, knows every regular, and settles anything difficult at the door.
It works. It works better than most managed venues, which is exactly why it goes unexamined for years.
Then they are ill for a week, and the week costs more than a year of the alternative.
What actually fails first
Not the obvious things. The floor runs; the staff know their jobs.
What fails is everything with no second holder:
Decisions with no rule. How much can be comped, whether this guest is let in, whether that supplier is paid early. The staff are not incapable — they simply have no authority and no stated policy, so everything queues.
Knowledge with no record. Which regular is which, who is not allowed back and why, what was agreed with the landlord.
Access. Banking, the booking system, the supplier accounts, the utility contracts. Frequently all under one login and one phone.
⚠️ Access is the one that turns a bad week into a crisis, and it is the cheapest to fix.
The order to fix it in
By cost, cheapest first. This matters, because owner-operators have very little spare time and the usual advice ("hire a manager") is the most expensive item on the list.
One — access. An afternoon. A second person able to reach banking, the booking system, and the key supplier accounts. ⚠️ This has real security and legal implications — who may authorise payments, what your bank permits, what your insurance requires — so set it up properly rather than by sharing a password. That is a conversation with your bank and your accountant, not a workaround.
Two — the rules that are currently in your head. A week of noticing. Every time you make a judgement call, write the rule in one line. Comp limits, entry refusals, when to call you. After thirty of these you have a policy, and you did not sit down to write one.
Three — the knowledge that is currently in your memory. Guest history, notes on regulars, what happened with that supplier. This is the slowest to build and the one that pays for itself first, because it is what makes anyone else's judgement decent.
Four — the second person. By the time you get here, the job is possible for someone else to do, which is the reason hiring one usually fails when it is tried first.
The trap
"Nobody can do it like I can."
Frequently true, and it is also the description of a business that cannot be sold, cannot be scaled, and cannot survive a broken leg.
⚠️ The honest version is: nobody can do it like you can, because nothing you know has ever left your head. That is fixable, and it is a different problem from talent.
The one-week test
Before anything breaks, pick a week and be unavailable for the decisions — present, but not deciding.
Write down every time somebody had to ask you anyway. That list, in one week, is your entire dependency map, and it costs nothing to produce.
Most owners are surprised by how short it is. Five or six recurring questions cover most of it, and each one is a rule that could have been written down years ago.
What this is really about
Not succession, not selling, not scale — though it enables all three.
It is about the week you do not choose. Illness, a family emergency, a genuinely necessary holiday. Those arrive without notice, and the preparation for them is the same preparation as for everything else.
Three to hold
Number of systems only one person can reach. The crisis number.
Recurring questions per week that only you can answer. The dependency map. It should fall over time.
Days since the last time you were unreachable for a full shift. If the answer is "I don't know" or "never", that is the finding.
Where the record has to sit
Rules in your head, guest history in your memory, and access on your phone is a venue that runs on one person by construction. Every fix above is the same fix: move it somewhere another person can reach.
tasteck keeps guest history, notes, and staff access on shared records, so what you know is not the same thing as what only you can see.
It works, and it is one person deep. Both are true, and only the first one gets noticed.
Related articles
Your Pour Cost Is a Schedule Problem
Most venues chase pour cost with tighter counts and better jiggers. The variance usually tracks who was behind the bar, not what they were pouring. How to read pour cost by shift, and why the fix is often on the roster.
Your Coat Check Is a Queue Problem
In cold markets the coat check decides how your night starts and how it ends. What the queue costs in unbought first drinks and in clearance time at close, and the three changes that move it without new staff.
Your Best Night Was Not Your Best Night
The night with the highest take is rarely the night that earned the most. What has to be subtracted before a night can be ranked, and why the answer usually reorders the whole week.
Map out your operations in 5 minutes
Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.
Your answers are not stored. The assessment runs entirely in your browser.
Try tasteck free for 30 days
No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.
- No card required
- Free data migration support
- All features unlocked for 30 days