🤝Product · Community CRM

The relationship layer your books don't have.

Pastoral care, development, family graph — in one workspace.

Membership systems are the books — dues, donations, accounting, billing. They're not the relationships. MyBimah Community CRM is the relationship + operational layer: pastoral touchpoints with follow-up workflows, donor cultivation pipelines for major-gift work, and a family graph that drives smarter honor auto-suggest and milestone reminders. The same data model that powers Pulse — adapted to relationship-tracking instead of help-desk.

In development

Beta cohort opening this year.

Architecture decisions in flight — leveraging the proven Pulse ticket model with a member_user_id FK. Different categories, same state machine + audit trail. We're lining up 3-4 launch-partner synagogues for the cohort. Request access if you'd like a seat.

Three flavors under one CRM

Member Relations

Pastoral touchpoints + life-event tracking

Track every meaningful conversation with a member: a hospital visit, a kiddush conversation about a kid leaving for college, a check-in after a yahrzeit. Follow-up workflows assigned to clergy or lay-leader teams. Visibility tiers respecting pastoral confidentiality. Bikkur Cholim deployable as a smaller standalone slice for synagogues that only need that piece.

Development

Donor cultivation + capital campaigns

Major-gift relationship tracking that doesn't live in your ED's personal email folders. Pipeline stages, next-action reminders, capital campaign workspaces with target tracking. Integrated with the membership system as the system of record for transactions — but capturing every relationship moment that isn't a transaction.

Family Graph

Who's related to whom — and when

Spouse, parent, child, sibling links across the membership directory. Drives smarter honor auto-suggest (\“the Goldman family hasn't had an aliyah in 14 months\”) and milestone reminders (\“Sarah Cohen's daughter Maya turns 12 next September — should we start B'not Mitzvah outreach?\”). Imports from membership system on first deploy.

Architecture preview

CRM reuses the Pulse infrastructure under the hood: the same ticket-style state machine + audit trail + email pipeline, with amember_user_idFK and CRM-specific category set (member_relation_call, donor_cultivation_meeting, pastoral_followup, …). Different surfaces, same backbone. Saves substantial build time and keeps the audit / email / search infrastructure unified across modules.

Want a seat in the CRM beta cohort? Tell us.

We're onboarding new launch-partner synagogues selectively while we mature the platform with our beta partner. Send a note and we'll set up a conversation.