What customers actually ship.

These are aggregated, anonymised outcomes from production IJRA@ deployments. The numbers are what the dashboards reported in the months following first wave.

Banking

From 14-day approvals to 3-day disbursements.

Regional Bank · 1.2M customers · Live since 2022

Loan origination at this bank had been a 14-day cycle of email hand-offs between origination, KYC, credit, legal and disbursement. Each function was efficient internally; the gaps between them were where the time hid. Customers who applied on Monday were lucky to be funded the following week.

The first IJRA@ wave modelled the whole flow as one BPMN process: parallel KYC-and-scoring branches, an automated risk-rules gateway, a human review user-task only for exceptions, and a single signed-document trigger to disbursement. Service tasks integrated the existing core banking system, the credit bureau, the document management system and the notification service. No new systems were bought.

14d → 3d
End-to-end cycle
22 → 6
Manual touches
+34%
Approval throughput
loan_origination · live
APPLY KYCSERVICE Score ? Auto-approve Review Disburse 3,142 LIVE INSTANCES · SLA 98%
Government

Citizen e-services across seventeen departments.

Public-sector authority · National scope · Live since 2023

Citizen requests for permits, registrations and certifications had to traverse up to seventeen departments — each with its own queue, intake form and SLA. Status visibility for the citizen was essentially zero. The dominant operational metric was the call-centre volume of “where is my application?”

IJRA@ became the orchestration layer. Each department kept its existing intake system. The platform routed requests across them, enforced cross-departmental SLAs, surfaced bottlenecks to a central operations dashboard, and gave citizens a single status view. The first-month effect was visible in the call-centre statistics, not the operations report.

17
Departments live
98%
SLA on-time
−61%
Status calls
e-services.flow
IJRA CITIZEN DEPT 01 DEPT 02 DEPT 03 +14 MORE DEPT 04 DEPT 05 17 DEPARTMENTS · 1 CITIZEN VIEW
Healthcare

Patient onboarding, end-to-end.

Private hospital · 108 beds · Live since 2024

Patient intake combined three independent systems — the EMR, the insurance verification gateway and the appointment scheduler — with a sequence of paper forms and phone calls between front desk, financial counselling and the clinical team. Time-to-care for non-emergency cases routinely stretched into hours; insurance discrepancies were caught at billing, not intake.

The orchestrated flow now runs intake forms, verifies insurance via a service task to the payer, schedules the first appointment, and triggers the EMR record creation in parallel. Financial counselling is invoked only as an exception path. Patients arrive at the clinical team with everything ready.

−54%
Time-to-care
0
Manual hand-offs
+22%
First-pass insurance
patient_intake.bpmn
IntakeFORM Verify Schedule EMR Care PARALLEL BRANCHES · AVG CYCLE 28 MIN
Enterprise

Procurement with policy-as-code.

Multi-national group · 4,000 employees · Live since 2022

The procurement policy was 38 pages long, lived as a PDF on SharePoint, and had eleven approval thresholds depending on category, vendor risk, and contract value. Compliance with the policy had become aspirational. Exceptions were the rule.

The IJRA@ deployment encoded the entire policy as rule expressions in the rules repository — versioned, audit-logged, and executable. The procurement workflow now consults the rules at every threshold, routes approvals to the correct seniority, and surfaces exceptions to a governance dashboard. The PDF still exists. It now matches reality.

live, versioned
Policy artefact
−72%
Policy exceptions
11
Threshold tiers
procurement_policy.rules
100% 87% 71% 50% 31% 8% M0M1M2 M3M4M5 EXCEPTION RATE BY MONTH
Real Estate

Property registration, orchestrated.

Regional real-estate authority · National scope

Property registration combined geospatial verification, ownership-chain validation, fee calculation, multi-party signatures, and final certificate issuance. The legacy process was almost entirely paper-based; transactions could sit for weeks waiting on a single departmental review.

IJRA@ now drives the registration flow end-to-end, with API integration into the GIS system, the legal-records database, the payment gateway, and the digital-signing service. Citizens upload documents through a portal; the workflow does the rest.

−68%
Cycle time
4
Systems orchestrated
100%
Digital from day one
property_registration
Submit GIS check Title Fee calc Pay Sign Notarise Certify 8 NODES · 4 EXTERNAL SERVICES
Energy

Field service dispatch.

Oil & gas services · Regional · Live since 2023

Field service requests for asset inspection, maintenance, and incident response had been managed through dispatcher spreadsheets and radio coordination. Field teams arrived at sites without complete safety documentation; equipment downtime was attributable, in retrospect, to coordination failures more often than to mechanical issues.

The orchestrated workflow now combines geographic dispatch logic, safety-document attachment, certified-personnel assignment, and incident-report capture in a single mobile-first BPMN flow. Teams arrive ready. Reports are filed at site, not retrospectively.

