Curiosity,
with a URL.

Why I built it I wanted more than a workout logger. I wanted to understand whether I was getting stronger and leaner, why my performance changed, and what I should do next based on my actual history. I built the smallest useful version, used it, found what was missing, and kept iterating until the software began changing how I behaved.

Why I built it Most people do not need another budgeting dashboard. They need a clear answer to a simple question. Drop in a CSV, XLSX, or PDF and the app turns spending into an immediate visual story. Files are processed locally in the browser and discarded after analysis.

Why I built it Someone shipped SolPrice, and I wanted to find out whether I could do the same thing without knowing how to code. Rather than write prediction contracts, I embedded Polymarket's existing markets. The liquidity was already there, so building my own would have been an exercise in vanity.

Why I built it You cannot sell a developer API you have never used. I built on ours the way a first-time integrator would, hit the same walls a customer would hit, and took the friction back to the team as fixes instead of opinions.

Why I built it I stare at screens all day. Every existing reminder fired an OS notification, which I had trained myself to dismiss without reading. This one takes over the page and makes you press the button, so ignoring it costs more than obeying it.

Why I built it Every task app wanted to be a tab, and a tab is a thing you close. I wanted the list to open where I already was, one click from whatever else I was doing, and still be there tomorrow.

What I explored Upload an image, understand the clothing and style, retrieve visually similar products, and rank matches across roughly ten marketplaces including Myntra, Nykaa, Flipkart, and Meesho. The product problem was not generating recommendations. It was making visual intent searchable.

What I learned The product was more than a prompt. It connected Telegram, a bot interface, an LLM and an API layer into a usable interaction, giving me practical experience with orchestration, prompt design, and turning model output into a product.

My role I did not build the product. I executed the launches, translating product value into clear launch narratives, distribution, and Product Hunt momentum for two distinct capabilities.

What this represents Product work is not only software. I also build the systems and narratives that help products launch, get understood, and find their first users.