Fuelly Join closed beta

The table takes the order.
The AI builds the plate.

Fuelly is AI ordering software for restaurants. Your guest scans the code on the table and reads your menu on their own phone. They can pick dishes themselves, or answer a few questions and let the AI fit a plate to what they are training for and what they cannot eat. Either way the order goes straight to your kitchen.

We are in beta, taking on a few restaurants at a time.

A phone on a restaurant table showing the Fuelly ordering screen

What your guests get

A menu on their phone, and a profile that remembers them.

Ordering takes about a minute, with the AI or without it. A guest who signs in keeps their goal, their allergies and their favourites, so the second visit is shorter than the first.

The welcome screen, asking for the table and any allergy

Scan and sit

The code carries the table number, so the order knows where to go.

Three plates suggested by the AI, with a macro breakdown

Three plates from the AI

Built for the goal they picked, then checked by our code against 25 allergens before they ever see them.

The order confirmation with an itemised bill

Straight to the pass

On the kitchen's screen with the table number and the allergy note on it.

What you get out of it

Four questions you already ask.

Each of them now has a screen behind it instead of a guess.

01

What did I actually earn?

Revenue net of tax and service, which is what you keep, with what guests paid beside it rather than blended into it.

The revenue card: what you earn, excluding tax and service, beside what guests paid
02

Which dish is quietly dying?

Sold, share of the menu, revenue, and the change against the whole previous period. Not against last month's top ten, which is how a dish that halved reads as a rise.

A table of dishes with quantity sold, share, change and revenue
03

Is the AI earning its keep?

What the AI brought, counted line by line on the dishes its own stored answer really proposed, so the figure survives the first hard question about it.

What the plate builder brought, with its share of orders and of revenue
04

What did they want and not get?

What guests typed at the AI, in their own words, grouped and counted. The one thing a paper menu can never tell you.

Guests' own phrases, grouped and counted
05

And a page more of them.

Uplift against hand-built orders, how often an AI plate gets reordered, which dishes it puts on the table, kitchen timings off your own tickets, peaks by hour, and the mix of goals your guests actually pick.

All of it for whatever period you choose, and out to CSV or Excel when somebody wants it in a spreadsheet.

Uplift against manual orders, the dishes AI plates put on the table, and the mix of guest goals

A demo restaurant we keep for showing this. The names and prices on it are invented.

Your till tells you what was paid.
Ask it which dish is dying.

Every number on this page comes from the order itself, which is why it can answer things a point-of-sale system was never built to hold. Send us your menu and we will stand the same dashboard up on your own dishes, so you can go looking.

Join closed beta

What we are building it to move

01  /  The check

Bigger, without anybody selling

Every plate the AI builds arrives with a drink and a side already on it. That offer does not depend on who is on shift, or how tired they are by nine.

02  /  The table

Turns sooner

Guests order the moment they have decided, not the moment somebody is free. Your floor runs food instead of standing at tables with a notepad.

03  /  The menu

Decisions with a number under them

Drop the dish that is dying, price the one that is growing, and know which of the two the AI is responsible for.

We are not going to print a percentage next to any of those. Fuelly is in beta, and the only honest uplift is one measured in your own room, against your own previous month. That is the first thing we set up with you.