Performed Internal Financial Controls (IFC) engagements covering process walkthroughs, Risk Control Matrices (RCMs), control design evaluation and operating effectiveness testing. Assisted organizations in strengthening compliance, improving control environments and implementing practical control enhancements aligned with business objectives.
Your SaaS product might be solving the wrong problem. And most designers don't realize it.
Before jumping into Figma, designing dashboards, or creating beautiful interfaces, there's something much more important to understand.
The difference between a Business Problem and a User Problem.
In Part 01 of my SaaS Product Design Masterclass, I'm breaking down:
🔹 1.1 — Start with the Business Problem
🔹 1.2 — Understand the Business Impact
🔹 1.3 — Identify the User Problem
🔹 1.4 — How Business Problems and User Problems are connected, but different.
Here's an important thought:
A business wants to achieve a goal.
A user wants to solve a problem.
Great digital products understand both.
This is where meaningful product differentiation begins — not with UI, but with problem understanding.
🎯 This is Part 01 of my 10-hour practical SaaS Product Design series, where I'll walk through the complete process of understanding and designing a SaaS product.
If you're a UX/UI Designer, Product Designer, aspiring designer, or SaaS founder, this series is for you.
One question: Do you start your design process with business problems or user problems?
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.
Before having a practical experience, I was always curious about how bank reconciliations were completed for real companies . Because my bookkish knowledge was to compare the bank statement with cashbook and adjust differences.
I often heard seniors discussing that we are doing bank reconciliation, but I always had that thought in my mind that how difficult it could be doing adjustments for the real company's financials and then reconcile bank.
When I finally started handling the full cycle accounts and bank reconciliation was a major task, then I started experiencing the real challenges involved in it.
Theory explains you the process, but the practical knowledge teaches you how to solve the real challenges.
We can't understand the theoretical concepts fully until we have applied in actual scenarios.
what is the one concept you understood better from practical experience?