A Newtown cafe owner reclaimed 8 hours weekly by automating ordering, rostering, and supplier follow-ups. Here's exactly what we built.
Article text
The notebook had coffee stains on page 47. That's where Maya kept her ordering notes—handwritten tallies of milk consumption, bread deliveries, and the vendor codes she needed to text before 8 AM if she wanted next-day delivery.
Every morning started the same way. 5:15 AM arrival. Lights on. Then the inventory walk: opening fridges, counting milk cartons, checking the produce order against what actually arrived, and scribbling notes about what was short or wrong.
By 6:30 AM, she'd be texting suppliers, chasing up missing items, and fielding calls from staff asking about next week's roster—which she hadn't finished because she'd run out of time the night before.
She was working 60 hours a week. Eight of those hours were pure administrative friction: ordering, supplier follow-ups, roster adjustments, and the mental load of remembering who needed what and when.
If you run a hospitality business and suspect you're spending more time on admin than you should, we do free 30-minute discovery calls to map exactly where your time is going.
The Problem That Hid in Plain Sight
Maya's cafe sits on King Street in Newtown, Sydney. Good foot traffic, loyal regulars, and a reputation for excellent single-origin coffee. She'd built it from scratch over five years. Revenue was healthy—around $780K annually. The problem wasn't the business. It was the invisible time tax that kept her from growing it.
Here's where her eight hours went every week:
Ordering (2.5 hours):
She ordered from six different suppliers. Milk, bread, produce, dry goods, coffee beans, and packaging. Each had a different ordering window, a different contact method (text, email, portal), and a different delivery schedule. She kept it all in her head and that coffee-stained notebook.
Supplier follow-ups (1.5 hours):
Deliveries went wrong about twice a week. Short orders, wrong items, quality issues. She'd text the supplier, wait for a response, text again. Some weeks she spent more time chasing down her orders than placing them.
Rostering (3 hours):
Sunday nights were roster nights. She'd sit at the counter after close, staff availability in one hand, OpenShifts in the other, trying to balance coverage against labour costs. Someone always wanted to swap a shift. Someone always forgot to submit availability on time.
Compliance paperwork (1 hour):
Food safety logs, temperature checks, waste tracking for the council. She filled them out by hand because "it's faster than figuring out an app."
None of this was hard work. But it was constant work. And it happened during the margins of her day—the early mornings, the late nights, the stolen moments between the lunch rush and the afternoon lull.
What We Found During the Diagnosis
We spent a week watching how the cafe operated. We sat with Maya during ordering, shadowed her through supplier calls, and reviewed her rostering process.
Three patterns emerged.
Information lived in too many places.
Supplier contacts were in her phone. Order histories were in her notebook. Delivery schedules were memorised. Staff availability came through Instagram DMs, WhatsApp, and text messages. Nothing talked to anything else. Every decision required cross-referencing multiple sources.
The ordering windows were predictable, but the reminders weren't.
She knew she needed to order milk by 6 PM Tuesday for Thursday delivery. But on busy Tuesdays, she'd forget until 8 PM—and then spend Wednesday morning chasing the supplier for an exception. The problem wasn't memory. It was that nothing reminded her at the right moment.
Rostering was stuck in a feedback loop of late availability.
Staff submitted availability late because they knew Maya would figure it out. Maya figured it out because she always had. The process rewarded lateness, and everyone was exhausted by Sunday night roster anxiety.
We also found something Maya hadn't noticed. She was over-ordering on three product lines by about 15% because she didn't have time to check what was already in stock before placing orders. That's roughly $340 a month in unnecessary inventory cost.
What We Built
We didn't overhaul the business. We automated the friction.
A unified ordering system with smart reminders.
We connected her supplier contacts into a single dashboard. Milk, bread, produce—all orders go through one interface. The system tracks what she ordered last week, what's currently in inventory (she does a 2-minute count each morning instead of a 15-minute notebook session), and sends her a push notification at 5:30 PM the day before each ordering window closes.
No more forgetting. No more chasing exceptions. And because the system knows what she typically orders, she can confirm with one tap or adjust quantities in seconds.
Automated supplier follow-ups.
When a delivery is short or wrong, she logs it in the system with a photo and a note. The system sends the supplier a templated follow-up email with the details, tracks the response, and escalates to Maya only if there's no resolution within 24 hours.
She went from spending 1.5 hours a week on supplier ping-pong to about 15 minutes.
Self-serve rostering with guardrails.
We set up a simple availability submission form that staff must complete by Friday at 5 PM. The system compiles responses into a draft roster that Maya reviews on Sunday afternoon (not night). Staff can request swaps through the system, which automatically checks coverage before approving.
Maya's roster time dropped from 3 hours to 45 minutes. And she no longer does it alone at 10 PM on a Sunday.
Digitised compliance logs.
Temperature checks and food safety logs now happen through a simple checklist on her phone. Two minutes a day. Automatic timestamping. Exportable for council audits.
Build time: 2.5 weeks. One week mapping the workflows. One week building and integrating. A few days testing with live operations.
Monthly running cost: $47 AUD.
The Results
We measured everything after six weeks.
8 hours reclaimed per week.
Maya's admin time dropped from roughly 8 hours to under 1.5 hours. That's 32 hours a month—nearly a full work week—back in her life.
She started taking Tuesdays off.
The first thing she did with the time was reclaim her one full day off. She hadn't had a proper day off in three years. Now she closes the cafe on Tuesdays and spends it with her kids.
Inventory costs dropped by $290/month.
The system's pre-order inventory check eliminated most of the over-ordering. She's now running tighter inventory without running out of stock.
Staff satisfaction improved.
The rostering changes didn't just save Maya time—they gave staff more predictable schedules. Swaps are now handled without a text chain of 47 messages. Availability is submitted on time because the system sends reminders.
Supplier relationships got better.
Maya admits she used to be "that customer" who texted at 7 AM with vague complaints about wrong orders. Now the follow-ups are clear, documented, and professional. Suppliers respond faster because they have the details they need.
What She Did With the Time
This is the part that matters. Maya didn't automate to work more. She automated to work better.
With her Tuesdays back, she started testing new menu items again—something she hadn't done in two years. She launched a loyalty program. She even started looking at a second location, something that had been "maybe next year" for three years running.
The automation didn't change her job. It gave her job back to her.
If you're running a hospitality business and suspect you're spending 8+ hours a week on work that could be automated, let's talk . The first 30 minutes is free, and you'll walk away with a clear picture of where your time is actually going.