Celevo
All-in-one event planning — guests, RSVP, seating & more
Hey IH 👋
Quick update on Celevo, my all-in-one event planning tool for the German/DACH market.
What's new since last time:
The feature list has grown significantly. On top of guest management, RSVP links, drag-and-drop seating chart and budget tracking, I've now added a full event website builder, bring-a-dish lists, carpool coordination, AI onboarding that generates a custom checklist per event type, and WhatsApp bulk messaging with personalized templates.
I also spent time thinking about something that most event planning tools get wrong: the person model. Right now a "guest" is just a row in a table. What I'm building toward is a proper person layer — the same human can be a guest at one event, a co-organizer at another, and eventually run their own events. One identity, multiple roles across events.
Where things stand:
Coming soon — waitlist is open. 47 people have signed up so far. Early bird pricing locked for the first 200.
Honest challenge:
Positioning. "Event planning" is accurate but too broad — no one thinks it's for them specifically. "Wedding planning" drives signups but misrepresents what Celevo actually does. Still working on this.
Question for the community:
Has anyone successfully launched a product in a non-English market first and then expanded? Curious how you handled the messaging shift when you went international.
Hey IH 👋
A while back I planned my 40th birthday, and then my wedding. Both times I ended up with the same chaos: guest list in Excel, RSVPs scattered across messages, seating chart on paper, budget somewhere in my notes app.
I looked for a tool that brings it all together. Everything I found was either too niche, English-only, overpriced, or missing half the features. Nothing was built for the German/DACH market.
So I started building Celevo — an all-in-one event planning tool. Guest list, personalized RSVP links, drag & drop seating chart, budget tracking, tasks, wishlists, vendor communication, and a public event website. Works for any event — weddings, birthdays, corporate parties, club events.
Currently in beta and building in public. If you're curious or know someone who'd find this useful — the waitlist is open: https://celevo.base44.app
Happy to answer questions about the build or the DACH market. And curious: has anyone here launched a product specifically for a non-English market? What worked for you?
-
1
The chaos you described is so real honestly. We built a similar event management app for a client and the exact same pain points came up during discovery. Guest list in one place, RSVPs in WhatsApp, budget in notes app, seating on paper.
The interesting part of your approach is going market specific. Most event tools try to be everything for everyone globally and end up being average for everyone.
DACH market specifically is interesting because German users have very different expectations around data privacy and UX compared to US products. GDPR compliance alone changes a lot of decisions in how you build.
One question from building side — how are you handling the personalised RSVP links at scale? That part sounds simple but gets technically interesting when you have events with 200 plus guests and need to track individual responses.
2 Comments
This is really interesting! The “person layer” idea sounds like it could be a huge differentiator — thinking about users across events instead of just rows in a table is smart.
Regarding your question: I’ve seen founders start in one language/market and then expand by first localizing content and marketing messaging while keeping the core product the same. Some also run small beta tests in the new market to validate terminology, cultural context, and feature expectations before a full launch.
Would love to hear how you plan to handle user support and communications when moving into new markets that often surprises people more than the product itself.
Love seeing the updates. Celevo is getting really robust! The “person layer” idea sounds especially smart; it’s such a clean way to manage identities across events.
About launching in a non-English market first: from what I’ve seen, the key is to focus on the core value in your messaging, then adapt the language and cultural context when expanding. People respond to benefits first, language second. Curious, are you planning to keep the same feature names and terminology for the international launch, or localize them?