You are not selling a product. You are selling a Tuesday at 7 p.m. — a seat at a table that exists once and never again. Escape rooms, supper clubs, tasting menus, hands-on workshops: the phygital experience business trades in time and space, not SKUs, and a VBWD analysis argues that single difference breaks most commerce tooling. The fix is a stack where the unit of sale is a seat, natively.

VBWD is a self-hosted, source-available full-stack SaaS SDK, and the constellation that makes timed experiences work is booking for seats and slots, cms for the story, bot_telegram for discovery and reminders, token_payment for prepaid credits, and email for the receipt. The invoice line item is not a thing in a box — it is a seat at a specific hour.

Booking is the product, the seat is the line item

A seat is perishable and scarce in a way a mug is not: sell one too many and you have an overbooked room, sell one too few and the empty chair is revenue you never recover. The booking plugin is built for exactly this — appointments, rooms, spaces, seats, slots — so a 6-person supper club at 8 p.m. Friday is a real, bounded object with exactly six seats and a hard start. As the original analysis puts it:

Overbooking is prevented by the seat count, not by a spreadsheet someone forgot to update.

Because the whole platform declares against one shared invoice interface, a seat sold through booking reconciles alongside credits, discounts, and add-ons, with no bolt-on reservations system off to the side.

CMS tells the story that sells the seat

Nobody books a “2-hour slot”; they book a candlelit five-course dinner or a locked-room mystery with a ticking clock. The cms plugin gives you the content, pages, and blog to build that anticipation — the landing page, the menu, the host’s story, the reviews. It is the front of house; booking is the reservation book. They live in the same deployment, so “Book Friday, 8 p.m.” leads straight into a real seat with no integration seam between marketing and availability.

Telegram is where discovery and reminders land

For local, time-bound experiences, the hardest problems are being discovered and being remembered. The bot_telegram plugin handles both — a channel announces “three seats left for Saturday’s tasting” the moment slots open, and a direct line to the guest carries the day-before nudge and the two-hours-out “your table is ready.” The source is clear about the economics:

A great supper club with no audience is empty; a booked guest who forgets is a no-show that cost you a seat you could have resold.

Prepaid credits and receipts

Experiences sell best prepaid. The token_payment plugin gives you a credit economy that fits naturally — guests buy credits and spend them on seats, which makes gift bundles and “buy 5 sessions” packs trivial, since a package is just a balance. Behind the credits sits the provider-agnostic payment core, so guests top up with a card, a regional rail, or non-custodial crypto to your own wallet. When the booking confirms, the event-driven core with native signed webhooks triggers the receipt email from the booking event itself, rather than a human remembering to send it.

The honest boundary

The caveat is not a footnote. VBWD sells the seat, takes the money, and reminds the guest — but it does not run the night. The room still has to be built, the food cooked, the host present, and the experience worth the seat. The platform gives you flawless availability, prepaid billing, discovery, and reminders; it does not give you a business people want to attend, nor does it manage capacity safety, staffing, or the logistics of the space, which remain yours along with self-hosting the deployment.

Each plugin here is a real, shipping capability, and the platform has already carried a tarot app, a dice-market game, a pharmacy shop, and dataset publishing. Read the full analysis on VBWD, or clone the public SDK to start.

Written for Red Robot with AI assistance and human editing. Adapted from an original analysis published on VBWD.