DrinkOwner of a 15–40 seat café or drinks shop

When I roster next week, I want staffing to match real footfall, so I neither pay for empty hours nor lose customers to queues.

Khi tôi xếp ca cho tuần tới, tôi muốn số người trực khớp với lượng khách thật, để không trả lương cho giờ vắng và không để khách bỏ đi vì chờ lâu.

Job context

Who: An owner rostering three to six part-timers
When: At each week's end for the next
Trigger: An afternoon with two idle staff and a morning with a long queue
Situation: Hourly footfall is remarkably regular and has never been written down
Constraints: Staff need shifts long enough to be worth coming in, and they have classes

No hourly footfall data
High
The till holds it and nobody has ever opened it.
Root cause: Reports are designed for daily revenue, not for the shape of a day
Nobody takes short shifts
High
The two peak hours are what the shop needs and what nobody wants.
Root cause: A worker's travel cost does not scale with shift length
Understaffing degrades quality immediately
High
A little rush changes the cup, and customers notice.
Root cause: Quality depends on time per cup
Weather changes footfall
Medium
An afternoon shower is enough to change a whole shift.
Root cause: The roster is set before the weather is known
Staff swap shifts without telling anyone
Medium
The written roster differs from reality, revealed only when something goes wrong.
Root cause: Swaps happen in a group chat nobody manages

A solution is not the same thing as a product — a customer can hire a behaviour or a workaround too.

A rostering app
Product
Arranges the roster and knows nothing about hourly demand.
The till's hourly sales report
Product
Exactly the needed data, buried in a screen nobody opens.
Call someone in when it gets busy
Workaround
Reacts after the queue forms, and depends on someone being free.
A group chat for swaps
Behaviour
The shop's actual rostering system, living outside every record.
Hand-count customers per hour for a week
Workaround
Owners collect by hand the data the till already holds.

Tills report the day's revenue while rostering needs the day's shape.
Why existing solutions fail: Daily revenue is the number owners are asked for and accountants need; hourly shape is demanded by nobody, so it sits three clicks away and nobody clicks.
Potential opportunity: Putting the hourly shape on the shift-opening screen, exactly when the rostering decision is made.
The shop needs exactly two peak hours while the worker's travel cost does not scale with shift length.
Why existing solutions fail: Every rostering tool optimises for the employer; none prices the worker's journey, so short shifts always look cheap on screen and are always refused in life.
Potential opportunity: Pairing the short peak with other work so those two hours become a shift worth travelling for.