Why I built Inyeet: the 50-call problem

Last November, my aunt was hosting her 25th wedding anniversary. She’d done everything right—the hall near GT Road was booked a full five months in advance, the designer invitation card was ready and printed by the Diwali break, and the caterer was the same one who’d done my cousin’s wedding. The function was on a Sunday. By the previous Wednesday afternoon, my aunt had no idea how many people were actually coming. I watched her place 50 phone calls in two days.

She wasn’t alone. Every uncle and aunty hosting a family event knows that phone number: 40, 60, 100 calls. Some guests never pick up. Some say “haan, pakka aa rahe hain” but don’t show. Some bring four extra family members you couldn’t plan for. The caterer wants a confirmed count by Thursday 6 PM because he orders mutton fresh. The tent guy needs chair numbers. The pujari for the griha pravesh wants to know how many havan kunds to set. All of this while you’re also doing the actual hosting—the tilak, the mehendi, the welcome drinks.

That Wednesday night, after my aunt showed me the notebook she was using—a spiral-bound diary with names, arrows, question marks, and things like “Bade Mamaji + family (4? 5?)”—I decided to build something so this wouldn’t keep happening to her, and to every Indian host I know.

The real problem isn’t the invitation—it’s what happens after

We Indians don’t struggle to send invitations anymore. If anything, we send too many: a printed card hand-delivered, a WhatsApp forward of the PDF, a follow-up “gentle reminder” on the family group, maybe a phone call. What we don’t have is a clean way to know who’s coming and how many plates.

The usual methods, as I saw them across my own family events and now hearing from dozens of early users:

• The Family Group Broadcast: You post the card on the group. People react with “🎉” or “Congrats” but never a headcount.
• The Phone Call Loop: You call each household. They’re driving, they’ll confirm later, “kidhar hai function?” for the fifth time.
• The Shared Spreadsheet: One well-meaning cousin makes a Google Sheet and drops the link on WhatsApp. Elder relatives can’t open it. Someone accidentally deletes a row. You still need calls.

None of these methods tell you, at a glance, things like: invited 87 guests, 43 have seen the invitation, 31 said yes, 12 maybe, 4 can’t come, 40 no response yet. And critically: none of them handle the plus-ones and family-bumps honestly.

I tried all of them before building Inyeet. The notebook was the most reliable backup, and that’s like saying “dribbling with one leg is fine”.

The failed fix that taught me everything

For a cousin’s pre-wedding sangeet last spring, I set up a WhatsApp poll. Simple questions: “Will you attend? Yes / No / Maybe.” I got 63 responses from a 120-person list. But I still had to call everyone who didn’t respond. And nobody could indicate how many family members were coming—the “yes” from one number could mean a couple or a family of five. The poll was fast but useless for counting plates.

Then we tried a shared note on the phone. Everyone could edit. Someone’s nephew added a list of his favorite Bollywood tracks into it by accident. We laughed, but the count was gone.

The insight landed slowly: what if each guest got a private link—just for them—that they could open on their own phone without installing anything? A link that told us: they’ve seen the invitation, they’ve responded, and here’s exactly how many people they’re bringing. And if they forward the link to someone else, the new person has to confirm their identity so the numbers don’t get padded.

That little mechanism—private, personal invite links with identity check on forwarding—changed everything. It meant a host could finally trust the dashboard, and the guests didn’t have to learn a new app or fill forms.

Building Inyeet, one real function at a time

I run a small product studio called Roy Digital. We’re not a giant team, and Inyeet wasn’t some VC-backed idea. It began as a tool for my own family functions, then for a few friends’ events. Each time, we’d notice a new edge case that’s deeply, specifically Indian:

• The relatives who don’t use WhatsApp but get a voicemail from the host, and then the host has to mark them “coming” manually. We added manual status overrides.
• The caterer who calls on Thursday demanding “final number with kids count separate.” We added headcount fields per family.
• The host who wants to send a reminder on Friday morning but doesn’t want to rewrite the same message 50 times. We added an AI assistant that drafts the message in English, Hindi, or Hinglish, and the host can edit before sending.

But we also decided what Inyeet would not do. It does not design invitation cards. You already have one—whether it came from a Canva template, a boutique designer, or the corner print shop. Upload it. Done. The app isn’t a social network; guests never create accounts. They tap a link, see a clean page with your card and some details, and reply in two taps. The host’s phone buzzes only when they choose to look at the dashboard.

The live dashboard became our most-requested screen. Open the app, and you see a table: Guest Name | Status (Opened / Yes / No / Maybe / Pending) | Family Count. You can sort, filter, export. It looks like something a host can stare at with a cup of chai and finally breathe.

