Ten companies. One family. Zero shared visibility.
Most Gulf family business groups run every company as its own island. This is the architecture behind a single layer that sits above all of them — without replacing any of them.
The situation
One question, three days, five numbers that don't agree
At the quarterly meeting, the chairman asks one question: how much cash does the group actually have right now. It's not a complicated question. He has a real estate leasing arm, a hospitality and F&B business, a trading company, and a retail chain — four entities, four finance managers, four systems.
The answer takes three days to arrive. When it does, it comes as five different numbers that don't reconcile, because each finance manager defines "available cash" differently — one nets out pending supplier payments, one doesn't, one includes a deposit that's technically already committed elsewhere.
This is not a technology problem inside any single company. Each of those four businesses may already run on decent, modern tools. The gap sits in the layer nobody owns — the view across all four, which currently exists only as a WhatsApp group, a handful of spreadsheets someone updates when they remember to, and whatever the chairman happens to hear on a phone call.
A renewal with no owner
A lease renewal sits unassigned between the real estate manager and the group's legal contact until it's 12 days from expiry.
Idle cash, three floors away
One entity carries an overdraft while another, in the same building, sits on cash nobody flagged as available.
News that arrives too late
A family member learns of a signed deal from a phone call days later, instead of from a system that should have surfaced it instantly.
The architecture
A layer above the entities, not a replacement for any of them
The fix is not a single new ERP that replaces what each company already runs — that conversation usually stalls for a year. The fix reads from each entity's existing system of record and surfaces the handful of figures the principal actually needs, with automatic flags when something crosses a threshold that matters.
Nothing here is replaced on day one — the layer reads from what already runs.
Method
Five steps, in order
Each entity keeps its existing system. The layer is built and proven on one entity before it extends to the rest.
Map every entity
Including the ones that aren't really a "system" — a WhatsApp group, a shared spreadsheet, a notebook on someone's desk.
Define the vital few numbers
For most groups this is 6 to 10 figures: consolidated cash, receivables aging, occupancy, upcoming renewals.
Build the integration layer
Connect each entity's system into one data layer that reconciles definitions across companies.
Add threshold alerts
A renewal flagged at 60, 30, and 7 days out. A large cash movement routed for approval before it executes.
Prove it, then extend
Roll out against the entity with the clearest pain first, then extend once the numbers are trusted.
What changes
Fragmented, today — versus a unified command layer
| What's being measured | Fragmented, today | Unified command layer |
|---|---|---|
| Time to a consolidated cash position | 3–7 days, several phone calls | Current, on one screen |
| Lease and contract renewals | Discovered after they're urgent | Flagged 60 / 30 / 7 days out |
| Moving cash between entities | Days, informal approval | Same day, logged approval |
| What the principal sees | Verbal updates, inconsistent | One dashboard, always current |
Direct answers
Questions asked directly about this specialization
No. The command layer is built to read from each entity's existing system of record. Replacing a core system is occasionally part of a later phase, but only when the assessment shows it is genuinely necessary.
The architecture has been designed for groups running anywhere from three to a dozen or more operating companies under one ownership structure. The relevant factor is fragmentation, not headcount.
Only what is necessary to map the systems and workflows involved is accessed, and only after a mutual non-disclosure agreement is in place. Access is scoped and time-limited.
The assessment phase runs two to three weeks. The first entity is typically proven and live within a further four to eight weeks, depending on how many systems it touches.
Is your group still running on WhatsApp groups and phone calls?
This is solved through a systems architecture engagement — mapping your specific entities and building the command layer over what you already run, not replacing it.
Start the conversation Confidential. No proposal before the assessment.