Sign inGet the wedding out of the WhatsApp group.
Budget, committee, vendors and guest lists in one place that everyone can see — instead of scattered across nine chats and a spreadsheet nobody trusts.
- For couples
- For planners
- For committees
Budget summary
ExampleComputed automatically · full audit trail
The reality
A Kenyan wedding is not one event.
It is several, spread over months, paid for by dozens of people, and coordinated by whoever happens to be holding the notebook. Spreadsheets do not survive this. Neither does a WhatsApp group with 300 messages a day.
3ceremonies
The traditional ceremony upcountry, the church or civil service, the reception in town. Three guest lists that overlap but do not match.
14on the committee
Each one pledged something. Some paid in full, some in bits, some not yet. Somebody has to know which is which without asking around.
40vendors
Quoted, booked, confirmed, paid, or gone quiet. The florist you spoke to in March is not the one you argue with in June.
Trust
Money that adds up.
Most of the money in a Kenyan wedding is not yours. It is pledged by family, collected by a committee, and spent by whoever is nearest to the vendor. That only works if the numbers can be checked.
The budget cannot drift
A budget line’s actual is the sum of its completed payments — computed, never typed. There is no field for anyone to fudge, including you.
Record it once, everywhere updates
Log a payment against a budget line — in full or in part — and the line, the category total and the overall budget all move with it. There is no second spreadsheet to remember.
Recent activity
Auntie Wanjiku — pledge
Contribution · Jul 28
Caterer — deposit
Manual · Jul 26
Uncle James — pledge
Contribution · Jul 24
Every entry links back to its original confirmation or receipt.
Every pledge accounted for
Who committed, who has paid, who has paid part, who is overdue. You will not have to chase your uncle three times because nobody wrote it down.
Nothing is quietly deleted
Every change is logged with who made it and when. Records are archived, not destroyed. When a vendor disputes something, you have the receipts.
Reliability
And it does not lose your work.
Not a headline feature so much as a floor. Everything writes to your phone first and syncs when it can, which matters on the handful of days when the network is against you.
Four hundred guests, one mast
Coverage is rarely the problem; congestion is. When the whole reception is on the same tower at 2pm, check-in and payments still write to your phone first.
Ceremonies away from town
The traditional ceremony is often somewhere the network is genuinely thin. That is the one day you cannot ask people to wait for a page to load.
If sync fails, it says so
After five failed attempts it stops and tells you, rather than quietly dropping work and letting you discover it on the day.
Fit
Your wedding, not a template.
Set the cultural type and the events you are actually holding. Each event carries its own guest list, budget, vendors and programme — so the traditional ceremony is not squeezed into a form designed for a reception.
Cultural types
- Standard
- Kikuyu
- Luo
- Kamba
- Kalenjin
- Coastal
Choosing a traditional type turns on the parts that only apply there — dowry tracking among them.
Events
- Traditional
- Engagement
- Civil
- Wedding
- Reception
- After-party
- Post-wedding
- Honeymoon
Hold two or eight. Guests can be invited to some and not others, and be counted correctly in both.
What’s inside
One place that agrees with itself.
Every part reads from the same records, so a payment recorded in one place changes the budget everywhere it appears.
The people
- Guests, households and RSVP
- Check-in, per event
- Transport routes and seats
- Accommodation
The money
- Budget lines and variance
- Payment tracking
- Committee contributions
- Dowry and gift registry
The suppliers
- Vendors and status
- Appointments
- Contracts and documents
- Notes on every conversation
The day
- Programme, hour by hour
- Who to call, and for what
- Incident log
- Risk alerts before the day
For planners
Running more than one wedding?
Each client gets their own workspace. Couples, committee members and vendors see only their part, every change is attributed, and the audit trail is there when a supplier remembers the quote differently than you do.
Early access
We are taking on a small number of weddings for the 2026 season.
Ndoa is new. There is no long customer list to show you yet, and we would rather say so than invent one. What there is: an offline queue that has been tested against real network failure, budgets that are computed rather than typed, payments that cannot double-count, and a log of every change ever made.
If you are planning a wedding in the next year — or coordinating them for a living — we would like you to use it and tell us where it breaks.
— Dennis Ndung'u, Nairobi
Free while in early access. Sign in with Google.