The Household Problem.

Every trip planning tool on the market models the same unit: the individual. Google Flights searches for one traveler. Airbnb lists properties for one booking party. Doodle polls ask when each person is free. Splitwise tracks what each person owes. The entire category assumes the atomic unit of group travel is one person with one calendar, one budget, and one set of preferences.

That assumption is wrong. And it’s the reason most group trips never happen.

A trip with three families doesn’t have fourteen users. It has three households.

The mismatch

Consider a fall weekend trip with three families. Six adults, eight kids. In a per-person model, that’s fourteen people who each need to create an account, submit availability, state preferences, and stay in sync. In practice, one partner in each family does the planning. The other partner wants to be told when to show up. The kids have constraints — school schedules, soccer tournaments, a birthday party on October 12 — but those constraints live in the planning partner’s head, not in an app.

The budget is per household, not per person. The calendar bottleneck is per household — two adults sharing one weekend window, not two independent schedules. The decision about whether to go is made once, by the household, not twice, by each individual.

When a planning tool forces six adults into six accounts with six logins and six polls, it creates work that doesn’t map to how the group actually operates. The partner who never opens the poll isn’t being difficult. The tool is modeling the wrong unit.

The household as the right abstraction

When the product reasons at the household level, everything simplifies. Each household submits once: calendar windows, budget ceiling, kid logistics, vibe preferences. The constraint solver finds the intersection of three households, not the intersection of fourteen individuals. The Reluctant Participant — the partner who just wants to know the dates — becomes a first-class user whose silence is data, not neglect.

Costs are tracked per household. Decisions are surfaced per household. The itinerary lands in one shared view per household, not fourteen inboxes. When the trip is over, the memory card belongs to the household — a shared artifact, not fourteen individual notifications.

The partner who never opens the doc is not being difficult. The tool is modeling the wrong unit.

Why this matters for the trip

Most group trips die not from conflict but from friction. The friction of re-asking availability. The friction of re-confirming budgets. The friction of switching between the poll, the doc, the thread, and the booking site. Every per-person tool adds a layer of friction that the per-household model eliminates.

When the unit is right, the coordination cost drops. Three households submit three constraint sets. The solver finds the one weekend. The planner returns three trip options. One page is the source of truth. The trip that almost didn’t happen, happens.