Policy-driven approvals and a shared sales pipeline on one platform
Mohsin Haider Darwish LLC (MHD) is one of Oman’s longest-established family-owned conglomerates, with more than 1,600 people across 72 locations. Brain Station 23 implemented Odoo 18 Community, replacing email-based approvals and personal lead tracking with configurable workflows and a role-secured CRM.
- Client
- Mohsin Haider Darwish LLC
- Country
- Sultanate of Oman
- Platform
- Odoo 18 Community
- Project start
- February 2026
-
Request
Structured forms
DSD, CER and petty cash with mandatory fields
-
Route
Approval matrix
By entity, division, department, budget type and amount
-
Approve
Email or dashboard
Approve, Reject or Hold from Outlook, with delegation
-
Report
Dashboards and audit
Live status by role, with every action logged
The project in three lines
The challenge
Approvals ran on documents circulated by email, with no approval matrix, enforced thresholds or audit trail.
The solution
A custom, configurable workflow engine and a role-secured CRM on Odoo 18 Community, hosted on-premise.
The outcome
DSD, CER, petty cash and CRM on one platform, with governance configured rather than coded.
Email was a channel, not a controlled workflow
Approval authority at MHD varies by entity, division, department, budget type and amount. Routing each request correctly depended on individual knowledge rather than system rules.
- CAPEX documents were routed case by case, leaving no single record of who approved what, and when.
- CERs were not linked to the approved DSD, so cumulative spend needed manual reconciliation.
- Requests stalled when approvers were unavailable, and delegation changes were coordinated by hand.
- Leads and customer communication sat with individual salespeople, so heads had no view of the pipeline.
A requirements-first build on Odoo Community
Odoo Community has no standard multi-level, parallel or threshold-based approval. After early feasibility validation, Brain Station 23 built a custom workflow engine: one configurable matrix supports 6, 8 or 10+ levels, sequential and parallel stages, and amount-based delegation-of-authority thresholds.
- Workflow and approval engine
- DSD (CAPEX pre-approval)
- CER (capital expenditure)
- Petty cash
- CRM
- Master data
- Dashboards and reporting
Configured, not coded. Admins maintain the approval matrix and thresholds through master data and Excel upload, with validation, dry run and rollback. Senior approvers act from Outlook through RPA-based email approvals, and the system runs on MHD’s own Ubuntu Linux infrastructure.
Governance management can see
- 4Business processes on one platform
- 10+Approval levels supported
- 8Tracked lifecycle states per request
- 4Lead-capture channels into one pipeline
- Management visibility: leadership sees pending requests, who holds them and pipeline value by division, without asking for a report.
- Audit and compliance: every action, delegation and attachment change is logged with user, timestamp and channel.
- Scalability: new entities, divisions, levels and thresholds are added through master data, with no code changes and no extra license fees.
Policy-driven approvals and a shared sales pipeline on one platform
Mohsin Haider Darwish LLC (MHD) is one of Oman’s longest-established family-owned conglomerates, with more than 1,600 people across 72 locations. Brain Station 23 implemented Odoo 18 Community, replacing email-based approvals and personal lead tracking with configurable workflows and a role-secured CRM.
- Client
- Mohsin Haider Darwish LLC
- Country
- Sultanate of Oman
- Platform
- Odoo 18 Community
- Project start
- February 2026
-
Request
Structured forms
DSD, CER and petty cash with mandatory fields
-
Route
Approval matrix
By entity, division, department, budget type and amount
-
Approve
Email or dashboard
Approve, Reject or Hold from Outlook, with delegation
-
Report
Dashboards and audit
Live status by role, with every action logged
The project in three lines
The challenge
Approvals ran on documents circulated by email, with no approval matrix, enforced thresholds or audit trail.
The solution
A custom, configurable workflow engine and a role-secured CRM on Odoo 18 Community, hosted on-premise.
The outcome
DSD, CER, petty cash and CRM on one platform, with governance configured rather than coded.
Email was a channel, not a controlled workflow
Approval authority at MHD varies by entity, division, department, budget type and amount. Routing each request correctly depended on individual knowledge rather than system rules.
- CAPEX documents were routed case by case, leaving no single record of who approved what, and when.
- CERs were not linked to the approved DSD, so cumulative spend needed manual reconciliation.
- Requests stalled when approvers were unavailable, and delegation changes were coordinated by hand.
- Leads and customer communication sat with individual salespeople, so heads had no view of the pipeline.
A requirements-first build on Odoo Community
Odoo Community has no standard multi-level, parallel or threshold-based approval. After early feasibility validation, Brain Station 23 built a custom workflow engine: one configurable matrix supports 6, 8 or 10+ levels, sequential and parallel stages, and amount-based delegation-of-authority thresholds.
- Workflow and approval engine
- DSD (CAPEX pre-approval)
- CER (capital expenditure)
- Petty cash
- CRM
- Master data
- Dashboards and reporting
Configured, not coded. Admins maintain the approval matrix and thresholds through master data and Excel upload, with validation, dry run and rollback. Senior approvers act from Outlook through RPA-based email approvals, and the system runs on MHD’s own Ubuntu Linux infrastructure.
Governance management can see
- 4Business processes on one platform
- 10+Approval levels supported
- 8Tracked lifecycle states per request
- 4Lead-capture channels into one pipeline
- Management visibility: leadership sees pending requests, who holds them and pipeline value by division, without asking for a report.
- Audit and compliance: every action, delegation and attachment change is logged with user, timestamp and channel.
- Scalability: new entities, divisions, levels and thresholds are added through master data, with no code changes and no extra license fees.