When you build for volunteers, every feature has a hidden cost: someone with a day job has to learn it, and then teach it to the person who replaces them next July. So our launch decisions were as much about what to leave out as what to put in.
Here’s what’s in the box — and the three things we’re deliberately not building yet.
The seven we’re shipping
1. The commitment ledger. The core. A typed, append-only record of what each family owes and has contributed — requirements, worked hours, buyouts, fundraising credits, exemptions, and adjustments, each with its reason. Everything else is a view onto this.
2. Volunteer sign-ups. Create an event, set the slots, let families claim them. No more reconciling three sign-up tools — the slots and the credits live in the same place.
3. QR check-in. A scan at the door posts the credit to the family’s ledger in real time. It removes the most error-prone step in the whole chain: someone re-keying names from a clipboard three weeks later.
4. Family self-service statements. Every family can pull up their own ledger any time — owed, worked, bought out, the rate, the dates. Most “how many hours do I have?” emails stop the day this goes live.
5. The treasurer’s reconciliation view. The year-end statement as a derived report, not a hand-stitched spreadsheet. The May reconciliation panic was the problem we started with; this is the answer to it.
6. Role-based access. Access follows the role, not the person. When the treasurer changes, the new treasurer inherits the treasurer’s access. Nobody is ever locked out because someone graduated their youngest and stopped checking email.
7. The handoff view. A guided walkthrough for the incoming board: open items, current configuration, and what’s unusual about your school. The July handoff turned into a checklist instead of a coffee that never gets scheduled.
The thread through all seven: the organization should never lose its memory just because its people changed.
The three we’re not building yet
We could have built more. Here’s what we chose to wait on, and why.
1. Payments and a built-in payment processor
Tempting — buyouts are money, money wants a checkout button. But payments mean PCI scope, refunds, disputes, and a support burden that a two-person company can’t carry well in year one. For now, you record buyouts in the ledger and collect them however you already do. We’d rather do the ledger excellently than do payments adequately.
2. Communications and mass email
Every parent org needs to email families, and it’s tempting to fold that in. But the email space is crowded and well-served, and building a deliverability-grade mailer is a company unto itself. We’d rather integrate cleanly with what schools already use than build a worse version of it.
3. Reporting dashboards and analytics
We’ll get there. But fancy charts are a year-two feature for a tool whose year-one users mostly want one clear statement per family and one clean reconciliation. Building dashboards now would be polishing a room nobody’s asked to sit in yet.
Why “less” is the right answer here
The instinct in software is to add. For a volunteer organization, addition is expensive in a way it isn’t elsewhere, because the cost lands on people who didn’t ask for it and won’t be here next year to maintain it.
Every feature we ship has to survive a brand-new board learning it cold in July. That bar quietly kills most “nice to have” ideas.
So our roadmap is deliberately narrow. Do the ledger, the sign-ups, the check-in, the statements, the reconciliation, the access, and the handoff — and do them well enough that a new treasurer can run the whole thing in her first week. Everything else waits until it has clearly earned its place.
We’ll keep these updates honest, including the parts we get wrong. If there’s a feature you think we’ve mis-prioritized, tell us — we read every note. Email hello@lumicura.org.
Filed under: Product updates. If you'd like one of these in your inbox monthly, subscribe to Field notes.