Guest context gets separated from the menu.
Dietary notes, preferences, and headcount often live in texts or memory while recipes live somewhere else.
Soiree keeps the guest list, dietary notes, menu, groceries, RSVPs, and prep in one place, so the plan changes when the dinner changes.
Built mobile-first. Guests can RSVP from a browser link.

A dinner party is a set of dependencies. Who is coming changes what you cook. What you cook changes what you buy. What you buy changes what needs to happen before guests arrive.
Dietary notes, preferences, and headcount often live in texts or memory while recipes live somewhere else.
Ingredients are copied by hand from recipes, adjusted for servings, then rebuilt again in a grocery app.
Cleaning, timing, setup, and day-of cooking tasks usually become visible only when time is short.
Soiree follows the way dinner planning actually unfolds: people first, food second, logistics after.
Save guests, groups, RSVPs, dietary restrictions, preferences, and notes before the menu takes shape.
Import recipes, assign courses, track servings, and keep guest constraints visible while deciding what to serve.
Create groceries and checklist items from the plan instead of maintaining separate lists by hand.
Guests can respond from the browser, share dietary notes, and see event details without installing the app.
Keep regular dinner groups, family lists, and recurring preferences ready for the next gathering.
Bring recipes into the plan so menu decisions can inform servings, groceries, and prep.
Use a list that reflects the menu, then share it when someone else is helping shop.
Join the waitlist for launch updates and beta invites.
Soiree is being built mobile-first, with iPhone as the initial launch target.
Yes. Shared RSVP pages work in the browser so guests can respond from a simple link.
Yes. Guest notes and dietary preferences stay connected to the party and menu planning flow.
No. Soiree works for casual dinners, brunch, cocktails, holidays, and recurring groups too.