From signed contract to first Shabbat live.

Before anything ships, we have a real conversation about what you currently use, what's painful, and which module gives you the biggest day-one win. Most synagogues start with Bimah + Honors (the run-of-service editor + honor planner) because that's the highest-friction surface for clergy + gabbaim. Some start with Pulse (the congregant help-desk) because it's a low-risk, high-visibility win.

• Discovery call: what your Saturday morning currently looks like
• Module selection: pick 1-2 to ship in week one
• Tenant provisioning: subdomain + auto-issued cert (~30 sec)
• First user invitations: you set passwords or use Google / Microsoft SSO

MyBimah ships with the Conservative service-order skeleton seeded — Pesukei D'Zimra → Shacharit → Torah Service → Musaf → Concluding, with proper section structure + standard prayer catalog + Sim Shalom + Etz Hayim page references. We adjust to your tenant's siddur, minhag, and scroll inventory. By end of week one you have a workable Shabbat Morning template that produces a full run-of-service with one click.

• Service-type catalog: confirm Shabbat Morning, RH Day 1/2, Yom Kippur Morning, etc. that your tenant uses
• Edition catalog: which siddurim + chumashim you have on the wall
• Liturgical sections + section leaders match your tenant's structure
• First template: "Conservative Shabbat Morning at [Your Tenant]" with your minhag baked in

Pick an upcoming Shabbat. Build the service order from the template. Add the parsha-specific Torah readings (auto-resolved from the ritual catalog). Assign section leaders + clergy. Plan honors via the Honors portal. Send a couple of test confirmation emails to staff. Do a dry-run of Bimah Mode + the SAGE projector so the operator gets comfortable.

• First service order built from template — usually < 10 minutes
• Honors planning for the upcoming date — share link with families
• Section-leader assignments + cross-role conflict detection
• Bimah Mode + SAGE dry-run on a weekday so Saturday morning is muscle memory
• Print Options modal: pick the PDF format your gabbaim prefer

First Saturday morning live. Operator runs SAGE from a laptop on the bimah; projector renders on the wall display. Clergy have the run-of-service open on their iPad with live ETA. Honor cards printed Friday afternoon from the Honors portal. Kitchen team has the facilities ETA kiosk URL on a tablet so they know when to pull the kiddush trays.

• Pre-service: holding screen with tenant logo + start countdown
• During service: operator drives Start / Next / Back / End; clergy can take the wheel from any device
• Live calibration when the dvar runs long — kitchen sees the delta in real time
• Post-service: wrap-up + honor history populated automatically

With Bimah + Honors + SAGE running smoothly, week 4 is usually when we add the next module. Pulse for the help-desk + community board. Lifecycle for the next shiva or B'nei Mitzvah. Yahrzeit Memorial Board if you're paying a kiosk vendor today. The infrastructure is in place; new modules ship without any tenant-side migration work.

• Pulse activation: tenant_settings.pulse_enabled flag, 8 pre-seeded categories
• Lifecycle: import existing Lifecycle templates, configure off-site venue defaults
• Yahrzeit Memorial Board: bulk import script from your current vendor's CSV / XLSX export
• Email templates: customize per-tenant for your voice + branding

Direct line to the founder during beta. Weekly office hours + Slack channel. Real responsiveness on edge cases — when your gabbai discovers an honor flow we hadn't considered, we ship the fix the same day. The launch-partner cohort directly shapes the product roadmap.

• Weekly 30-min office hours during beta
• Slack channel for fast-turnaround questions + feature requests
• Same-day bugfix turnaround on showstoppers (the platform deploys via push to main)
• First seat on every new module beta — CRM, Facilities, Building Access