Tell Beth about your restaurant
In your own words: what you offer, your tables, hours and the menu. She asks a question or two if she needs to, and she only talks about your restaurant.
For restaurant owners
Reservations for your restaurant, live today.
Guests reserve a table by party size, the waitlist texts them, the tab and the tip close on one card. Set up in minutes by describing your restaurant.
No demo call
No developer
Pay for what you use
Cancel any time
Beth, the assistant inside LatticeKit, builds it from what you tell her. Two minutes, no card: leave an email to see the preview, then see it running at its own address for a week.
How it works
Three steps. The first one takes two minutes.
Beth builds the first version
Leave your email and Beth drafts your booking page — your menu with prices and modifiers, your tables and seatings, your hours — the way a customer would see it. Change anything.
See it running, then go live
Press “See it live” and Beth builds a working copy of your restaurant at its own address — book yourself in and watch it land. It is a sandbox that lives a week, so nothing real happens in it. Happy with it? Create your account and add a card, and that copy becomes your restaurant’s site: Beth finishes it with you — your menu, your table plan, your kitchen routing. You can be taking bookings the same day.
What’s included
Everything a restaurant runs on, already talking to itself.
Your reservations, orders, tabs and messages all share the same guest record, so nothing gets out of sync.
Tabs that behave
Open a tab, add and modify dishes, route them to the kitchen, split the bill evenly, add the tip, close to the card. One receipt by text.
A menu with modifiers and recipes
No onions, extra cheese, gluten-free bun. Each dish knows its ingredients, so inventory drops when it sells.
Reservations and a waitlist
Seatings by party size and time. A walk-in joins the list and gets a text when the table is ready.
Purchasing that matches sales
Orders to your vendors, receiving against them, and reorder suggestions when the walk-in is low.
Your team
Shifts, swaps, a time clock and timesheets for the front and the back of house, next to the sales they worked.
Gift cards and regulars
Sell gift cards, run a punch card, and send a note to regulars you have not seen in a while — with their permission.
Built for restaurants and cafés
The days that break other software.
A party of six wants three separate checks and one of them is paying the tip.
Split the tab evenly or by item, put the tip on one card, close each check. The kitchen ticket never changes.
Friday at 7 and the waitlist is twelve names long.
Each party has a place in line and a text when the table opens. Nobody hovers at the host stand.
You ran out of salmon at 8:15 and nobody told the floor.
Inventory drops with each order. The dish goes unavailable on the menu the moment the last portion sells.
Pricing
Pay for what you use.
No monthly plan, no setup fee, no minimum. You add a card when you create your account, and each month you are billed for what your restaurant actually did — bookings made, sales rung up, messages sent. A quiet month is a small bill.
- Nothing to pay up front
- Every action and its price on your Usage page, updated hourly
- Your customers’ card fees go to your payment processor, not to us
- Cancel any time from your account page
$141
a month, at these volumes
$0 monthly plan · drag a slider to match your restaurant
Reservations taken
500$25.00
Orders and tabs closed
1,800$90.00
Email confirmations and receipts
500$0.30
Text updates to guests
900$18.00
Also on the bill
Questions you ask Beth
100$8.00
Views of your booking page
5,000$0.15
See the line items
Estimate, not a quote — you are billed for what actually happens, itemised on your Usage page. Bookings and sales are 5¢ each, email 60¢ a thousand, texts 2¢ each (what the carriers charge us), your booking page 3¢ a thousand views. Beth is billed by the token — about 8¢ for a typical question. Forms and API calls are free; imports and automations come to cents at these volumes. Your customers’ card fees go to your payment processor, not to us.
Questions
The ones restaurant owners ask first.
Do I need someone technical?
No. You describe your restaurant in plain words and Beth — the assistant inside LatticeKit — builds it and finishes the setup with you. If you can write a text message, you can do this.
Do I have to book a demo or talk to sales first?
No. The preview is of your restaurant, not a sample one, and one click turns it into a working copy you can book into. Real people are one email away at hello@latticekit.app if you want them.
What about the clients and services I already have?
Bring a spreadsheet or an export from whatever you use today. LatticeKit imports your people, services and products and shows you exactly what it will create before it saves anything.
How do payments work?
Cards run through Stripe or Finix under your own account with them, so the money is yours from the first sale. Card numbers are entered on the processor’s secure page and never pass through LatticeKit.
Does it work with my card reader?
Cards run through Stripe or Finix under your own account. In-person card readers are early on LatticeKit; ask us at hello@latticekit.app about your hardware before you switch a busy service to it.
What does it cost?
There is no monthly plan, no setup fee and no minimum. You add a card when you create your account and pay each month for what your restaurant actually did. Cancel any time from your account page.
Is LatticeKit ready for a real business?
It is new, and we are welcoming businesses a few at a time. You will be talking to the people who build it, and what you see in the preview is what you get.
Tell us how your restaurant works. We’ll build the software around it.
Two minutes to describe it. Your booking page, drafted for you. No call, no card until you decide to create the account.