- Year
- 2025
- Timeline
- 2025
- Our part
- Full stack build
- Where it was built
- Built in-house at Bling Square Events
The brief
Event hosts were confirming guest lists by text and email, coordinating vendors with no shared portal, and had no real-time view of ticket sales. Large events meant hundreds of vendors and guests spread across fragmented tools.
What was actually hard
The bottleneck was never the software. RSVPs go stale silently: a guest who does not reply looks exactly like one who has not seen the message, so the host chases everybody. The system had to close that gap without adding another thing for the host to check.
What we decided.
- 01
The system chases, not the host
Automated SMS confirmations and calendar links go out on a schedule, so the host stopped being the reminder mechanism.
- 02
Check-in by QR, not by list
Guests check in against a scanned code instead of someone finding a name on a printed sheet, which is where on-site queues actually come from.
- 03
One portal for vendors
Timelines and requirements live in one place instead of being forwarded vendor by vendor, so a schedule change reaches catering and decor at the same moment.
Where it landed
Used across dozens of events, with check-in handled by scan and vendor communication running through one portal.
How it fits together
- What it is
- Events · Stripe · QR
- Status
- Live in production
- Type
- Event platform
- Live since
- 2025
- Payments
- Stripe
- Check-in
- QR scan
- Stack
- Next.jsTypeScriptNodeStripeQR check-in