SUSU

The Problem

Trust built on paper, rotations tracked in memory.

Rotational savings groups (ajo, esusu, susu) depend entirely on trust and manual tracking - usually managed via WhatsApp messages, handwritten notebooks, and personal relationships. The challenge was designing one consistent, trustworthy experience across three fundamentally different mediums: a website, a conversational WhatsApp bot, and a native mobile app. And to do it starting only from raw feature documentation, with no existing userflow to build on.

Signature Visual

One action. Three surfaces.

Website

WhatsApp Bot

Mobile App

Building trust into the system.

Trust isn't a feature you add at the end - it's an outcome of good information architecture. A layered combination of a rotation tracker, due-date reminders, and a group activity feed gives every participant visibility into the group's state in real time. When everyone can see what's happening, the system polices itself.

The payout tracker and group activity feed - primary trust surfaces in the design.

Outcome

In progress

SUSU is currently in active build - designed solo, end-to-end, from documentation to high-fidelity screens across three channels. Designing one coherent system for web, conversational, and native contexts simultaneously forced sharp decisions about what stays consistent (language, trust signals, data hierarchy) versus what adapts to each medium (interaction patterns, layout, information density).