Cultural intelligence is not a theme — it configures the product. The Islamic giving pack sets up zakat, sadaqah jariyah, and waqf fund designations; sadaqah vocabulary runs across all 13 product surfaces; recurring follows devotional rhythms; seasonal intelligence is keyed to the Hijri year; the language stays riba-free; and the content runs through our expert (SME) review system.
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 on the Umm al-Qura calendar basis. Every major Islamic observance available as a seasonal appeal template, with Ramadan cadence and fiscal-year reporting context kept together.
Vocabulary that fits Islamic giving
Vocabulary is the surface area where bad fit shows. Mohseen's vocabulary overlay renames the product's nouns across all 13 product surfaces — dashboard, contributor portal, widgets, sadaqah pages, email, PDF receipts, SMS, push, in-app, announcements, kiosk, mobile, and live pages.
| Label | Masjid (Sunni) | Masjid (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 |
Capability packs
Pick your tradition at signup and the platform configures itself — onboarding cards confirm what it inferred rather than interrogate you. This isn't a color scheme; it flips real behavior.
Zakat, Sadaqah Jariyah, and Waqf fund designations created from day one — zakat never mixed with general sadaqah, every fund separately reportable. Waqf governance features coming later in 2026
The pack knows Ramadan giving runs 2–4× a normal month — seasonal appeal drafts keyed to the Hijri year, ready for staff review, with encoded restraint in the last ten nights.
Financial copy stays riba-free across receipts, appeals, and contributor communications — language a shura can sign off on, written into the pack itself.
Right-to-left support is pre-enabled in the platform architecture — ready for Arabic and Urdu interfaces as they arrive. اللغة العربية قريباً
Multi-language ready
Product UI is English today. Islamic giving categories are already localized in seven languages, 14 locales handle dates, numbers, and currency formats, and suggested amounts come tuned in 15 currencies. Full local-language UI is on the roadmap; the platform is RTL-ready at the architecture level.
RTL stylesheet ready in the architecture. Per-language expert (SME) review ensures cultural fit, not just translation accuracy.
The expert (SME) review system
Vocabulary, seasonal templates, fiqh-relevant copy — none of this is hardcoded by a software team. It runs through a built-in review workflow: credentialed subject-matter experts with real identities and scoped review domains. Content that hasn't been approved yet says so — a visible "cultural guidance under review" ribbon stays on until it is. We claim the system, not blanket certification.
Platform curator or masjid 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 masjids 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.
Seven dimensions — religion, denomination, category, organisational form, cultural affinity, geography, language. Inferred at signup from your name and country, confirmed by you, refined by your actual giving patterns. Stays inside your tenant — never shared with another masjid.
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 appeal drafts, seasonal outreach text. AI composes drafts tuned to your tradition + your patterns. Staff reviews; AI doesn't autosend.
Privacy-preserving comparisons against similar-size masjids or charities in your tradition — aggregate only, with no individual contributor data ever exposed. On the roadmap; your own analytics, lifecycle stages, and Giving Health Score are live today.
Your data, your scope
Your contributor records are yours. The platform never trains a model on your data, and never shares your data with other masjids or charities. AI drafts; your staff approves; nothing auto-sends. When cross-org benchmarks arrive (roadmap), they will be privacy-preserving aggregates only — individual contributor records are never exposed.
Security & data governance →