Tell it what you want and it sets it up.

The part of running a venue that usually means a support ticket, a screen share, or an afternoon lost in settings, done by describing it in a sentence.

Book a Demo

Set the venue up by describing it.

Bays, opening hours, session lengths and booking flows. Tell it how the room works and it builds the configuration to match.

Build a membership without a support ticket.

"A ten hour pack that gives members fifteen percent off and expires after a season." It creates the product, the credits and the rules behind it.

Pricing is where it earns its keep.

Peak and off-peak, member rates, league nights, seasonal changes. Pricing rules are the hardest thing to set up by hand and the most common thing operators ask it for.

Write an automation in a sentence.

"Email anyone who has not booked in sixty days." It builds the trigger, the wait, the check and the message, and you look at it before it runs.

Change the look without a designer.

Colours, logo and the way your booking page reads, adjusted by asking, so your booking flow keeps looking like your venue as it changes.

It asks before it changes anything.

Every action is shown to you for approval first. Nothing touches your live venue because it decided to, and you can say no.

It only ever sees your venue.

Each conversation is tied to your venue and your login, and it works with the same permissions you already have.

FAQ

Frequently asked questions

Bays and hours, membership products and credit packages, pricing rules, automations, and branding, from a description of what you want.

No. Every action is shown for approval before it runs.

No. It is scoped to one venue and to the signed-in user's own permissions.

Staff. It sits inside the manager console.

See the platform built for your operation.

30-minute demo. Configured to your venue's layout, staffing model, and existing hardware.

Book a DemoView pricing

No contract required.