No audited outcomes
No commercial outcome for these projects has been measured by an independent tool, and we do not publish inferred percentages. Where a number appears on this site it comes with its source and limits.
Real projects,
documented scope — not badges.
Every project below is written in the same order: brief, constraints, our role, approach, artifacts — then exactly what can be published and what cannot. You will not find “proven results” or screenshots from a client who has not approved publication.
Projects on this page3
Publicly usable1
Under NDA1
Concept diagrams3
01Healthcare · Multi-tenant SaaS · 2024–2026
صيدليتي Pharmacy OS
Doctor Pharmacy
A pharmacy chain running point of sale, stock, prescriptions and finance in separate tools, with no single view of a shift or a branch.
Constraints
- Arabic RTL as the primary interface, not a translated skin
- Multi-tenant from day one — branches must not see each other’s data
- Must work on the counter hardware already in the branches
- Pharmacy workflows: batch numbers, expiry and prescription linking
Our role
Architecture and full-stack delivery by the studio — data model, multi-tenant boundaries, RTL interface system and the module rollout order.
Approach
- Modelled the pharmacy day first: counter, shift, stock receipt, prescription, month-end
- One tenant-isolation rule enforced at the data layer, not in each screen
- Shipped in modules, each one usable the week it was delivered
Artifacts
14 modules shippedPoint of sale, invoicing, inventory and goods receipt, prescriptions, customer records, shifts, reports
Multi-tenant data modelTenant isolation, branch roll-ups and per-branch permissions
Bilingual interface systemRTL-first components reused across every module
Next.jsNestJSTypeScriptPrismaPostgresPWA
Publication status & evidence
No public screenshots. Screens contain branch data, so any published view would need written client approval first.
Live product, private deploymentDiscuss a similar build
02PWA · Offline-first · Public project · 2026
زاد Zad
Worship Companion
A daily-use worship companion for the first ten days of Dhul-Hijjah — used in places with weak or no connectivity.
Constraints
- Fully usable offline — the offline state is the normal state
- Bilingual Arabic/English with correct RTL presentation
- Readable type for Quranic text at phone sizes
- No account, no tracking, nothing to sign up for
Our role
Concept, interface design and front-end implementation, including the offline data strategy and type system.
Approach
- Data cached on first load; every core feature works with the radio off
- Arabic typography tested on a small screen before the language switch was built
- Gesture and thumb reach drove the layout more than the desktop comp
Artifacts
12 worship modulesPrayer times, Qibla, Quran, adhkar, tasbih, Ruqyah, Asmaa Allah, Ramadan, Hajj, kids section
Offline-first data layerService worker and local storage — no network calls required for core reading
Public releaseDeployed publicly, open for anyone to use without an account
PWAService WorkerVanilla JSlocalStorageVercel
Publication status & evidence
The live app is the evidence — anyone can open it and use the offline state.
03Pharma ERP · Internal system · 2026
نايل فارما Nile Pharma ERP
Nile Pharma, Food & Supplements
A pharmaceutical distributor running the full sales cycle on paper and spreadsheets — including expiry-sensitive stock and rep incentives.
Constraints
- FEFO allocation is compulsory, not a best effort
- Consignment (amanah) stock must be tracked separately from owned stock
- Rep incentives calculated from actual collections, not invoices issued
- The team had to keep working during rollout — no downtime window
Our role
Business analysis, system design and delivery of the ERP modules with the client’s operations team.
Approach
- Mapped the sales cycle end to end with the reps before designing any screen
- FEFO enforced in the allocation engine so no screen can bypass it
- Incentive rules written down as formulas and reviewed with finance
Artifacts
10 ERP modulesCatalogue, inventory, consignment, FEFO sales orders, invoicing, collections, incentives
Allocation engineFEFO rules applied to every order, with an audit trail
Incentive calculationRep ranking and payouts derived from collected amounts
React 18RTLIBM Plex Sans ArabicFEFO logic
Publication status & evidence
Nothing can be published: commercial volumes, margins and rep data are all under NDA. What can be discussed on a call is the design approach, not the numbers.
Internal system — NDADiscuss a similar challenge
LIMITSWHAT THIS SECTION DOES NOT CLAIM
No audited numbers, no borrowed client imagery.
Three honest limits, stated up front — so nobody has to discover them later.
No protected client material
The three visuals are scope diagrams, not product screenshots. Client material under NDA is not published — it can be discussed on a call.
No testimonials
We have not solicited and will not invent client testimonials. Anyone who wants a reference asks on the call, and it is handled within what each contract allows.
Want to see a working system?
The Zad app is public and you can open it right now — eleven of its modules work offline, and that is the fastest proof we can offer.
NEXT STEP
Have a system worth documenting?
Bring the situation and we will tell you which of the three shapes — product, platform or brand — it actually needs.
info@codeandcanvas.net · +966 54 552 0750 · +20 109 250 0454