How it works

From your spreadsheet to live, in about six weeks

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.

Getting you running

Six steps. Two of them need real time from your office; the rest are ours.

A conversation, and a look at your books

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 time: about an hour.

We set up your congregation

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.

Your time: none. Takes us a day.

Your data comes across

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.

Opening balances become dated charges so the arithmetic works out. Pledges become real pledges with real payment history. We do a dry run first, every time, and back everything up before writing.

We configure it to your shul

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.

Your time: a couple of sessions to get the wording right.

Your team gets access

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.

Go live — and the website with it

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.

Typical total: four to eight weeks, mostly waiting on content and data.

A week in the office, afterwards

What actually changes about the job.

WhenWhat happensWhere 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.

Who sees what

Three roles. One person can hold more than one — a treasurer who is also a member sees both, and switches between them.

🔑

Administrator

The office. Full access to contacts, money, settings and the website.

  • Two-factor required, always
  • Every action is stamped with their name and role
📝

Pledger

The gabbai. Records pledges without seeing anybody's financial history.

  • Cannot open another member's record
  • The contact list they see carries no personal details
👤

Member

Their own account, and only their own.

  • Pay, sponsor, download a statement, update their details
  • A spouse can have their own separate login

Questions we get asked

What if our data is a mess?
It usually is, and that is normal. Duplicate households, payments with no name on them, balances nobody can explain. We load it, then hand you a reconciliation showing exactly what came in and what did not tie out, so you can make the calls. Merging duplicates and re-attributing payments are both ordinary operations afterwards, not emergencies.
Do we have to move our payment processing?
Card payments run through the processor the platform integrates with, so that tokenisation, refunds and receipts all work as one piece. Cash, cheques, Zelle and bank transfers are recorded as they always were — the office enters them, and they behave identically in the ledger.
What happens to members who will never log in?
They never have to. They get a statement by email with a personalised link that opens straight onto what they owe and lets them pay it — no password, no account. And the office can always take a payment on their behalf, exactly as it does today.
Can we keep our current website?
Yes. It keeps its design; we wire in the parts that need to be live — schedule, events, donate, sponsorship — and leave the rest alone. Or we build you a new one. Both are covered on the Your Website page.
Who owns the data?
You do. It is your congregation's records, held in your congregation's own isolated space. If you ever leave, you get a full export of everything — contacts, pledges, transactions and history — in a format you can actually use.
What if two people edit the same thing at once?
Settings changes are merged field by field rather than last-one-wins, so two administrators working at the same time do not silently undo each other. This is the kind of thing that only shows up in a real office, which is where we found it.
How much of our time does this take?
Realistically: an hour for the first conversation, a few hours gathering data and content, and two or three sessions agreeing the wording of pledge types and membership tiers. The migration itself is ours.

Start with a conversation

No obligation, and no slide deck. We would rather look at your books and tell you honestly whether this fits.