Six modules, one employee record
Each module is worth a page of its own. What makes them worth having together is that none of them keeps its own copy of your people.
Employee Management One record per employee — contracts, documents, org chart. Attendance QR check-in, shift rules, and overtime that reconciles itself. Payroll Run payroll with components, advances, and per-period snapshots. Recruitment Post a role, track candidates, hire without a spreadsheet. Performance Reviews, goals, and KPI plans that managers actually finish. Leave Management Balances, policies, and approvals that respect tenure rules.
The handover between modules is the part that usually breaks
A hire becomes an employee, a shift becomes an overtime line, an approved leave becomes a payroll deduction — without anyone retyping a name.
- A candidate who is hired becomes an employee record, with the documents already attached.
- Approved leave lands in the payroll run for the period it falls in.
- A check-out that never happened shows up before payroll closes, not after.
Today · Riyadh office
Recorded by QR scan at the door
- Layla HaddadFinance
Present 08:52 – 17:04 - Omar SiddiquiSales
Late 09:41 – 18:10 - Mona FahmyMarketing
Remote 08:30 – 16:45 - Yousef BarakatOperations
On leave —
What adoption usually looks like
- 1
Start with the record
Import people, departments and reporting lines. Everything else has something to point at.
- 2
Add the daily modules
Attendance and leave are what most teams feel first, because they run every day.
- 3
Close the month
Payroll last, once the hours and balances feeding it are already trusted.
Start with the module that hurts most
Most teams begin with attendance or payroll and add the rest once the record is trusted.