Senpai Collective

The problem

A talented African designer or engineer has no credible way to prove what they have actually done. A portfolio is a claim. A referral is a favour. Neither survives contact with a client who needs to know whether this person can be trusted with the work.

The same gap runs the other way. Programmes that train people are run on spreadsheets and WhatsApp groups, so when a funder asks what changed, somebody reconstructs an answer from memory.

What we did

We built the system our own community runs on, and made the record the by-product of doing the work rather than a report written afterwards.

Applications and vetting. Cohorts and pods. Projects with real teams. Tasks that carry the skill they exercise and the person who will review them. Peer review that produces a score, not just an approval. Every contribution lands in a record attached to the member who earned it.

What exists now

Live and in use. Members apply, are vetted, join a cohort, claim work from an open board, submit it, and have it reviewed by a named reviewer. Skills move from claimed to verified only on the strength of reviewed contributions from multiple raters.

What it produced

The founding cohort is in progress. Figures will be published from the platform’s own record rather than estimated.

What we learned

The record only works if reviewing is as easy as approving. Early on, marking a submission complete and rating it lived on two different screens, so work got approved and never scored — which meant it counted for nothing toward the member’s verification. Putting the two together is what made the record real.