Panache & CYES

Public voting, verification, and the organizer’s side of an event.

Full-stack developer · Panache Foundation client project

2026

Panache Foundation website introducing its event platforms — The foundation’s public website brings its event platforms together.

The problem

An event website is only the public-facing part of the job. Panache needed nominee pages, voting and payment verification, standings, and a way for organizers to understand activity while campaigns were running.

What I built

Built public event and nominee interfaces, voting flows, leaderboards, and organizer analytics.

Implemented paid-vote verification, receipts, reconciliation, and payment recovery for Panache event workflows.

Supported CYES verification through captcha, email OTP, and WhatsApp voting, with reporting that distinguishes vote sources.

Inside the product

Open an image to inspect the interface at full size.

CYES voting interface in its current closed state — The CYES voting screen after voting closed. Its verification flow is distinct from paid Panache voting.

CYES public leaderboard interface after voting closed — The public leaderboard after voting closed. Exact vote counts are not published here.

Keep the workflows distinct

Paid voting and CYES verification solve different problems. I kept payment verification and recovery separate from the captcha, OTP, and WhatsApp paths, while giving organizers visibility into the activity behind each flow.

Across the events

Aggregate figures across Panache events; not a single-event breakdown.

23k+ verified votes processed
16k+ votes handled through WhatsApp
19k+ unique voter phone numbers
6.8k+ peak votes in a single day

Built with

React, TypeScript, Supabase, Cloudflare, WhatsApp

Something similar?

Tell me about the workflow you want to build.

Discuss a project

Next case studyKoloKut