Shipping Fintech in Regulated Markets: What Jordan, Saudi, and the UAE Taught Me
Shipping Fintech in Regulated Markets: What Jordan, Saudi, and the UAE Taught Me
Building digital banking products across Jordan, Saudi Arabia, and the UAE, I learned quickly that "move fast and break things" is the wrong instinct in fintech. When money and regulation are involved, the thing you break is trust, and you rarely get it back. The work isn't slower because people are cautious; it's slower because the stakes are real.
Regulation is a design input, not an afterthought
Early on, it's tempting to design the experience you want and then bolt compliance on at the end. That never works. KYC, onboarding limits, and the rules a regulator expects shape the flow itself, what you can ask, when you can ask it, and what has to happen before a user can move money.
The teams that struggle treat compliance as a tax on the product. The teams that ship treat it as a constraint to design around, the same way you'd design around a slow network or a small screen. Once you internalise that, the requirements stop feeling like obstacles and start feeling like the shape of the problem.
Three markets, three different users
Jordan, Saudi, and the UAE look similar from a distance and feel very different up close. Regulatory expectations differ, payment rails differ, and what a user trusts differs. A flow that converts in one market can quietly stall in another because the assumptions baked into it don't hold.
Working across all three taught me to separate the *core* of a product from its *local edges*. The lending or onboarding logic underneath can be shared; the documents you collect, the language you use, and the trust signals you lean on have to be local. Pretending a single flow fits every market is how you end up with a product that's technically live everywhere and genuinely loved nowhere.
Conversion and activation are won in the boring details
In consumer fintech, the dramatic features rarely move the numbers. What moves conversion and activation is the unglamorous stuff: one fewer screen in onboarding, a clearer error message, a payment confirmation that arrives when the user expects it.
I've watched activation climb because we removed a field nobody needed, and watched it fall because one step felt slightly uncertain. The regulated context raises the bar even higher, a user who feels unsure about a money product doesn't retry, they leave. So I obsess over the moments where doubt creeps in, because that's where the funnel actually breaks.
What I carry into every fintech build
Start with the failure cases, late payments, rejected documents, reversed transactions, because in financial products they aren't edge cases, they're a real share of usage. Map the regulatory constraints before the happy path. And stay close enough to the data to know which step is quietly costing you users.
Get those right and the product feels calm and trustworthy, even in a regulated, high-stakes market. And in fintech, calm and trustworthy is what converts.
Layth skipped presentations and built real AI products.
Layth Ismail was part of the April 2026 cohort at Curious PM, alongside 18 other talented participants.