1. Volunteers are the operating system of a synagogue.
Staff are essential. But the sheer volume of work — the kiddushim, the shiva meals, the minyanim, the committee meetings, the youth programs, the chevra kadisha calls at 3am — is done by unpaid people. The software needs to know that.
2. Gatekeeping isn’t governance.
A system where a volunteer has to wait three days for a room booking or a listserv email isn’t careful — it’s broken. Real governance is visibility, accountability, and alignment. Not a ticket queue.
3. The office isn’t the enemy — it’s the bottleneck.
Synagogue staff are usually overworked, underpaid, and wearing six hats. Routing every request through them is unfair to them and corrosive to the volunteers. The fix is not to replace staff — it’s to stop routing everything through them.
4. Tools shape culture.
When the only way to get something published is to email the office, the office becomes the gatekeeper of the culture. When volunteer groups have their own tools, they start acting like owners instead of petitioners. That shift alone is worth building for.
5. Respect the seriousness of the work.
Chevra kadisha is not a group chat. Leining rotations are not a Google Sheet. Bikur cholim is not a sticky note. The tools should match the gravity of what’s being coordinated.
6. Bilingual, proper Hebrew, always.
If the software touches liturgy, it has to render Hebrew correctly — not as an afterthought. Proper fonts, proper bidi, proper name conventions (ben/bat, with both parents, reflecting egalitarian minhag). This is a floor, not a feature.
7. Integrate, don’t replace.
We are not building a ChMS. We are not replacing ShulCloud, Rakefet, Breeze, or your existing systems of record. We’re building the layer that sits alongside them — the layer for the people whose work doesn’t fit inside administrative software.
8. Transparency over permission.
Staff and clergy should have visibility into what’s happening across volunteer groups. That’s healthier than making them the approval step for every action. Observer-by-default, gatekeeper-only-when-necessary.
9. Start where the pain is sharpest.
The gabbai sheet. The shiva meal train. The chevra kadisha rotation. The B’nei Mitzvah order of service. We’re building where the pain is real and specific — not a generic “synagogue platform” that never ships.
10. Built with congregants, not just for them.
Every feature is shaped by people doing this work on a Friday night. We’re not writing software for synagogue staff to administer volunteers. We’re writing software for volunteers to run their own work — and inviting staff to watch.