Platform Overview · System Design2026
ZAAD Platform
A multi-tenant business operating system for UAE & GCC SMEs.
HR · Accounting · Inventory · Verticals — one core, one ledger, AI-native, sold à la carte.
The core idea01
The differentiator isn't a feature — it's an architecture.
Automatic cross-module posting (HR→Finance) exists only if there is one database and one ledger. So a thin always-on Core owns the General Ledger; every module is a producer of ledger entries on top of it.
What it is02
Three products, one core.
ZaadWorks
HR & payroll — WPS, gratuity, visa, attendance, ESS
ZaadBooks
Accounting — GL, VAT, Corp Tax, e-invoice, AR/AP
ZaadStock
Inventory — multi-warehouse, WAC/FIFO, COGS
+ vertical packs · AI agents · chatbots · integrations — all on the same ledger.
Why rebuild03
Today: two apps, two databases.
- ZaadWorks (HR) — its own database
- zaadaccounts (Books) — its own database
- → "automatic HR→Finance" cannot physically exist
Greenfield rebuild on one core. ERPNext = reference for the ledger; Odoo = reference for modular resale. Built on neither.
Architecture04
The layer cake.
- Channels — web · mobile/ESS · WhatsApp/IG · chatbots · API
- Vertical packs — Field · Logistics · Health · SCM · Sports · Build
- Horizontal modules — HR · Books · Stock · CRM · Projects · Procurement · DMS
- Shared engines — Scheduling/Booking · Assets/Maintenance · Recurring-billing
- Core — tenancy+RLS · parties · General Ledger · lifecycle · workflow · AI · connectors
The ledger spine05
How auto-posting works.
Salary slip · Invoice · Goods issue → on submit → General Ledger (append-only)
↳ Financial statements · AR/AP · COGS · per-vertical P&L
Every module is a producer of ledger entries. Immutable — a cancel posts a reversing entry → audit-proof & retention by design. HR-only tenants still post to the GL → add Books later, zero migration.
Multi-tenancy06
Isolation enforced in the database.
- Single DB · tenant_id on every row · Postgres RLS
- JWT carries tenant_id → set on the DB session
- Policy lives on the table — no code path can cross tenants
- Escape hatch: large/regulated tenants → dedicated DB, no code change
Commercial model07
Sold à la carte.
- Entitlements — one module, several, or the whole suite; gate UI, API & data
- Pricing — per active module + per seat + usage (payslip / e-invoice / AI call)
- Reseller & white-label — partner-owned tenants, branding, custom domains
- Later — app marketplace · embedded fintech (payments, payroll disbursement, lending)
Technology08
Modern, modular, AI-native.
- Stack — Next.js + PostgreSQL/Supabase; modular monolith, one transactional DB
- Vectors / jobs — pgvector (tenant-partitioned) · worker tier for posting, sync, payroll
- AI — Claude via a PII-masking gateway; agents are scoped users, draft-only
- Not microservices — cross-module posting needs one transactional database
Modules · Core09
ZaadWorks · HR
core HR · org chart · visa/doc expiry · onboarding · attendance & biometric · leave · payroll · WPS SIF · gratuity + EOS scheme · ATS · performance (9-box) · ESS · expenses
ZaadBooks · Finance
GL · statements · AR · AP · banking & reconciliation · VAT · Corp Tax · e-invoicing (Peppol ASP) · fixed assets · budgeting · cost centers
ZaadStock · Inventory
items (variant/batch/serial/expiry) · multi-warehouse · WAC/FIFO · landed cost · COGS auto-post · GRN/issue/delivery · reorder · QC
ZaadCRM
leads · pipeline · WhatsApp · quotes→Books
Projects
tasks · timesheets · Gantt · profitability
Procurement
req→RFQ→PO→GRN→3-way match→bill · portal
DMS
controlled docs · versioning · e-sign · retention
Modules · Verticals10
Field Service
work orders · dispatch · technician app · AMC/SLA · parts→COGS · T&M→invoice · customer portal
Logistics / Fleet
vehicles (Mulkiya/Salik/fuel) · maintenance · drivers · trips/ePOD · routes/GPS · freight billing
Healthcare
patient EMR-lite · appointments/queue · Rx · lab · pharmacy · insurance e-claims (DHA/DOH)
Supply Chain
demand/supply planning · multi-echelon · import/landed cost · van sales · track & trace
Sports & Facilities
court booking + queue/waitlist · memberships/credits · academy · leagues · pro-shop POS · utilization
Construction · Estate · Retail · Edu · Pro
BOQ/progress billing · leases/Ejari/rent · multi-outlet POS · students/fees · retainers
Shared engines11
Build once, reuse everywhere.
- Scheduling / Booking / Queue — Sports · Health · Field · Logistics dispatch · rentals
- Assets / Maintenance — fleet · Field Service · Sports facilities · real-estate FM
- Recurring billing / Contracts — memberships · AMC · subscriptions · leases · retainers
Verticals become thin packs + config — that's why they're cheap to stamp out.
AI · Agents · Automations12
Three different things.
| Layer | LLM | What | Example |
|---|
| Automations | no | "when X then Y" rules | overdue 7d → reminder |
| Copilots | yes | ask / draft, in the loop | "overdue invoices > 10k" |
| Agents | yes | autonomous, multi-step | payroll run + anomalies + draft |
Value order: automations + copilots first; agents once guardrails are solid. v1 flagship agent = payroll.
AI · Safety model13
AI is just another user.
- Authenticates as a scoped identity — same RLS + entitlement + permission as a human
- Can't see other tenants · can't touch disabled modules
- Never writes the ledger directly — produces drafts → normal submit/approve
- Gateway: PII masking before egress · tenant-scoped RAG · model routing · metering (Claude)
Integrations14
One connector framework.
| Type | Examples | Mechanism |
|---|
| Migration (wedge) | Tally · QuickBooks · Zoho | batch ETL + AI mapping |
| Live sync | HubSpot · Shopify · banks | webhooks + polling |
| Channels | Meta — WhatsApp / IG / FB | event streams |
| Gov / compliance | EmaraTax · Peppol ASP · WPS | certified, auditable |
"Switch from Tally in a day" kills the #1 switching objection. Long tail via public API + webhooks + Zapier.
Chatbots15
A channel over the AI layer.
Internal
Staff copilot, the employee's permissions — "who's on leave", "draft this PO", "VAT due?"
Customer-facing
Guest-scoped to their own record — book a court / appointment over WhatsApp, pay, get a payment link.
No new primitive — AI gateway + tool registry + tenant RAG + a thin conversational layer. WhatsApp-first.
Commerce16
Integration only — no native store.
- Shopify / Noon / Amazon are channels into one order pipeline
- ZAAD is the back office — inventory truth, VAT, COGS, accounting, fulfilment
- Channel-agnostic order pipeline + connector framework, designed in from day one
"Keep Shopify; ZAAD wires its inventory, VAT, COGS and fulfilment automatically."
UAE compliance17
The regulatory moat.
- WPS — new regime (Min. Res. 340/2026): wages by the 1st, 85%, penalties day 5
- Corporate Tax — small-business relief ends 31 Dec 2026
- E-invoicing — Peppol PINT AE via accredited ASP; SMEs 1 Jul 2027
- EOS — gratuity + Alternative Savings Scheme (Cab. Res. 96/2023); GPSSA = nationals only
- Retention — 7y (CT) · 5y (VAT) · 15y (real estate)
Goal: FTA TAS accreditation + MoF-accredited ASP path. ("Digital Tax Integrator" is vendor marketing, not a real program.)
Market context18
Large, under-served, on a deadline.
557K+
UAE SMEs · ~94%
of all companies
~$2B
UAE ERP market
~15.6% DX CAGR
~75%
still on manual /
basic tools
~63.5% of non-oil GDP · ~250K new companies in 2025 (>1.4M total) · target 1M SMEs by 2030. Sources: WAM/MoE 2023 · Gulf News/MoE 2026 · Grand View/Mordor 2025–26.
Competitive landscape19
No one does both sides.
| FTA TAS | Native WPS/HR | Accounting GL | Inventory | One ledger |
|---|
| ZAAD | goal | ● | ● | ● | ● |
| Zoho | — | thin | ● | separate | in One |
| Tally | ● | thin | ● | ● | ● |
| Xero / QuickBooks | Xero only | — | ● | weak | — |
| Bayzat / Keka / Jisr | HR-only | ● | — | — | — |
| Odoo / SAP B1 | Odoo ● | ● | ● | ● | heavy |
HR tools have no ledger & no inventory. Cheap accounting tools have no real WPS. Unified suites are heavy/partner-led. White space: mid-SMEs between. Watch: Jisr (KSA) converging.
Build phases20
Sequenced behind the WPS wedge.
| Phase | Build | Outcome |
|---|
| 0 · Core | tenancy+RLS · party · GL spine · lifecycle · entitlements | foundation — all depends on it |
| 1 · WPS wedge | HR · payroll · WPS SIF · ESS · payroll agent · Tally migration | first revenue |
| 2 · Books | AR/AP · banking · VAT · statements — same ledger | differentiator goes live |
| 3 · Stock + compliance | inventory/COGS · Procurement · Corp Tax · e-invoicing (ASP) | ahead of 2027 mandate |
| 4 · First vertical | one vertical + shared engine · CRM · Projects · more agents | prove the vertical playbook |
| 5–6 · Platform + GCC | reseller/white-label · API/marketplace · fintech · KSA/Bahrain/Oman/Qatar | scale & expand |
Rationale: Core before anything · WPS sells standalone · Books turns the promise into a live upsell · verticals only after shared engines exist.
Locked decisions21
- Greenfield · modular monolith · single Postgres
- GL spine in Core = the differentiator
- Multi-tenancy = shared DB + RLS
- À-la-carte modules · reseller / white-label
- Immutable ledger · submit/cancel/reversing
- Commerce = integration only (no native store)
- AI = scoped user · drafts only · masked · Claude
- v1 = Core + WPS wedge · payroll = flagship agent
Open questions · next22
To decide before build.
- À-la-carte granularity — module vs add-on
- Reseller: channel / white-label / both
- Pricing axes → is metering Phase 0
- First vertical (real pipeline)
- Reuse legacy pieces or clean-build
- Anything pulling ahead of WPS
Full detail in docs/ — architecture · data model · modules · market · competitors · decisions.