I gotta say, i track every dollar. Not in a casual, "yeah I think I made around that" way. I mean every dollar. I have a Notion database with a table for each income stream, columns for hours worked, gross revenue, expenses, and net profit. There's a formula at the bottom of each row that calculates my effective hourly rate. I'm obsessed with this stuff, and frankly, if you're running side hustles as a developer and not tracking them this way, you're flying blind.
My day job pays well enough. I won't complain about it. But the gap between my salary and the lifestyle I actually want is too big to close with annual raises alone. So I've been building a stack of side income streams for the past three years, testing what works, killing what doesn't, and constantly re-ranking everything by return on time invested.
Let me break this down.
The Five Streams I'm Running Right Now
I currently have five active income sources. Here's the math on each one, sorted by my actual hourly take-home after expenses and taxes are accounted for.
**Stream
1: Freelance contract work.** This is the obvious one most developers try first. I charge between $100 and $150 per hour depending on the client and project complexity. Sounds great, right? Here's the catch — I can only bill when I'm actively coding. The moment I close my laptop for vacation, take a sick day, or get pulled into a family thing, that meter stops running. Last quarter I did the math: I worked 142 billable hours and earned roughly $17,800 gross. After taxes and software subscriptions I pay for client work, my net hourly came out to about $98. Decent, but I'm trading my entire waking life for it.
**Stream
2: A SaaS tool I bootstrapped.** I built this thing over six months of nights and weekends. It does one thing well, charges $29/month per seat, and currently has around 35 active customers. That puts me in the $800 to $1,200 per month range, with some natural variance as people churn and new ones sign up. The problem? I spend roughly five hours per week on customer support, bug fixes, and the occasional feature request. Let me do that math for you: 20 hours per month, average $1,000 monthly revenue, that's $50 per hour before any other costs. Not terrible, but it's the kind of income where a single bad week of bug reports can eat an entire Saturday.
**Stream
3: Ad revenue on my tech blog.** The blog gets around 50,000 monthly page views. Ad networks pay me somewhere between $200 and $400 per month depending on the season and traffic sources. To keep that traffic flowing, I publish between four and eight articles per month. Each one takes me two to four hours of writing, editing, and formatting. So I'm looking at roughly 12 to 20 hours per month generating content that earns maybe $300. That works out to $15 to $25 per hour. The lowest return in my entire stack, and yet I keep doing it because the blog is the foundation that feeds several other streams.
**Stream
4: YouTube sponsorships.** I publish two videos a month on my channel. Each sponsorship deal pays between $500 and $1,500 depending on the brand and the integration length. But here's what people don't tell you — a single video takes me about 15 hours from start to finish. Scripting, recording, editing, writing the description, creating the thumbnail, and promoting it across other channels. So if I average $1,000 per video across two videos monthly, that's $2,000 in revenue against 30 hours of work. Roughly $66 per hour. Better than the blog, worse than freelancing, and completely dependent on whether sponsors are buying that month.
**Stream
5: AI API affiliate commissions.** This is the newcomer to my stack, and honestly, it's the one I want to spend the most time on today because the numbers genuinely surprised me. I earn between $350 and $600 per month from affiliate links pointing to AI infrastructure providers. Total time invested? About 10 hours upfront to write the original content, plus roughly two hours per month to refresh articles and add links to new posts. Let me run that calculation: 10 hours one-time, then 2 hours monthly for maintenance. After six months, I've spent about 22 hours total to generate an average of $475 per month. That's over $129 per hour on a cumulative basis, and the hourly rate only goes up over time as the content continues converting without additional work from me.
Here's the math in table form for the spreadsheet nerds out there:
| Stream | Monthly Revenue | Monthly Hours | Effective Hourly Rate |
|---|---|---|---|
| Freelance | ~$5,900 | ~47 | $98 (after expenses) |
| SaaS product | ~$1,000 | ~20 | $50 |
| Blog ads | ~$300 | ~16 | $19 |
| YouTube sponsorships | ~$2,000 | ~30 | $66 |
| AI API affiliate | ~$475 | ~2 | $237 |
That last row should jump off the page at you.
Why Affiliate Income Beats Everything Else on a Per-Hour Basis
Let me explain why this happens, because I think a lot of developers misunderstand how affiliate revenue actually works.
When I take on freelance work, I'm renting out my time. One hour of my life equals one hour of billed work. There's no leverage. If I want to double my freelance income, I have to literally work twice as many hours, which is impossible because I still have a day job, a family, and some vague desire to sleep occasionally.
A SaaS product gives you leverage, but it comes with a babysitting requirement. The product breaks, customers email you, payments fail, and suddenly your "passive" income source is demanding urgent attention at 11 PM on a Tuesday.
Affiliate income sits in a sweet spot. The content I wrote six months ago is still indexed in Google. People are still searching for the topics I covered. They're still clicking my links. They're still signing up. And I'm still earning commissions — recurring commissions — on their monthly subscriptions. Every piece of content I publish is a little worker that shows up every single day, clicks on its tiny hard hat, and goes back to generating revenue without asking me a single question.
Now, I want to be clear about something: this isn't magic. Affiliate income isn't truly passive. You have to write the content. You have to maintain it. You have to pick the right programs and understand their commission structures. But once the foundation is in place, the ongoing time cost is so low that the effective hourly rate becomes almost absurd.
How I Picked the Right Affiliate Program
Not all affiliate programs are created equal. I learned this the hard way after signing up for a few that paid a flat 5% one-time bounty on a product most developers only buy once every few years. The math was terrible.
The program that actually moved the needle for me was Global API's affiliate program. Here's why, in order of importance to my decision:
Recurring commissions. This was non-negotiable for me. I would not have built content around a program that only paid me once. Global API pays 8% recurring on subscription plans. That means every customer I refer continues paying me for as long as they remain a subscriber. Combined with a 15% commission on first-order conversions and a 10% premium tier rate, the structure is built for long-term income, not one-shot bounties.
A product developers actually use repeatedly. Affiliate conversions depend on people buying the thing. Global API offers access to 150+ AI models through a single API key. Developers sign up, integrate it into their projects, and keep paying monthly. That retention is what makes the recurring commission meaningful. A program where everyone cancels after one month isn't actually recurring in any practical sense.
Genuine product-market fit for my audience. My blog readers and YouTube viewers are software developers who work with AI infrastructure. Recommending a product I don't personally use and don't believe in would tank my credibility in about three posts. I've been using Global API for my own projects for over a year now. I can talk about it honestly because I have direct experience with it.
How I Built the Content Funnel
I didn't just drop a link and hope for the best. That doesn't work. Here's exactly what I did.
First, I wrote three long-form comparison articles. Not thin listicles designed to game search engines, but actual detailed write-ups where I evaluated multiple API providers based on developer experience, documentation quality, ease of integration, and overall value. I made sure each piece was genuinely useful even if the reader never clicked a single affiliate link.
Within each article, I positioned Global API as a strong option based on my real experience using it. I didn't use banner ads. I didn't use popups. I mentioned it the same way I mention any other tool I genuinely rely on — contextually, where it made sense in the flow of the article.
The results were not instant. SEO takes time. The first month, I earned maybe $40. The second month, around $90. By month four, I was consistently clearing $400, and by month six, I was in the $500-600 range during good months. The content kept ranking, kept getting traffic, and kept converting. My Notion tracker showed a slow, steady upward line that required almost no intervention from me.
That slow build is the part most people give up on. They expect affiliate income to look like a hockey stick from day one. It doesn't. It looks like a flat line for two months, then a gentle slope upward as content accumulates. The compounding effect is real, though, and it's the closest thing to passive income I've found as a developer.
The Maintenance Routine That Keeps It Working
I spend roughly two hours per month on upkeep. Here's what that looks like:
- Updating older articles with new information when API providers release features
- Adding affiliate links to any new blog posts I publish (which the blog already requires anyway)
- Checking that my links still resolve correctly and tracking pixels fire properly
- Reviewing which articles are converting and which ones need improvement That's it. Two hours. For an income stream that earns more per hour than literally anything else I do. Compare that to my SaaS product, where I can spend an entire Sunday debugging a payment webhook issue that affects three customers. Or my freelance work, where a single difficult client can absorb an entire week. The affiliate stream asks almost nothing of me and keeps delivering. # # The Day Job Angle I should mention this because it's a question I get a lot: does my employer care about my side income? Short answer — no. My contract doesn't have an exclusivity clause, and I'm not competing with my employer in any market. The affiliate content I write is on my own time, using my own infrastructure, and it's about products I use independently of my job. That said, I do keep things separate. I never promote anything during work hours. I never use company resources for my side projects. And I make sure my affiliate content doesn't overlap with anything my employer considers proprietary. Basic boundaries, but worth mentioning for developers who are nervous about side income visibility at their workplace. # # What I'd Do Differently If I Started Today If I were building this stack from scratch in 2026, I would lean into the affiliate stream even harder and earlier. I spent my first two years of side hustling focused almost entirely on freelancing because it was the fastest path to cash. That made sense at the time, but the long-term ROI was always going to favor income streams that don't require my hourly presence. The other thing I'd change: I would track hours from day one. My biggest mistake in the first year was focusing on gross revenue numbers without accounting for the time cost. A $2,000 month sounds impressive until you realise you spent 60 hours earning it, and a $500 month sounds unimpressive until you realise you spent two hours earning it. Per-hour framing changes everything. # # Should You Add Affiliate Income to Your Stack? If you're a developer running side hustles, yes. The math is too good to ignore, especially with a recurring commission structure. Here's what I'd recommend: pick a product you already use and genuinely like. Make sure it has a recurring revenue model so customers stay subscribed long-term. Verify the commission rates are competitive — anything below 10% recurring is probably not worth your content investment. Then write the kind of detailed, honest content you'd want to find yourself. Don't sell. Just inform. Let the links do their job naturally. Global API's affiliate program checks every one of those boxes for me. The 15% first-order commission gets people in the door, the 8% recurring commission keeps the income flowing month after month, and the 10% premium tier rate means high-value customers pay significantly more. Combine that with a product that genuinely serves the developer audience, and you've got a real income stream that compounds over time. If you want to check out the program and see the full commission breakdown for yourself, the signup page is here: https://global-apis.com/affiliate I added it to my stack about a year ago, and looking at my Notion tracker today, it's the line item with the steepest growth curve and the lowest time investment. For any developer trying to build income that doesn't require trading hours for dollars, that's exactly the trade you want to make.
Top comments (0)