Funeral Fund

Full-stack developer / Product design · 2026

From membership to back-office, end-to-end design.

The need
Running a community funeral fund requires standalone online membership, a complete member record (household members, contribution based on age and family composition, documents), a sensitive death procedure and a back-office, all multi-tenant.
My contribution
I designed and wireframed the member lifecycle, wrote the user stories, then built the member portal, household management, the death procedure, the back-office and the matching API.
What was delivered
End-to-end ownership, from design to delivery, of the member portal, household management, the death procedure and the back-office.

What I built

A member portal, a back-office and a public site, served by one Clean Architecture API.

Member portal
Manage your record online.
Dashboard, household, payments and documents: members follow their own record.
React
Death procedure
Declare a death, with supporting documents.
Declaration, supporting documents and tracking of the procedure, in a flow designed for a sensitive moment.
React · Hono
Back-office
Records, funeral costs and billing.
Records, funeral costs, annual billing and pricing grid, for the fund's administration.
React · PostgreSQL
API and security
A solid API, battle-tested OTP codes.
Membership, household composition, contribution calculation and scheduled jobs for due dates. Security campaign on OTP codes: attempt-limiting audit, integration tests against brute force.
Node.js · Hono · PostgreSQL

1. Payments (ledger and Stripe) were built together with the mission architect.