Expenddy vs a group chat
Almost every shared expense is mentioned in a group chat first. That is where the coordination happens — and it is the one place the numbers can never be totalled.
What a group chat does well
- Everyone is already in it. No install, no invitation, no adoption problem.
- Deciding things. 'Shall we get a taxi?' belongs in a conversation.
- Context. Photos of the restaurant, the reason someone left early, who was actually there.
- Speed. Sending 'I got the tickets, £34 each' takes three seconds.
None of that is in dispute. The problem starts when the chat is also expected to be the record.
What a chat structurally cannot do
It cannot total anything
Forty messages containing amounts do not produce a balance. Somebody has to scroll back, extract the numbers, and do the arithmetic — which is precisely the work everyone was trying to avoid.
It cannot distinguish intent
“I'll get this one”, “shall we split it?” and “I paid £60” look the same to a message thread. Weeks later, nobody can tell which were decisions and which were suggestions that came to nothing.
It has no concept of who shared what
The single most important fact about a shared expense — which people it applies to — is expressed in a chat as social context that everyone is assumed to remember. They will not.
It buries the record
Expense messages are interleaved with hundreds of unrelated ones. The information technically exists, in the way a receipt technically exists at the bottom of a bag.
The same weekend, two ways
What the chat holds
Four people, one weekend. This is what the thread actually contains, in order, among the other messages.
| Message | What it leaves unresolved |
|---|---|
| “Booked the cottage, £400” | Split how many ways? Has anyone paid towards it already? |
| “Got the food shop” | How much? Nobody said. |
| “I’ll sort petrol” | Future tense. Did it happen? |
| “Spa was lovely!” | Was it shared, and by whom? Who paid? |
| “what do I owe everyone?” | The question the thread cannot answer. |
Result: Answering the last message means one person scrolling back through the weekend, chasing two missing amounts, and doing the arithmetic — for four people, from memory.
The same weekend recorded as four expenses produces one number per person immediately. The worked version of this example is on the how-it-works page.
Side by side
| Group chat | Expenddy | |
|---|---|---|
| Everyone already has it | Yes | No — people need an account |
| Coordinating and deciding | Excellent | Not its job |
| Recording an amount | Yes, as text | Yes, as data |
| Totalling amounts | No | Yes |
| Who owes whom | No | Yes, per person |
| Who shared a given expense | Implied at best | Recorded explicitly |
| Finding an expense from three months ago | Scrolling | It is a row in a ledger |
| Settling and marking it settled | A message that says so | A settlement that clears the balance |
| Correcting a mistake | A later message contradicting an earlier one | Edit the expense, or void the settlement |
| Export | No | CSV |
Using both, which is what actually happens
Nobody is going to stop using their group chat, and they should not. The division of labour that works:
- Chat for deciding. Where to eat, whether to book the car, who is coming.
- Expenddy for the numbers.The moment money leaves someone's account, it becomes an expense with an amount, a payer and a list of people who shared it.
- Share the invite link in the chat. It is the natural place to get everyone into the group.
The habit that makes this work is small: when you would have typed “got the taxi, £22”, record it instead. It takes about the same time, and it produces something that can be added up.
Move the numbers out of the chat
Record a shared expense, see the balance update, and settle it when the money moves.
Free to use. Available for Android and in any web browser. An iOS app is in development and is not released yet.