Case Study / MedicAI

Ship like a full engineering team. Without hiring one.

MedicAI is a live UAE tele-health platform connecting patients, doctors, labs, pharmacies, and corporate employer health plans across three codebases. In roughly six and a half weeks, one operator — using DouJou and Kaizou rather than a hired engineering team — took it from an earlier-stage product to a consolidated, enterprise-grade platform.

987

commits shipped to production

~94%

produced through DouJou

3

products shipped in lockstep

~6.5 wks

earlier-stage to enterprise

Every figure independently verifiable in MedicAI’s git history.

Where it landed

Three codebases, one engagement.

Codebase
Commits
What shipped
Backend API
510
Enterprise RBAC, employer/contract/census data model, wearables ingestion, DHA & MOHRE compliance, in-product multilingual AI assistant.
Web Console
360
Employer self-service portal with workforce analytics, admin consoles, identity-verification flows, Help Center, Arabic/RTL localisation.
Mobile App
117
Wearables support, step-by-step identity verification and booking flow, in-app bug reporting.

Two layers, not one product

DouJou is infrastructure. Kaizou is the work.

DouJou is the governed infrastructure layer — it installs inside a customer’s own cloud account, maps their real technical estate, and keeps that map current and provably true. Kaizou sits on top, running S+3 Agile to turn that governed context into shipped product work. Around both sit the Shields — paid add-ons that extend what the platform governs and defends, including the Data Shield (data sovereignty and egress governance, the module MedicAI leaned on hardest).

The short version: this stack didn’t just make one engineer faster. It absorbed the discovery, context-retrieval, quality-review, and a slice of the bug-fixing work that a multi-person engineering team would otherwise do by hand.

Musheb Maniyar

“In six weeks, MedicAI went from an earlier-stage app to an enterprise-grade platform — employer portals, UAE healthcare compliance, wearables, and an in-product AI assistant — without standing up an engineering team. DouJou didn’t just make one person faster; it did the work of a whole squad, entirely inside our own cloud where our patient data has to stay. It changed what a team our size can ship.”

Musheb ManiyarCo-founder, MedicAI

The MuShuHaRi framework

How MedicAI matured: Mu → Shu → Ha → Ri.

DouJou deploys once, then takes an organization through guided, evidence-gated stages of AI maturity. In six weeks, MedicAI moved through three of the four — from first enterprise context to shipping customer-facing AI.

Mu

Deploy & Context

DouJou installs inside your own cloud and maps your real estate. MedicAI: self-hosted in their own AWS, three codebases auto-discovered.

Shu

Datasets & Internal AI

Curate datasets, wire them into internal ops AI. MedicAI: the bug-fixing pipeline began triaging and fixing the real repos.

Ha — MedicAI is here

Customer AI & Projects

Deploy customer-facing AI and ship AI-native projects. MedicAI: shipped an in-product multilingual health-triage assistant, grounded and hallucination-checked.

Ri — next horizon

Leadership Runs It

The C-suite manages the whole infrastructure and product estate through DouJou.

Read the full story

The complete case study, as a PDF.

The full document — methodology, framework detail, and every figure sourced to MedicAI’s own git history.