Case study
Event ticketing system
Queue-it style waiting room, fraud checks, and mobile wallets—so launch day feels exciting, not embarrassing.
Overview
Event ticketing system
Scope, timeline, and context—how the work was framed before a single sprint shipped.
A ticketing flow for stadium-scale drops: hold inventory fairly, block bots, and deliver barcodes that scan at gates.
Organization
Meridian Ops
Duration
7 weeks
Project type
Ticketing platform
Role
High-traffic commerce
Case study
How we got there
From constraint to release: the problem, the approach, the build, and what changed after go-live.
The problem
Last year’s on-sale melted the site; bots ate inventory; fans blamed the brand on social within minutes.
The approach
We added a tokenized waiting room, device fingerprinting light enough for privacy, and idempotent checkout APIs.
The solution
Fans see position in queue, complete purchase on mobile, and add tickets to Apple Wallet—ops monitor live sell-through.
Product views
Event ticketing system
Interface moments that show hierarchy, density, and polish—the same bar we bring to stakeholder reviews.
Results
The result
Outcomes we optimize for: less manual work, faster decisions, and software that stays trustworthy in production.
The next on-sale cleared inventory without downtime; fraud chargebacks stayed under threshold; NPS for purchase flow jumped.
Peak RPS
12×
Vs. prior baseline
Bot checkout
−91%
Estimated blocked
Error rate
0.08%
During on-sale
Next step
Want a build like this?
We scope in milestones, ship in slices, and keep communication crisp—so your roadmap stays honest.