Why I'm Building LumX
LumX exists because I want to build products, operate them, and share the process with enough detail that other builders can learn from it.
LumX is my one-person product studio.
That definition matters. LumX is not a single app, a generic portfolio, or a vague AI lab. It is the operating base I use to build independent products, write about the process, and turn lessons into repeatable systems.
Why a one-person product studio
I want a structure that can hold more than one product over time.
A personal website is too small for that. A startup-style brand can become too performative too quickly. A studio is the right frame: it can contain products, experiments, notes, case studies, and the operating principles behind them.
LumX gives that work a home.
Why build in public
Building in public creates accountability. It forces the work to be concrete.
If a product decision works, I can explain why. If a launch is messy, that is part of the record. If an AI workflow fails, the failure is useful when it becomes a note, a system, or a better product loop.
The point is not to look finished. The point is to make the process observable.
Why Clad is first
Clad is the current product under LumX.
It is an AI personal color service that helps people discover their colors, palettes, and beauty recommendations. I chose it because it sits at a useful intersection: AI vision, consumer UX, recommendation design, and trust.
It is also a good test for a bigger question: how do you turn AI capability into a product experience people can actually use?
What I will share
LumX Writing and X are where I will share product decisions, AI workflows, architecture notes, launch lessons, user feedback, and the operating systems I build around the work.
The goal is simple: build products, learn in public, and make the learning useful.