ShulCloud consulting, from someone who worked there.
I worked at ShulCloud as its main trainer and financial expert, and I built its training protocols. Since then I've spent years implementing, repairing, and optimizing ShulCloud for congregations across the country and the world.
Where congregations get stuck
Congregations reach me at every stage: before they switch, a couple of months in, and sometimes many years later. The sentence is almost always the same. It isn't supposed to be this hard.
ShulCloud is a capable platform. Most of the frustration I'm called in for isn't the software — it's a configuration decision made in year one that nobody has revisited, or a set of features the congregation is paying for and not using.
A setup nobody owns
Initial configuration is largely left to the congregation, and the person who did it has often moved on. Nobody now knows why the account types are the way they are, so nothing gets changed and everything gets worked around instead.
Member records that don't hold the truth
Yahrzeit dates entered against the wrong calendar, households that never got restructured after a divorce or a death, b'nei mitzvah dates living in someone's spreadsheet instead of the system. It surfaces as an embarrassing letter to the wrong person, usually at the worst possible moment.
Billing season is coming
Dues billing goes out once a year, and every mismatch in the member file goes out with it. I work through the run with your staff: checking account types against billing types, running a test billing that sends nothing, and only then sending statements.
Reports the board doesn't trust
Dues, pledges, and payments are recorded inconsistently, so the finance committee asks a simple question and gets three different answers.
Features paid for, never turned on
Integrated payments, SMS, Enterprise capability — sitting unused because nobody had time to evaluate whether they'd help or how to roll them out.
Migration coming up
Moving onto ShulCloud, or moving payment processing onto SIP, and the data cleanup is the part everyone underestimates.
"When Temple Beth Or decided to move to ShulCloud, several administrators and executive directors warned us the switch would be painful. Working with Joseph Greenberg proved them wrong. We had no downtime and very few delays or issues, and we didn't lose any historical data from our 41 years."
Mark Gruenberg
President, Temple Beth Or, Dayton, OH
"Joseph Greenberg has been an incredible resource and support for our team. He was instrumental in making our migration to ShulCloud a success. Joseph knows ShulCloud inside and out and he also understands the complex needs of synagogues. I highly recommend that you contact Congregation Consulting today."
Reesa Olins
President, The Emanuel Synagogue, West Hartford, CT
"Joseph is knowledgeable, patient, and extremely responsive. He is always available when we need him and quickly resolves issues. I highly recommend him to any synagogue looking for ShulCloud assistance."
Michael Reichwald
Treasurer, Young Israel of Jamaica Estates, Queens, NY
How the work usually goes
A quick assessment first. I go through your ShulCloud site on my own, then we spend an hour on Zoom on what I found and what deserves attention — which is also your chance to tell me where the pain actually is.
Then the changes that matter. Reconfiguration and cleanup, starting with the demographic and membership records, and then the financial framework built on top of them — done with you rather than handed to you, so your team can maintain it.
Then training, if you want it. On your system, with your data, for your staff.
And implementation when you need it. Forms, emails, events, statements — the parts of ShulCloud that take longer than anyone has. When your office needs another pair of hands, I'm still here. I don't hand over a plan and disappear.
Bring me your ShulCloud problem
Migration, cleanup, financial setup, or a system that just isn't giving you what you need.