Live Lebanese education-technology platform
Prepify
I led Prepify's non-AI engineering from an inherited baseline to live operation, covering the web platform, service integration, payments, SMS/OTP, automated quality, deployment, operations and support.
01 / Context
What needed to change
Prepify began with an inherited education-platform baseline that still needed to become a deployable, supportable live product.
02 / Role
What I owned
As contract Head of Systems, I independently owned delivery of the non-AI platform and coordinated its integration with a separately accountable AI team.
03 / Constraints
Scope and limits
I inherited the starting point rather than authoring every component. A dedicated AI team retained ownership of its module; my scope was the non-AI platform, product integration, deployment, operations and support.
04 / Approach
How I approached it
- Modernized and completed the .NET and SQL Server web platform.
- Integrated separately owned FastAPI services through explicit contracts and release checks.
- Implemented payment and SMS/OTP paths with confirmation, idempotency and reconciliation patterns.
- Built environment-separated CI/CD, readiness diagnostics and browser smoke verification.
- Created a central documentation, operations and guided support-onboarding system.
05 / Verification
How the result was checked
Prepify launched with its public product, registration and sign-in surfaces live, supported by the platform, integration, quality and delivery systems described above.
06 / Outcome
What changed
I took Prepify live at the end of June 2026 and committed to one month of post-launch bug support. The separately staffed AI team remained accountable for its module.
07 / Lessons
What I carried forward
Clear ownership boundaries are not administrative overhead; they make contracts, automation, handover and support stronger.