Work
The decisions behind the products.
Six systems, mapped from customer experience through to operator tooling, repository boundaries and the evidence behind every claim.
- Case studies
- 6 mapped product systems
- Perspective
- Customer, operator and system
- Evidence
- Live, implemented, demo and exploratory
/work/qzee
Flagship systemQZee
How a booking product became a shared operating system for customers, venues and events.
2023 to now · owned product
2,527 ancestor commits across six pinned repository snapshots
/work/runite
Live runner product + owner previewRunite.Club
A two-sided running platform joining discovery, communities, events and club operations.
2025 to 2026 · platform
Two purpose-built experiences over one product model
/work/coast-competitions
Live customer product + implemented CMSCoast Competitions
A complete competition lifecycle with operator control, payments and inspectable results.
2026 · product launch
Publish, qualify, transact, draw and record
/work/base-blu
Live brand + implemented booking integrationBase Blu Training Club
A distinct training brand connected directly to QZee classes, identity and booking operations.
2026 · integrated product site
One customer journey across Base Blu and QZee boundaries
/work/mtcc
Deployed platform + continuing developmentMTCC Diagnostics
A consultant methodology turned into configurable diagnostics, scoring and actionable reports.
2025 to 2026 · deployed product
Three applications and a shared scoring core
/work/mantyl
Live site + published CLI · alphaMantyl
A local-first CLI that turns AI-built repositories into verified, recipient-ready project passports.
2026 · owned product · solo build
A CLI, a web product and fourteen shared packages in one monorepo
Want this detail on your product?
Tell us where the product is now and where it needs to get to. We'll map the decisions in between.
Discuss a project