−43%
Coordination delay
100%
Safety doc compliance
on-site
Report capture
field_dispatch · live
ACTIVE FIELD TEAMS TEAM A · Site 12 · en-route TEAM B · Site 04 · on-site TEAM C · idle · accepting TEAM D · Site 21 · reporting 4 TEAMS · DISPATCH LATENCY 3.2 MIN
Government

Five workflows. One engine.

Anonymized representative deployments across ministries, authorities and regulators. Each runs on the same platform, configured for its domain.

UC / 01 · Citizen e-Services

One front door. Seventeen departments.

A citizen request that previously traversed up to seventeen ministries — each with its own intake form, queue and SLA — now runs on one BPMN model. Status visibility is end-to-end. Cross-departmental SLAs are enforced as policy. The dominant operational metric used to be "where is my application" calls. The metric still exists. The number is different.

Stakeholders
  • Citizen
  • Service Owner
  • Department Reviewer
  • Compliance Auditor
  • Operations Manager
  • Treasury
−72%
Cycle time
21d → 6d
100%
Status visibility
citizen self-track
+340%
Daily throughput
same staff count
citizen_eservices.flow
IJRA CITIZEN DEPT 01 DEPT 02 DEPT 03 +14 MORE DEPT 04 DEPT 05 17 DEPARTMENTS · 1 CITIZEN VIEW
UC / 02 · Permits & Licensing

Configure once. Issue forever.

Construction, commercial, professional, environmental — every permit type lives as its own versioned BPMN model. Policy-as-code rules govern eligibility, reviewer routing, fee calculation, and renewal scheduling. The PDF policy document still exists. It now matches reality.

Integrations
  • Business Registry
  • GIS Mapping
  • Digital Signing
  • Tax Authority
  • Police / Security
  • Civil Registry
−85%
Issuance time
30d → 4d
100%
Rule consistency
policy-as-code
0
Missed renewals
auto-scheduled
permits_licensing.bpmn
Apply Verify eligible? Issue Inspect RENEWALS · AUTO-SCHEDULED
UC / 03 · Internal HR & Admin

Approval chains, not email chains.

Vacation, procurement, expense, recruitment, transfers. Every internal request as a BPMN flow. Multi-tier thresholds enforced as rules. Approval routing follows the org chart, not the inbox. HR stopped being a forwarding service for emails — they now run analytics on what they used to barely keep track of.

Tier handlers
  • Employee
  • Direct Manager
  • Department Head
  • HR / Procurement
  • Finance / CFO
  • Compliance
−90%
Email overhead
chains digitized
100%
Policy adherence
rules-driven
+5×
Request volume
same admin staff
hr_admin.flow
Submit Manager tier? T1 Auto T2 Dept Approve Review Rules Audit MULTI-TIER · POLICY-DRIVEN · AUDIT-READY
UC / 04 · Documents & Contracts

Bilingual. Versioned. Audit-ready.

Every government contract, MoU and agreement in one repository. Drafted from templates, redlined by legal, signed digitally, distributed to counterparties, archived for instant retrieval. Arabic and English versions linked at the structure level. When auditors arrived asking for 2018 records, retrieval took eight seconds.

Lifecycle owners
  • Contract Drafter
  • Legal Reviewer
  • Counterparty
  • Signatory Authority
  • Records Officer
  • Auditor
100%
Version integrity
no lost originals
−75%
Draft-to-sign
14d → 3d
0
Expired lapses
auto-scheduled
contract_repo · live
VERSIONED · BILINGUAL · INDEXED Margin Agreement v3 · م ع 3 Apr 2023 · v3 اتفاقية تداول 2022 · Trading Agmt 2022 Apr 2023 · v2 Service MoU 2024 · مذكرة تفاهم Jan 2024 · v1 Procurement Master · إطار المشتريات Mar 2024 · v5 83 ENTRIES · 9 PAGES · INSTANT RETRIEVAL
UC / 05 · Tender & Vendor

Procurement with policy-as-code.

RFP publication, vendor pre-qualification, sealed bid submission, rubric-driven evaluation, contract award, vendor performance tracking. Audit transparency built in. The audit committee asked us to recreate one award decision from 2023. We replayed the entire evaluation, with every score and every signature, in under a minute.

Lifecycle actors
  • Procurement Officer
  • Pre-qualifier
  • Evaluation Committee
  • Awarding Authority
  • Vendor
  • Compliance Officer
−68%
Tender cycle
RFP-to-award
100%
Evaluation transparency
rubric-driven
0
Audit findings
on transparency
tender_lifecycle.bpmn
RFP PreQ Bid Eval Award Track 90D CYCLE → 29D CYCLE
— Begin

Bring your most-broken process. We'll show you what one model can do.

Most first deployments go live in 6–12 weeks. Pick a single process, see it modelled, automated and measured — then decide what to roll out next.