HUGO.CHARMIES(1)
PRODUCTION
$ hugo --whoami
Full stack developer in Belgium. I build internal tools that replace manual and paper-based work, most recently at Vanwezel Autoparts.
$ hugo --status
status : ● Open to full stack roles location : Limburg · Belgium daily_driver : Claude Code favourite_stack: Next.js · Postgres
$
$ hugo --now
$ hugo --featured








$ hugo --stack
AI
────────────
FULL STACK
────────────
INFRA & TOOLS
────────────
$ hugo --origin
I studied Applied Computer Science in Leuven. For a school project, a client needed indicators scraped from the web, which was all manual work. I automated it with an AI model and saw how much faster you can build now.
Since then I build with AI coding tools like Claude Code, and I test and review what they produce. What I like most is finding a slow process and replacing it with a small app.
EDUCATION
UC Leuven Limburg
BSc Applied Computer Science · 2022–2025
FIRST AI PROJECT
Ecofoodmap · n8n → code-native
WAY OF WORKING
Claude Code, then test and review
$ hugo --archive
$ hugo --contact
$ open ~/projects/loodgieter
HUGO.LOODGIETER(1)
STACK
Next.js · Supabase · Coolify VPS · Codex + Claude two-agent build
01 / 04
The brief. Parallel Studio is my small service for Belgian SMEs, Google Business Profiles, lead capture, light automation. To know exactly what I was selling, I built it. A fictional plumber, a full platform behind it. Customer-facing site, admin dashboard, quote requests, jobs, invoicing, finance, analytics, cron-driven reminders. The whole vertical, in one codebase, deployed on a Coolify VPS I run myself.
02 / 04
Belgian, not English-template. Routes are Dutch, /klanten, /opdrachten, /offerteaanvragen, /financieel. The invoicing logic is Belgian. The quote flow is shaped like how Belgian trades actually work. Most "SaaS for SMEs" pitches in 2026 are English-first slop applied to a market they don't understand. This one was built for one specific market and one specific trade, on purpose.
03 / 04
The part most hidden in the codebase. I built it with two agents, not one. Codex writes server actions, DB queries, Playwright specs, Vitest tests. Claude writes the UI, runs the tests, executes the shadcn and supabase CLIs. The division is forced by Codex's sandbox, no network, can't run what it writes. So Codex specifies, Claude verifies. There's a documented fallback when Codex isn't available. The orchestration is the work.
04 / 04
Honest status. Internal commercial demo. No prospect has seen it yet, Parallel Studio is on the back burner while I work on Charmies and Kompass. The platform exists, runs, and tells me precisely what I'd offer when I turn the service back on. Building the asset before selling it changes the sales conversation.
SCREENSHOTS
$ Try the live demo at jannsen.parallelstudio.dev.