Representative · TripLedger

How nine riders settled a Sylhet tour without a single argument

2026-08-094 min readBy Black & White Studio
About this study: A representative scenario built from real user conversations and support threads. Names and identifying details are changed and numbers are rounded. The workflow, the objections and the outcomes are faithful to what actually happens.

Nine riders, four days, Dhaka to Sylhet and back. Tea estates, Ratargul, one puncture, one rain day. The riding was the easy part.

The group had done this before. The previous tour ended with a WhatsApp thread that ran for eleven days after everyone got home, and one rider who quietly never paid his share because nobody could work out precisely what it was.

Why the WhatsApp method fails at scale

With three or four people, a chat thread and a bit of goodwill works fine. At nine it collapses, for reasons that are structural rather than social:

9
Riders
60+
Shared expenses
5
Final transfers
11 days → 0
Post-trip chasing

The four rules they set before leaving

This is the part that generalises. The app matters less than the agreement.

1. Everyone puts in a deposit up front

Each rider contributed to a kitty before departure. This does not change the maths at all, but it changes the psychology completely — the group spends from a pot rather than one person perpetually fronting money and feeling like a creditor for four days.

2. The split mode is chosen per expense, not per trip

Fuel was split by bike, because a 150cc and a 500cc do not consume alike and pretending otherwise is the classic bike-tour argument. Hotel rooms were split among their occupants only. Meals were equal. The boat was split among the seven who went.

Getting this right at the moment of entry is the single biggest lever. Every expense logged with the wrong split is a renegotiation waiting to happen at the end.

3. Log it within the hour, or it didn't happen

A soft rule, enforced by mockery rather than policy. Same-day entries are accurate; three-day-old entries are archaeology. Because the ledger works offline, the tea-estate roads with no signal were not an excuse.

4. Nothing gets deleted

Mistakes get voided, not erased, and stay visible in the history. This sounds bureaucratic for a group of friends and turned out to be the reason nobody contested the final numbers — anyone could scroll back and see exactly what had been corrected and when.

The ledger didn't prevent disagreement. It made disagreement cheap — you point at the entry instead of at each other.

The settlement

Over sixty expenses across nine people implies a genuinely ugly web of obligations. Settled naively — every debt repaid to whoever paid — it would have meant well over twenty transfers.

Netting the positions collapsed it to five transfers. Three riders paid, five received, one was already square. It took about four minutes in a roadside tea stall on the way home, and the trip was closed before anyone reached Dhaka.

What we'd do differently

  1. Agree the fuel rule before the first fill-up. Not the second. The first fuel stop is where the bike-size argument is born, and having it in the rain at a pump is worse than having it on a WhatsApp call a week earlier.
  2. Set the deposit high enough to cover roughly 70% of the trip. Too low and one person still fronts everything; too high and people resent the idle money.
  3. Nominate a second ledger-keeper. The one weakness in this trip was that a single person's phone held the state. A backup and a co-editor removes that.
  4. Settle before you get home. The tea stall settlement worked because everyone was still together. Once the group scatters, chasing resumes.

The transferable lesson

Group-trip money is not really an arithmetic problem — the arithmetic is easy. It is a record-keeping and legitimacy problem: everyone must be able to see how a number was reached, and no one must be forced into the accountant role. Solve those two and the settlement is trivial. Solve neither and you get an eleven-day thread and one friendship quietly taxed.

TripLedger — group trips, settled

Per-tour ledger with four split modes, deposits and refunds, and a one-tap settlement that minimises the number of transfers. Offline-first — the whole ledger fits in your pocket.

See TripLedger →