Payroll, cost, visas and the forecast in one database. The assistant reads it all, and changes nothing until you confirm.
A visa expires because the reminder lived in a file nobody opened. Payday becomes an argument because hours were keyed by hand. The overrun surfaces at month-end, long after you could have changed the crew.
One log, four ledgers
Each number used to come from its own spreadsheet, kept by its own person. Here there is one row, and four systems read it.
Reads hoursotattendance
A WPS-compliant salary run, payslips and deductions, with no timesheet re-keying.
Reads hoursoutput
Actual cost to date, EAC, CPI, SPI and the S-curve, while you can still act on it.
Reads output
Actual against planned output, by trade, per project, per day.
Reads workertradeattendance
Assigned against required headcount by role, six months out.
A crew lead logs the day once, on site, offline if the signal has gone. The moment it syncs, payroll, cost, productivity and the forecast are all working from the same row.
Most construction software bolts a chatbot onto a help page. This one has permission-scoped access to your roster, forecast, payroll and costs, and makes the change you ask for. Never on its own.
Every number on this page starts as one entry a crew lead makes on a phone, usually with no signal. So it works without one.
Hours, overtime, attendance and output, logged against the roster the crew lead is holding.
Entries save on the phone and post in one de-duplicated batch when coverage returns.
Payslips, leave and approvals in the same app. No company email needed.
Once a log lands, the assistant can answer questions about it.
Every module writes to the same place, so the assistant reads across all of them at once, not one report at a time.
Keep plant, subcontract commitments and variations in separate files and you learn at month-end that earned value was measured against a cost missing three of its five parts. Here every source writes the same number.
Actual cost feeds CPI, SPI and EAC
Gulf-native, not a Gulf skin
A global HR tool asks you to bend your process to fit it, then quotes you for the gap. Same build here, Dubai main contractor or Riyadh subcontractor.
Allowances computed inside the 40 to 80% basic-pay band, and the bank file generated rather than assembled.
Gross from hours logged on site × the hourly rate, with your own overtime multipliers.
Enter a last working day and see the end-of-service figure immediately.
Currency, working week, pension rates, WPS band and Emiratisation target, switchable for any GCC market.
The fastest way to kill a rollout is to make finance re-learn their ledger and IT run a second directory. Neither happens here.
Priced on active workers and the modules you switch on. The AI assistant is in every plan, not an add-on. So is an install that serves one company: yours.
AED 19 per worker / month
Founding pricing
A contractor who needs compliant payroll and the worker lifecycle, end to end.
AED 29 per worker / month
Founding pricing
A multi-project contractor managing cost, not just headcount.
Custom
500+ workers, on-prem, multi-entity
A group standardising every entity on one way of working.
Before you ask
Answered before the call, so the call can be about your projects.
No. The field app writes to its own database on the phone first, so a log is saved whether or not there is a network. Entries queue with a visible pending count and post in one batched, de-duplicated sync when the device is back in coverage, so sending the same entry twice cannot create a second payroll record.
No. SiteSync exports a general-ledger journal in the format your accountant already imports (Tally Prime XML, Zoho Books journal CSV or QuickBooks IIF) for any date range. There is also a REST API with scoped keys and webhooks if you would rather push the data yourself.
Wherever you decide. Each SiteSync install serves exactly one company, yours, and can run on-premise or in your own private cloud. The database is standard PostgreSQL, so your records stay queryable and portable, with nightly compressed backups you can restore with a single command.
Yes. Currency, working week, working days per month, overtime multipliers, the WPS basic-pay band, pension rates and the gratuity formula are all settings, not code. A Saudi contractor switches to a Sunday to Thursday week, SAR and GOSI rates; a free-zone entity outside WPS turns the WPS check off entirely.
Three steps, none of them a programme. A scoped demo runs on your own project list and headcount plan, not a generic sandbox. Workers, projects and assignments then import by CSV against the same tables the app uses. Finally a first-run wizard sets currency, working week, overtime, WPS band and gratuity, and you switch on only the modules you want today. This is configuration, not transformation.
It cannot change anything without you. Read access mirrors your own role exactly, and every write is a proposal showing the record, the field and the new value. It stays a proposal until you press Confirm, and the confirmed change lands in the audit log like any other. You can also point the assistant at a model you host yourself, so nothing leaves your network.
Bring a project list and a headcount plan. SiteSync is onboarding a small cohort of GCC contractors before general launch, with a direct line into what gets built next.
No sales spam, no obligation.
Check your inbox: we've sent a one-click confirmation to that address. A SiteSync specialist will be in touch within one business day.
