Abu Dhabi
Software development for Abu Dhabi organisations
Abu Dhabi work often sits with a headquarters, a government supplier, or a group that must explain its systems to more than one committee. Raab Group still aims for a short path to a first release, and the release has to be documented well enough to survive that scrutiny.
- Operational workflow
- Secure custom systems
- Portals
- Internal assistants
Two offices
Dubai: 45th Floor, The One Tower, Sheikh Zayed Road, Barsha Heights. Ajman: 26th Floor, Amber Gem Tower, Nuventure Free Zone. The drawing marks those two offices.
A different buying rhythm from Dubai
Stakeholders may include operations, technology, procurement, and a risk function. Demos that skip security questions waste the second meeting. We write the access model, the hosting choice, and the handover as part of the proposal. ADGM and other regulated addresses come up for financial firms. We implement controls. We do not advise on licensing.
Systems that match the local mix
Energy and industrial operators need maintenance, contractor, and document workflows more often than a consumer app. Healthcare and education groups need appointments and portals with strict separation of roles. Headquarters teams need a reporting view that matches the operational record, not a second spreadsheet maintained for the board pack.
Delivery without theatre
A short timeline here means a narrow pilot a department can run, with a security review proportionate to the data, and a plan for the wider rollout. It does not mean an untracked prototype on a personal cloud account. Production accounts belong to the organisation.
Abu Dhabi briefs that must be explained
Plan for
- A stakeholder who needs the design in writing
- A longer approval path
- Systems that have to be operated, not demoed
Do not assume
- A headquarters address for us
- That procurement is the same as Dubai
- A public-sector claim we have not scoped
What changes an Abu Dhabi engagement
The explainer
The architecture and the access model need to be readable by someone who will not live in the code.
The data
Say where information may sit before a cloud is chosen.
The pilot
One department that will use the release beats a programme slide.
What an Abu Dhabi brief should carry
- 01
The reader
Who must understand the design without living in the code.
- 02
The approval
How long a yes actually takes.
- 03
The data
Where information may sit.
- 04
The pilot
One department that will use the release.
Marks an Abu Dhabi brief is its own
- 01
The Abu Dhabi operation
Branches, approvals, or a government-facing process are described as they are.
- 02
Their process
Where a submission or an internal approval already exists, the software follows it.
- 03
No office is implied
Meeting in Abu Dhabi does not require an address we have not published.
- 04
Language is chosen
The first release says which language staff and customers will use.
Typical Abu Dhabi starting points
Operational workflow
Approvals, contractors, and documents for industrial and headquarters teams.
Secure custom systems
Access, audit, and a hosting decision that can be explained.
Portals
A limited view for partners, patients, parents, or vendors.
Internal assistants
Answers from approved procedures, with the same permissions as the user.
Related reading
Secure software
Threats, access, and release checks built into the way software is made.
Document management
Versions and permissions, so the current file is obvious.
Healthcare
Appointments, clinic workflow, and portals with strict access.
Manufacturing
Orders, batches, inventory, and quality records.
AI assistants
In-product help for staff, grounded in the systems they already use.Questions we hear
Do you have an Abu Dhabi office?
We do not publish an office address we do not occupy. We work with Abu Dhabi teams on site and remotely, and we will update this site when a premises claim is true.
Can you join an existing vendor panel?
If the procurement process requires it, we will supply the technical and company information we actually have. We will not invent certifications.
Is energy-sector software in scope?
Operations software around maintenance, contractors, and documents, yes. Plant control systems and safety-critical OT are a different discipline and are not casually included.