A product studio for compelling services
LumX builds and operates its own products, and helps people and teams shape, build, and launch services of their own. The decisions behind both are written down here as they are made.
Service archive
These are the services LumX operates or validates in public, along with the questions each one started from and how it keeps changing.
Clad, 1 / 4
AI personal color service
A live web service that turns two questions and one photo into a personal colour card — the season, the colours that suit, and the ones better kept away from the face — and says so out loud when several photos disagree.
View the development process
From the field
Not only the wins — the decisions and lessons behind each product, written down as the work happens.
The colour table said navy and crimson, and nobody checked the values. Rather than just swap colours, I made each season's description a rule they must pass.
When code breaks a promise the screen made, lowering the promise is always cheaper. Two cases where I kept the words and fixed the behaviour instead.
Clipped toasts and trees hidden behind landmarks threw no errors. Instead of fixing each one, I fixed the container and measured what is seen, not what exists.
When the red light keeps being someone else's fault, people stop reading it. Another site's uptime and an exception I never declared did that to two CIs.
Capabilities
Every capability below is listed because a live product depends on it, not because it belongs on a résumé. The product that proves each one is named beside it.
A pixel town that has to hold sixty frames a second in a browser and still install as an app. A colour result that has to stay readable on a phone in bad light. A reading that has to make sense before anyone is asked to sign up.
HappyBirthTown, Clad, somesignal
Clad fuses pixel measurement, quiz answers, and a model under fixed weights, and each signal is scored separately against expert labels. When one scored below chance, the answer was a golden-set A/B — which reversed the hypothesis and left the weights alone.
Clad, somesignal
Three different clouds, chosen per product rather than by habit: AWS with Terraform for Clad and this site, Cloudflare Workers with D1 for DUGOUT 9, Vercel with Supabase for somesignal. Each carries its own deploy gate, observability, and way back.
Clad, DUGOUT 9, somesignal, lumx.im
A pixel town where every friend who left something stays as a character, so a gift completes without anyone online at the same time. Sound synthesised at runtime, so the product ships zero audio files.
HappyBirthTown
How LumX is run
One product engineer directly operates LumX's services and archive.
I use experience across software, cloud, and AI to plan and operate LumX products directly.
Decisions and lessons from each product feed the next improvement.
Connect planning, user experience, implementation, and operation inside a real product.
Use software, AI, and cloud experience in proportion to the product's current problem and risk.
Publish why a choice was made and how the thinking changed after meeting real use.
Services, feedback, and notes
Tell me the problem you want to solve and who it is for — that is enough for a first message. You can also try the services first, or read how the decisions behind them were made.
