Skip to content

Ndoa Plan

Event Tech / Fintech

Offline-first wedding coordination platform for Kenyan events - payments API reconciliation, budget tracking, and day-of execution tools.

View Live Site
Ndoa Plan

In progress

Offline-first wedding coordination platform built for Kenyan weddings, with payments API reconciliation, multi-event planning, budget tracking, and real-time day-of execution tools.

Background

Kenyan weddings are complex, multi-day events involving dozens of vendors, hundreds of guests, and financial contributions collected through digital payment channels. Spreadsheets and WhatsApp groups collapse under that weight. Ndoa Plan was designed for event coordinators who need reliability - the app works fully offline, syncing data when connectivity returns, and reconciles payment-provider callbacks to track who paid what. Building offline-first with Dexie (IndexedDB) as the primary store while keeping a Postgres backend in sync was the most technically demanding part of the project.

What it has to get right

Building a reliable planning tool for low-connectivity environments while keeping financial data consistent across offline-first sync, payment-provider callbacks, and a multi-user role system.

Solution

Implemented a Dexie-based local-first store with a background sync queue, conflict resolution strategy using server timestamps, and a webhook handler for payments API callbacks that reconciled payments against guest contribution records.

Tech Stack

Next.jsTypeScriptPrismaPostgreSQLDexie (IndexedDB)Payments APIsSupabase StorageTanStack QueryTailwind CSS

Related Service

Payment edge-cases in high-volume events can drain startup capital fast. The payment reconciliation system built for Ndoa Plan is the same pattern I apply across fintech projects.

See Fintech Automation & Payments API Integrations

Project Profile

2026
Full-Stack Developer
Ongoing

Evidence

Offline support
Full create, read, update and delete
Reconciliation
Payment callbacks matched to contributions
Local store
Dexie over IndexedDB with a sync queue
No label
An implementation fact: this exists in the system.

Interested in building something similar?

Get in touch