Project 05 · Case study
Clinavi — medical-practice platform
Cofounding a pilot-stage product for Moroccan doctors across product, full-stack engineering, infrastructure, and security controls.
Cofounder and full-stack engineer · small founding team
Clinavi is a comprehensive medical-practice platform built with Moroccan doctors and currently in pilot. As a cofounder, I work across architecture, backend and frontend, product decisions, infrastructure, and security in a small founding team.
01 · Product context
A connected practice workflow, not a single clinic feature
A medical practice has interdependent work: patient records, consultations, prescriptions, scheduling, waiting-room and billing workflows, alongside specialty needs. The product is designed with Moroccan doctors around those practical operating contexts.
The current stage matters. Clinavi is in pilot, so this case describes the work and product scope—not broad adoption, commercial traction, compliance certification, or clinical outcomes.
02 · Founding scope
Product judgment and engineering share the same boundary
I work hands-on across the Next.js and TypeScript product, PostgreSQL-backed systems, infrastructure and deployment, and the product decisions that connect them. Structured doctor interviews and pilot feedback inform the product work.
I also contributed with the team to an intelligent WhatsApp assistant. That work is collaborative; it is not presented as sole authorship.
01 · Product
Workflows shaped with practitioners
The product is built around practical practice workflows and feedback from doctors rather than a generic administrative template.
02 · Platform
A full-stack product surface
My work crosses architecture, backend and frontend engineering, product experience, infrastructure, and deployment.
03 · Security
Controls made explicit in the product work
Tenant isolation, role-based access, encrypted transport and secrets handling, audit logging, backup and recovery, security review, and testing are part of the engineering scope.
03 · Product stage
Build rigor before claims of scale
Early-stage product work rewards clear boundaries: what is being learned with users, what the system must protect, and what has not yet been proven. I treat that honesty as part of the product and technical practice.
Evidence treatment · contribution map
The parts of the product I worked on
Scope is deliberately grouped by my ownership boundary. It is not a claim about the whole system.
Work across
- Architecture and backend systems.
- Frontend and product experience.
- Infrastructure, deployment, and product decisions.
Implemented controls
- Tenant isolation and role-based access.
- Encrypted transport and secrets handling.
- Audit logging, backup/recovery, security review, and testing.
Contributed with the team
- An intelligent WhatsApp assistant.