Built around a table.
Born from a campfire.

Could you imagine just bringing chips and feeling like you need to bring the dip too?

That was the problem. Not just chips and dip — it was all of it. The duplicate casseroles at Thanksgiving. The three people who all brought potato salad to the camping trip because nobody wanted to be the one who showed up empty-handed. The holiday potluck where everyone defaulted to their "safe dish" without knowing what else was coming.

BringWhat started as a response to a very specific kind of social anxiety: the pressure to over-bring, the fear of duplicates, the group-chat chaos of "who's bringing what?" threads that somehow never get fully resolved.

The idea is simple: a host creates an event, guests claim what they're bringing, and everyone shows up knowing exactly where they fit. No duplicates. No group-chat archaeology. No chips without dip.

It started with a camping trip and a very basic form.

The first version of BringWhat was not a product. It was literally a form and a link. A group of friends needed to coordinate a camping trip — who's bringing the propane, who's got sandwich supplies, who remembered condiments — and the existing solution was a phone thread nobody could keep up with.

The first version went live and solved the immediate problem. But what made it stick wasn't the technology. It was the moment someone noticed that because items were claimed, people started piggybacking — "oh nobody's bringing pickles, I'll grab a jar." The list became a conversation. Ownership spread naturally. Comradery followed.

That camping trip is still the north star. Every feature decision comes back to one question: does this make that trip better?

Jazzy Annies and the art of elevating something simple.

There's a particular kind of gathering that captures everything BringWhat stands for: Jazzy Annies. The premise is straightforward — take a box of Annie's mac and cheese and make it extraordinary. Everyone brings their version. Everyone competes. Everyone eats.

It's a blueprint: take a shared base, let people express ownership over their contribution, and watch what happens when the stakes are low but the creativity is high. That's potluck culture at its best — and it's exactly the kind of gathering BringWhat is built to support.

The vision has always been broader than food, though. A wish list for a birthday. A camping gear manifest. A white elephant exchange. Any time a group needs to coordinate who's bringing what, without leaning on a spreadsheet or a forgotten message thread.

A friend pitched the name. He's been waiting for his cut ever since.

Naming a product is hard. The domain potluck.fans was purchased early — it felt right, warm, specific. But the right name came from a friend one evening over a conversation about the project. He offered "BringWhat" and asked for a share of revenue for the first five years the site is live.

That was over sixteen years ago. BringWhat.com was sitting with a domain squatter for a decade before it was finally acquired. potluck.fans is still in a drawer, waiting for its moment.

The friend is still waiting too. He knows who he is.

Three things BringWhat stands for.

Not features. Not pricing tiers. The things that guide every decision about what to build and what to leave out.

A community built around showing up in person.

The ambition is straightforward: build something that sustains itself, that keeps getting better, and that helps people find more reasons to gather in the same physical space over food.

In a world that increasingly lets us opt out of physical presence, there's something worth protecting about sitting around a table with people you care about — everyone having contributed something, everyone with ownership over a small piece of the evening.

That's the long game. A passion project that earns its place. A community that doesn't need to be manufactured because the gatherings themselves create it.