Who we are
A product team in the Gulf, building for the Gulf
We build one product, and we build it here: close to the employers, the banks and the ministries it has to work with every month.
Dawmo 2026.9 is out — rendered payslips, a public API and calendar feeds. See what changed
Most HR software sold in this region was designed somewhere else and adapted afterwards. That shows up in the details: the file the bank rejects, the gratuity basis nobody can explain, the app that assumes a signal.
Who we are
We build one product, and we build it here: close to the employers, the banks and the ministries it has to work with every month.
What we make
Hiring, the employee record, attendance, payroll and the final settlement, all on one record that every module and the employee's own phone read from.
Why it exists
The punch, the leave balance and the salary all exist somewhere. In most companies here they meet for the first time after the file has gone to the bank.
A month-end, the usual way
Three systems, joined by one person, after the fact.
A spreadsheet holding the salaries, a biometric machine that would not export, and an accountant finding out about the leave after payroll had run. That is not an unusual setup here. It is the default one.
Dawmo exists because the three-system problem is not a software gap, it is a joining-up gap. The punch, the leave balance and the salary all exist somewhere; they just never meet before the file goes to the bank.
Not module by module. One employee record first, and everything else reads from it.
So the product is built from the record outwards rather than module by module: one employee record that payroll, attendance and the employee’s own phone all read from. That is why the gratuity figure an employee sees in the app is the same one that appears on their final settlement, rather than two calculations that agree by luck.
One gratuity figure, in two places
One calculation, not two that agree by luck.
One employee record
Contract, documents, salary and balances
Every module reads it
The parts that are specific to this region (WPS file formats per bank, GPSSA splits, Emiratisation reporting, Ramadan hours, right-to-left payslips) are the product, not a localisation layer over something else.
WPS files, per bank
In the format each bank accepts
GPSSA splits
Worked out per employee, every run
Emiratisation reporting
Tracked as you hire, not at audit
Ramadan hours
Applied to the shift, not by hand
Right-to-left payslips
Set in Arabic, not mirrored English
Each one is a constraint you could catch us breaking. That is the only kind worth publishing.
Every compliance claim on this site carries its source and the month it was last verified. If a date has gone stale, that is our failure and worth telling us about.
Attendance integrity raises a pattern with the evidence attached. It never deducts pay, marks an absence or triggers discipline on its own, and it never will.
Two things we are building are deliberately absent from this site. They arrive the week they are genuinely shippable, not the week they demo well.
A full export, in a usable format, without asking, negotiating or paying for it. A product that keeps customers by holding their data hostage is not a product we want to run.
The details a Gulf buyer checks before picking up the phone, in one place rather than in the small print.
Office
Hours
More detail, or a conversation with someone specific, is available on request.
Talk to usTwenty minutes, on a call, with your payroll rather than our demo data. Bring last month’s run and we will compare it line by line.
In the call
No slides and no obligation. Book a time that suits you.