Launching Jordan's First Neobank: Lessons From a 0-to-1 Digital Bank

5 MINS

As Product Owner for Reflect, Jordan's first neobank, I got a rare thing in fintech: a genuine blank page. No legacy app to migrate, no existing users to keep happy, just the question of what a digital bank should feel like for people who'd never had one. Building 0-to-1 in banking is exhilarating and terrifying in equal measure, because every default you choose becomes the standard users judge you by.

Being "first" is a trust problem before it's a product problem

When you're the first neobank in a market, you're not just launching an app, you're asking people to do something they've never done: trust their money to a bank with no branches. That doubt sits underneath every screen. No feature matters if the user doesn't believe their money is safe.

So a lot of the early work wasn't features at all. It was the signals: clear language, visible security, predictable confirmations, and an onboarding that felt official without feeling bureaucratic. In a first-mover banking product, credibility *is* the feature set.

0-to-1 means choosing what not to build

A blank page is dangerous because everything feels possible and important. The discipline of 0-to-1 is deciding what the first version genuinely needs to prove, and ruthlessly cutting everything else.

For a neobank, the thing to prove is simple: a user can open an account and start using it without friction or fear. So the early roadmap centred on onboarding and the core money journeys, and explicitly deferred the long tail of features that would have been fun but wouldn't have answered the only question that mattered, will people actually trust and use this?

Requirements are where ambition meets reality

Coming from business analysis, I learned to write requirements that survive contact with engineering, compliance, and operations all at once. In a neobank that's everything, because a single onboarding flow touches regulatory rules, core banking systems, and the user's first impression simultaneously.

The trick is to make every requirement unambiguous *and* honest about its constraints. A spec that ignores the regulatory limit or the system's real behaviour isn't a spec, it's a wish. Writing them down until they're genuinely buildable is unglamorous work, but it's what keeps a 0-to-1 launch from collapsing under its own ambition.

What launching first taught me

Move deliberately on the things that build trust, and ruthlessly on the things that don't. Prove the core before you decorate it. And remember that in a brand-new banking product, your first users are doing you a favour by trusting you at all, so the least you can do is never surprise them.

Building Reflect taught me that 0-to-1 isn't about doing more. It's about doing the few right things so well that people are willing to be first with you.

From Business Analysis to Product: Why Writing It Down Is a Superpower

Shipping Fintech in Regulated Markets: What Jordan, Saudi, and the UAE Taught Me

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.