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

A church admin shouldn't have to translate "donor" to "giver" 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.

Seven dimensions, resolved at signup

Cultural intelligence starts with a precise model of who you are. ACI resolves every organization across seven dimensions — and every downstream choice the platform makes keys off that profile.

🕊️

Religion

Christianity, Judaism, Islam, Hinduism, Buddhism, Sikhism, secular, and more

Denomination

A Catholic parish and a Pentecostal church get different defaults — so do Reform and Orthodox communities
🏷️

Category

Congregation, school, foundation, relief charity, community center, civic group
🏛️

Organization form

How you're constituted — temple, gurdwara, synagogue, nonprofit, endowment
🌏

Cultural affinity

The community you serve — diaspora ties, regional customs, naming conventions
📍

Geography

Country and region drive receipts, currencies, payment rails, and observance dates
💬

Language

Localized giving categories and formats for the languages your community uses
Zero-question onboarding
Your organization's name and country are usually enough. ACI infers your likely denomination, cultural affinity, calendar, vocabulary, and starting funds — and onboarding shows you cards to confirm, not a questionnaire to fill out. Adjust anything; nothing is locked in.

Every screen speaks your tradition's language

Same database. Same features. Different words. ACI's vocabulary overlays rename the product's nouns across all 13 surfaces — dashboard, donor portal, widgets, donate pages, email, PDF receipts, SMS, push, in-app, announcements, kiosk, mobile, and live event pages.

⛪ Church admin sees

DonationsGifts
DonorsGivers
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
Example — vocabulary resolution across programs
The same underlying record — a donation — renders with the tradition-correct noun on each program's donate page:
Christian program
Tithes & offerings
Jewish program
Tzedakah
Muslim program
Sadaqah & Zakat
Hindu program
Daan / Seva
Sikh program
Dasvandh / Seva
Secular program
Donation
Same platform. Same data model. The right word on each program's pages — automatically, from the program's tradition profile.

Packs that flip real product behavior

Cultural intelligence isn't a coat of paint. When ACI activates a capability pack, the product itself changes — fund designations, seasonal automation, checkout flows, even text direction.

🕌

Islamic giving pack

Zakat, sadaqah jariyah, and waqf designations kept cleanly separate; Ramadan auto-campaign drafts; riba-free language throughout; right-to-left script support.

✝️

Christian pack

Advent and Easter seasonal automation — with the Western/Orthodox date split handled correctly — pledge-card flows for commitment campaigns, and tithe, building, and missions fund presets.

✡️

Jewish pack

Yahrzeit remembrance giving, tribute and dedication flows, High Holy Days seasonal templates, and the Hebrew calendar woven through dates and schedules.

More packs cover the other traditions ACI models — and interfaith organizations can run different packs per program.

Recurring giving that follows devotion, not just the 1st of the month

Donors pick a devotional rhythm at checkout, and the platform schedules each charge on the tradition's own clock — computed against the right calendar, every cycle.

🕌

Jumu'ah weekly

Every Friday, charged after Maghrib
🌙

Ramadan daily

A gift each day of Ramadan, timed to iftar
🕯️

Shabbat weekly

Weekly, at candle-lighting minus 18 minutes

Sunday tithe

Every Sunday, with the offering
🕎

Hanukkah eight nights

One gift per night, all eight nights
🥚

Easter offering

Annual — honoring the Western/Orthodox date split
🪔

Diwali annual

Each year on Diwali, wherever it falls
☸️

Vesak annual

Each year at the Vesak full moon
🎊

Vaisakhi annual

Each year at Vaisakhi
🍲

Gurdwara langar monthly

Monthly support for the langar kitchen

Every devotional intent carries an expert-attestation status — donors see an honest "cultural guidance under review" label until a Subject Matter Expert signs off.

The right calendar for the right community

226 seeded observances across 10 calendar traditions. The platform knows your community's calendar and surfaces upcoming observances as draft campaigns — you approve, it ships on 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
☪️

Islamic Hijri

Lunar, recalculated yearly
Ramadan, Eid al-Fitr, Eid al-Adha, Muharram, Mawlid — tracked as the lunar year shifts
🛕

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

Plus Bahá'í, Jain, and Zoroastrian observance sets — 226 observances in all, resolved by eight calendar-system plugins. Explore the multi-calendar engine →

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 →
University interfaith chaplaincy
Example configuration
Programs configured:
Campus chapel (Christian)
🕍Jewish student foundation
🕌Muslim students 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.

A review system, not a rubber stamp

Vocabulary mappings, seasonal templates, devotional schedules, communication tone — none of it is hardcoded by a software team in Silicon Valley. ACI ships with a built-in review workflow: credentialed Subject Matter Experts — scholars, clergy, and cultural experts with real identities and scoped review domains — examine cultural content and attest to it. And the product is honest about status: content still awaiting review carries a visible "cultural guidance under review" ribbon until an expert approves it.

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.

Attest & publish

Approved content carries its expert attestation; until then it stays visibly marked as under review. Future orgs signing up with that tradition + region get the 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. We claim the review system, not blanket certification: some content is still pending review, and the product shows it.

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 contextRoadmap

Coming: privacy-preserving comparisons against similar-size organizations in your tradition — aggregate only, never individual donor data. On the roadmap, not live today, and we won't pretend otherwise.

AI that never trains on your data

Your donor records are yours. The platform never trains a model on your data, and never shares your data with other organizations. When cross-org benchmarks ship — they're on the roadmap — they will be privacy-preserving aggregates only; individual donor records are never exposed.

Security & data governance →