Inspiration
Our inspiration comes from the traditional Ajo (rotating savings) systems used by millions of people across West Africa and the diaspora to build communal wealth without traditional banks. While these systems are built on incredible social trust, they are often hindered by manual record-keeping and a lack of direct utility for the payouts. We wanted to build a bridge between this cultural financial pillar and the modern digital economy.
What it does
Captain’s Pot is a digitized Rotating Savings and Credit Association (ROSCA) platform that adds a critical layer: a direct-to-payout marketplace. Users join a "Pot," contribute fixed amounts on a schedule, and when it is their turn to receive the payout, they can instantly deploy those funds into an integrated market for business inventory, tuition, or essential goods—all within one secure ecosystem.
How we built it
We prioritized a mobile-first, high-performance architecture to ensure accessibility:Frontend: Developed using React and Tailwind CSS on the Lovable platform to achieve a clean, intuitive "Fintech-grade" UI.Backend: Leveraged Supabase for real-time data syncing, user authentication, and secure transaction logging.Mathematical Logic: We implemented a payout rotation algorithm to manage cycles. The distribution follows the standard ROSCA model: P = \sum_{i=1}^{n} c_i where P is the total pot, $n$ is the number of participants, and c_i is each individual contribution.
Challenges we ran into
The biggest technical hurdle was managing concurrency and state. In a rotating pot, the sequence of "who is next" must be immutable and transparent. We had to architect the database schema specifically to prevent "double-payouts" and ensure that the transition from a "Savings" state to a "Market" state was seamless for the user. We also wrestled with designing a UI that felt "communal" rather than just "transactional."
Accomplishments that we're proud of
We are incredibly proud of the Marketplace Integration. Most savings apps stop at the payout; we built a functional flow where the payout is immediately actionable. We also successfully implemented a "Captain's Dashboard" that allows group leaders to monitor contributions in real-time, significantly reducing the "social friction" of manual chasing.
What we learned
Building a fintech tool taught us that trust is the most important feature. We learned how to translate social contracts into code and discovered that the "Ajo" model actually scales beautifully when you remove the overhead of physical bookkeeping. We also leveled up our skills in real-time database management and component-based UI design.
What's next for Captain’s Pot
We want to take Captain’s Pot from a prototype to a production-ready tool by: Vendor API: Opening up the "Market" section so local vendors can list products directly for Ajo groups to purchase.
Built With
- lovable
- react
- supabase
Log in or sign up for Devpost to join the conversation.