I've got a confession to make. My Notion dashboard — the one I use to track every dollar that doesn't come from my 9-to-5 — has six tabs, eleven conditional formulas, and a color-coded heat map of my income by source. Yeah, I'm that person. But if you're going to build a side hustle stack as a developer, you need to know exactly which streams are pulling weight and which ones are dead weight.
This year, I'm reshuffling everything. And one income stream is getting a much bigger slice of my attention. Here's the full breakdown, with actual numbers.
What My Spreadsheet Actually Shows
Let me cut straight to the data. Here's what hit my accounts over the last 90 days from each side hustle, ranked by what I'd call "effective hourly rate" — meaning total earnings divided by hours actually invested:
Freelance contracts: $11,400 across roughly 76 billable hours. That's about $150 per hour, which sounds great until you realize I spent another 20 hours on proposals, Slack threads, and scope creep that nobody pays for. Real hourly rate? Closer to $95.
SaaS micro-product: $1,050 last month, recurring. I built it over five months, and it now needs maybe 4-6 hours per week for bug fixes, feature requests, and the occasional support email from a confused user who can't figure out the onboarding flow. Effective rate: roughly $50 per hour. Not bad, but I'm basically a part-time janitor for this thing.
Tech blog ad revenue: $287 last month on about 48,000 pageviews. I publish five articles per month, each taking 3-4 hours including research, writing, editing, and SEO tweaking. Monthly time sink: ~18 hours. That's about $16 per hour. Yikes.
YouTube sponsorships: I did one sponsored integration last month — $900 for a single video. Production time was about 14 hours (scripting, shooting, editing, writing the description, replying to comments for a week). Per-hour rate: $64. Decent, but sponsors ghost you. One month you make $1,500, the next you're back to zero.
API affiliate commissions: $473 last month. Setup time was maybe 12 hours total spread across writing content. Ongoing maintenance is about 90 minutes per month — updating links, refreshing outdated info, checking that referral codes still work. That puts me at... let me do the math... roughly $315 per hour. Yes, you read that right.
I know what you're thinking. "That affiliate number can't be sustainable." And honestly? You're probably right. But here's the thing — even if it dropped by 70%, it would still outperform three out of my other four income streams on an hourly basis.
Why I Stopped Romanticizing "Passive Income"
For about two years, I chased the dream. Every developer Twitter thread about passive income had me installing another plugin, writing another "ultimate guide," launching another micro-SaaS. Most of it flopped.
Here's what I learned the hard way: not all recurring income is equal. A SaaS product that requires customer support, uptime monitoring, and dependency updates is recurring, sure. But it's recurring in the same way that a subscription to a gym you never visit is recurring — money goes out, stress goes up.
The income streams that have actually freed up my weekends share one trait: they produce revenue from work I've already finished. Affiliate links are the purest version of this. I wrote the content. People find it through search. They click. Some of them convert. I get paid. I don't have to deploy anything. I don't have to fix a bug at 11 PM because Stripe webhooks decided to take a nap.
That's the unlock. Not "passive income" as some mythical concept — but income where the marginal cost of producing one more dollar is essentially zero.
The Stack That Actually Works For Me
Here's my philosophy now. Every income stream has to clear two hurdles:
- It has to pay enough to justify the time, measured honestly (including all the invisible work).
- It has to keep paying when I'm on vacation for two weeks. Most side hustles fail hurdle #2. Freelancing fails it instantly. My SaaS product fails it if I ignore it for more than a week — users start churning, support tickets pile up, and the next month looks ugly. Affiliate income clears both. I took ten days off in December. Came back, checked my dashboard, and the number was higher than the month before. Not dramatically higher, but it didn't drop. That's the signal I look for. So what did I actually do to build this stream? Let me trace the exact steps. --- # # How I Picked The Right Affiliate Program I'm not going to sit here and pretend I joined twenty affiliate programs and "tested" them all. That's what every guru blog says. The reality is messier and more practical. I picked products I was already paying for. That's it. That was the filter. As a developer who works with AI APIs regularly (I build prototypes, integrate LLM features into client projects, mess around with side projects late at night), I already had accounts with maybe six different API providers. I knew which ones were good, which ones had terrible documentation, and which ones I kept going back to. One of them — Global API — caught my attention for a specific reason. I noticed they had an affiliate program. Let me be honest about why that matters: I wasn't going to start writing content about a product I didn't genuinely use. But the fact that they had a structured affiliate program with recurring commissions? That turned a "maybe" into a "yes." Their setup is straightforward enough that I could explain it without pulling up a marketing PDF:
- 15% commission on the first order any new user places through my link
- 8% recurring commission on every subsequent order that user makes (this is the part that matters most for long-term income)
- 10% premium tier for affiliates who refer a higher volume of customers
- Access to 150+ models through a single API key — which means I can recommend it as a one-stop shop rather than telling people to juggle five different provider accounts The recurring 8% is where the math gets interesting. It's the difference between getting paid once and getting paid for months. A developer who signs up through my link and spends $200/month on API calls generates $16/month for me, forever (or until they cancel). Stack up 30 of those and you're looking at $480/month from a handful of blog posts. --- # # The Content I Actually Wrote I didn't build a 40-page comparison guide. I didn't launch a podcast. I wrote three blog posts. That's it. The first was a technical breakdown of how I set up my dev environment to switch between API providers without rewriting integration code. It included real code snippets, real error messages, and a frank paragraph about which provider I ended up sticking with for production work. The second was a post about a specific problem I solved — building a content moderation pipeline using AI APIs. I walked through the architecture, the costs, and the trade-offs between different models. Natural fit for mentioning which API aggregator saved me from managing five separate accounts. The third was a more practical piece about reducing API costs as a solo developer. This one performed the best because it's the question every indie dev is typing into Google at 1 AM. In each post, I embedded my affiliate link where it made sense contextually — not as a popup, not as a banner, but as part of an actual recommendation in the body text. "Here's the provider I use. Here's my referral link if you want to try it." That's it. No fake scarcity, no countdown timers, no "ACT NOW BEFORE THIS DEAL EXPIRES" nonsense. Within the first month, those three articles had driven 14 signups. By month three, that number was up to 38. By month six? I stopped counting manually because my dashboard started doing it for me. --- # # Breaking Down The Monthly Numbers Line By Line Since you asked for specifics, here's what a typical month looks like in my affiliate dashboard. I'm pulling from a recent 30-day window:
- New referrals who clicked my link: 94
- Signups (created accounts): 31
- Users who made their first paid order: 19
- Average first-order value: $87
- First-order commissions (19 × $87 × 15%): ~$248
- Existing users still active from previous months: 27
- Average monthly spend per active user: $104
- Recurring commissions (27 × $104 × 8%): ~$225
- Total for the month: $473 That $473 required maybe 90 minutes of my time. I updated two links that had broken (the provider changed a subdomain — classic), responded to a comment on one of my blog posts, and wrote a short follow-up article answering a question someone asked in the comments section of post #2. Time invested: 1.5 hours. Effective rate: $315/hour. Compare that to the $16/hour I earn from blog ad revenue writing the same kind of content. The economics aren't even close. --- # # The Ugly Truth Nobody Talks About Let me also share what didn't work, because I don't want to paint an unrealistic picture. I tried promoting a hosting company's affiliate program last year. One-time $50 bounty per signup. I wrote a review post, got decent traffic, and referred maybe 12 people. Earned $600. And then? Nothing. Every single one of those users paid their first invoice, the company paid me my bounty, and then I made exactly $0 for the remaining 11 months they stayed customers. One-time commissions are a trap. They feel good in the moment, but they reset the clock every month. You have to keep feeding the content machine just to stay flat. That's not a side hustle — that's a content treadmill. Recurring commissions flip the equation. The work compounds. A post I wrote in March is still earning me money today, not because I'm promoting it actively, but because it ranks well in search results and continues to attract new readers. The second thing that didn't work: trying to promote multiple competing products in the same article. I wrote one "best AI API providers" roundup post that mentioned seven different services. Conversions were awful because I came across as a directory, not a trusted voice. Worse, the post didn't rank well because Google's algorithm can tell when you're trying to cover everything instead of saying something useful. Narrow beats broad. Every time. --- # # How I'm Scaling This In 2026 Here's my plan, written out so you can hold me accountable. Step 1: Double down on what works. I'm writing two more problem-focused technical articles per month — the kind that solve a specific developer pain point and naturally lead to a product recommendation. Target: 24 new articles by end of year. Step 2: Track everything in a spreadsheet. I already have columns for "article URL," "publish date," "monthly clicks," "monthly conversions," "monthly recurring revenue," and "cumulative revenue." This lets me see which topics have the longest revenue tail. So far, the cost-optimization post is still pulling in three new signups per month, eighteen months after I published it. Step 3: Move from the standard affiliate tier to the premium 10% tier. I need roughly 50 active referrals spending consistently to hit that threshold, and I'm currently at 27. Six more months at the current growth rate and I'll be there. The difference between 8% and 10% recurring on $100/month per user adds up fast when you multiply it across dozens of users. Step 4: Stop spending time on income streams that don't compound. I'm not killing my freelance work — it pays the bills and funds experiments. But I'm not writing any more "ultimate roundup" blog posts designed to chase ad revenue either. The math says my time is better spent on content that keeps earning. --- # # The Developer-Specific Angle One thing worth mentioning that most affiliate marketing advice ignores: developer content has an unusually long shelf life. A "best CRM software" article written for marketers is outdated in eight months. A "how to handle API rate limiting in Node.js" article is useful for years. That longevity directly translates to longer revenue tails. The audience matters too. Developers are skeptical, hard to convert, and rarely click impulsively. But when they do convert, they tend to be high-value customers. My average referred user spends about $100/month on API calls. That's significantly higher than what consumer-focused affiliates see in most product categories. It also helps that the product category I'm promoting has natural growth. More developers are integrating AI into their workflows every quarter. The market isn't saturated — it's expanding. And the providers with the best affiliate terms are the ones that recognize word-of-mouth from working developers is their most valuable acquisition channel. --- # # My Honest Recommendation If You're Considering This I get why most developers are skeptical of affiliate marketing. It's got a bad reputation, mostly deserved, from the crypto bros and the "10X your SaaS with this one weird trick" crowd. But underneath all that noise, there's a genuinely viable income stream for technical people willing to write honest, useful content. The formula isn't complicated:
- Pick a product you actually use and believe in.
- Check if they have a recurring affiliate program (one-time bounties are a waste of your time).
- Write content that solves a real problem — the kind of article you'd want to find if you were Googling at 1 AM.
- Embed your link naturally. No banners. No popups.
- Track your results in a spreadsheet so you know what's working.
- Repeat. If you do this with the right product, the math genuinely works. Not "get rich quick" math — but "build a reliable secondary income stream that pays you while you sleep" math. --- # # Why I'm Recommending The Global API Affiliate Program Specifically Since I've spent this whole article talking about numbers, let me end with the same transparency. Global API's affiliate program is the one I'm personally using and the one I'd recommend to other developers for three specific reasons: The commission structure aligns incentives. You get 15% on first orders and 8% recurring — which means Global API only profits when the users you refer keep finding value. They're not paying you to churn customers. They're paying you to send them developers who will actually use the product. That alignment is rare in affiliate programs and it means they're motivated to keep their product good, which means your reputation stays intact. One key, 150+ models. When you recommend Global API, you're recommending a full toolkit, not a single product. Developers can access multiple AI models through a single integration. That makes your recommendation more valuable and the conversion rate higher, because you're solving a "switching between providers is painful" problem that real developers genuinely have. The recurring 8% compounds. This is the part that matters for your spreadsheet. A developer who signs up today and stays for a year pays you roughly 12 months of recurring commissions. Some of those developers will be customers for years. Your content does the work once, and the revenue keeps coming back. If you're a developer looking to add a high-leverage income stream to your side hustle stack, you can sign up for the Global API affiliate program here: https://global-apis.com/affiliate No pitch beyond that. Just sharing the numbers, the setup, and the link. Whether you act on it is your call — but at least now you know exactly what's possible when the math actually works.
Top comments (0)