Proposals and contracts in two languages
The English version and the Arabic version drift apart because they are edited separately.
Consultancies, engineering offices, accountants and law firms share the same problems: proposals in two languages, work that is hard to link to billing, and knowledge buried in folders.
The English version and the Arabic version drift apart because they are edited separately.
Project tasks sit in one tool and invoices in another, so billing is rebuilt from memory at the end of the month.
Who approved a fee, an expense or a concession is found by searching a mailbox.
Staff ask each other questions that previous projects already answered, and nobody can search across them.
In a firm that sells people, payroll is a large part of cost, and it carries obligations of its own.
These are the Saudi regimes that touch this sector, and what the software does about each. Your proposal confirms which apply to your company. This is not legal advice; confirm obligations with your adviser.
| Requirement | What the software handles |
|---|---|
| VAT at 15% | Calculated per invoice line and posted to VAT accounts. |
| ZATCA e-invoicing | Invoicing is built to work with ZATCA e-invoicing requirements. The scope for your company is confirmed in your proposal. |
| Client documents and personal data (PDPL) | Access by role and hosting location by choice, written into the agreement. Documents containing personal data are not exposed to everyone. |
| GOSI, WPS and Saudization | Contributions, salary files and headcount tracking in the HR module. |
Quotes and deals, projects with tasks and timelines, invoicing and approvals that keep the approver's name and the time.
Learn morePayroll, leave, hiring and Saudization tracking for the people the firm sells.
Learn moreStaff or client assistants that answer in Arabic and English from your own documents.
Learn moreSteady Arabic and English content with every post checked and approved by a person.
Learn moreA client-facing project view or a document workflow, built around how the firm delivers.
Learn moreThe order differs a little by sector. The principle does not: a written scope comes first, and you test with your own data before anything goes live.
We trace a recent engagement from proposal to final invoice to see where information is retyped.
Who approves fees, expenses and discounts, up to which limit, written down once.
Client records and open projects are migrated and tested with the people who use them.
Document search and assistants come after the core records are accurate.
Do not assume it. If you bill by the hour, we confirm at scoping how hours are captured and billed, and build the part that is missing.
Access is by role. Restricting a project to named people is confirmed at scoping and written into the configuration.
Yes. Assistants are built to answer from the documents you provide, and to say when the answer is not there instead of guessing.
A client-facing project view is a custom build, scoped with what clients may see and who approves what is shown.
A consultant from our Riyadh team replies with next steps. A written, itemised proposal follows before any work starts.