A ticket platform takes a cut of every sale.
Card payment and e-tickets on your own site, with the money in your own payment account.
Sell every ticket on your own site. Keep the money and the guest list. Tickets, nights and check-in, ready for sale day.
No platform cut on every ticket. Ticket types, nights, payment, e-tickets and check-in on your own site, with the money in your account. Kept running on the day sales open.
From €4,000 · fixed price agreed before any work · free first meeting
First step
Your own booking flow
When every ticket sells on your own site, the money and the guest list are yours.
No cut on every ticket
2018
Building and running live software since
200+
Tickets and stays on Outdoora, the marketplace we run
3
Hotels in one festival booking flow we built
3
Cities: Istanbul, Amsterdam and Miami
What we usually hear
Where event sales lose time and money, and what we change
Who it is for
Built for organisers with dates and capacity
Festivals · Camps · Retreats · Tours · Congresses · Stays
A good fit
The platform fees add up every season.
- You run events or stays with dates, ticket types and capacity.
- Platform fees, DMs and spreadsheets cost you money and time.
- You want the sale and the guest list on your own site.
Not a fit yet
One small event a year?
A ticketing platform will do, and costs less than a build.
Come back when you run events every season.
Not a fit yet
Many organisers on one site?
Sign-ups, payouts and reviews for each organiser make it a marketplace.
See the Experience Marketplace.Before sales open
The booking flow checklist
Fourteen checks we run on every event booking flow. Tick what yours already does. Your ticks are saved only in your browser.
0 of 14 confirmed
Tick only what you can confirm, not what you assume. Several of these are not in place yet. That is common for organisers who sell through DMs and a platform, and it is where the booking quote starts. Most of the flow is there. The unticked items are what usually goes wrong on sale day or at the gate. All 14 in place. Check them again before the next sale opens.
-
01
Tickets and stays
4 checks -
02
Payment and tickets
4 checks -
03
At the gate
2 checks -
04
When plans change
4 checks
How we work
Your tickets and rules first, then the gate
-
01 · Map
What happens
Tickets, Nights and Rules
We list every ticket type, stay, capacity and refund rule with your team. That list becomes the booking flow, and the fixed price.
-
02 · Build
What happens
The Booking Flow on Your Site
Ticket types, nights, payment, e-tickets and accounts, in your guests’ languages, on a test copy you can try.
-
03 · Gate
What happens
Check-in Without a Signal
Phones that scan tickets offline and sync later, tested with your team before the first event.
-
04 · Run
What happens
Kept Running on Sale Day
The pages checked before sales open, the site watched on the day, and the next event set up.
In production
Ticketing and booking we have built
A ticket and a hotel room in one payment, and tickets and nature stays from many organisers.
FAQ
Questions organisers ask about booking
For a few events a year, stay. The fee buys you a checkout that works. Your own site makes sense when the fees add up every season, when you need ticket and room together, or when you want the guest list to be yours.
Yes. Ticket and stay go into one cart and one payment, and the guest sees both in their account. We built this for Magic Break, a festival held at hotels.
Yes. The guest list is loaded onto the phones before the gate opens. Tickets are scanned offline, and the scans sync when the signal comes back.
Your refund rules are written into the system. A cancelled date can be refunded or moved for every guest at once, with an email to each.
Before sales open, we go through the booking pages the way guests will on the day and fix what is slow. On the day, the site is checked every five minutes, and an alert reaches the engineers who built it.
We have built checkouts with Stripe and iyzico, and we check how your provider confirms payments before we build on it. The site, e-tickets and emails run in your guests’ languages.
