A cooking class website needs three things: the menu you are cooking that evening and what it costs per person, dates people can claim a place on themselves, and a seat count that matches the number of workstations you have. Posato is a service that rebuilds the site you already have with all three built in, approved by you before it replaces anything.
Someone books a cooking class the way they book a night out. They read the page on a Sunday, picture a Thursday evening making fresh pasta, and then want to know what is on the menu, whether they eat what they cook, and whether the date they have in mind still has room. Most class sites answer the menu question and leave the rest to a contact form. That puts four things on the page:
Photos of the finished table do more work here than photos of the kitchen. When someone asks Google, ChatGPT, Claude or Perplexity for a cooking class in their city, those are the lines being read.
A cooking class fills a room, it does not fill a diary. You put on a handful of dates a month, and what decides whether one goes ahead is how many places are still free. A tool built for one person meeting another cannot count places. In Posato a date is a room with a fixed number of places in it:
A booking drops into your back office and writes itself into the schedule. The confirmation email goes out on its own, and whoever paid you cash at the market you enter by hand.
Single places sell best when someone can pay for one there and then. A company night or a hen party is a different conversation, usually about a date you have not opened. The two cards below show what each means for the person booking.
Someone picks a date, pays for a place through Stripe, and the count drops by one as they do. Once the final place is taken the date stops accepting bookings, so you are never standing in front of nine people with eight workstations. Call a date off and you refund each booking from the screen where it sits.
You put the private class on as its own service, with the hours you would consider running one. A group picks a date and the booking is held until you approve it, so nothing is confirmed before you know how many are coming and what they want to cook. You can price it per person or as a flat rate for the group.
You send the address of the site you have now, on Wix, Squarespace, WordPress or anywhere else, and we rebuild it on a private preview link. Your current site stays up and keeps taking bookings until you sign off on the new one; the three steps and what they cost you in time are on the home page.
While the beta is open there is no subscription and no build fee. When someone pays for a place through your site, we take a 5% commission on that payment, so a quiet month between seasons costs you nothing. The rest of the answer is in the questions on the home page.
Set a deadline for cancelling, decide what you keep when someone pulls out after it, and allow a short grace period straight after booking. You can send back all of the money or some of it, from the booking itself.
Yes. Each class is its own service with its own length, price, seat count and hours per weekday, so Thursday evenings open for one and Saturday mornings for the other.
Put the private class on as its own service, with the hours you would consider. A group books a date and it is held until you approve it. A date you settle over the phone you enter into the back office yourself.
Yes. An add-on carries its own price, charged per head or once for the whole group, so the pairing rides along with the place rather than being settled at the door.
Send us your cooking class website.
We rebuild it with booking built in and send you a preview. You approve before anything replaces what you have.
Free while in beta. A 5% commission on payments taken through your site. That is how we make money.