GMAI · Generative Menu & Invoice Intelligence

The number you can trust.

From invoice to insight — every important answer traceable to its source. GMAI turns food-and-beverage purchasing data into verified recipe, menu, and margin intelligence, without replacing the systems your operation already depends on.

Paolo Fontana · Founder

The Hidden Operational Problem

The information exists. It just doesn't connect.

Every food-and-beverage operation produces the data it needs — invoices, recipes, price books, menus, POS exports, banquet documents. But the pieces don't connect.

A pack shrinks quietly

A vendor changes a case size while the case price stays the same. No one sees which recipes it affects.

The chef can't prove it fast

Costs are rising, but there is no quick, defensible way to show management exactly why.

The controller lacks context

The variance is visible in the financials, but the culinary story behind it isn't.

The banquet loses margin early

An event menu contracted months ago erodes quietly as ingredient costs move.

Why Current Systems Leave a Gap

Each system does its job. None connects them.

Your POS records sales. Accounting records spend. Recipes live in spreadsheets. Invoices live in a drawer. The decisions live in between.

POS
— what sold
Spreadsheets
— what recipes cost, once
Accounting
— what was spent
Invoices
— what prices really are

The gap

No system traces a purchasing change through ingredients, recipes, menus, and events to the margin decision.

What GMAI Is

An intelligence layer that turns purchasing data into verified recipe, menu, and margin intelligence.

Capture the Truth

Disconnected purchasing documents become structured, usable information.

Connect the Impact

Purchasing changes traced through ingredients, recipes, menus, and events.

Act with Confidence

Understandable answers with inspectable evidence behind every number.

Works alongside your POS, accounting, and club-management systems. Nothing is replaced.

How the Intelligence Chain Works

From invoice to decision, one traceable chain.

01

Invoice

GMAI reads purchasing documents from multiple vendors.

02

Price book

Items, packs, units, and prices are identified and checked.

03

Ingredient

Information becomes normalized, usable ingredient costs.

04

Recipe

Costs flow into recipes with yields handled correctly.

05

Menu / Event

Margin changes surface across menus, events, and operations.

06

Decision

Every answer carries inspectable evidence behind it.

The real product is not document reading. It is the verified decision that becomes possible once the invoice is understood.

What GMAI Does

Three disciplines, one system.

I

Capture the Truth

Turn disconnected purchasing and operational documents into structured, usable information.

  • Multi-vendor invoice intake with OCR-assisted extraction
  • Product, pack, quantity, and unit normalization
  • Unit-of-measure conversions
  • Human validation for uncertain or financially important data
II

Connect the Impact

Trace purchasing changes through ingredients, recipes, menus, and events.

  • Ingredient and price-book management
  • Yield-aware recipe costing
  • Menu engineering
  • Vendor price-change visibility
III

Act with Confidence

Give chefs and managers understandable answers with inspectable evidence.

  • Source-grounded answers with provenance
  • Auditability on every figure
  • Role-aware access
  • Conversational intelligence through Chef Oracle
Built for the Whole Leadership Table

One set of numbers everyone can stand behind.

Fewer surprises between the kitchen and the board.

Visibility into where food-and-beverage margin is moving, before it shows up as a variance you have to explain. One defensible set of numbers across culinary and finance.

  • Margin movement surfaced as it happens, not at month-end
  • Answers you can repeat to the board with the evidence attached
  • No replacement of your existing club systems

Variance you can explain, line by line.

Every cost figure ties back to a source document, so month-end analysis starts from evidence instead of archaeology — and the culinary context arrives attached.

  • Invoice-level detail behind every ledger question
  • Price and pack changes surfaced with the documents attached
  • One set of numbers culinary and finance both accept

Proof, not arguments.

When costs rise, show exactly which vendor moved, on which item, and what it did to your recipes — in minutes, not a weekend of spreadsheets.

  • Recipe costs that stay current with purchasing
  • Yield-aware costing that respects trim, shrink, and usable yield
  • Evidence you can bring to the GM without a spreadsheet war

Menus and events, priced on today's reality.

Banquet menus contracted months out are checked against the costs you're actually paying today, so margin erosion surfaces early enough to act.

  • Contracted event menus tracked against current costs
  • Items drifting above target food cost flagged early
  • One picture across outlets, menus, and events

Confidence in the number, not just the person.

Answers that reach the board carry their evidence with them — an inspectable trail from the figure on the page back to the invoice that set it.

  • A defensible audit trail behind every figure
  • Role-aware access aligned with governance
  • Nothing replaced, nothing locked in
Invoice & Purchasing Intelligence Illustrative example — not a customer result

The case price didn't change. The cost did.

Invoice · March Canola oil, 1 case 35 lb · $87.50
$2.50 / lb
Invoice · April Canola oil, 1 case 30 lb · $87.50 — pack shrank
$2.92 / lb · +16.7%
What GMAI Surfaces
  • Effective unit cost up 16.7% on an unchanged case price
  • Every recipe using this ingredient, flagged
  • Source: the two invoices, side by side
