Software that doesn't understand its users will always feel off

A church admin shouldn't have to translate "donor" to "member" in her head every time she logs in. A synagogue treasurer shouldn't have to manually map fiscal-year deadlines onto the Hebrew calendar. A foundation shouldn't have to explain to a generic CRM what a restricted grant is. The platform should already know.

Every screen speaks your tradition's language

Same database. Same features. Different words. The platform's vocabulary engine substitutes terminology based on your org type — across the navigation, emails, donate pages, receipts, every screen.

⛪ Church admin sees

DonationsGifts
DonorsMembers
Sidebar sectionStewardship
RecurringRecurring gifts
CampaignInitiative

🕍 Synagogue treasurer sees

DonationsTzedakah, contributions
DonorsCongregation, members
Sidebar sectionTzedakah
RecurringRecurring tzedakah
CampaignAppeal

🛕 Temple or gurdwara coordinator sees

DonationsSeva, dakshina, daan
DonorsDevotees, sangat members
Sidebar sectionSeva (or community-specific term)
CampaignInitiative, appeal

🤝 Foundation or nonprofit admin sees

DonationsGifts, grants
DonorsDonors, funders
Sidebar sectionFundraising
CampaignCampaign, program
Live example — donor-facing vocabulary resolution
The field label "Offering" on a donate page resolves to a different tradition-correct noun for each donor cohort:
Christian donor
Tithes & offerings
Jewish donor
Tzedakah
Muslim donor
Sadaqah & Zakat
Hindu donor
Daan / Seva
Sikh donor
Dasvandh / Seva
Secular donor
Donation
Same platform. Same form. The right word for each person — automatically, based on their tradition profile.

The right calendar for the right community

Seasonal giving patterns differ by tradition. The platform knows your community's calendar and surfaces upcoming events as draft campaigns — so you launch on time, every time.

📅

Gregorian + secular

Fiscal year, civic holidays
Year-end giving, Giving Tuesday, Independence Day, civic anniversaries

Liturgical (Christian)

Advent · Lent · Easter · Pentecost
Christmas, Easter, Pentecost, Reformation Day, Advent Sunday, Lenten devotionals
🕍

Hebrew calendar

Lunar-solar, ~5786
Rosh Hashanah, Yom Kippur, Hanukkah, Pesach, Shavuot, Sukkot
🛕

Hindu calendars

Diwali · Holi · Navaratri
Diwali, Holi, Navaratri, Ganesh Chaturthi, Janmashtami, regional festivals
☸️

Buddhist observances

Vesak · Asalha · Magha
Vesak, Asalha Puja, Bodhi Day, Ullambana, regional new year traditions
🕉️

Sikh calendar

Nanakshahi calendar
Vaisakhi, Guru Nanak Gurpurab, Hola Mohalla, Bandi Chhor Divas

For Islamic giving (Hijri calendar, Ramadan-aware campaigns, Zakat tracking), see our companion platform Mohseen.

One platform for every tradition you serve

University chaplaincies, military religious-services programs, prison ministries, hospital pastoral care, hospice chaplaincy — your community isn't one tradition. The platform doesn't make you pick.

Configure multiple traditions side by side. A campus that supports Christian, Jewish, Muslim, Hindu, Buddhist, and secular humanist programs runs them all from one dashboard — each program's donors see vocabulary appropriate to their tradition, each program's seasonal calendar populated correctly.

Interfaith solution details →
Stanford Memorial Chaplaincy
Programs configured:
Memorial Church (Christian)
🕍Jewish Studies Foundation
🕌Muslim Student Association
🛕Hindu Cultural Council
☸️Buddhist Sangha
🕉️Sikh Student Union
Each program with its own donate page, vocabulary, calendar, and donor pool. Central admin sees aggregate; programs stay independent.

Subject Matter Experts review the platform's cultural content

Vocabulary mappings, seasonal templates, communication tone — none of this is hardcoded by a software team in Silicon Valley. Each tradition's content is reviewed by Subject Matter Experts from within that community. The SME workflow is built into the platform.

Submit

Platform curator or org admin submits a cultural overlay — vocabulary entries, seasonal events, communication tone for a specific tradition + region.

Assign

The platform assigns the overlay to an SME whose expertise matches: tradition, region, language. SMEs are real people, vetted, accountable.

Review

SME reads, comments, requests changes, withdraws, or approves. Every decision is captured with rationale. Full audit trail.

Publish

Approved overlay goes live for that tradition + region. Future orgs signing up with that combination get the SME-reviewed content automatically.

Example SME review — Ramadan appeal vocabulary
Original draft "Make your donation before the end of Ramadan"
SME revision "Give your Sadaqah before Laylat al-Qadr — the Night of Power amplifies every act of generosity"
SME note: "Sadaqah" is tradition-correct over "donation." Reference to Laylat al-Qadr provides theological motivation that Muslims respond to. "End of Ramadan" as a deadline is generic; the last 10 nights are the giving crescendo.

Your organization can also nominate its own SMEs for tradition-specific content review — turning leadership at your community into authorities on what the platform says.

Four layers, clearly separated

Cultural Intelligence isn't a feature flag. It's an architecture. Four layers, each doing one job, never confusing your data with anyone else's.

1

OrgContext — your org's profile

Tradition, region, denomination, size, history. Built from your signup choices and refined by your actual giving patterns. Stays inside your tenant — never shared.

2

Pattern analysis — your community's rhythm

Donor lifecycle stages, giving cadences, seasonal peaks. Inferred from your data, used only for your data. Drives autopilot recommendations and at-risk-donor flags.

3

AI generation — write-for-me

Campaign copy, message variants, thank-you wording. Anthropic Claude composes drafts tuned to your tradition + your patterns. Staff reviews; AI doesn't autosend.

4

Cross-org benchmarks — peer context

k-anonymity-preserving comparisons against similar-size orgs in your tradition. "Your average gift vs. median for similar churches in your region." Aggregate only; no individual donor data ever exposed.

AI that never trains on your data

Your donor records are yours. The platform never trains a model on your data. The platform never shares your data with other orgs. Cross-org benchmarks are k-anonymity-preserving aggregates only — your individual donor records are never exposed.

Security & data governance →