The date never lands
Enthusiasm gets reactions. A gathering needs a host, a date, and a visible decision.
Foodies gives a private, recurring dinner club one place to choose the next gathering, invite the group, coordinate who brings what, and keep the story after the plates are cleared.
A private clubhouse for your people—not restaurant discovery, a public feed, or another group chat.
A dinner club rarely dies because nobody wants to meet. It fades when every gathering starts from zero: dates drift in chat, contribution plans split across messages, and the next host inherits no useful history.
Enthusiasm gets reactions. A gathering needs a host, a date, and a visible decision.
Contribution state belongs in one current plan, not scattered across yesterday’s messages.
Without recaps and a club book, the traditions, photographs, and lessons leave with the thread.
Foodies connects the whole club lifecycle. It is built for an ongoing private group, not only a single dinner invitation.
Choose the name, crest, cadence, and the tradition you want to keep.
Invite the members with one private club link.
Name the theme, host, date, place, and the details the group needs.
See RSVPs and let members claim contributions in the current plan.
Save photographs, notes, and the moments worth remembering.
Carry the rhythm, history, and next host forward instead of restarting.
No menu generator, shopping list, public follower count, or restaurant directory. Foodies focuses on the coordination and continuity a real private club needs.
Put the theme, host, date, location, and invitation details in one current gathering. Members see the plan that exists now rather than reconstructing it from chat.
Illustrative Foodies product state using the first-party Tower Duels club story.
Members can respond and claim what they are bringing. The host sees the current state without collecting answers manually or promising specialist allergy, reminder, or shopping-list features Foodies does not offer.
Private member state stays inside the clubhouse.
Recaps, photographs, traditions, and the club book make each gathering useful to the next. The handoff is part of the product, so the same organizer does not have to revive the club alone every time.
Tower Duels: the real cook-off format and founding reference for Foodies.
Tower Duels is the real cook-off format behind the product examples on this page: two competitors, two apartments, two kitchens, and two teams. The winners earned bragging rights, making it clear that the club needed both a plan for the next duel and a record of the matchups, dishes, and results.
Foodies is the private clubhouse we kept wishing existed—the identity, next plan, contributions, photographs, and club history in one place.
— Tower Duels, the founding cook-off
A supper club app helps a recurring group organize its identity and gatherings. Foodies is specifically for private friend groups: it combines invitations, gathering details, RSVPs, contribution claiming, recaps, and club history.
Yes. “Supper club,” “dinner club,” and “food club” often describe the same private recurring ritual. This page combines those organizer needs in one product instead of creating separate, overlapping versions.
No. Foodies does not list restaurants, public dining events, or local clubs to discover. A founder creates a private clubhouse and invites the people who belong there.
Yes, members can claim contributions for a gathering. Foodies does not currently claim specialist features such as grocery lists, payments, allergy detection, or SMS reminders.
The recap, photographs, traditions, and club book stay with the private club. The group can hand off the next gathering without rebuilding its identity or history from scratch.
Choose the club identity, bring the group in with one link, and put the next dinner on a date that exists.