Tell Beth about your inn
In your own words: what you offer, your rooms, rates and seasons. She asks a question or two if she needs to, and she only talks about your inn.
Guests pick their nights and their room, breakfast and bikes go on the folio, and nothing is charged until they arrive. Set up in minutes by describing your property.
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.
In your own words: what you offer, your rooms, rates and seasons. She asks a question or two if she needs to, and she only talks about your inn.
Leave your email and Beth drafts your booking page — your room types and rates, your minimum stays, your check-in hours — the way a customer would see it. Change anything.
Happy with it? Create your account and add a card, and Beth finishes the setup with you: your rooms and rates, your deposit policy, your calendar sync. You can be taking bookings the same day.
Your stays, folio charges, deposits and messages all share the same guest record, so nothing gets out of sync.
Two nights or two weeks, minimum stays on weekends, check-in and check-out times you set. The calendar never double-books a room.
Room types with their own rates, seasonal pricing, weekend rules. A change on one page changes the booking site.
A deposit held on the card at booking and applied to the stay. Your cancellation policy, enforced.
The room, the breakfast, the bottle from the bar: one running tab per stay, settled at checkout, one receipt.
Share a calendar both ways with the other places you list, so a booking there blocks the room here.
Front-desk and housekeeping shifts, swaps, a time clock, next to the arrivals they cover.
A guest extends by two nights on the morning of checkout.
If the room is free the stay stretches; if not, the desk sees which room is. The folio follows the guest.
The same weekend sells on two sites at once.
Calendars sync both ways. The first booking blocks the room everywhere else.
A no-show for a three-night stay in peak season.
The deposit at booking covers the first night under your policy. The room goes back on sale.
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 inn actually did — bookings made, sales rung up, messages sent. A quiet month is a small bill.
Also on the bill
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.
No. You describe your inn 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.
No. The preview is the demo, and it is of your inn, not a sample one. Real people are one email away at hello@latticekit.app if you want them.
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.
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.
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 inn actually did. Cancel any time from your account page.
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.
Two minutes to describe it. Your booking page, drafted for you. No call, no card until you decide to create the account.