A growing SME does not lack software. It lacks the links between them.
Documents live in one place, accounting in another, operations somewhere else. Each works. Together, they do not tell the same story. Qasax connects the three in one environment, with separated responsibilities and an audit trail.
The problem
What breaks as a company grows up.
None of these symptoms is dramatic. That is exactly why they last for years.
Documents have to be hunted down
One supplier invoice arrives by email, another as a photo, a third in a binder. Nobody is lying; nobody knows where they are.
Operations do not talk to finance
Stock moves, tills run, teams execute — and none of it reaches the books without re-keying.
Several companies, one spreadsheet
From the second legal entity onwards, data separation rests on everyone’s discipline rather than on the tool.
Two countries, two rule sets, one director
What is compliant on one side is not on the other. Reconciliation happens by hand, late, under pressure.
The answer
An execution chain, not a collection of modules.
A document arrives, it is filed, it triggers an operation, the operation produces an entry, the entry reconciles against the bank, and the whole thing stays auditable. That thread is the difference.
Documents
Intake, filing, linking to third parties and accounting records.
Finance
Invoicing, purchases, accounting, bank reconciliation, closings.
Operations
Inventory, tasks, incidents, activity per establishment.
Control
Roles, permissions, audit log, strict separation between companies.
What sets us apart
What exists, and what is being built.
Every item carries its real status. Anything not available today is announced as such — it is the only way to make the rest credible.
Multi legal entity architecture
Each company carries its own jurisdiction, rules and access perimeter. Separation is enforced by the data model, not by a naming convention.
France ↔ Tunisia bridge
One common engine, two distinct national frames. Rules, formats and obligations stay separate per country; nothing is merged for the sake of simplicity.
Verticals on a shared core
Hospitality, restaurants, healthcare, industry, retail: business lines reuse the same document, finance and operations engine instead of duplicating one per sector.
Per-company data separation
Isolation is verified by automated checks on every delivery, not observed after the fact.
Data Brain — deterministic event backbone
An append-only business event log and a versioned contract covering the core domains. The foundations are in place; the analytics layer remains to be built, and we do not present it as delivered.
Governed business agents
An optional assistance layer, under human validation, with no autonomous sensitive action. It is not available today.
Our position on AI
No artificial intelligence in execution, today.
This is not a delay, it is a decision. A business rule must be explainable, replayable and defensible. Generated text is not.
- The source of truth is a deterministic rules engine: the same input always produces the same result.
- No accounting entry, no regulatory validation, no sensitive action is produced by a generative model.
- The AI assistance we are preparing will stay optional, governed, and always subject to human validation.
- We would rather announce a capability once it is proven than sell a promise that is hard to defend.
The model
How Qasax is sold, and sized.
A subscription, modules you switch on when you need them, and support sized case by case.
- Software subscription, with no paid tier for updates.
- Modules activated separately — you do not pay for what you do not use.
- Business verticals for the activities that need them.
- Multi-site and multi legal entity extensions.
- A dedicated offer for accounting firms managing a portfolio.
- Support: data migration, sector configuration, training.
The company
Who builds Qasax.
A product is also judged by how it is run. Here is what we can state without reservation.
A written delivery discipline
Every change goes through automated checks, validation in a pre-production environment, then a production release of the exact version that was validated — never a rebuild.
Three languages from the start
French, English and Arabic, with the right reading direction. Not a layer added afterwards.
Data separation by design
Access is partitioned by company and by role, and that separation is checked automatically, not merely documented.
Nothing is announced before it is proven
No regulatory status, no accreditation, no partnership is claimed until obtained. This page is that principle applied.
Let us talk about your organisation.
In a few minutes we understand your context — companies, establishments, countries — and show you what actually applies.