Case study · Al Minsa
Al Minsa is a system of work for the community organisations of a diaspora: one deployment that hosts many separate organisations, each with its own members, roles, campaigns, events, documents, governance records and payment credentials. A SolutionsCrafters product, engineered and demonstrable, and available to license or acquire.
Al Minsa is a SolutionsCrafters product: multi-tenant architecture, engineering and product design in-house. It is engineered and demonstrable, and available for licensing or acquisition, and we welcome a private conversation. Out of respect for the community behind it, no member, donor or organisation data is shown.
A SolutionsCrafters product, engineered and demonstrable. We welcome conversations about investment, licensing or acquisition — by private arrangement.
An umbrella of community organisations rarely behaves like one body. Each keeps its own members, its own board, its own campaigns and its own bank account, and each has grown its own way of recording them: a spreadsheet here, a shared inbox there, a folder nobody else can open. Al Minsa is built for exactly that shape. It suits the community organisations of a diaspora that want to run as themselves, under one roof, without giving up what makes each of them distinct.
Give every organisation its own space and the work scatters across dozens of disconnected tools, each with its own gaps in governance and record-keeping. Centralise it and you flatten organisations that are legally and financially separate into a single account that fits none of them. The harder problem sits underneath. This is a community's most sensitive information: member registers, minors, financial disclosures, whistleblower reports. It has to stay isolated per organisation, provable on request, and never mixed between one house and the next.
03 · Approach
We built Al Minsa as one deployment that behaves like many. Each organisation gets its own slug, its own roles and settings, its own members and its own payment credentials, isolated from every other, with a platform layer above that can see across them without breaking the wall between the houses. The records a community answers for, from governance minutes and elections to financial disclosures and data-subject requests, became first-class parts of the system rather than attachments bolted on the side. Payments were designed for real diversity: multiple providers and bank transfer, per organisation, so each one collects under its own account. And Arabic is a first-class language of the platform, written and read the way the community does, not a translation layer over an English core.
04 · What changed
Have a project in mind?
Tell us what the product must do, who it serves, and where the current process breaks. We will help shape a practical next step.