What we build

Six things a build can do.

Each one has a "today" that costs a house something every night, and each one is scoped for your list, your menu, and your rules. Five work in the demonstration build; the sixth runs on our own paperwork. A build usually starts with the one that costs you the most.

01 · During service

Answers at the table

Wine, spirits, dishes, and allergens in one place, on the phone already in their pocket.

Today

Four sources, none of them searchable, none of them current, and none of them usable while standing at a table. A server who hesitates defaults to the bottle they remember.

With the agent

They ask out loud or by text and get an answer from tonight’s list in seconds, with the bottle, the price, and why it works. The by-the-glass list the agent reads is the one the floor is pouring, because they are the same list.

What a build of it involves

  • Your wine, spirits, and food lists in a structured form, with a version that reaches every phone within a minute of a change
  • A voice and text assistant that answers only from that list and says when a wine has been eighty-sixed
  • Bottle images, tasting notes, and a sell line drafted by a model and approved by a person
02 · During service

Allergen answers that cite their source

The line from your own allergen sheet, or "not recorded, ask the kitchen."

Today

Servers walk to the kitchen, wait, and sometimes guess when the line is slammed. Guessing is the part that carries the real risk.

With the agent

A guest mentions shellfish and the assistant switches into a protocol: every answer is checked against your sheet, the dishes that conflict are flagged, and where the sheet is silent it says so instead of reassuring anyone.

What a build of it involves

  • Reconciling the allergen sheet with what the kitchen actually does, which is where most of the work is
  • A protocol mode in the assistant that flags conflicts and refuses to guess
  • Allergen filters on every menu screen and a dish page that shows the components
04 · Between shifts

Training that fits before a shift

Short modules on the phone, written answers graded, and practice on a difficult guest.

Today

A thorough set of onboarding documents that almost nobody reopens after week one. Training quality depends on who is running it that day.

With the agent

The material becomes short modules with examples drawn from your own list rather than textbook wines nobody pours. Quizzes grade written answers, not just multiple choice. A simulated guest pushes back, asks for something off-list, or wants a cheaper bottle, and the server is graded on what they actually said.

What a build of it involves

  • Your existing material rebuilt as tracks with progress that carries over, and a manager view of who has finished what
  • Graded written answers with a rubric you can read
  • A guest simulator whose grader checks facts against the live list, so it never marks a real wine as invented
05 · After service

Shift notes that outlive the shift

What was 86’d, who complained, what changed, captured at close and briefed tomorrow.

Today

Written on a pad and binned. Institutional memory lasts one shift, and everything learned on a Friday is gone by Saturday.

With the agent

The closer jots a few lines at close and a service report is drafted from them, cross-checked against the night. Where a house wants tickets captured too, payment and identity details are blacked out before anything is stored. The manager gets a morning digest built from the numbers.

What a build of it involves

  • Optional ticket capture with redaction that runs before storage, and an archive nobody outside the house can read
  • An end-of-shift report drafted for the closer to correct and sign
  • A morning digest for managers and a pre-shift briefing for the floor, both read from the same record
06 · Between shifts

Agents for the paperwork

Invoices, supplier sheets, and the inbox, read and filed, with an interruption only when something changed.

Today

Supplier invoices, receipts, and bulletins arrive by email and photo and are handled by hand, or not at all, until the end of the month.

With the agent

An agent reads what arrives, files it where it belongs, records what it found, and only raises a hand when something needs a person: a price that moved, a document that does not match the order, a notice with a deadline.

What a build of it involves

  • An inbox and document pipeline scoped to the paperwork your house actually receives
  • Rules you can read for what gets filed silently and what gets escalated
  • A daily or weekly summary of what came in and what changed
Artificial Systems Integration

Not sure which one to start with? Nobody is.

The assessment exists to find out. We spend a shift on your floor, score each fix with you, and come back with an order and a fixed quote. Bring the thing that goes wrong most nights.

Talk about a build See the build

Prefer email? contact@asisystems.io