Implementations that go live, and stay live.

Nine years of exactly this at ELO — enterprise implementations for customers in London, Zurich, Oslo, Dubai, Florida, Montreal and Laval, carried from scoping and security review through rollout to post-go-live support. At Frontgo it ran end to end: engineering practices set, Vipps and financing integrations advised, requirement gaps closed before they became rework, and a documented codebase and infrastructure handed to the client's incoming in-house team.

The named contact, not a layer above one. Frontgo ran on weekly and monthly syncs with the client's own project manager owning the roadmap and me owning the engineering side — hiring, practice, integration advice, and the communication gaps nobody else was closing. The AudioBin, SkyTracks and SoftCollab engagement held that same contact role across a four-year lifecycle.

SSO and the API surface are home turf: Anygum, on the Cloudsight identity backbone, is Auth0-based SSO with org- and instance-level RBAC under a layered proprietary permission model, so one organisation runs isolated instances of the same application without separate auth silos — built, not merely configured. Around it sit REST and event-driven integrations on AWS (EventBridge, SQS/SNS, Lambda) with idempotent, retry-safe write paths, plus Microsoft 365 and Azure APIs.

Ramp · iManage and NetDocuments are the genuine ramp — I have not connected either. What transfers is the shape underneath them: auth handshake, permission mapping onto an existing directory structure, sync semantics, and what happens when a sync half-fails. Two to three weeks with sandbox credentials and a real customer matter structure to be useful unsupervised; the first live rollout is where it actually sets.

Every engagement in the delivery record outlived its go-live. EKAGRA ran as a live clinical platform from Nov 2023 to Mar 2026, scaling to 64 doctors, 3,242 patients and 13,340 clinical schedules across 7 centers — a system where downtime is not an option and the audit trail is part of the product. The Canada engagement ran four years across three named clients.

At ELO this was structural rather than occasional: a 22-person product engineering venture firm (52+ FT and contract) where I carried the technical relationship from the commercial conversation through delivery. That included what the commercial side needs to close — custom-branded proofs of concept, clear mitigation paths for security and compliance review, and precise return-on-investment framing.

Global Jute Trading is the sharpest version: instead of teaching a 25-year-old export house Git or handing them a heavyweight CMS, a Claude layer turns plain-English edit requests into pull requests that trigger the deploy. The client now self-serves content without waiting on developers, and every change still lives in Git, reviewable and revertible. Training measured by the customer no longer needing me.

Anygum exists because of this loop: recurring client-side authorization friction across engagements became a reusable multi-tenant RBAC identity backbone rather than the same fix rebuilt per client. EKAGRA's product direction came the same way, from observations on the clinic floor.

Nine years, co-founder through CIO at ELO and now stakeholder and advisor, with the customer-facing technical role constant throughout. Vimalgo is the clearest single case: I led the AI demo that opened the engagement, and the platform launched in January 2025 and is in production.

SSO, authentication and enterprise API integration are demonstrable at the architecture level — Auth0-based SSO with a layered proprietary permission model above it, multi-tenant per-organisation isolation, least-privilege and consent-scoped access, event-driven integrations with idempotent write paths, and GDPR / HIPAA / WCAG 2 compliance led across 5 client organisations.

Ramp · DMS platforms specifically are the gap. Closest adjacent work is HIPAA-compliant document management over diagnostic records and patient histories at EKAGRA, with time-stamped audit logging on every record change — document permissions and audit trails under a regulator, just not through iManage or NetDocuments' own APIs.

Parallel is the default, not the exception — the delivery board on this page is six concurrent engagements across six geographies and six integration surfaces. CSPO (Scrum Alliance), and the operating record behind it: cut time-to-market 4× (75% cycle-time reduction) by replacing manual deploys with GitHub Actions CI/CD across the portfolio.

The Vimalgo demo is the proof that carries money: a working AI matching flow a non-technical recruitment firm could try against their own material, which is why they committed early instead of waiting. Same skill at EKAGRA, translating clinical constraints into product decisions with doctors, and at Global Jute, turning a plain-English request into a deployable change.

Measured in duration and in what people did next: a four-year Canada engagement across three clients, a Norway pod handed over cleanly, and engineers coached into senior roles abroad — two alumni now lead teams in Norway, plus alumni now leading at two local Bangladeshi tech firms.

Remote-first since 2020 across EU, UK and North American time zones. Current build is Wiregent, an agentic due-diligence platform shipped solo and live at wiregent.com — 251 commits, 77 test files against 289 in source, where the verdict cites its evidence and names what it could not score.

CEFR A2, on a 972-day unbroken daily practice streak, with grammar explainers published publicly on YouTube (@FrenchwithFauzul) and Instagram. Honest level: I can read and follow, not run a technical implementation call in French yet.

Ramp · The streak is the point — 972 consecutive days without a miss is the same discipline that shows up in delivery cadence and follow-through after go-live. On a daily practice already in place, conversational working proficiency is a realistic 2026–27 horizon, and being inside a French-speaking client context would accelerate it sharply.