People ask why I built TableFolk and they expect a pitch. A market gap, a thesis, a deck. What they get instead is a dinner story, because that's the honest answer. TableFolk started the way most good ideas do: with a dinner that almost didn't happen.
Here's what that night taught me, and what two years of building this thing keeps confirming. Nobody needs another app. What people need is a reason to say "come over," and a way to make it actually happen, because the gap between "we should do dinner" and dinner actually happening is where most friendships quietly thin out. The app is the excuse. The table is the point.
The gap between "we should do dinner" and dinner happening is where friendships quietly thin out.
That's why TableFolk isn't really about food, even though food is everywhere in it. It's about the thing that happens around food: strangers at hour one, group chat by dessert. It's why supper clubs are having their biggest summer yet, and why the most exciting dining in Chicago right now is happening in apartments and backyards instead of behind a host stand.
Hosting your first supper club: steal this checklist
If reading this gave you the itch, good. Here's the checklist I wish someone had handed me before that first dinner.
One dish you've made at least twice before. One thing store bought, zero shame (bread, dessert, ice). A start time and a soft end time, because guests relax when they know the shape of the night. Music quieter than you think. And the only rule that actually matters: invite one person who doesn't know the others. That's the difference between dinner with friends and a supper club.
Your first event takes five minutes to create and one brave text to fill. The second one fills itself. Promise.