Somewhere in your phone right now there's a WhatsApp group running real money. A savings circle. A wedding asoebi. A family compound's monthly contributions. A trip pool. A school reunion fund. One of these works because somebody is keeping the spreadsheet , and that person is almost certainly tired.
Kehbar's group agreements give that structure a proper home. The contributions arrive on schedule. The rotation is visible to everyone. The admin role is still there, but the role is holding the structure, not chasing payments. The judgement stays human. The repetition gets handled.
Group money tends to flow in one of four shapes. The template you pick decides how the group runs.
The classic ajo or esusu. Members contribute regularly; each round, one member receives the pot. Kehbar handles the rotation, the collection, and the payouts so the admin isn't carrying a spreadsheet.
Wedding asoebi, a group gift, a birthday party, a family event. Members contribute toward a single outcome, the pool fills, the money is spent. Visibility for everyone; chasing for nobody.
The trip, the dinner with twelve people, the group rental. Whoever fronts logs the cost; the running total is live for everyone. Settle when the moment is over.
Family money coordination, recurring obligations, the agreements that have their own shape. The structure holds what's actually happening without forcing it into a clean template.
From setting it up to the inevitable moments that need your judgement, group agreements follow a clear lifecycle. The admin role on Kehbar is smaller than the one you've been carrying.
Name, contribution amount or pool target, frequency, currency. The mechanics that define what the group is.
By email or phone. They get a link, join, link their bank account, and they're in.
Members appear in your approval queue when they accept the invitation. You confirm each one before they're active in the group.
When the membership feels right, you activate the group. From that moment, contributions and the rotation begin running on the schedule you set.
Someone misses a contribution. Kehbar surfaces two paths: extend the deadline to give them more time, or proceed partial so the recipient takes what was contributed while whoever fell short still owes that cycle. You make the call; the system carries it out.
Months in, you have a complete picture: who contributed when, who received which payout, what happened during the moments that needed admin judgement. Nothing to reconstruct from memory.
Each of these is a specific moment we've written about. The product underneath is the same: a group agreement, with the templates and lifecycle you've just seen. The pages below describe how it lands in the real situation.
Set up the structure, invite the members, approve who joins. The first contribution makes it real.
Join the waitlist