Why Jum
Less coordination.
More playing.
Every feature in Jum exists to remove a piece of admin from a game, not to add another thing to manage. That's the whole philosophy.
Before → after
The same weekly game. Two very different amounts of effort.
Today, without Jum
- Post "who's in?" and manually count replies scattered across a chat.
- Split players into teams by hand, five minutes before kickoff.
- Remember who paid for what, days after the event.
- Chase individual transfers, one DM at a time.
- Start next week's version of the exact same conversation.
With Jum
- RSVP is a running count everyone can see, live.
- Teams are drawn from confirmed attendees, published in one tap.
- Expenses are logged the moment they happen, by whoever paid.
- Settlement is one shared ledger — mark it paid, and it's done.
- Next week starts from the same group, already set up.
Jum isn't trying to replace your group chat.
WhatsApp is still where the banter happens, and it should stay that way. Jum only takes on the one job a chat log was never built for: being a system of record for who's coming, who's on what team, and who owes what.
It's built for the organiser as much as the player.
Running a weekly game is real, unpaid work — usually done by one person who quietly becomes the group's unofficial accountant. Jum is designed so that job takes minutes, not an evening every week.
Play first. Sort the rest.
That's the standard every feature in Jum is measured against: does this get a group of people onto a pitch, court or track faster and more fairly than a chat thread could — and does it get the money sorted without anyone having to ask twice? If not, it doesn't belong in the app.