Skip to content

How it works

Four stages.No surprises in any of them.

It starts with a free audit and a written findings document you keep either way. We confirm scope and timeline in writing before any build starts.

Process

Audit, migrate, launch, manage.

The same four stages on every engagement. You get a written audit before you commit to anything.

  1. 01

    Audit

    At no charge. We list what you run today, where the data lives and what the migration really involves. You keep the written findings either way.

  2. 02

    Migrate

    We move employees, customers, tickets, assets and history onto the open-source stack, then reconcile it against your old system.

  3. 03

    Launch

    Cutover on a date you pick, with training for admins and the people who enter data. Parallel run where payroll is involved.

  4. 04

    Manage

    Patching, upgrades, backups with tested restores and monitoring, with a named engineer who knows your system.

AUDIT REPORT / SAMPLEFindingsSystems in useData sourcesMigration risksCompliance checksRecommended track

FAQ

Questions, answered plainly.

Who owns the software and the data?

You do. The applications are open source and licensed to you by their maintainers, not by us. Your database and documents are yours, exported on request in open formats at any time, with full documentation. If you end the engagement, nothing is held back.

What does the annual managed fee cover?

Infrastructure, which means the server itself is included and paid for by us, plus security patching, software updates and upgrades, backups with tested restores, monitoring with alerting, and ongoing maintenance with a named engineer. Implementation, data migration and user training are part of the engagement too.

What is not covered?

Custom development. Net-new features, bespoke integrations, or anything beyond standard configuration is quoted separately, per request. We tell you before the work starts whether something counts as configuration or custom development.

Is open source always the better choice?

No. If a per-seat or cloud product suits your team better, we say so during the audit, in writing. We also implement Zoho and Cflow, so we have no reason to push one track.

How long does an implementation take?

It depends on the number of systems, the state of your data and how many entities you run. We confirm the timeline in writing after the audit, rather than promising one before we have seen your data.

Can you handle WPS, GOSI and end-of-service rules?

Yes. WPS files, GOSI contributions, Mudad formats, Nitaqat inputs and Iqama expiry tracking are part of a KSA payroll build, with the UAE equivalents for UAE entities. Portal specifications change, so we verify current formats per engagement.

What if we already tried an ERP rollout and it failed?

That is a common starting point. The audit looks at why it failed, usually scope, data quality, or nobody owning the system after go-live, and we scope around it. If your process needs fixing before any software will help, we say that in writing.

Tell us what you run. We'll tell you what to do with it.

We use this only to reply to you.