Back-office software for independent restaurants

Photograph an invoice.
Everything else follows.

Every line read, priced, and coded to your books. Every recipe re-costed the moment a price moves. Your prep cook told what to make. Bills in QuickBooks with one tap — and never without one.

Talk to us Sign in
A real invoice · 6 pages · 52 lines
Lines read52
Lines sum to$3,097.45
Invoice states$3,097.45
Difference$0.00
It checks its own arithmetic against the invoice's printed total before it trusts a single number. If they disagree, it refuses rather than guesses.

The loop

Nothing is entered twice. Each step feeds the next, and the gap between what you should have used and what you did is where the money is.

01

An invoice arrives

Photographed, uploaded, emailed in, or typed. Any vendor, any format — no templates.

02

Every line is read

Item, pack size, quantity, price. Reconciled against the document's own total. Coded to your chart of accounts.

03

Recipes re-cost

Butter goes up 7% and every dish containing butter knows — the same day, with the working shown.

04

Inventory rises

What came in is on hand. Counted in your walk order, on your devices.

05

Sales deduct it

Your POS says what sold. The system knows what that should have used.

06

A count checks it

Expected against actual. Five pounds short is a number, not a feeling — and it opens to every transaction behind it.

What's in it

Built in a working restaurant, one module at a time, each used before the next was started.

Invoice capturePDF, photo, email, or manual · every line coded · refuses rather than guesses
Recipe costingReal plate cost with the conversion working shown · a cup becomes grams, and you can see how
InventoryCount sheets in your walk order · partial counts say what they are · products that open to their history
PrepPars by period · the cook counts, the system decides · yield measured, labels printed
Price intelligenceAlerts ranked by dollar impact, not percentage · thresholds tested against your own history first
QuickBooksBills and purchases coded to your accounts · posted on a tap · never automatically
Tasks & line checkBy position · photo-verified · works offline · nobody leaves with open work
WasteThree taps · anonymous by design · because a log people use beats an accurate one nobody fills in
MaintenanceVendor dispatch with a no-login reply link · approval-gated
Food safetyTemperature logs, health-code defaults on every recipe, printable for the inspector

How it's built

Four rules that decide more than any feature does.

It refuses rather than guesses.

Where a number can't be verified, it says so instead of producing something plausible. A wrong figure that looks right is worse than no figure.

Nothing touches your books on its own.

Every entry to your accounting system happens because a person tapped to send it. No automatic path exists.

Every number opens.

Tap a plate cost and see the ingredients. Tap a price and see the invoice. Tap a line and see the receipt.

Your data is yours.

Exportable any time, in a usable format. Never sold, never shared, never used to train anything.

"The alternatives were expensive, complicated, and built by people who had never worked a Saturday brunch service."

Vorsa runs FH Brunch Factory in Farmington Hills, Michigan, every day — the invoices, the prep, the counts, the checklists. It was built there by its owner, one module at a time, and each one had to work on a real service before the next was started.

It exists because an operator's day is already full. The tools that were supposed to help added screens to check instead of removing work to do.

Built for the operator who runs the restaurant.

Not the one who has time to run reports.

Talk to us