The hardest decision on Haia wasn’t which model to use. It was what happens when a plan breaks halfway. Our rule is that the agent stops and asks, and never fixes things on its own. Happy to share how we built the approval flow if you’re working on something similar.
Happy to share a little piece of what I've been working on lately: Nexus.
Nexus is a concept for a network that moves money and data as fast as the internet moves information. Payments, tokenized assets, AI agents that pay for things on their own, apps that need privacy by default.
The full website is coming soon.
Business banking is already complex. The product shouldn’t make it feel even harder.
That was the thinking behind Bankora.
Payments, invoices, cash flow, financial overview. These are things business teams deal with constantly, yet many banking products still bury simple actions under dense data, long paths, and complicated navigation.
So I started with the workflows, not the screens.
I looked at the tasks people need to complete most often, where unnecessary steps appear, and what information actually needs attention first.
From there, I built the experience around clearer priorities: key actions available quickly, predictable navigation, structured financial data, and modular UI that makes things like pending and overdue invoices easier to understand at a glance.
I also designed an interactive cash flow calculator to help users see where the business may be heading, not just what has already happened.
The goal wasn’t to make financial operations simpler than they really are.
It was to make interacting with them feel simpler.
Less searching. Less cognitive load. More confidence in what to do next.
And it was especially nice to see Bankora later featured by Contra.