Sectors
Different sectors, the same unanswered questions.
Kerah builds for organizations across sectors, and can deliver across the United Arab Emirates and the wider Gulf. What changes between them is which obligation shapes the system — a contract, a regulator, a public duty, a donor's condition. What does not change is that the answer has to come out of the records, rather than out of a spreadsheet assembled for the occasion.
Who Kerah builds for
- Private companies
- Operators, groups and family businesses replacing a core process that currently runs on spreadsheets, inboxes and one person's memory.
- Government and public-sector bodies
- Authorities and public institutions whose systems have to satisfy procurement, audit, records and accessibility obligations as well as the operational requirement.
- Non-profit and charitable organizations
- Licensed organizations whose funds arrive with conditions attached and leave under permission, and whose reporting has to satisfy a donor, an auditor and a regulator from the same records.
Sector
Private companies and group operations
The system has to earn its place against the spreadsheet it replaces. No regulator compels anyone to use it, so it survives only if the common task is faster inside it than outside it — and it is abandoned quietly, not formally, when it is not.
Constraints on every design
- The process has to keep running while it is being replaced
- Access follows commercial confidentiality, not only job title
- Reporting has to reconcile with the finance system, or it will not be believed
- A business rule must be changeable without waiting for a release
Systems Kerah can build
- Operations, sales and back-office portals with workflow and approvals
- CRM and ERP integration, extension and data migration
- Customer-facing web and mobile applications
- Operational reporting drawn from the systems people already work in
Sector
Government and public-sector bodies
Procurement, audit and public accountability shape the system as much as the operational requirement. What cannot be evidenced cannot be reported, and what cannot be reported did not happen.
Constraints on every design
- Architecture, data residency and exit are contractual matters from the start
- Bilingual delivery is a product requirement, not a translation task
- Accessibility is tested, not asserted
- Records must be exportable in open formats without vendor assistance
- A decision taken today has to be reconstructable for an appeal or a disclosure request years later
Systems Kerah can build
- Public-facing services and case intake in Arabic and English
- Case, workflow and approval platforms with full audit history
- Integration with identity, document, finance and messaging infrastructure
- Reporting and disclosure packs built from source records
- Documented exit and handover from day one
Sector
Regulated and supervised operations
A supervisor's rulebook is a system requirement, not a policy document filed beside one. Whether the supervisor is a financial authority, a health authority or an education authority, the obligation arrives with a date attached, and the organization has to show someone who was not present how the system behaved on a given day.
Constraints on every design
- A rule changes on a date, so the system records which version applied when
- Special-category data is separated by class, environment and access model, not by convention
- A controlled process keeps a change history an examiner can follow without the supplier's help
- Functionality that is itself regulated — clinical decision support, a medical device, a licensed financial activity — stays out of scope without specialist review and explicit approval
Systems Kerah can build
- Policy, rule and control registers carrying version history and effective dates
- Workflow with segregation of duties and enforced approval limits
- Evidence packs assembled from source records for an examination or a disclosure request
- Integration with the identity, document and screening systems already in place
Sector
Non-profit, charitable and humanitarian organizations
Money arrives with conditions attached and leaves under permission. The system of record has to satisfy a donor, an auditor and a regulator at the same time, using the same underlying data — and where delivery happens in the field, the evidence gathered there has to hold up months later in another country.
Constraints on every design
- Restricted funds keep their restriction from receipt through to disbursement
- Campaigns publish only through approved permits and licensed channels
- Beneficiary data is held under a separate access model from operational data
- Safeguarding and complaints route to a responsible person by design
- Every material decision carries an identifiable approver
Systems Kerah can build
- Programme, project and campaign registers with approval gates
- Restricted-fund and donation-purpose accounting
- Beneficiary casework with a defensible decision trail
- Offline-first field applications and partner portals
- Partner assurance, obligation tracking and screening integration
- Donor and regulator reporting generated from operational records
Sector
Real estate, endowments and asset-heavy operations
An asset carries obligations that outlive the people who recorded them — a lease covenant, a maintenance duty, a designated purpose. A system that records the asset but not the obligation attached to it is not a system of record.
Constraints on every design
- Designated purpose and contractual obligation travel with the asset through its whole life
- Revenue, cost and obligation are reportable against the asset, not only against the ledger
- Change of designation is an authorised act with an evidence trail
- Valuation and disposal are controlled decisions, never derived automatically
Systems Kerah can build
- Asset, property and endowment registers carrying condition, valuation and obligation
- Lease, tenancy and revenue lifecycle with renewal and escalation dates
- Maintenance, inspection and works management held against the asset record
- Linkage between an asset, the fund that holds it and the programme it supports
- Board and trustee reporting generated from operational records
Sector
Logistics, field and site operations
The work happens away from a desk, and the record of it is made by the person doing it, on a phone, in conditions nobody designed for. Evidence captured at a site has to be as defensible a year later as a form completed in an office.
Constraints on every design
- Capture works offline and reconciles later without losing provenance or order
- Location and time are recorded as captured evidence, not reconstructed from memory
- The application has to be usable one-handed, outdoors, by someone who is not sitting down
- Subcontractors and third parties carry obligations that must be tracked, not assumed
Systems Kerah can build
- Offline-first mobile applications for inspection, installation and maintenance
- Job dispatch, scheduling and completion evidence
- Distribution, delivery and chain-of-custody tracking
- Contractor and supplier portals with obligation and document tracking
- Reconciliation between what was dispatched, what was done and what was invoiced
Tell us what has to be evidenced.
The constraint is usually more informative than the requirement. Start there.