Case study · 09 of 27

AedahSuite: twenty-two business apps for UAE and GCC companies on one platform

Small and mid-sized companies in the UAE usually run on a patchwork: one tool for the books, a payroll bureau for WPS, a CRM that does not know about invoices, inventory in a spreadsheet, approvals on WhatsApp. Every month…

Role: Founder, product owner and architect; built with AI-assisted engineering under my direction and reviewStack: Next.js 16, NestJS 10, Prisma 5 (multi-schema), PostgreSQL 18, Claude tool-use for the Co-Pilot, PM2 and nginx on Linux, CloudflareLive: aedahsuite.com
AedahSuite: twenty-two business apps for UAE and GCC companies on one platform, live site
Live: aedahsuite.com

Context

Small and mid-sized companies in the UAE usually run on a patchwork: one tool for the books, a payroll bureau for WPS, a CRM that does not know about invoices, inventory in a spreadsheet, approvals on WhatsApp. Every month somebody re-keys the numbers before the VAT return. AedahSuite is my answer to that: separate apps for finance, people, sales, operations, documents and compliance that share one login, one set of companies and permissions, one ledger and one AI Co-Pilot.

It is my own product, not a client build, and it is pre-launch. It runs as a demo and staging environment with five industry demo companies loaded, and production hosting in the UAE is planned for when the first customer contract closes. I am stating that plainly because the scale of the engineering is real, while the customer base is not yet.

What I built

Twenty-two apps, each a bounded context

Finance and Accounting, HR and Payroll, CRM and Sales, Marketing, Project Management, Inventory and WMS, Procurement, Legal and Compliance, Customer Support, Fleet, Real Estate, Trade and Logistics, Analytics and BI, Retail POS and E-commerce, Events and Ticketing, e-Signature, Expenses and Cards, Business Mail, Drive and Docs, Password Vault, Learning and Training, and the AI Co-Pilot. Each app owns its own PostgreSQL schema with no foreign keys into another app, so an app can be licensed, removed or deployed on its own without dragging the others with it.

A shared platform layer

Approvals, audit trail, idempotency keys on money-moving and sending routes, an outbox for events between apps, notifications, background jobs, custom fields and per-company app licences are built once and used by every app. Tenant isolation is enforced at the data layer: every request sees exactly the company it is authorised for.

An AI Co-Pilot that cannot act alone

The Co-Pilot reads across every app a company licenses, within the permissions of the person asking. It analyses, drafts and proposes actions through tool calls, and every create, approve or update waits for a human to confirm. Salaries and vault secrets are never readable to it, each step is audited, and a customer can switch it off, point it at a local model or use an approved provider.

Apps that would be products on their own

Decisions worth noting

Why it is in the portfolio

It shows the full breadth of what I do in one place: product definition across twenty-two business domains, a multi-tenant architecture that stays separable, regional compliance turned into software, AI that is useful without being trusted blindly, and the operations to run it. It is also the platform I implement for clients who want one system instead of a patchwork.

Next step

Have a system like this to build, rescue or scale?

I run technology for several companies at the same time and take on a small number of fractional engagements. The first step is always a scoped audit.