About

I'm a Management Engineering sophomore who approaches every role like a consultant: understand the business, then fix what's slowing it down. I founded Klick n Code at 13 and built for 30+ international clients. Since then I've consulted for Ritual Matcha Co., where I turned 8+ scattered Google Sheets into one Shopify-connected portal behind a business with seven-figure monthly sales, cut purchase-order turnaround from a week to same-day, and now lead the move to Supabase and Cloudflare. At GoRocky, I built the financial model for a joint venture projecting seven-figure monthly EBITDA, which leadership approved to launch. Code is how I execute, but the work starts with understanding the business and the people it serves.

I don't take on a role just to run last year's playbook. Whether I'm a head or a core member, in recruitment and secretariat, operations, recruitment strategy, or OSR, I look at the system I inherited and ask how it should work instead. For Rose Sale, I replaced the legacy Google Forms with a full-stack store that served about 850 users, and built a delivery portal that raised delivery volume by 35%. For Celaball, I built a centralized table reservation system for 70+ attendees. As an OSR analyst, I write audit reports so the next team starts from a better system than I did.

As Project Manager of Celadon's Recruitment Week, the first run by project managers instead of the executive board, I recruited the core team through open applications for the first time; my primer and publicity materials drew more applicants than the organization's yearly projects. I led 44 people across 6 committees to 832 recruits, returning about 10x on project costs, and launched three firsts for the organization: a mobile-game tournament at 2x the expected turnout, CelaWrapped, a Spotify Wrapped-style recap of each member's week, and a mahjong leaderboard portal with 350+ users and 1,000+ games in 4 days. The marketing and creatives team I led was voted best design among all organizations in ADMU. For the JADE Business Summit and LEADS 2627, I rebuilt the registration, tracking, and backend systems behind events for 80+ and 100+ participants.

When I lead, a better system for the project is only half the goal. The other half is my team: everyone should leave knowing a tool or a way of working they didn't know before, so the improvement outlasts my term. I also consider every stakeholder a system touches, from the participants to the executive board (EBCB) to my own core team, and design so each of them has an easier time using it. The changes I push for tend to stick, and the feedback from the people using them has been consistently strong.