BOOTCAMP

The Real Problem

Small-format restaurants and cloud kitchens were juggling three tools that didn't talk to each other: a POS for the till, a spreadsheet for stock, and a WhatsApp group for orders to suppliers.

A week of site visits made the cost obvious:

• Owners were closing the kitchen 40 minutes early to "do stock."
• One in four supplier orders was off by at least one item.
• Nobody trusted the numbers in the spreadsheet by Wednesday.

The problem wasn't lack of software — it was too much, badly stitched.

Finding the Fix

We spent two weeks behind the counter at four pilot kitchens, taking notes on every interruption to the cook's rhythm.

Three product bets came out of it:

• One screen, one number — today's stock at a glance, nothing else.
• Voice-first re-order ("two more bags of basmati") for hands that are usually wet.
• A weekly summary that the owner reads on the bus home, not in a back office.

What Actually Happened

Bootcamp ships as a single screen pinned to the wall of the kitchen — no log-in, no menus, no settings. It listens for short voice commands and shows the day's stock as a tall list of friendly cards.

Behind it, a quiet sync layer pushes orders to the same supplier WhatsApp group the kitchen was already using — so the supplier didn't need to learn a thing.

The first night a pilot kitchen used it, the owner closed the laptop spreadsheet for good.

What Changed

Across the first eight pilot kitchens, three months in:

• End-of-day stock-take time dropped from ~40 minutes to under 5.
• Supplier order errors fell ~70%.
• Six of eight owners renewed at the end of the pilot.
• Two kitchens added a second outlet in the next quarter, citing "we can finally see the numbers" as the unlock.

What I Tried to Work With

Voice in a noisy kitchen turned out to be the hardest constraint. The first prototype mis-heard "two" as "ten" enough times that owners stopped trusting it. The fix wasn't smarter voice — it was a confirmation card that read the order back in a single line, big enough to glance at while flipping a roti. Trust came from the read-back, not the recognition.

What I'd Do Differently

I'd start the supplier conversation in week one, not week six. The kitchens loved Bootcamp; the suppliers — who suddenly had cleaner orders — were a few weeks behind, and we lost momentum chasing them down later. A small onboarding tool for suppliers would have been a force-multiplier we under-invested in.

What I Learned

Designing for hands-on businesses means designing for the moment when both hands are full. Every UI choice ends up answering: "can the user still do this if they can't touch the screen?"

The version of the product that survived the kitchen was, not by accident, the simplest one we drew. The kitchen rewards restraint.