Requests arrived as messages
Material and maintenance requests came through chat groups with no ticket, no status and no record of who approved what.
Mobile · Gambit Gulf Contracting
The ERP in the crew's pocket
An office system only works if the people on site actually use it. Drivers, technicians and employees needed the parts that concern them on a phone, in Arabic, without training — so we built the field half of the platform as its own app.
- iOS and Android
- Arabic-first interface
- Connected to the same ERP
- Client
- Gambit Gulf Contracting
- Sector
- Infrastructure & contracting
- Delivered
- 2026 — in production
- Services
- Mobile apps, Custom software
Project at a glance
The situation
The office had a system; the site had WhatsApp
Everything that starts in the field — a trip, a breakdown, a receipt, a material request — was arriving as a message or a piece of paper, then being retyped by someone in the office days later.
01 02 Expenses were reimbursed late
Employees paid out of pocket, kept paper receipts and waited for someone to enter them, which delayed both the claim and the cost landing on the project.
03 Drivers had no assignment screen
Trips were allocated by phone call, and completion was confirmed the same way, so utilisation could not be measured.
04 HR answered the same questions daily
Leave balance, iqama expiry, bank details and payslips were all requests to a person rather than something an employee could check.
What we built
The field half of the platform
Built on the same API as the ERP, so what happens on site appears in the office immediately.
Expense claims by camera
Photograph the receipt, and the amount, VAT and date are captured with it — linked to an employee, vehicle, asset or equipment, and routed to finance with the cost centre attached.
Driver trips
Assigned trips, status updates and completion recorded by the driver, feeding the fleet utilisation figures the office reports on.
Material and maintenance requests
Site teams raise requests against a project or machine, with approval routing and a status the requester can follow.
Employee self-service
Leave balance and requests, iqama and document status, bank details and payslips — available to the employee instead of arriving as an HR question.
Mobilization and support
Crew and equipment mobilization steps recorded from the site, and an in-app support channel that creates a real ticket.
Push notifications
Approvals, assignments and status changes reach the phone, so work is not waiting on someone opening a laptop.
What changed
Work is recorded where it happens
The app removed the re-typing step entirely. A receipt photographed on site becomes an expense line with VAT and a cost centre, and a request raised at a machine becomes a tracked ticket rather than a message.
- Expenses reach finance the day they are incurred, not weeks later
- Every field request carries a status the requester can see
- Fleet and equipment usage is measured from what drivers record
- Routine HR questions are answered by the app
- 2
Platforms from a single codebase
- 0
Re-entry between the field and the office
- AR
Arabic-first, for the people using it
Built with
A single codebase for both platforms, sharing the ERP's API and authentication.
- App
- React Native
- Expo
- TypeScript
- Expo Router
- Data & state
- React Query
- Axios
- Secure Store
- Device
- Camera & image picker
- File system
- Push notifications
- Backend
- Shared ERP API
- Node.js
- PostgreSQL
Is your field work still arriving by WhatsApp?
Tell us which step gets retyped in the office. That is usually the first screen worth building.