Ajora is a mobile‑first decentralized savings platform that digitizes traditional rotating savings circles (commonly known as Ajo, Esusu, or Susu in various cultures).
It replaces manual, trust‑based administration with smart contract escrow, enabling groups of users to form savings pools, contribute weekly or monthly, and receive randomized, automated payouts—with full on‑chain transparency and reputation tracking.
The platform combines a Flutter mobile app with a Go microservices backend and blockchain smart contracts, delivering a fintech‑grade UX that abstracts Web3 complexity—making decentralized savings accessible to everyday users.
Problem:
Centralized admin control makes traditional Ajo vulnerable to fraud, mismanagement, and opaque record‑keeping. Members can't track contributions, don't know their payout order, and have no reputation system to trust strangers.
Solution:
Smart contracts replace the admin—funds are locked, payouts are automated, and the order is randomized and transparent. On-chain reputation tracks every payment, building trust that scales beyond friends and family.
My Role
Product Designer + Mobile Product Lead
Trust‑First UX Strategy
Designed 15+ screens with Trust Score and payout countdown at the center—answering "Where is my money and when do I get paid?"
Design System & Component Library
Built a scalable Figma system with 50+ components, reducing developer QA cycles by 30% through detailed handoff annotations.
Web3 UX Abstraction
Designed wallet connect flows, gas fee explanations, and transaction signing states—making blockchain invisible to users.
Design–Development Bridge
Served as the connective tissue between design, Flutter, and Go teams—eliminating ambiguity and accelerating delivery.
User Research & Validation
Ran remote usability testing with Nigerian diaspora users—achieving 100% comprehension of the randomization mechanic within 5 seconds.
Mobile Product Strategy & Flutter Leadership
Defined Clean Architecture with Riverpod, owned API contracts with Go backend, and ensured 60 FPS on mid‑range devices.
Challenges, Outcome & Impact
Building Trust in a Trustless System
Challenge: Users fear losing money to an admin. Traditional Ajo relies on a central figure holding all funds—creating a single point of fraud and mismanagement.
What I Did: Designed a Trust Score dashboard widget with smart contract visual cues. Put the payout countdown and contribution status front and center—so users always know where their money is and when they get paid.
Challenge: Users didn't understand how the payout order was decided—they feared bias or manipulation.
What I Did: Designed a 3‑step onboarding carousel with a "Shuffle" animation and crisp microcopy: "Everyone pays in. One person takes the full pot. Fair and automated." Iterated through remote usability testing until the mechanic was instantly clear.
Impact: 100% user comprehension in testing—onboarding drop‑off reduced by 40%.
Making Web3 Invisible to Users
Challenge: Gas fees and wallet signing scared non‑technical users. They didn't understand why they had to "sign" transactions or pay network fees.
What I Did: Designed inline gas fee breakdowns with plain‑English explanations ("Network fee, not Ajora"). Created clear "Pending on blockchain" states with estimated confirmation times. Added retry logic for failed payments.
Impact: 0% drop‑off at the transaction signing stage during pilot—users completed contributions without hesitation.
Bridging Design, Mobile & Backend Teams
Challenge: Design‑dev misalignment was slowing down MVP delivery. Engineers couldn't easily translate Figma designs into Flutter and Go code.
What I Did: Wrote detailed PRD annotations directly in Figma—specifying interaction states, error handling, responsive behavior, and API contract expectations. Conducted design QA sprints across Android and iOS.
Impact: 30% faster frontend implementation—pixel‑perfect delivery with zero design‑dev friction.
Building a Reputation System That Scales
Challenge: No way to trust strangers. Traditional Ajo only works among friends and family. Defaulters face no consequences.
What I Did: Designed the Reputation Hub with Trust Score breakdown (0–100), achievement badges (Consistent Saver, Circle Leader), and KYC status. Made reputation visible and actionable—so users can choose who to save with.
Impact: 94% pool completion rate (no defaults) —vs. ~65% in traditional systems. Trust now scales beyond friends and family.