A cafe we own in Islamabad
A cafe we own, and the site that opened with it
A page for every drink on Next.js and Sanity; the owner edits prices without a deploy. 25 drinks, each with a page of its own.
Our own product, built for the cafe we own in Islamabad. March to June 2026.
The operations system behind a cafe, from tills to loyalty
The cafe runs its till on a third-party point of sale, with stock, recipes, shifts and loyalty living outside it. 93 Brew OS puts them on one schema of twenty tables, where a sale draws down stock through its recipe and a void leaves a trail.
Specialty coffee. Build and Automate.
A link is coming soon.
93 Brew OS in figures
- 20tables in one PostgreSQL schema, from orders to loyalty
- 22workflow maps over a 22-entity domain model
- 1 weekfrom the first commit to a point-of-sale MVP, March 2026
Orders and till
- orders
- order_items
- payments
- tills
Menu and recipes
- products
- product_variants
- recipes
- recipe_items
Stock
- ingredients
- stock_levels
- stock_movements
- suppliers
- purchase_orders
Shifts and people
- staff
- shifts
- shift_assignments
Loyalty and access
- customers
- loyalty_points
- users
- roles
Screens from this system are being added.
The situation
The cafe runs its till on a third-party point of sale, and its stock, recipes, shifts and loyalty live outside it, so nobody can answer what was sold against what was used. The owner wanted operations tooling the cafe could run itself, on one schema where a sale draws down stock through its recipe and a void leaves a trail. 93 Brew OS is that system, built as our own product.
What we built
- Point of sale with a barista queue, so an order moves from the till to the bar without being re-read
- Void reversals with an audit trail, so a cancelled sale is reversed rather than deleted
- A stock record tied to recipes, so each sale draws down the ingredients it used
- Shift management and a loyalty scheme over the same customer records
- A 20-table PostgreSQL schema with Drizzle for typed access, Zod validation, JWT auth with bcrypt hashing and a Jest suite
- A product requirements document, 22 workflow maps, a 22-entity domain model and a five-wave implementation roadmap
What changed
The point-of-sale MVP was ready a week after the first commit, and the cafe has an operations system of its own to grow into: one schema where a sale, its stock, the shift it happened on and the customer's loyalty balance are the same record. We walk through it on a call.
Along the way
Repository created and the first deployment project set up, 24 deployments on the first day
Authentication landed: JWT sessions with bcrypt password hashing, across a second deployment project
Point-of-sale MVP ready
Product requirements, the workflow maps, the domain model and a five-wave roadmap written up in the product hub
Read next
A prototype we built for wholesale order desks
Order emails that turn themselves into quotations
An email becomes order lines against a catalogue, stock moves to reserved, and a quotation drafts itself. 3 quantities per stock item: on hand, available and reserved.
Transcend Ltd, a UK wholesaler in perfumes and FMCG
An order desk built twice, from both sides of the trade
An order-to-purchase system built twice for a UK wholesaler and reviewed line by line by their own team. 59 requirements reviewed, across 17 sections.
Elsewhere on the site
Related
- PracticeThe Build practiceWhat the practice covers, what it costs to start, and the work behind it.
- The workDemosThe demos you can open now: the two that run in your browser, the hosted prototypes, a walkthrough on video and a live cafe site.
- The workThe five practicesBuild, Automate, Data, Growth and Talent: what each one covers, the work behind it, and what it costs.
Where to next
Have a problem in this shape?
Say so in a few sentences. The reply comes from the person who built this one.