Lönar
Chasing clients and tracking payments is a mess. Lönar keeps it all in one place. Manage clients, automate invoices and always know who owes you.
Intro
Most invoice tools make you choose between simplicity and control. The simple ones do not track anything. The powerful ones bury you in onboarding before you can send a single invoice.
I wanted to open a platform, create an invoice, send it, and track the payment. All in one place, with no setup friction. That was the whole idea.
My role
Co-founder and product lead.
- Product strategy and UX direction
- User research synthesis
- Information architecture
- Design system
- High-fidelity UI design
- Interactive prototyping
- Design-engineering collaboration
- Social presence and brand design
- Light frontend engineering
Solution
You land on the platform and the invoice generator is the first thing you see. Client details can be saved so you are not re-entering the same information every time.


From there, the invoice goes directly to the client by email.

That is where creation ends. Then there is the dashboard.

Total earnings, broken down across all time and the last 30, 60, and 90 days. Number of clients, number of invoices. It gives the platform a memory beyond just the last thing you sent.
Invoices are also grouped by client, so you can see everything attached to one person at once. During research, someone running a clothing business told me he needed to know how much each client had spent in total. That became a core part of how the client view works.


Most of the features came from conversations exactly like that.




Payment tracking works by status. Full payments are not on the platform yet, so for now the flow relies on the client confirming via email. The system sends automatic reminders to clients when due dates pass. It is a lightweight version of something we plan to own fully.
Process
Questionnaires came first. The responses confirmed what I suspected: people were stitching together multiple tools to do something that should take one.
From that I built a user flow, pressure-tested it with potential users, and made corrections before touching the UI. A few assumptions did not survive that round.
The invoice generator shipped before the full platform. That meant by the time I was deep in high-fidelity design, there were already real users sending feedback. Revision requests came directly from them, not from internal assumptions.

The final phase covered APIs, the pro plan, account management, and download and export. Getting the details right after the structure was already proven.
Lessons
Shipping the generator before the full platform was the right call. It meant real feedback arrived early, when the cost of changing things was still low.
It also pushed me further into the engineering side. Owning a product end to end means the line between design and implementation gets blurry fast. I stopped treating that as a problem.