One Elevator Service ERP. Three Gulf Markets. No Local Office.

What we learned rolling out ElevatorPlus across the UAE, Saudi Arabia and Bahrain—from Pune.
Most software case studies start with a percentage.
“40% faster.”
“30% more productive.”
“50% fewer errors.”
We are not doing that here.
We cannot evidence those numbers for these three operators to a standard we would defend in front of their customers.
What we can show is what actually changed during the rollout—and what the field forced us to change.
Three operators. Three countries. One platform.
The same elevator service platform now supports:
EPIC ME Technical Works LLC in the UAE
Triolift in Saudi Arabia
Gulf Integrated Vertical Solutions in Bahrain
Accucia delivered the platform from Pune, India. We have no Gulf office, trade licence or local delivery team. Pasted text
That made the implementation question more interesting:
Can one system support technicians, AMCs, breakdowns and service operations across three different Gulf markets remotely?
Yes—but the software itself was not the hardest part.
The difficult part was adoption
The platform creates one operational record around each lift.
That includes the asset register, AMC and warranty details, complaints, technician scheduling, spare parts, preventive maintenance and customer-facing job status. Pasted text
But a good feature list means very little if technicians do not use it.
We therefore trained supervisors first using real jobs from their own operation. Those supervisors then trained their technicians.
That produced much more useful feedback than sending an outside trainer into the field. Pasted text
We deliberately ran two systems for a month
For the first month, the old and new processes ran together.
Paper job cards and spreadsheets stayed active alongside the app.
It was slower. It created duplicate work. Nobody particularly enjoyed it.
But it exposed problems before the old system disappeared.
By week three, the field had already forced three important changes. By week six, spreadsheets were retired from daily work. Pasted text
Three things technicians changed

1. We simplified the reason codes. The original closure screen used a long dropdown written in engineering language. Technicians often selected the first available option. We shortened it, rewrote it in plain language and used mandatory photos instead of relying heavily on free text.
2. We made job cards offline-first. Machine rooms are often in basements or roof plant rooms where mobile signal is unreliable. The app now stores the job locally and syncs when the device reconnects.
3. We moved final closure confirmation to supervisors. The technician marks the work as done. The supervisor confirms closure. That made the complaint-to-closure history more trustworthy. Pasted text None of these changes were in the original scope. That became one of the biggest lessons from the rollout: When implementing field-service software, budget for a change window in month one. Treat field feedback as part of the build, not rework.

Then came the Gulf working-week problem
Running one platform across the Gulf does not mean running one calendar.
Saudi Arabia operates Sunday to Thursday. Bahrain makes Friday the weekly rest day while the second rest day can depend on the employer. UAE private-sector companies can also set their own working arrangements within applicable rules.
So we stopped thinking in terms of a “Gulf working week.”
The calendar is configured per client, not simply per country. Pasted text
Timezone overlap helps too.
A Pune team working 9:30 AM–6:30 PM overlaps with 8:00 AM–5:00 PM in Dubai and 7:00 AM–4:00 PM in Riyadh and Manama.
Sunday requires a separate on-call arrangement because it is a working day for Saudi and many Bahrain operations while being a weekend day in India. Pasted text
So what actually changed?
Not a marketing percentage.
Something more concrete.
Asset records: branch spreadsheets → one register keyed to each lift.
Complaints: phone calls and WhatsApp → timestamped job cards with reason codes and photos.
Preventive maintenance: manually prepared schedules → generated from AMC records.
Stock: month-end reconciliation → parts issued and returned against jobs.
Renewals: price-only conversations → service history available for each lift. Pasted text
The lesson we would carry into the next rollout
We would build offline-first job cards from day one.
And we would migrate one branch completely before expanding to the others.
Because the biggest implementation risks were not hidden inside the code.
They were in basements with no signal, spreadsheets with duplicate lift records, technician habits, different working calendars and workflows that looked perfectly reasonable until someone actually tried to use them. Pasted text
That is what implementing field-service software actually looks like.
Not installing software. Changing how the work moves.
Read full blog