SEED Afrique
Membership management for a multi-app platform, plus the database-per-app architecture holding athletics, forms, accreditation and membership together.
- Admin overhead cut
- 30%
- Apps on the platform
- 4
Case study
SEED Afrique's admin team was spending real hours on membership work that software should have been doing. Registration, renewals, records, reporting, all of it manual enough to be a bottleneck.
I designed and built the full-stack system that replaced that process. Both halves, which is the part worth pointing at: the interface was drawn in Figma before any of it was written, so the thing that shipped is the thing that was designed rather than whatever the components happened to allow. Admin efficiency went up 30%. Firebase analytics went in behind it, so post-launch decisions came from what people actually did rather than what we assumed.
The wider platform
Membership was the first app, not the only one. SEED Afrique runs four surfaces: athletics, forms, accreditation and membership, and they share a MongoDB Atlas cluster on a database-per-app architecture.
That choice is worth explaining, because the obvious alternative is one database with a tenant column. Per-app databases keep the blast radius small. An accreditation migration can't corrupt membership records, each app's indexes are tuned for its own access pattern, and restoring one app from backup doesn't mean restoring all of them. The cost is cross-app queries, which turned out to be rare enough not to matter.
This is also where the sports work connects. SEED Afrique runs the athletics side operationally, which is how the competition software and the platform work ended up in the same orbit.
Screens
