I design the point where a user has to trust a financial product enough to commit: the first sponsorship, the exchange rate before payout, the permissions over shared money, the state after a bank delay.
Four products, in the order a financial-product team would ask about them. Each links to the case study that carries the detail.
A transfer crosses a crypto asset, a changing rate, a Naira payout and a bank’s settlement state. I designed the journey so the rate, fee, recipient amount, payout state and recovery path remain legible from quote through settlement, including slow-bank states that need a different message from a failed transfer.
$2.1M+ processed · 19K+ transactions · 5,400+ users · 80+ business accounts
Read the Mular case study →Nigeria’s first digital agriculture crowdfunding platform asked urban Nigerians to commit money to farms they might never visit. First-time commitment is the hardest moment in any financial product: the user has no history with you and every reason to be careful. I rebuilt the mobile journey around the questions people needed answered before committing — which farm, what return, over what cycle, and what happens to the money in between.
18% → 60% first-time sponsorship conversion
Read the Farmcrowdy case study →A parent, a child, a school and a merchant each needed different authority over the same balance. That is a permissions problem before it is a payments problem: who may spend, who must approve, who can only request, and who is allowed to reverse something the others thought was finished. I reframed the product from child savings into a four-sided permissions model and designed the delegated-authority flows across it.
3,416 active users · 10 schools / merchants
Read the Earlybean case study →Regulatory dashboards, data visualisation and a cryptocurrency-monitoring concept for CBN- and SEC-facing contexts. Regulators reading crypto activity face a reading problem before an enforcement problem, and the three people looking at the same risk data want different things from it. Rather than one dashboard for everyone, the interface separated executive oversight, analyst review and investigation over the same underlying records.
Read the regulatory dashboards & crypto monitoring case study →The recurring problem is making money state, authority and failure legible before the user has reason to trust the system.
If you are building payments, money movement or financial products where trust depends on state, I would like to compare notes. Email is fastest.