Why we're building TripSync.

The trip that started it

A few years ago I went on a trip with three other families. Eight adults, four kids, one rental house, six days. The planning chat thread had over 400 messages by the time we landed. Two restaurants got booked twice. One family thought we were going to Topgolf Wednesday night; three of us were committed to a different dinner at the same time. Everyone had been agreeing in the chat — except nobody had agreed to the same thing.

We had a great trip. But the planning was its own little disaster, and the disaster wasn't anybody's fault. The tools we were using — group chat, Notes app, a shared spreadsheet, four different booking confirmation emails — weren't built for the shape of the decision.

The shape of the decision

Here's what's strange about planning a group trip: the actual decisions aren't really group decisions. They're household decisions, layered into a coordinated trip.

My family eats together; my buddy's family eats together; sometimes we eat together as one big group, sometimes we split. The kids have bedtimes. Some adults want a 6am hike, others want to sleep in. "What are we doing tonight?" isn't one question — it's six overlapping questions, one per household, and the right answer is often "different things, at the same time, by choice."

Most planning apps treat the group as one entity that needs to vote on a proposal. That's the wrong primitive. Trips don't run on consensus. They run on coordination — every household knowing what's happening, picking what they're in for, and trusting the rest to do the same.

What changed when we built TripSync around households

Once households became the primitive, three things fell into place:

• Interests replaced proposals. Instead of "vote yes or no on this restaurant," it's "react if it looks fun, pass if not." Reactions add up into moments — actual time-bound things where the crew picks where they're going. Lighter weight. Less consensus theater.
• Silence stopped being assumed consent. If you don't react, the moment doesn't decide for you. There's a nudge before the deadline so nobody's quietly steamrolled. And once a moment is real, picks stay editable until you actually walk in the door.
• Splits became normal. Three families want three different dinners on the same night? Fine. Each household's pick is a sub-event of one moment. The Plan tab shows them side by side. No friction, no awkward "are we all going?" — everyone's on the same page about who's where.

Where we are now

TripSync is in public beta. Free to use, mobile-first, available on iOS today (Android shortly). Real households use it for real trips — the next-trip cache that lights up your launch screen with "Vegas! · Apr 23–28 · 3 travelers" is built around how my family actually opens the app.

We're building this in the open. Decisions are documented, design choices are reasoned about, every iteration is shipped to the same beta channel I personally smoke-test. If you have feedback, the contact page is one tap away.

Who's behind it

TripSync is a product of Elev8 Ventures LLC, a small product studio I run. I'm Jason Wait — I've spent the last few years building consumer software for problems my friends and family actually had. TripSync is the most personal of those, because the trip that started it was a real trip with people I love.

— Jason Wait, founder