Something I changed my mind about while building a finance app for freelancers.
Say someone made $2,000 last month and $0 this month. The math says -100%. A big red number.
It's correct and it's still misleading. For a freelancer, an empty month often just means a payment is late. So in my app, when a month is at zero, that comparison doesn't show at all. Same with small samples: if there isn't enough history to say something, the screen says that instead of guessing.
I'm not a developer. I came up writing HTML, CSS and Sass, and now I build by directing AI agents.
With AI, adding a feature is cheap. That makes scope creep really easy.
One thing that helps me: my project's README has a "what it doesn't do" section. Things I decided on purpose not to build, each one because it would add legal risk, security risk, or a number I couldn't defend.
Since I don't write the code, my control lives in decisions like those.
Hey everyone. I'm Nico, Argentinian, living in Costa Rica. Most mornings I'm surfing by 6, and then I get to work.
I've been building digital products for 12+ years: healthcare, government, fintech, media. I started out writing and laying out HTML, CSS and Sass, then moved into product design and leading design teams. Today I call myself an AI Product Builder: I take a problem and ship it to production.
That's how I built Alisio, a multi-currency invoicing app for freelancers who invoice and get paid in different currencies. I built it on the side of my main role as a Senior Design Lead (contractor).
I'm not a developer. The technical side isn't foreign to me, but I don't write application code. Every line in Alisio was written by six AI agents I direct (PM, UX, UI, Dev, QA, Content). The judgment stays with me: what to build, for whom, and which number should never be shown.
