Skip to content
Hypamoon

Everyone picks before eleven. The bakery gets one order.

Lunch and Friday drinks for a team of fourteen: a menu per supplier, allergies that travel with every order, and the costs per month. Built from a chat, for a fictional installer called Vosmeer.

The Vosmeer lunch menu: sandwiches and soups with prices and allergens, items with nuts greyed out for someone with a nut allergy, and Your choice on the right. The lunch menu on a phone: the rounds for lunch and Friday drinks at the top, the time to pick before, and sandwiches with a plus button.
The app with example data, in Dutch. Orders land in the app instead of at a supplier, and what you change resets after a week.Open the app

Lunch was a round of messages and one person with a notepad.

At half past ten the office manager went round the desks and the group chat, wrote it all down and called the bakery. Someone always answered too late, and the nut allergy lived in her memory.

At the end of the month nobody knew what lunch and drinks had cost, or for which team.

Built from their chat.

An app with its own database for the menus, the orders and the costs, built from the office manager's chat.

  • Pick before the deadlineLunch closes at eleven, drinks on Friday at two. Everyone sees who has already chosen.
  • Allergies per personSet once. What someone cannot have, they cannot pick, and the order says so.
  • One order per supplierA count per item and the names with their allergies, sent with one button.
  • Costs per monthPer person or per department, split into lunch and drinks.

How the team uses it now.

  1. Everyone picks on their phone.Before eleven, without a message to the office.
  2. The bakery gets one clear order.With the allergies on it, not in someone's head.
  3. The monthly cost is one screen.Per person or per department, ready for the books.

The build, in short.

  1. deploy_appMenus, orders and costs, with its own database.
  2. apply_app_migrationThe menus of four suppliers and the tables for the orders.
  3. deploy_siteThe app on its own address, for phone and desktop.

The gap between the AI and the floor.

The model is not the hard part. The hard part is getting it into the way a team already works: their mail, their systems, their approvals. That is the work of a forward deployed engineer, and Hypamoon is where the tool runs the same morning.

What would your team run on it?

Connect your chat and build the first tool. Or talk to us about yours.

Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT Add to Copilot