Mindset of 0 → 1 → 100

The part most people avoid is my favourite part: the ambiguous zero-to-one, where there's no spec, no design, and no certainty, just a vague idea and a deadline. On the OtonomiQ console I translated raw product requirements into a production UI with zero design handoff, because someone had to turn nothing into something.

But shipping the MVP is only the beginning. I think constantly about the one-to-hundred: architecture that won't buckle under growth, design systems that keep a whole team fast, and the unglamorous reliability work (accessibility, performance budgets, error states) that decides whether a product survives its own success.

Founders need both instincts in one person: the recklessness to ship something on day one, and the discipline to make it last past day one hundred. I try to be that person.