Hijri calendar 20 years out. Tradition-specific vocabulary across every screen. Fiqh-aware giving frameworks. SME-reviewed copy with input from scholars and community leaders. Multi-language ready — built into the architecture, not bolted on.
The problem with generic platforms
An imam shouldn't have to translate "donation" to "sadaqah" in his head every Jummah. A treasurer shouldn't have to manually map the Hijri year onto a Gregorian fiscal calendar. A Waqf trustee shouldn't have to explain to a generic CRM what a perpetual endowment is. The platform should already know.
The Hijri calendar — pre-loaded
Computed via astronomical calculation; moon-sighting overrides supported. Every major Islamic observance pre-drafted as a campaign template. Hijri dates shown alongside Gregorian throughout the platform.
Vocabulary that fits Islamic giving
Vocabulary is the surface area where bad fit shows. Mohseen's substitution layer adapts terminology across the navigation, emails, sadaqah pages, receipts, and notifications to fit Islamic-giving culture.
| Label | Mosque (Sunni) | Mosque (Shia) | Madrasah | Relief / charity |
|---|---|---|---|---|
| Sidebar | Sadaqah | Sadaqah | Sadaqah | Sadaqah |
| Donations | Sadaqah, gifts | Sadaqah, Khums | Tuition gifts, sadaqah | Aid contributions |
| Donors | Contributors | Contributors | Patrons, contributors | Contributors, supporters |
| Categories | Zakat, Sadaqah, Waqf, Jariyah | Khums, Zakat, Sadaqah | Tuition aid, Hifz support, Jariyah | Emergency aid, orphan, food aid |
| Campaign | Appeal | Appeal | Appeal | Emergency appeal |
| Recurring | Recurring sadaqah | Recurring sadaqah | Monthly tuition support | Sustainer contribution |
| Receipt | Year-end Zakat statement | Annual Zakat / Khums record | Annual tuition-aid record | Annual aid receipt |
Multi-language ready
English at launch — high-quality, professionally edited. Arabic, Urdu, Bengali, Bahasa Indonesia, Turkish, and more on the roadmap. The platform is RTL-ready at the architecture level.
RTL stylesheet ready in the architecture. Per-language SME review will ensure cultural fit, not just translation accuracy.
SME review by scholars
Vocabulary, seasonal templates, fiqh-relevant copy — none of this is hardcoded by a software team. Each tradition's content is reviewed by Subject Matter Experts. Imams for Sunni copy. Scholars for Shia copy. Sufi mashayikh for Sufi content. The SME workflow is built into the platform.
Platform curator or mosque admin submits a tradition-specific overlay — vocabulary, seasonal templates, fiqh-relevant copy.
The platform routes the overlay to an SME whose expertise matches: tradition, region, language. Imams, scholars, community leaders — real people, vetted and accountable.
SME reads, comments, requests changes, withdraws, or approves. Every decision captured with rationale. Audit-ready trail.
Approved overlay goes live for that tradition in that region. Future mosques signing up with that combination get the SME-reviewed content automatically.
Your organisation can nominate its own SMEs for tradition-specific review — turning your imam, your trustee board, or your religious advisory council into an authority on what the platform says.
Under the hood
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.
Tradition, region, size, history. Built from your signup choices and refined by your actual giving patterns. Stays inside your tenant — never shared with another mosque.
Contributor lifecycle stages, giving cadences (heavy Ramadan vs steady year-round), seasonal peaks. Inferred from your data, used only for your data.
Appeal copy, Ramadan campaign drafts, Zakat-anniversary reminder text. Anthropic Claude composes drafts tuned to your tradition + your patterns. Staff reviews; AI doesn't autosend.
k-anonymity-preserving comparisons against similar-size mosques or charities in your tradition. "Your average Ramadan contribution vs. median for similar mosques in your region." Aggregate only; no individual contributor data ever exposed.
Your data, your scope
Your contributor records are yours. The platform never trains a model on your data. The platform never shares your data with other mosques or charities. Cross-org benchmarks are k-anonymity-preserving aggregates only — your individual contributor records are never exposed.
Security & data governance →