Teams who switched

Problem: Tour dates lived on a minimal site while ticketing and email sat elsewhere — hard to see which cities fans actually wanted.

Switch: Moved to Kintana for a branded public site, Stripe checkout on-domain, and Request a Show to capture city-level demand.

Outcome: One admin for on-sales, CRM from every order, and routing signals before committing dates.

“Request-a-show gave us city-level demand before we committed routing. Fans tell us where to go — we sell tickets on our own site, not a marketplace.”

Problem: Needed a polished personal site with tour info and ticket links while touring internationally — without juggling separate builders.

Switch: Built block-based pages on Kintana with hero, bio sections, and ticket CTAs tied to the same CRM as checkout.

Outcome: Professional brand presence and direct ticket sales without duct-taping a website builder to Eventbrite.

“My site and checkout finally match — fans stay on liamslater.com end to end, and every buyer lands in my list automatically.”

Problem: Co-headline bills meant reconciling orders, refunds, and artist splits across spreadsheets and a third-party box office.

Switch: Consolidated show setup, orders, and promoter-side analytics in one workspace with branded customer emails.

Outcome: Fewer support tickets on refund flows and revenue visibility per show without CSV exports.

“Refund and comp flows don't look third-party anymore. Branded emails and PDFs cut support noise, and we see revenue by show in one place.”

Problem: Ticket sales lived on a marketplace while door staff used a separate scanner app — fan data never stayed with the room.

Switch: Moved to on-domain checkout, native QR check-in, and a check-ins-today view on the venue dashboard.

Outcome: Regulars land in the venue CRM from every show, and door staff run one focused app on show night.

“Check-in and ticketing finally share the same list. We see who's in the room before the headliner walks on.”