CASE STUDY
İlkEvet
One link instead of paper invitations and phone calls; 4 themes, RSVPs per event and a one-tap English version.
Where it started.
A couple getting married wanted to send a link instead of paper invitations. Guests needed the venue and time without the couple explaining it to each one, and RSVPs had to be visible on one screen. Existing digital invitations did not look right, and none had everything needed, RSVP tracking above all.
What was done.
- Built for many couples from day one, not just one. When more couples asked to use it, payment and new themes were added. An invitation is used once, so payment is one-time.
- Every couple gets their own address, generated from their names. If it is taken, the wedding date is added, then a short unique code.
- 4 themes share the same content. What the couple enters fits every theme without being rewritten.
- One-tap English for guests from abroad. The couple’s text is translated automatically, interface text is written by hand, and the couple can review and edit the translation.
- Separate RSVPs for engagement, henna night and wedding on one screen. Map, countdown and add-to-calendar on the guest’s phone. Calendar was chosen over WhatsApp reminders to keep costs down.
Outcome.
Live since May 2026. The first couples sent their invitations with İlkEvet. Guest lists closed quickly, and guests from abroad and out of town found the venue and time on their phone, in their own language. Sample invitation: Summer Shore.
- Next.js
- TypeScript
- Supabase
- Lemon Squeezy
- Vercel
THE NEXT IDEA
What should we build together?
Three short steps. A written reply within 2 days.