Regulatory approval gives a fintech permission to operate, but customers still need a compelling reason to leave the tools they already use. The next test is demand: a specific customer, facing a costly problem, choosing to switch.
At 8:12 on a Monday morning in Tunis, Youssef opened the regulator’s email with one hand and held a paper cup of coffee in the other. The approval was there. Months of document revisions, technical checks and careful replies had reached the answer his small team wanted.
He called his co-founder. They spoke about launch day.
By lunchtime, a harder question had replaced the celebration: who would actually move money through the product?
Youssef is an invented composite, but the decision is familiar. A founder can spend so long working toward permission that permission starts to feel like proof. It proves the company cleared an important gate. It says nothing about whether a shop owner, freelancer or small business will change a financial habit that already works well enough.
Approval removed one risk and exposed another
Before the email, Youssef could explain the delay in one sentence: the company could not launch yet.
After the email, every weak assumption became visible.
The team believed small exporters would use the product to receive payments and track what had arrived. Their interviews had produced encouraging reactions. People described slow reconciliation, unclear payment references and hours spent checking messages against invoices.
Encouragement had felt close to demand. It was not close enough.
When Youssef returned to three interviewees with a live onboarding path, one asked to see the fees before continuing. Another said her accountant already had a spreadsheet and did not want to change it. The third offered the response founders hear when the problem sounds real but the product does not feel urgent: “Send it to me. I’ll look later.”
The company now faced a specific bad ending. It could spend the next stretch of runway polishing onboarding, hiring support and preparing launch announcements, only to discover that customers preferred their current inconvenience to the effort of switching.
For a regulated fintech, that mistake carries extra weight. Compliance work, partner coordination and operational controls continue consuming attention even when transaction volume remains near zero.
A signed commitment changed the launch plan
Youssef paused the public launch.
Instead, the team chose one narrow customer situation: small exporters who received several payments and struggled to match each one to the right invoice. They stopped asking, “Would you use this?” The new conversation began with the last payment that had taken too long to identify.
That change made the interviews less flattering and more useful.
One founder in Sfax described forwarding screenshots between two people before updating her records. She understood the product’s promise, but switching still meant teaching her finance assistant a new process during a busy month. Her hesitation had little to do with the interface. The existing workaround was annoying, familiar and already paid for.
Youssef offered a limited pilot built around her next batch of payments. Before his team configured anything, he asked for three commitments: a named person responsible for the pilot, a date for the first transaction and agreement to pay if the process handled the job they had defined together.
She agreed to the owner and the date. She would not agree to payment.
That answer nearly ended the pilot. With runway tightening, a free test could become another polite experiment that produced feedback but no commercial evidence.
The turn came when Youssef narrowed the promise again. His team would help reconcile one defined payment flow, not replace the company’s wider finance process. The customer accepted a small paid pilot tied to that job.
This was the first useful launch signal. A customer had accepted the cost of changing because one problem was painful enough to justify it.
Switching requires a reason stronger than curiosity
Founders often compare their product with competitors on features. Customers compare it with everything required to change.
That includes learning a new process, moving sensitive information, explaining the decision internally and taking responsibility if the new tool fails. In fintech, trust adds another layer. Approval helps establish legitimacy, but it does not carry the whole decision.
The practical question is not whether customers like the idea. Ask what they will stop doing, who must approve that change and what event makes the switch worth doing now.
A paid pilot can answer those questions before a broad launch consumes the remaining runway. The point is not the amount collected. Payment forces both sides to define the job, the boundary and the consequence of failure. That is why a narrow commitment can be more informative than a long list of interested contacts, a pattern that also changed the roadmap in Kweku’s paid pilot.
Launch begins with one observable change
Youssef’s team did not celebrate by adding more features. They watched the first workflow closely.
The customer sent the payment information through the agreed process. Her finance assistant matched it to the correct invoice without returning to the screenshot trail they had used before. The product still had rough edges, and one successful pilot could not prove a market. It did prove something narrower and more valuable: a real customer would change a real behaviour for this result.
That became the next operating rule. No launch task could outrank evidence of switching. Marketing copy had to name the old process being replaced. Product work had to support the committed use case. New segments had to wait until the first one produced repeatable behaviour.
The regulator’s email remained important. It opened the door.
A few days later, the more consequential moment happened at a desk in Sfax, when a finance assistant completed the job without opening the old thread of screenshots.
Comments
No comments yet.