Restaurant apps

// The problem

A restaurant group takes most takeout orders through delivery marketplaces, and its own ordering page is slow and does not remember regulars.

// What we would build

A direct ordering website and iOS and Android app for pickup and delivery, with loyalty that rewards ordering direct, menus and prices from the point of sale, and orders sent straight to each kitchen.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• Stripe
• Point of sale interface
• DigitalOcean

// The problem

A group of five restaurants counts stock on clipboards, prices recipes in an old spreadsheet, and finds out its food cost was too high only when the accountant closes the month.

// What we would build

An Android app for kitchen counts, waste and deliveries, and a web app for recipes and food cost, reading sales from the point of sale so theoretical and actual food cost are compared every week.

// What is in it

// Stack

• Next.js
• React Native (Android)
• PostgreSQL
• Point of sale interface
• DigitalOcean

// The problem

A franchise owner with eight locations gets sales from the point of sale, labour from the scheduler and delivery from three marketplaces, each in its own report.

// What we would build

A dashboard that reads the point of sale, the scheduler and the delivery marketplaces into one model, so the owner sees sales, labour cost and delivery share by location and by hour, compared fairly.

// What is in it

// Stack

• Next.js
• PostgreSQL
• dbt
• Point of sale and scheduling interfaces
• DigitalOcean

// The problem

A restaurant's staff retype delivery marketplace orders into the point of sale, and someone copies sales into accounting and hours into payroll every week.

// What we would build

An integration hub between the delivery marketplaces, the point of sale, the scheduler, payroll and accounting, so an order lands in the kitchen once and sales and hours reach the books without retyping.

// What is in it

// Stack

• Node.js
• PostgreSQL
• OpenAPI
• Marketplace and point of sale interfaces
• DigitalOcean

// The problem

Independent restaurants on one main street want a gift card guests can spend at any of them, and none wants a rival or a card company to hold the balance and the money.

// What we would build

One gift card across the member restaurants, with each sale and redemption recorded on a private permissioned ledger every restaurant runs a node of, so balances are shared and each restaurant is settled from one record nobody can rewrite. If a business association runs the card and everyone trusts it, a database is simpler, and we will build that.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Hyperledger Besu (private, permissioned)
• Point of sale interfaces
• DigitalOcean

// The problem

A busy pizzeria misses phone and chat orders at the dinner rush, and staff answer the same questions about hours, delivery areas and specials all evening.

// What we would build

An assistant on the website and chat that answers from the restaurant's own menu and information, takes orders through the point of sale, and passes every allergy question and anything unusual to staff. It uses a frontier model through its API: menus are public and the order volume is moderate.

// What is in it

// Stack

• Frontier model API
• Next.js
• PostgreSQL with pgvector
• Point of sale interface
• DigitalOcean