Published on:
Author: Aryan Singh — Founder & CEO, Event Flo
About this case study: names and figures are an illustrative composite of typical host activity on Event Flo, not the audited records of one individual. Event Flo never processes payments — guests pay hosts directly — so revenue numbers are host-reported ticket arithmetic, not platform-verified income.
Key results: Karan Mehta grew HSR Founders Table from a 12-person dinner into a waitlisted monthly community within a year, with zero paid promotion. Monthly dinners now sell out in 90 minutes. No-show rate: 4.8%. Every session is still manually curated.
Karan Mehta started by hosting twelve people for dinner at his HSR Layout apartment. All founders or operators. No investors, no press, no agenda beyond good conversation. He called it HSR Founders Table and charged Rs 800 per person to cover catering. A year later, HSR Founders Table had a monthly event that fills within 90 minutes and a waitlist for every session.
Why ID verification mattered from day one
Most networking events fail because signal-to-noise collapses as they scale. Karan wanted to avoid this. His solution: require government ID verification for every member and personally approve every RSVP. For every session he reviews each request, checks if the person is a founder or operator, and declines anyone who looks like sales or recruiting. A year in, he still does this for every session — about 45 minutes per waitlist.
The growth curve
Months 1–3: word of mouth (3 sessions)
Months 4–6: the community's Event Flo page starts ranking on Google
Months 7–9: attendee shares on LinkedIn and X
Months 10–12: organic growth, no paid promotion
What community builders can take from this
Set the identity bar first. Verification before RSVP means quality is protected from event one.
Keep approval manual for as long as you can. The 45 minutes per session is directly responsible for the community reputation.
Use a discoverable page, not a WhatsApp group. Organic Google traffic for founder dinner Bangalore contributed meaningfully to growth.
Charge from the start. Even Rs 400 separates genuine attendees from the merely curious.
Related on Event Flo
What the event format looks like now
The core format has not changed: 22 to 25 people, one dinner table in long format (not cocktail-style), one topic introduced at the start, two hours of conversation. The ticket price is now ₹1,200, up from ₹800 at launch, and still covers food costs with a small surplus.
Karan added two formats once the waitlist outgrew the table: a quarterly larger gathering of 60 people at a separate venue (₹600 per person) for members who cannot get into the monthly dinners, and a bi-monthly early-stage dinner for pre-seed founders only — 12 people, ₹400, more informal.
The quality problem that never materialised
Karan expected that growth would dilute the community. It did not, for reasons he attributes directly to the verification and approval system.
When I talk to members who have been coming for a year, they say the quality of conversations is better now than at the start. I think it is because the people who stayed are the ones who genuinely valued the format. The verification filter means we never had a phase where randos joined and made it feel generic.
The no-show rate across a year of monthly sessions: 4.8%. The average guest returns for 3.2 events before falling off (life logistics rather than disinterest). The longest-tenured members have attended 12 consecutive sessions.
More from the Event Flo blog
Frequently asked questions
How did the community grow?
Through word of mouth, an Event Flo community page ranking on Google, and consistently high-quality events enabled by ID verification and manual RSVP approval.
Can I charge for networking events on Event Flo?
Yes. Event Flo supports paid events at 0% platform fee. Hosts keep 100% of revenue.
How do I maintain quality as my community grows?
Keep approval-based registration active and review each RSVP manually. The combination of ID verification and manual approval keeps quality consistent at scale.