The beta that’s changing Saturday afternoons

Right now, Inyeet is an Android app in private beta. The free plan covers one event with up to 50 guests—enough for an engagement, a small puja, or a baby shower. Paid plans for larger events start at ₹99 as introductory beta pricing. We’re keeping it simple because the only thing that matters right now is whether it actually makes hosting less stressful.

If you host a function with Inyeet, here’s what your Saturday afternoon looks like: you’ve already uploaded your card on Thursday, sent private invite links to each WhatsApp contact from your own phone (not a broadcast, not a business API—just your own WhatsApp, like you always message), and by Friday evening the dashboard is filling up. Saturday morning you glance at it, send a gentle Hinglish reminder to the “pending” folks with one tap, and give the caterer a real number. That’s it.

No 50 calls. No notebook with question marks. No “Beta, ek baar fir se count kar lo” from the caterer.

A small table: what we tried vs. what we use now

Method	Headcount clarity	Guest effort	Host time	Does it handle “Chachaji + 4”
Phone calls	Low, manual	Zero (for them)	Very high	Depends on memory
WhatsApp group poll	None	Low	Medium	No
Shared spreadsheet	Medium	High for elders	High	Rarely
Private invite link (Inyeet)	High, per-guest	Two taps	Low	Yes, with ID check on forward

If you’re debating whether you even need a guest-management tool, why guests don’t RSVP might feel painfully familiar. I wrote that post because in our beta events a big share of invitees always needed a nudge, and the pattern was always the same: they saw the invite, meant to reply, forgot. The app doesn’t force them to reply—it just makes it so easy that replying feels lighter than ignoring it.

When NOT to use Inyeet

I’m the founder, so I’ll say this plainly: if you’re hosting a function with 20–30 people, all of whom you talk to daily anyway, you probably don’t need the app. A few phone calls and a WhatsApp group will do. The tool makes sense when the list crosses 40–50, especially when you have a mix of close family, extended family, office colleagues, and neighbors—each expecting a different level of personal attention. That’s when the private-link model earns its keep.

Also, if you don’t have a clear invitation card yet or want someone to design one, Inyeet won’t help. We’re not designers. We’re the layer that handles the chaos after the card is ready. If that’s where you’re stuck, first read our wedding RSVP tracking without calls guide—it walks through the exact process even without any app.

Three things we keep hearing from early users

(No surveys, no statistics—just patterns we notice in calls and messages.)

1. “Maine bas link bheja, log khud respond kar rahe hain.” A friend hosting a griha pravesh told me he sent links at 10 PM on a Tuesday; by the next morning, 28 of 45 guests had responded. He hadn’t called anyone. He thought the app was broken because it felt “too quiet.”
2. Forwarded cards finally have accountability. In a joint-family setup, one household often forwards the invite to another branch. Without the identity check, the host would double-count or miss people. The confirmation step—just a name prompt—makes sure the numbers stay honest.
3. Elders who never “do online RSVP” are using it because there’s nothing to set up. A 67-year-old fufaji opened a link, saw the photo of the invitation he’d already received in print, and tapped “Yes, 2 people.” That was it. His host (my cousin) said it was the first time she’d gotten an RSVP from him without calling twice.

If any of this sounds like the relief you need for your next celebration, you can learn about how the invite sending works or peek at the paid plan structure. We’ve kept everything transparent because the product needs to earn its place in your phone, not be sold into it.

FAQ: the three questions I get after every chai

Do my guests need to download an app?
No. Guests tap a link that opens in their phone browser. No install, no sign-up, no login.

Can I use my own invitation card?
Absolutely. Upload the image or PDF you already have—the app doesn’t design cards and we never intend to.

What if I’m not on Android?
Right now, the host-side app is Android only (private beta). You can join the early access waitlist below, and you’ll get the iOS timeline when we’re ready.

If the 50-call problem is your problem too

I built Inyeet because I saw my aunt lose two days of celebration prep to guest-tracking. Since then, each beta event has been another lesson in how Indian hosts actually communicate, plan, and follow up. The specifics are fascinating: the way a Marathi host phrases a reminder is different from a Punjabi host; the way a griha pravesh invite needs muhurat details is different from a birthday party; the way guests reply to a link at 11:30 PM because that’s when they finally sit down.

We’re taking all of that and making the product better, one function at a time. No investors, no hype—just a bunch of us who’ve been the host, the caterer-caller, and the chai-making co-host trying to save you the 50 calls.

If that resonates, you can join the early access list at inyeet.com/early-access. If you have questions, email me or DM on the social that brought you here. I read everything, because that’s how this whole thing got built in the first place.

— Hrishikesh