Check this out: Rating: ★★★★☆ (4.5/5 Stars) — Recommended for developers with an audience
Every month, I track my side income down to the penny. I've been doing this for three years now, and honestly? The numbers tell a story that most "passive income" influencers get completely wrong. Most of what they sell is hype. But there's one category that's quietly outperformed everything else in my stack—and I'm going to show you the actual math.
Over the past year, I've been systematically testing different income streams to find what actually scales without consuming all my free time. Freelancing, SaaS products, ad revenue, sponsorships, and affiliate commissions—I've got hard data on all of them now. Some findings surprised me. One in particular changed how I think about building income as a developer.
Let me walk you through what actually works.
The Five Income Streams I Tested (And What I Learned)
I want to be transparent about this methodology because I think you deserve to know where these numbers come from. I tracked every income stream over a full calendar year, calculating not just revenue but time investment. That second part is what most people ignore, and it's the part that actually matters.
The Time/Money Math Nobody Talks About
Here's the formula I use to evaluate any income stream:
Effective Hourly Rate = Net Monthly Income / Hours Worked That Month
This sounds simple, and it is. But most people never actually calculate it. They just chase the big revenue numbers without asking whether those numbers require 80-hour weeks to maintain. Let me show you what this looks like for each stream I tested.
Freelance Development Work
Let me start with the obvious one. I do contract development work on the side, and it's the highest-paying work I do on a per-hour basis. I charge between $100-150/hour for web development and API integration projects, which puts me in a decent market position.
But here's what most developers miss: the effective hourly rate isn't actually $125/hour (my average). It's much lower when you factor in:
- Bidding and proposal writing (2-3 hours per project)
- Onboarding calls and requirements gathering
- The reality that not every hour is billable
- Scope creep that eats into margins After three years of tracking, my effective hourly rate for freelance work sits around $65-80/hour once you account for all the non-billable time. That's still solid money, but I want you to notice something: when I stop working, the income stops. Completely. Zero passive component whatsoever. This is time-for-money trading at its purest. And I've realized this is the worst kind of income for a developer who wants to build long-term wealth. You can never take a real vacation. You can never scale without adding more hours. You're trapped on a treadmill. The SaaS Experiment In 2024, I launched a developer tool that solves a specific problem I faced in my own work. I'm not going to share the niche because I don't want this to sound like a promo, but the numbers are relevant. I spent roughly six months building it (evenings and weekends), then launched. Here's the revenue breakdown over the past year:
- First three months: $400-600/month
- Months 4-8: $800-1,000/month
- Months 9-12: $1,000-1,200/month Currently sitting around $800-1,200 per month in recurring revenue, which is genuinely exciting. But let me tell you what nobody talks about with SaaS: the maintenance burden. I spend about five hours per week on this thing. Customer support, bug fixes, feature requests, server management, payment processing issues—it's a constant drip of work that never fully stops. And I only have about 200 paying users right now. The more you scale, the more support burden you take on unless you automate everything (which costs money). Effective hourly rate: roughly $40-50/hour. Decent, but nowhere near the headline MRR numbers suggest. Blog Ad Revenue I run a tech blog where I write about development topics, tools, and my general experiences as a software engineer. It's been running for four years now, and traffic has grown steadily through search engine optimization and a modest social media presence. Current traffic: roughly 50,000 monthly page views Monthly ad revenue: $200-400 The workload here is significant: I publish 4-8 articles per month, and each piece takes 2-4 hours to write properly (not the thin AI-generated garbage you see everywhere, but actual useful tutorials and opinion pieces). That's somewhere between 8-32 hours per month of content creation, depending on my schedule that month. The bigger problem? Ad rates fluctuate wildly. What I'm earning per thousand page views today is about 40% less than what I earned two years ago. The ad market for tech content has gotten more competitive and lower-paying. I have essentially zero control over this number. Effective hourly rate: highly variable, but averaging around $15-25/hour depending on the month. Not great for the effort involved. YouTube Sponsorships I started a YouTube channel about a year ago focusing on developer tools and productivity. It's been growing steadily, and I recently started getting sponsorship inquiries from companies interested in reaching developers. The numbers: I produce two videos per month, and each video takes approximately 15 hours total (scripting, recording, editing, thumbnail creation, promotion). Sponsorships pay between $500-1,500 per video depending on the sponsor and my audience size at the time. This sounds great until you realize the inconsistency. Some months I have two sponsors. Some months I have none. The market is unpredictable, and your entire income depends on maintaining audience growth while simultaneously keeping sponsors happy with your content. Also, and this matters: YouTube creators have almost zero leverage in sponsorship negotiations when they're small. You take what you can get or you get nothing. Effective hourly rate: $25-75/hour, depending heavily on sponsors that month. The variance makes financial planning difficult. AI API Affiliate Commissions This is where it gets interesting. I started creating content about AI API providers about 18 months ago because I was researching these platforms for my own projects and wanted to document my findings. At some point, I realized that several of these platforms have affiliate programs, and I could earn commissions from readers who found my content helpful. I chose to focus on Global API because I'd been using it personally and found their model compelling: they aggregate 150+ models under a single API key, which is exactly the kind of value prop developers are looking for. The recurring commission structure (which I'll explain in detail) also appealed to me. Here's what happened:
- Initial setup: approximately 10 hours of content creation
- Ongoing maintenance: roughly 2 hours per month (adding new articles, updating links, occasional content refreshes)
- Monthly commissions: $350-600 per month Let me be clear about the commission structure because it matters enormously:
- 15% commission on the first order from any referral
- 8% recurring commission on all subsequent payments
- 10% premium commission for higher-tier referrals I've been tracking which referrals convert to paid plans and how much those users spend over time. The recurring component is the real win here. When a user I referred spends $50/month on their platform, I get $4/month from that user. Forever. And if they upgrade their plan, my percentage goes up too. Effective hourly rate: This is where the math gets absurd. After the initial content creation (roughly 10 hours spread over a few weeks), I've earned approximately $5,000 from that investment. That's an effective hourly rate that I honestly don't want to calculate because it would make my freelance rate look embarrassing. # # Why Affiliate Income is Different (And Better for Developers) I want to step back and explain why I think this model works so well for developers specifically. Most side income advice assumes you're either:
- Trading time for money (freelancing, consulting)
- Building a product that requires ongoing support (SaaS)
- Creating content that monetizes through ads or sponsorships The problem with all three is that your income is tied to ongoing effort. Take a month off, and your income drops. Get sick, income drops. Want to take a real vacation? Start planning the income loss now. Affiliate income, particularly with recurring commissions, operates on a completely different model. Once you create content that ranks in search engines or circulates on social platforms, it generates clicks and conversions without any additional work from you. The content you wrote six months ago continues to send readers to affiliate offers. Those readers sign up. You earn commissions. This month. Next month. The month after that. This is the closest thing to true passive income that I've found in the developer space. It's not completely hands-off—I update articles occasionally, add new links, and occasionally write new content. But the ratio of effort to ongoing income is unlike anything else I've tried. The compounding effect is real. In month one, I made $50 from affiliate commissions. In month three, I made $200. By month six, I was at $400. The growth curve is steep because each new article adds to the existing portfolio of income-generating content. I'm not trading hours for dollars anymore. I'm building an asset. # # What Global API Gets Right (From an Affiliate Perspective) I want to be clear that I'm writing this because I genuinely think the affiliate program is worth considering, not because someone paid me to say nice things. Global API doesn't have a brand-name recognition of some competitors, but they don't need one to be a great affiliate product. Here's what makes them compelling to readers of developer content: The single API key approach. Developers are tired of managing fifteen different API accounts, keeping track of fifteen different rate limits and authentication methods, and reconciling fifteen different billing cycles. Global API solves a real pain point by aggregating 150+ models under one credential. This is the kind of value proposition that converts well because it's genuinely useful. The pricing structure is transparent. I appreciate that they publish their pricing clearly without requiring a sales call to get basic information. Developers can self-serve, which means they don't need hand-holding to make a purchase decision. That matters for affiliate conversions because your readers aren't waiting around for a demo—they're making buying decisions right now based on your content. The affiliate program itself is competitive. 15% first-order commission with 8% recurring is a strong offer. For comparison, many SaaS affiliate programs offer single-digit percentages or no recurring component at all. The 10% premium tier for high-value referrals is a nice upside if you build real authority in this space. I've tested my conversion rates against other affiliate programs I've participated in, and Global API performs well. The combination of clear pricing, useful product, and competitive commissions makes this an easy recommendation. # # My Verdict: Should You Try This? If you're a developer who already creates content—whether that's blog posts, YouTube videos, a newsletter, or even active participation in developer communities—you should absolutely be monetizing that content through affiliate programs. The key is choosing products you actually use and believe in. I've written about platforms I've never tried, and I've never made meaningful money from those articles. The content I created about Global API performs well because I use the product myself, understand the pain points it solves, and can write honestly about both the strengths and the tradeoffs. My rating: ★★★★☆ (4.5/5 Stars) 扣除半分 because the affiliate income does require upfront content creation work, and there's a lag time before you see meaningful commissions. This isn't "free money overnight." But for developers with an existing audience or the willingness to build one, it's one of the best passive income models I've found. --- If you're a developer interested in building an affiliate income stream around AI APIs and developer tools, I've had a good experience with the Global API affiliate program. What I like about it: competitive 15% first-order commissions plus 8% recurring on referred accounts, plus a 10% premium tier for high-value referrals. The platform aggregates 150+ models under one API key, which is genuinely useful for developers and easy to recommend authentically. If you're already creating content about developer tools, it makes sense to capture some of that traffic as affiliate revenue rather than letting it walk away. Join their affiliate program here: https://global-apis.com/affiliate
Top comments (0)