The five minutes that decided whether a bank was real
Openbank had already won in Spain, Germany and Argentina. Launching in all fifty states meant deposits, fast, against the best fintech ever built.
Somewhere in Ohio, a woman with twenty minutes to herself opens an app she downloaded that morning. She has heard of Santander, vaguely. She has not heard of Openbank. In front of her is a form, and behind the form is a decision she has not consciously made yet: whether to move real money, five hundred dollars or a thousand, to a bank that until today did not exist for her.
Everything my team spent a year on happened inside her next five minutes.
The brief we were given did not describe her at all. It described a business need: deposits, fast, nationwide, compliant on day one, to fund a lending pipeline that was already counting on the money. Openbank had launched before, in Spain, Germany and Argentina, and won. America was different in one specific way. Every customer here had already seen every fintech pitch, and most were carrying a perfectly good money app in their pocket.
Deposits do not arrive in bulk. They arrive one person at a time, each of them alone with a phone, deciding. That reframed the question we were actually answering. Not how to sell the bank. Which product had to exist before a single transfer could happen at all.
Three forces, and nothing that satisfied all three
The year was governed by three pressures that did not agree. The business needed velocity, because deposits fund lending and there was no second attempt. Customers needed the standard set by the apps already on their phones: instant onboarding, instant confirmation, anything slower reading as legacy. Compliance needed fifty states and zero mistakes: KYC (know your customer), AML (anti-money-laundering) and fraud prevention that could not fail publicly.
Every decision that follows is a trade between those three. It helps to see them pulling.
Deposits fund lending. No time for iteration, polish, or a second attempt.
I signed up for Cash App. Then SoFi. Then Chime.
Each time with the same question in mind: when did I decide this bank was real? We mapped the journeys, audited the onboarding flows, and put that question to everyone we interviewed, both people who had recently switched banks and people who had given up on banks altogether.
The answers barely varied. It was not the sign-up page, and it was not the card arriving in the mail. It was the first time money moved and landed. Before that, a bank is a set of promises on a screen. After it, the relationship exists.
Using the competition rather than reading about it is what made the difference visible. On a feature chart these apps sit in roughly the same place. In the flows they do not. Where a first transfer confirmed quickly, the whole product changed character. Where the confirmation was slow or vague, nothing further down the app recovered it.
The funding moment is the product. Everything before it is theatre, and everything after it depends on that one transfer having worked.
Which left an uncomfortable conclusion in the room. The roadmap described a full-service bank: checking, debit, bill pay, transfers, savings, investing, budgeting, rewards, credit. Nine products, one year, and eight of them nobody would reach until the ninth worked.
Nine sponsors, one launch date
Nine products also meant nine people accountable for shipping one, and none had volunteered to go last.
So the argument was not about value. It was about sequence. Bill pay, cards, transfers and investing each assume an account with money in it. Savings, funded in minutes, is what creates one. Going first was not a preference; it was the condition the other eight needed in order to exist at all.
The cut had a real price, and it is worth saying plainly. A one-product bank compares badly against a full-service app and gives a customer fewer reasons to stay past the first month. We took that exposure knowingly, because the alternative was nine unfinished products arriving late in a market that decides in five minutes.
What the five minutes had to contain
Calling the funding moment the product is only useful if you can say where it ends. Ours ran from opening the app to money confirmed in the account: identity established, an outside account linked and verified, a transfer sent, and a confirmation the customer could believe. Under five minutes, on a phone, on the first attempt.
That line did the rest of the year's prioritisation for us. Inside it, work was launch-blocking and got everyone's attention. Outside it, work was deferred.
It also settled what "done" meant. A step that worked most of the time was not done, because nobody making a first transfer to an unfamiliar bank tries twice. Three decisions came out of that standard, and each one is a trade that shows up on the woman in Ohio's screen.
Instant verification, not three-day micro-deposits
Micro-deposits were the conventional choice and the easier one to defend in a fraud review. They also put three days between her decision and its confirmation. In a market where instant is the baseline, that gap is where accounts are abandoned, so verification had to finish inside the session, and the risk of finishing it there had to be carried elsewhere.
A visible compliance wait
Identity and anti-money-laundering (AML) checks happen whether or not anyone designs around them. Undesigned, they read as an unexplained pause: the exact moment a new customer assumes something has broken and closes the app. We said what was happening, how long it would take, and what came next. The most regulated step in the flow became one of the most carefully written.
Failure states with words of their own
For the person standing at the funding moment, the edge case is the product. Timeouts, delayed settlement and fraud review were written as flows with their own copy and their own next step, rather than routed to a generic error screen, and they were reviewed as closely as the path where everything works.
Owning the moment meant owning its failures
Once the moment is the product, a payment failure is not an infrastructure incident. It is the product failing in front of someone deciding, right then, whether to trust a bank she had never heard of a week ago. Rail availability stopped being an engineering matter and became a product one.
So we specified the moment to survive itself: one promise to the customer and three ways of keeping it. A transfer leaves on ACH (Automated Clearing House, the bank-to-bank network). If ACH fails it reroutes to RTP (Real-Time Payments, the instant rail). If RTP is unavailable, a debit top-up through Plaid, the service that links an app to a customer's existing bank account, carries it. The customer never hits a wall.
Four cities, one sentence
Engineers in Madrid. Legal in Boston. Design in London. Product in New York. That arrangement usually loses its time to translation between teams rather than to the work itself.
What held it together was not process. It was a single shared test. Every region, every discipline, every review measured against the same sentence: the funding moment is the product. Work that could explain itself in those terms went ahead. Work that could not was deferred, without anyone arguing about whose function mattered more.
What the numbers said
Then the money started arriving, and it did not stop.
Taken together they say the same thing: the constraint was the strategy. Two billion is what the market paid for one product that worked. Fifty states on day one is compliance built in rather than bolted on. Five minutes is the line that made both possible.
Earn the moment, then earn the next one
That is how you build a bank from zero. Everything we deferred came later, because the foundation earned it.