Food businesses run on systems that don't talk to each other.
An order arrives in one app. The kitchen plans from memory. Stock is bought over the phone. Payments settle somewhere else. Each system holds part of the picture, and nobody holds all of it.
01Customer demand
02Ordering
03Kitchen operations
04Sales
05Procurement
06Payments
07Fulfillment
08Data
Eight parts of one food business.Usually eight separate vendors, logins and spreadsheets.
02 — Our approach
We don't build one giant application. We build focused products that understand each other.
01
Focused products
Each product solves one part of the food business exceptionally well, and is worth using on its own.
02
Shared context
When products connect, they share the signals that matter — demand, sales, stock, money — and nothing more.
03
Interoperability over lock-in
Use one product or several. Keep the tools you already rely on. Intelligence should lead to action, not dependence.
03 — Available today
Two products, each built to stand on its own.
This page explains where they fit. Features, pricing and demos live on each product's own site.
PrepOrder
PrepOrderAvailable
Customer demand, food discovery and ordering.
A marketplace where people find restaurants and order food — and where restaurants reach the customers already looking for them.
We're clear about direction, and honest about status. These layers are future capabilities, not products you can buy today.
03
Sourcing & procurement
Connect kitchens with suppliers, driven by forecast need.
Future capability
04
Commerce & point of sale
The transaction and operational commerce layer.
Future capability
05
Fulfillment & delivery
Infrastructure for getting food orders to customers.
Future capability
06
Payments & settlement
Payments, commissions and restaurant settlement flows.
Future capability
05 — How the stack connects
One loop. Every layer makes the next one smarter.
Demand becomes a plan. The plan becomes a purchase, a sale, a delivery and a settlement. Then the outcome flows back as data — and the next decision is better than the last.
01Available
Demand
Customers discover restaurants, browse menus and place orders. Every search and every order is a signal of what people want, where and when.
A restaurant never needs the whole ecosystem to use one product. Start with what solves today's problem. Connect more when it helps.
PrepIQ on its own
Works from your own sales data. No marketplace required.
PrepOrder on its own
Reach customers and take orders. No kitchen system required.
Connected
Tomorrow's orders inform today's prep. Demand reaches the kitchen before the rush does.
PrepStack / Kampala
07 — Where we start
Built from Africa. Designed beyond it.
We build in markets where food businesses work around real constraints every day. Designing for those realities makes technology that holds up anywhere.
Fragmented infrastructureTools rarely share data
Mixed payment systemsCash, cards and mobile money
Difficult POS integrationsClosed or local systems
Fast-changing demandHabits shift month to month
Africa is the origin and proving ground — not the ceiling.
Our mission
To connect the systems behind how food is discovered, prepared, sold, sourced, paid for and fulfilled.