We do the migration. You review it. Nobody on your board has to become a database administrator, and no volunteer has to re-type a thousand rows.
Six steps. Two of them need real time from your office; the rest are ours.
We want to see how your shul actually works — what you call your aliyot, how membership is billed, whether you sell High Holiday seats, what the office currently dreads. An hour, usually.
Your own walled-off space in the platform, with your name, your logo and your colours. Nothing is shared with any other congregation — not the data, not the settings, not the login list.
Send us what you have — a membership spreadsheet, a year of transactions, a list of who owes what at the start of the year. We load it, then send you back a reconciliation showing every total so you can check it against your own books before anything goes live.
Pledge types in your wording. Membership tiers and what they cost. Payment methods your office actually uses, including cheques and Zelle. Products for tickets, seats and sponsorships. Kiddush and Seuda pricing.
Administrators, and anyone who should only see pledges. Every administrator sets up two-factor authentication on first login — that is not optional. Members are invited when you are ready, in batches or all at once.
The portal opens to your members. If we are doing your website, it points at your domain the same week. We stay close for the first month of statements, because that is when the questions come.
What actually changes about the job.
| When | What happens | Where it lands |
|---|---|---|
| Shabbat morning | Aliyot are pledged during the service and noted the way your gabbai has always noted them. | Nothing happens electronically until Shabbat is out. That is the point: the entry afterwards takes minutes, not an evening. |
| Motzei Shabbat | Someone types in the week's aliyot from the gabbai's list. | Each one raises a pledge and its matching charge together, on the right household, so the ledger is current before anybody asks. |
| Sunday | A congregant's cousin donates $118 on the website for a yahrzeit. | In the Transactions tab within seconds, flagged as an unattached guest payment, waiting for one click. |
| Monday | Somebody rings asking what they owe. | Filter Transactions to them: outstanding, paid this year, unpaid pledges and credit are on screen before the sentence finishes. |
| Tuesday | A cheque for $2,000 arrives with no note attached. | Enter it once; it pays down their oldest pledges in order, and anything left over becomes account credit rather than a mystery. |
| Wednesday | The Rabbi wants a kiddush sponsor for three Shabbatot. | Open the dates at a price. They appear on the website that minute, and the first person to pay gets each one. |
| Thursday | Statements go out to everyone carrying a balance. | Selected from the dashboard, sent in one pass, with a pay-now link in each. Payments arrive attributed, overnight. |
| Month end | The treasurer wants the numbers. | They are already the numbers. There is nothing to reconcile, because there was only ever one ledger. |
Three roles. One person can hold more than one — a treasurer who is also a member sees both, and switches between them.
The office. Full access to contacts, money, settings and the website.
The gabbai. Records pledges without seeing anybody's financial history.
Their own account, and only their own.
No obligation, and no slide deck. We would rather look at your books and tell you honestly whether this fits.