Personal product / Event host and guest coordination
Arrivo
A guest management product for event hosts: private guest links, arrival awareness, requests and communication in one place.
- Status
- Demo deployed and tested at Sankalp Setu. Still in development
- Year
- 2026
The live product, embedded. If it does not load here, use the button above to open it.
My role
- Sole builder. Product concept, interface design and development.
At an event, hosts juggle messages, arrivals and special requests across several apps, and guests are left wondering where to go.
Why it mattered
When hosts can see who is arriving and what they need, guests are looked after and the team stays calm.
- Give every guest a private link so there is no app to install.
- Give hosts one console for arrivals, requests and schedule.
What it does
- Designed scope: arrival alerts near the venue, escort and beverage requests, multiple admins, in-app calls, schedules and reminders, and a guest-facing assistant.
- Only features that work in the deployed demo should be treated as operational. The rest is planned scope.
What I wanted to build: One console for hosts and one simple private link for each guest.
How it came together
- Mapped the host and guest journeys, then built the core screens first.
- Used structured prompts to generate and refine each flow, then tested them.
- Deployed a demo to Vercel to keep iterating on something real.
What I did
- Defined the requirements and the user journey before any code was generated.
- Made the design and product decisions, and reviewed what the tools produced.
- Tested, debugged and decided what to keep, rewrite or cut.
- Configured the services and handled deployment.
Where AI tools helped
- AI tools drafted and refactored code from structured prompts, and I iterated on the results.
Services connected
- Next.js, Supabase, OpenStreetMap for maps, WebRTC for in-app calls.
Working today
- A deployed demo. Which features work end to end is listed in the confirmation checklist.
Still prototype or planned
- Several planned features, and email delivery, which is waiting on a domain.
Written from my own account of the build.
- Scoping a large feature set honestly and building the core flows first.
- Email delivery is waiting on a domain.
A deployed demo you can explore above, tested at Sankalp Setu. No usage numbers are claimed.
Event tools succeed on the day, so reliability beats feature count.
Hosting an event and need guest tooling?