Chef Oracle Controlled Pilot

Ask in plain language. Get the answer with its evidence.

  • Which recipes are now above their target food cost?
  • What caused the projected margin on this banquet to change?
  • Show me the invoice behind this number.
Chef Oracle
Which vendor price changes affected my menu this month?
Three ingredient costs moved enough to affect menu items. Six items are now above target food cost.
↳ Invoice #4821 · Apr 12↳ Price book · canola oil
Illustrative conversation. Answers draw only on your approved data.
Trust, Provenance & Architecture

Built to be examined.

Source links

Every important answer links back to the document it came from.

Human review

Uncertain or financially important extractions go to a person, not a guess.

Tenant boundaries

Your club's data is structurally separated from every other operation's.

Role-aware access

Chefs, controllers, and managers each see what their role requires.

Audit history

Costs carry their history: what changed, when, from which document.

Export & deletion

Your information remains yours, with controls to take it or remove it.

MODERN MULTI-TENANT ARCHITECTURE · ROLE-AWARE ACCESS · DOCUMENT PROVENANCE

The Intelligence GMAI Is Building Toward

Where GMAI is going.

Forward product direction — not current functionality.

Pack-Size & Catch-Weight Sentinel

Detect changing pack sizes, billed weights, and effective unit-cost changes that case-price comparisons miss.

Banquet Cost Shadow

Compare future contracted event menus with changing purchasing costs to catch projected margin erosion early.

Dock-to-Statement Credit Reconciler

Connect delivery exceptions, shortages, and vendor statements to identify missing credits.

4D Menu Engineering

Weigh sales velocity, ingredient cost, prep labor, usable yield, and waste volatility — beyond classic popularity-vs-profit grids.

Vendor Renegotiation Package

Organize verified spend, price movement, and discrepancy evidence into a professional package for vendor conversations.

Paolo Fontana · Founder
Official portrait, v1.0
Founder

Built by an operator, for operators.

GMAI was not conceived in a software boardroom. It grew from years of trying to make difficult food-and-beverage decisions from disconnected invoices, recipes, spreadsheets, reports, and institutional knowledge.

Paolo Fontana has spent his career inside hospitality operations: executive culinary leadership, private-club and general management, restaurant ownership, culinary education, recipe development, and food-cost and financial oversight.

GMAI reflects that experience — a product that respects how chefs, controllers, GMs, and ownership actually work through service, month-end, menu changes, banquets, and vendor problems.

Founding Club Program

A limited program for clubs that want to shape GMAI.

The Founding Club Program is for a small group of clubs and serious F&B operations willing to work directly with the founder during a controlled rollout. Participation is limited.

Request a Founding Club Review
You receive

What participants receive

Direct founder involvement, priority onboarding of your vendors and recipes, and influence over the product roadmap.

You bring

What GMAI asks in return

Real invoices and recipes to work with, honest operational feedback, and a monthly working session with your culinary and finance leads.

You commit

The next step

A working review of your operation with the founder — your documents, your menus, your questions. No obligation follows.

Questions

Questions clubs ask.

Is GMAI an accounting system? +

No. GMAI is an intelligence layer, not a ledger. It reads your purchasing documents and connects them to recipes, menus, and margins — your accounting system remains the system of record, and nothing is replaced.

Does it replace our POS or club-management platform? +

No. GMAI works alongside your POS, accounting, and club-management systems. They keep doing their jobs; GMAI connects what they can't see between each other.

How does GMAI handle imperfect invoices or scans? +

Documents run through OCR-assisted extraction with confidence scoring. Anything uncertain — or financially important — is routed to human review. A person confirms it, not a guess.

Can users inspect where a number came from? +

Yes. Provenance is the product. Every important answer links back to its source document, and costs carry their history: what changed, when, and from which document.

Is GMAI built only for private clubs? +

GMAI is built first for private clubs and serious F&B operations. If your operation runs on invoices, recipes, menus, and events, the intelligence chain applies.

What does implementation require? +

A conversation and a handful of recent invoices. There is no rip-and-replace project — your existing systems stay exactly where they are.

How is customer information separated and protected? +

Structured tenant boundaries keep your club's data separated from every other operation's. Role-aware access controls who sees what, and an audit history records what changed and when.

What happens if we want to export or delete our information? +

Your information remains yours. Export and deletion controls are built in — you can take your data with you or have it removed.

Which integrations are currently available? +

GMAI starts from the documents you already receive, so no integration is required to begin. Current and planned integrations are reviewed together during the Founding Club conversation.

How do we apply for the Founding Club Program? +

Request a Founding Club Review. It takes one conversation and a handful of your invoices. Nothing is replaced, nothing is committed, and participation is limited.

See your own numbers, traced to their source.

A working review takes one conversation and a handful of your invoices. Nothing is replaced. Nothing is committed.

Request a Founding Club Review