Event ticketing built in-house
instead of a €29,000 licence
Jenewein, a Swiss training and coaching provider, needed ticket sales, door check-in and clean attendee data in its CRM for its own conference. An established vendor quoted €29,000 – and would have kept the data in a system Jenewein didn’t own. So the whole flow was built from scratch.
€29,000 – and the data somewhere else
For its own conference, Jenewein needed three things: ticket sales, door check-in and attendee data that actually lands in the CRM. An established ticketing vendor quoted €29,000.
There was a catch that weighed more than the price: attendees would have ended up in a third-party system, not in HubSpot, where Jenewein runs its marketing. The very data you work with after the event would have sat outside their own reach.
Built in-house, modular
The whole flow runs on in-house building blocks, each one working on its own. Checkout sits as an embedded Stripe form directly on the Jenewein website. The QR ticket only goes out once Stripe confirms the payment via webhook. Purchase data, ticket delivery and check-in status flow back into HubSpot, while Stripe stays the system of record for payments. Getting purchase data cleanly into HubSpot is part of a well-thought-out HubSpot implementation.
From purchase to the door
Checkout on your own website
The purchase runs through an embedded Stripe form directly on the Jenewein website. No redirect to a third-party ticketing page, no break in the brand.
Ticket only after confirmed payment
The QR ticket goes out as soon as Stripe confirms the payment via webhook. That cleanly covers SEPA direct debit and bank transfer, where the money only arrives days later.
Check-in via PWA
Door check-in is a PWA that runs on iOS and Android without an app store. One scan shows valid or already used. If the network drops or a code is damaged, name search and ticket ID serve as a fallback.
Team packages and flow back to the CRM
Team packages come in through a HubSpot form and are settled via Stripe invoice. Purchase data, ticket delivery and check-in status flow back into HubSpot – where the follow-up happens.
Built for the cases that actually happen
Ticket sales don’t fall apart in the happy path – they break on the late payment and the scanner with no signal. That’s exactly where the build focuses.
Payment first, ticket second
No ticket without a confirmed payment. Stripe's webhook is the trigger, not the click on “Buy”.
SEPA and bank transfer covered
For payment methods that only clear days later, the system waits for confirmation. Nobody gets a ticket that isn't paid.
A fallback at the door
Network down or QR code damaged? Name search and ticket ID still get the guest in, without a queue at the door.
Stripe stays the system of record
Stripe remains the system of record for payments. HubSpot gets the data but doesn't handle the billing.
Before vs. after
Before – the off-the-shelf tool
- €29,000 for a ready-made ticketing tool
- Attendee data in a third-party system
- Cut off from HubSpot marketing
- Locked into that one tool
After – built in-house
- A fraction of the €29,000
- Attendee data lives in HubSpot
- Checkout directly on their own website
- Modules reusable for further events
Who this pays off for
Organisers with their own conference or event
Who want ticket sales and check-in in their own hands instead of paying a licence per event.
Teams that need attendee data in their own CRM
So follow-up and marketing happen where the contacts are already maintained.
Anyone planning several events
The modules aren't tied to one event and can be reused.
Questions & answers
An established vendor quoted €29,000, and the attendee data would have ended up in a third-party system instead of HubSpot. The in-house flow costs a fraction of that and keeps the data where marketing and follow-up happen.
The QR ticket is only sent once Stripe confirms the payment via webhook. For payment methods where the money only arrives days later, the system waits for that confirmation – there is no ticket for a payment that is still open.
Check-in runs as a PWA on iOS and Android, with no app store. If the network drops or a QR code is damaged, name search and ticket ID serve as a fallback so there is no queue at the door.
Yes. Purchase data, ticket delivery and check-in status flow back into HubSpot. Stripe stays the system of record for payments, while HubSpot is the source for marketing and follow-up.
Yes. The flow is built modularly, with each part working on its own. The modules aren't tied to this one event and can be used for further events.
Your own event, your own ticketing?
Let’s look in a free call at how ticket sales, check-in and your CRM can run together – without a licence per event.