Skip to content
Currently available — for the right work·France903+ Day French Streak·2026 Q2 calendar — open now
Part of ELOEmbedded Logic Operations · Founding engineer → engagement lead
↩ Projects · Six-year engagement · Acquired by Loopcloud (2026) · 0→1 → scale → acquisition
Acquired · Founding engineer → engagement lead (via ELO) · European Union

Jamahook

Created Jamahook’s first web product and admin panel from a blank canvas — a music loop matching and discovery service powered by AI model–extracted weights. After early traction I stood up the full-stack team (React + Node/NestJS on an NX monorepo) and kept hands-on through the first market release. Six years later the product runs on web, as a DAW plugin, and as a desktop app with a much richer feature set; Loopcloud acquired it in 2026 and the dedicated team I helped build still ships modern integrations. Since 2023 my seat has been primarily client and business relationship — engineering leadership in the early years.

Role
Founding engineer → engagement lead (via ELO)engineering
Period
Six-year engagement · Acquired by Loopcloud (2026)completed
Stack
ReactNestJS · NX monorepo · Storybook
Location
European Unionremote
$ wsl --mount /dev/sda3 ↳ ✓ mounted at /mnt/wsl/sda3$ ext4 read 1.8 GiB ⏎ ➜ 71ms · 4.2× faster$ █
01 · Blank canvas to market

Blank canvas to market

Jamahook started as a greenfield bet: no existing product surface, only the problem of helping producers find and match musical loops fast enough to stay in flow. I designed and built the first customer-facing web app and internal admin panel — loop matching and discovery driven by weights extracted from an AI model, not a hand-curated catalogue alone.

That 0→1 phase was fully hands-on: product shape, React front end, NestJS APIs, and the admin workflows the ops team needed to keep the catalogue honest as usage grew.

02 · Team, monorepo, and compliance at scale

Team, monorepo, and compliance at scale

  • Team stand-up after initial success — once the product proved itself in market, I hired and directed the full-stack pod under ELO, with a deliberate split between frontend (React + Storybook) and Node/NestJS integration work.
  • NX monorepo — consolidated web, shared libraries, and admin tooling so multiple engineers could ship without fragmenting the codebase.
  • Stripe + GDPR/VAT — checkout, tax, and EU compliance baked into product flows for 15,000+ active users, not bolted on after the fact.
  • AWS Lambda admin panels + S3 Glacier — internal tooling on serverless compute and cold storage for massive audio archives.
03 · Six years on — and acquisition

Six years on — and acquisition

The product outgrew the first web-only vision: today it ships as a web app, a DAW plugin, and a desktop application, each with enriched features accumulated over six years of iteration. Loopcloud acquired Jamahook in 2026; the dedicated engineering team I helped assemble still works on modern integrations and keeps the platform moving.

My role shifted naturally with maturity — hands-on through the early build and team formation, then primarily client and business relationship from 2023 onward while the team owned day-to-day delivery.

Performance Metrics

By the numbers.

Acquired
By Loopcloud (2026)
15,000+
Active users at scale
3 surfaces
Web · DAW · desktop
6 yrs
Product evolution
Collaborate

If we worked together.

I bring high-leverage product engineering and absolute operational discipline: shipping weekly, pressure-testing user inputs, and automating delivery pipelines.

Visit project

See it in the wild.

This case study covers how Jamahook was built — these links open what ships today: the live product, repo, demos, and supporting material.

Next case study

Anygum

Anygum (codename Cloudsight) is an enterprise software marketplace hub built to expose and consume software products as a service. Conceived, designed in Figma, and architected by Fauzul to serve ELO Books (ERP) as a service. Built in collaboration between ELO's Dhaka and Norway engineering teams, and led by Fauzul, it has now scaled to service clients globally and acts as the central AuthN/AuthZ layer for ELO's products. Has the potential to be in public.