Project study / editorial review
VIPCheckin
VIPCheckin helps a Las Vegas nightlife promoter manage guest registration and event guest lists through a responsive web application.

- Digital product
- Founder-led independent project · Unpaid · Responsive web application
- Independent project
- Founder-led and unpaid, created for a family member who works as a Las Vegas nightlife promoter. The founder supplied discovery, branding, UX/UI, React frontend, Python REST API, and launch. Not an E12 client engagement. It serves one active user and is not a commercially launched subscription SaaS.
Challenge / workflow-change
The founder described the previous guest-list work as manual management, then transfer into an existing third-party platform. VIPCheckin adds public registration and event-level guest management, with a CSV export for that existing workflow. Copying and transfer to the existing platform were not independently exercised, and this study does not imply an automatic third-party integration.
Before / manual workflow
- 01
Manual guest-list management
- 02
Transfer into the existing third-party platform
After / with VIPCheckin
- 01
Public guest registration
- 02
Guest management by venue / event
- 03
CSV copy / download
- 04
Manual transfer to existing platform
Founder-described task flow. CSV download was inspected; copying and transfer to the existing platform were not independently exercised.
Guest-facing registration
Guests register through a public form. The capture is the actual production form, shown empty. No entry was submitted.

Promoter operations
Promoters manage guests from the production event-management interface. The capture is deliberately empty, with no guest records. This remains a desktop capture at mobile viewport sizes; it is not a mobile management screenshot.

Scroll horizontally to inspect the production desktop interface.

CSV export and existing-platform handoff
The production export control opened a save/download dialog, which was cancelled. No CSV was retained. Copying and downstream transfer into the existing platform remain founder-described. No clipboard-workflow screenshot is available.

Founder-described handoff
- 01
Download guest-list CSV
- 02
Manual transfer
- 03
Existing third-party platform
Outcome
Reported before
6–7
hours per day
Reported after
≈30
minutes per day
The original user estimated that daily guest-list work went from approximately 6–7 hours to approximately 30 minutes. These are user-reported estimates from one active user, not independently measured analytics.
Contact
Let’s talk about the work ahead.
Whether you are starting a scoped project or looking for an ongoing digital partner, tell us what you're building, what isn't working, and where you need support.
Opens a new message in your email app.
admin@e12.agency
Helpful to include
- What you're building, and for whom
- What isn't working today
- Where your team needs support
- Timing and constraints, if you know them