man gdsc
GDSC
Ran a builder community before I called it strategy.
Same muscles I use for brand work today — pick a thesis, gather the right people, make small bets in public, keep what compounds. Different name back then.
- 400+Active members
- 24Events shipped
- 18Workshops led
- 60+Builds in the wild
A campus chapter that needed to feel like a real community.
Most student tech clubs run on momentum from one or two passionate people, then evaporate. The chapter had the official badge and a Discord, but no rhythm, no signature events, and nothing to point at when someone asked what we did. The job: turn a logo into a community that compounded.
How I attacked it.
Weekly cadence
Saturday hack jams every week. Same time. Same place. The reliability did most of the work — people built routines around it.
Public artifacts
Every build, every workshop, every talk — captured, posted, credited. Visibility attracted the next wave of members.
Builders over attendees
Programming favored doing over watching. Workshops ended with a thing in hand, not just a slide deck.
Three that compounded.
Saturday Hack Jams
Weekly drop-in builds. Theme rotates, hardware optional, ship-before-you-leave culture. Became the chapter's signature.
24 sessions · 60+ projects shippedIndustry Nights
Brought in operators from local AI / cloud / open-source teams. Small rooms, real Q&A, no panels. Always packed.
9 sessions · 100% attendance rateDemo Day
Closed the year with members showing their builds to industry guests. Three of the projects turned into job offers.
3 conversions to industry rolesThis was strategy in a hoodie.
Programming a calendar = programming content
Same hypothesis-test-learn loop. Same compounding effect when you stay consistent. Different distribution channel.
Credit is free, share it
Every workshop name-dropped the people who built things that week. Cheapest way to make a community feel like home.