Services
Software maintenance and support in the UAE
Software maintenance in the UAE is the work after the launch applause. Raab Group keeps a named list of what support includes: defects, small changes, dependency updates, and a route for an incident.
- Named scope
- Fixes and small changes
- Updates with a reason
- Separate from the build price
Designed in Dubai and Ajman.
Dubai office
45th Floor, The One Tower, Sheikh Zayed Road, Barsha Heights
Ajman office
26th Floor, Amber Gem Tower, Nuventure Free Zone
Contact
Email, call, or WhatsApp info@raabsoftwares.com
What we build
- Defects
- Small changes
- Updates
- Incident route

How we work
- Discover
- Plan
- Design
- Build
Services
The UAE teams start here
The existing maintenance and support service is the engineering view. This page is the commercial view: what you are buying after go-live, and how it relates to a new release.
- Named scope
- Fixes and small changes
- Updates with a reason
- Separate from the build price

Services
Capabilities
From the first conversation to handover
- 01Discover
- 02Plan
- 03Design
- 04Build

How it runs
What has to be true before the next slice
- 01
DiscoverWe sit with the people who do the work and list what the live system must do in the first release. - 02
PlanThe plan names users, data, integrations, and an incident path nobody owns on a Thursday night. Everything else is written down as later. - 03
DesignScreens and the record are designed together, so the interface does not promise a field the system cannot store. - 04
BuildEach slice of the live system is reviewed before the next slice depends on it.
In practice
Capabilities
Fixes, small changes, and a person who answers after launch.
Maintenance fails when it is a vague retainer. Teams in the UAE need to know which environments are covered, how a defect is judged, and what counts as a new feature. We write that down.
- Defects
- Small changes
- Updates
- Incident route
- Discover
- Plan
- Design
- Build
On the screen
What the work can include
A support engagement covers the system we built or a system we have been allowed to learn. We do not pretend to support a codebase we have never seen.

Capabilities
- Defect fixes against an agreed severity
- Small changes inside a monthly bound
- Dependency and security updates with a test pass
- A contact path during agreed hours
In this build
Capabilities

- DefectsA broken path is fixed against the original release, not redesigned by surprise.
- Small changesA field, a report, a rule, inside a bound.
- UpdatesDependencies move with a test, not on a Friday with no note.
- Incident routeYou know who is called and what they can roll back.
What the work can include
A support engagement covers the system we built or a system we have been allowed to learn. We do not pretend to support a codebase we have never seen.
- Defect fixes against an agreed severity
- Small changes inside a monthly bound
- Dependency and security updates with a test pass
- A contact path during agreed hours
- Notes so the next change is not folklore

How operations change
The product stays deployable. A system nobody can release is not maintained, even if a server is still on.
New ideas stay visible as changes, so support does not quietly become an unquoted rebuild.

Where the same pattern shows up
Any live portal, app, or internal tool. The industry does not change the need for an owner. It changes which incident hurts most, and we write that into the severity list.

Why companies ask Raab Group
We would rather a short handover at the end of a build than an implied forever-warranty. If you want us to stay, the maintenance quote says so.
If your own team will own the system, handover is the product. Maintenance is optional.

How a release is run
Discovery for the live system is a working session. We write down who uses it, which data already exists, and the first release a person can try. Planning then fixes the record and the access rules before a large amount of code depends on a guess.
Design, build, and test stay in one slice. A release is ready when the critical path has been reviewed, the unhappy cases have a check, and someone on your side can follow the handover notes. Deployment includes the environment, logging, and a way back if the release misbehaves.

Technologies we use on this work
We maintain stacks we can still build and test.
- The repository and the pipeline
- Staging that resembles production
- Monitoring you can read
- A backlog that separates defects from features
- Access that survives staff changes

Security and access
Updates that close a known hole are maintenance. A full audit is a project. We do not mix those prices.

What changes the price
Retainers follow the size of the system and the hours you need a person. A tiny internal tool does not need a large stand-by fee.
Ask for maintenance when you ask for the build, or after launch once the real incident pattern is visible.

The UAE coverage
The Dubai office is 45th Floor, The One Tower, Sheikh Zayed Road, Barsha Heights. Ajman is 26th Floor, Amber Gem Tower, Nuventure Free Zone.
Talk To Sales, WhatsApp, and the phone on this site all reach the same team. The brief is saved so the reply is about your release, not a generic brochure.

Services
Capabilities
Defects
A broken path is fixed against the original release, not redesigned by surprise.
Small changes
A field, a report, a rule, inside a bound.
Updates
Dependencies move with a test, not on a Friday with no note.
Incident route
You know who is called and what they can roll back.
How we work
From the first conversation to handover
- Step 01
Discover
We sit with the people who do the work and list what the live system must do in the first release.
- Step 02
Plan
The plan names users, data, integrations, and an incident path nobody owns on a Thursday night. Everything else is written down as later.
- Step 03
Design
Screens and the record are designed together, so the interface does not promise a field the system cannot store.
- Step 04
Build
Each slice of the live system is reviewed before the next slice depends on it.
- Step 05
Test
Checks cover the path that changes money, stock, or access, and the failure you have already seen in daily work.
- Step 06
Hand over
We deploy into an environment you can see, then leave notes for running, changing, and recovering it.
Related
Related reading
Common questions
Questions we are often asked
Do you support software you did not build?
After a paid period to learn the system and the deploy path. We will not sell a retainer on a codebase we cannot release.
Is warranty included in the build?
The quotation states the defect window. Ongoing change is maintenance.
Can our team do the maintenance?
Yes. We hand over the pipeline and the notes. Stay with us only if you want us in the rotation.
What hours do you cover?
Agreed in the support terms. We do not promise a follow-the-sun desk we do not staff.
How are features handled?
They are quoted as slices. They do not hide inside a bug fix.
How do we ask?
Tell us the system, who deploys it today, and what broke last quarter. Use Talk To Sales.
Ready to operate
Marks the work can be operated
- 01A first releaseA slice users can try, with a clear owner.
- 02A repeatable pathBuild and deploy that someone else can run.
- 03Recovery triedBackup or rollback practised before go-live.
- 04Access namedWho may change production is written down.
Use this list on the call. Tell us which marks are missing today, and which can wait.
Write to us
Tell us about the work.
Share the outcome, the deadline, and the constraints. We reply from Dubai or Ajman with a practical way to start, including what should wait.
Dubai 45th Floor, The One Tower, Sheikh Zayed Road, Barsha Heights
Ajman 26th Floor, Amber Gem Tower, Nuventure Free Zone

