Use case · Trip
Group trips don’t fail at the beach. They fail three weeks earlier, when one person puts the whole villa on their card because the booking would lapse — and becomes the group’s bank, collector, and pressure point for the next month. A trip room reverses the order: everyone commits first, the room collects, and only then is anything booked.
The real problem
The villa costs €3,000.00. The owner wants a €1,500.00 deposit within three weeks or the dates go to someone else. Nobody has agreed exactly who’s coming, so somebody — call her Maya — pays the deposit to stop the clock. From that moment the trip has a bank, and it’s Maya.
Now Maya chases three friends across two chat apps, keeps the running total in her head, absorbs the awkwardness of every reminder, and carries the whole loss if someone quietly drops out. None of that is a money problem. It’s a commitment problem — and it’s the part Rooms exists to take off one person’s shoulders.
The model room
Here’s the same trip as a room, mid-collection. Four people, €1,500.00 deposit, commit-by June 6, collection closes June 20.
Trip room
CollectingSandbox4 people · every promise is in · closes June 20
€750.00settled of €1,500.00 deposit
Who’s in
Sandbox — no real money moves here. Realistic sample data, not a live room.
The participant
You get a link in the group chat. Before you sign in — before any wall — you can see what you’d be joining: the room’s name, who’s organizing, your expected share (€375.00), and the commit-by date. Enough to understand and decide, never the group’s full money detail.
Committing is one step: “I’m in for €375.00.” That’s a promise, and the room shows it as one — a dashed line, plainly labeled, visibly not a payment. When collection opens, you pay, and your amount moves through states everyone can read: promised, then on its way, then settled. The room never calls money “paid” until the payment partner has actually confirmed it.
And that’s the last thing anyone has to ask you about. Your standing is on screen — the same calm typography for everyone — so no friend ever has to send the “did you pay?” text.
Edge cases
Sam’s project ships late and he pulls out before collection opens. The room recomputes on the spot: three shares of €500.00 instead of four of €375.00, with the change and the reason recorded where everyone can read them. Whether the trip still works at three is the group’s call — the room just makes the new numbers and the decision honest. If Sam had already settled, his money comes back as a refund entry with its own line in the record.
The owner drops the deposit by €200.00. The organizer edits the target, the room recomputes every share, and the timeline shows exactly what changed, when, and by whose hand. If the group has over-collected, the difference is returned — visibly, not absorbed.
Priya’s bank declines. Her thread breaks — a broken line marks the failed payment— and the room says exactly what happened: “We couldn’t reach Priya’s bank — nothing moved. Try again, or pick another way to chip in.” No money is in limbo, nothing is mislabeled, and the retry is one action.
Refunds are never quiet edits. Each one is its own entry with its own math — who, how much, why, and where it went — because the history of a trip’s money should read like a record, not a shrug.
Division of labor
That split is deliberate. Software should carry the arithmetic, the chasing, and the memory. It should never make a judgment call that belongs to four friends.
Start
The trip template preconfigures the threshold, the commit-by deadline, and the deposit-then-balance shape you saw above. Adjust any of it; the record starts at “The room opened.”
SandboxNo real money moves here yet.