Product & UX practitioner who can't write code — and shipped a production SaaS anyway.
I built Alisio end-to-end by orchestrating AI as my engineering, design, and strategy team while I drove product decisions and quality. Invoicing, expense tracking, AI receipt scanning, and cash runway for freelancers who work across borders and currencies — live in 13 languages.
Building in public. Here to share what I learn and learn from the people doing the same.
Alisio is invoicing and financial clarity for freelancers who work with the world. Create professional invoices, snap a photo of a receipt and let AI log the expense, track every currency separately (no fake conversions), and see your cash runway — how long your money lasts. Personal finance + business invoicing + native multi-currency, in one place. Built solo by a non-technical founder directing AI.
URL: https://getalisio.com
Six months ago I couldn't write a line of code. Today I have a SaaS in production, in 13 languages — and zero customers yet.
I'm a product/UX person, not an engineer. So instead of using AI to autocomplete code, I treated it like a team — one for strategy, one for design, one for engineering. My job stayed the same: decide what gets built, question everything, refuse "done" without proof.
The biggest lesson: verification beats trust. I once shipped a migration that never hit production. Now nothing is done without a real test — not the AI's say-so.
I'm a solo, non-technical founder building Alisio, an invoicing tool for freelancers who work across currencies. Early days.
Every dashboard I tried made me feel richer than I was: it counted an invoice as revenue the second I hit send, and blended every currency into one fake number.
So I gave the app one rule: never lie about the money. Sent is not paid. Each currency stays itself. An empty month shows "no data", not a scary -100%.
Have you shipped something that looks weaker but is more honest, and did users reward it?
(Building out loud at getalisio.com/?utm_source=indiehackers&utm_me)