Manifesto

One person always plans the trip.

You know who they are. In every friend group, every family, every team, every bachelorette weekend — there is one person who ends up doing all of the work.

They are the one who opens the group chat and asks who's in. They are the one who finds the accommodation, checks the flights, negotiates the dates, chases the deposits, and answers the same three questions from six different people, in three different apps, four times each.

They love the group. That is why they do it. But somewhere between the fifth "wait what time are we leaving?" and the third time explaining the split, they quietly stop enjoying the trip they're planning.

The tools aren't broken. They're just not built for this.

WhatsApp is a chat app. Google Maps is a map. Sheets is a spreadsheet. Splitwise settles receipts. Notes is a notepad. Each of them is great at exactly one thing, and none of them know that a trip is happening.

So the organiser becomes the integration layer. They copy links. They screenshot the itinerary into the chat. They paste the map pin. They chase the payments in DMs. They are the API. And APIs get tired.

Assemble is one workspace per trip.

The itinerary, the map, the budget, the polls, the chat, the media — all attached to the trip itself. Not to a person. Not to a thread that scrolls away.

When plans change, nobody misses it. When it's time to pay, everyone sees the same balance. When the group has to decide, they vote once and the answer sticks. The organiser stops repeating themselves. The members stop asking. The trip stops being a project and starts being a trip.

We're building this for the person who always plans the trip.

And for the people they take on it. Because group travel shouldn't cost one person their weekend before it even starts.

— Oreneile & Nkululeko, founders of Assemble