Introduction
TBD Lounge set out to give conference and event attendees a better way to discover events, engage before arriving, and network once there. But the founder had one core assumption to test first: would people actually sign up and return, or just stick with tools like Eventbrite or LinkedIn Events? NexiOrbit built the MVP to answer that question in 45 days.
The Challenge
The MVP had to be compelling enough to drive real sign-ups and generate genuine engagement data — while staying lean enough to pivot quickly if the first version missed the mark. Getting people to try a new events app is hard; getting them to come back is harder, and that return behavior was the real thing being tested.
The Approach
We kept version one focused on browse, discover, and save. RSVP functionality and in-app networking — both compelling features — were deliberately scoped for version two so the team could validate the core discovery loop first.
Tech Stack
- Framework: Flutter for a polished cross-platform experience from a single codebase
- Backend: NestJS and PostgreSQL
- Integration: RESTful APIs powering event data and user interactions
- Engagement: Push notifications and personalized event feeds as the core engagement loops
The Results
TBD Lounge launched in 45 days. The founder onboarded early users from their existing network and used engagement data — session length, event saves, return visits — to confirm that the discovery experience was the strongest hook in the product. That gave them clear signals on what to build next, without spending six months on assumptions.
Key Takeaways
- Test the return behavior, not just the sign-up. The real question wasn't whether people would try TBD Lounge once — it was whether they'd come back.
- Engagement metrics can validate a hook before a single RSVP feature is built. Session length and saves told this founder what was working before the harder features shipped.
- A narrow version one protects against a costly pivot. Because RSVP and networking were deferred, changing direction based on early data didn't mean throwing away months of work.
Frequently Asked Questions
What core assumption was TBD Lounge's MVP designed to test?+
Whether people would actually sign up and return to a new events discovery app, rather than sticking with existing tools like Eventbrite or LinkedIn Events.
Why were RSVP and networking features left out of version one?+
To validate the core discovery loop first — browse, discover, save — before investing in more complex features, so the team could pivot quickly if the first version missed the mark.
How did the team measure whether the MVP was working?+
Through engagement data — session length, event saves, and return visits — which confirmed the discovery experience was the strongest hook in the product.