Investment Thesis
Everything we build starts because something broke.
Kitchen Code runs physical hospitality businesses. When something breaks, we build the software to fix it. Then we sell that software to everyone else with the same problem.
The Flywheel
Hospitality generates insights. Insights create software. Software scales independently. The cycle repeats.
Hospitality
Run real physical businesses — coffee shops, hotels, bars
Operational Pain
Hit a wall that existing tools can't solve
Software Product
Build the tool internally, battle-test it on our own operations
Standalone Revenue
Productize and sell to the broader market
The Building Blocks
The Pattern in Action
The pain:
5,000 stamp cards/year — a small deforestation project
The product:
B3 App — loyalty + Brewing Academy, built in-house
The pain:
Enterprise PMS at 2008-era UX
The product:
SabaiFlow — hotel management software, now live at sabaiflow.co
The pain:
Coffee distribution unit economics do not scale manually
The product:
BrewBox — hardware + software for distribution (R&D)
Why Hospitality + Software?
Most holding companies are either all-hospitality or all-software. Kitchen Code is both — and that's the point.
Hospitality brands generate cash and customer insights. Every day, thousands of real interactions create real operational data. When the tools to manage those operations don't exist (or are overpriced and outdated), we build them.
The software that emerges isn't theoretical — it's battle-tested on daily operations before it ever reaches an external customer. That's a moat most SaaS companies can't replicate.
Software then becomes standalone revenue. Cross-pollination between brands creates operational leverage. The cycle repeats.