One of the hardest parts of building CallCatch wasn't technical - It was realizing the product I really wanted to create had a constraint I couldn't just design away.
CallCatch automatically texts someone when you miss their call.
The obvious version would just send that text from your existing phone number.
Except iOS won't let an app quietly watch your personal number for missed calls and fire off an SMS in the background.
So I had to make the product work differently.
Instead, I built it around provisioning a dedicated business number that forwards calls to the user's existing phone. If they answer, great. If they don't, CallCatch knows about the missed call and can immediately text the lead.
The decision changed everything - onboarding, messaging, UX, infrastructure, and even how I needed to position the product in the App Store.
A minor hiccup.
But... that's one of the things I've really started to love about product design and implementation.
The job isn't always figuring out how to build the feature that I imagined... it's often just figuring out how to accomplish the same outcome within constraints that may arise.
But I knew with CallCatch, that outcome was always going to be the same - helping small business owners know that even if they miss a call, they won't miss a job.
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.