Client referrals used to require permission and coordination.
Then prospects started reviewing my GitHub activity instead. They examined commits, pull requests, and code reviews in public repositories to evaluate my skills before contacting me. 18 clients in the past 9 months mentioned checking my GitHub profile during discovery calls.
Public contributions provided verifiable evidence
Traditional referrals relied on someone vouching for my work. GitHub let prospects examine actual code quality, communication style in PR comments, and consistency of contributions. One prospect hired me after seeing 6 months of regular commits to an open-source project relevant to their tech stack.
I compared lead sources: 31 inquiries came from prospects who reviewed my GitHub activity, 19 came through direct client referrals. The GitHub leads asked fewer qualifying questions because they had already assessed my technical abilities independently.
Active contribution replaced referral requests
Instead of asking clients to refer me, I focused on contributing to 3 open-source projects my target clients commonly used. This made my work visible to anyone researching those tools, and maintainers occasionally tagged me in issues that became consulting opportunities.
My contribution graph became a referral mechanism that worked continuously without requiring client action. Prospects could verify my skills at any time, in detail, without scheduling reference calls or waiting for email responses.
Word-of-mouth transformed from people describing my capabilities to prospects directly observing my work quality and professional behavior in public technical communities.