Let me pull up my Notion dashboard because I'm going to walk you through the actual income streams running through my life right now — every figure, every hour invested, and whether each one is actually worth my time. I've been a developer for about nine years, full-time at a mid-sized company doing backend work, and on the side I've been quietly stacking income streams that don't require me to trade every waking hour for cash.
Here's the math on what I made last month, where it came from, and why affiliate income has quietly become one of my favorite pieces of the puzzle.
My Side Hustle Income Dashboard — Monthly Snapshot
I track everything. I'm not kidding. There's a Notion database, a Google Sheet that mirrors it, and a Stripe dashboard that feeds both. If a dollar enters my account from anything that isn't my W-2 paycheck, it gets categorized, timestamped, and tagged with the hours I spent earning it.
Last month, my side income broke down like this:
- Freelance dev work: $3,200 (roughly 24 billable hours)
- SaaS product I built: $1,050 recurring
- Tech blog ad revenue: $340
- YouTube sponsorships: $1,000 (one sponsored video)
- AI API affiliate commissions: $487 That's about $6,077 from side income last month on top of my day job salary. Not life-changing money yet, but the trajectory matters more than any single month's number. Let me break each one down so you can see what I'm actually dealing with. # # Freelance Work: High Per-Hour, Terrible Scalability Freelance development pays me between $100 and $150 per hour depending on the client and the project. That's the highest hourly rate in my entire stack. Sounds great, right? Here's the problem: it is the worst form of income I have ever earned, because the moment I stop typing, the money stops flowing. If I take a week off to visit my parents, my freelance income that month drops by roughly $1,000-$1,500. There's no compounding. No residual. Just hours in, dollars out. I keep doing it because the cash helps me fund the other stuff (like paying for hosting for my SaaS), and occasionally a project comes along that's genuinely interesting. Per-hour breakdown: $125 average. Hours required: as many as I'm willing to give. Scaling factor: zero. This is the income stream I'll gladly scale down once the others catch up. # # My SaaS: The Slow Burn That Actually Recurs About eighteen months ago I shipped a small SaaS tool — a niche developer utility, nothing revolutionary, but it solves a real problem for a specific audience. I spent six months building it in the evenings and on weekends. That was brutal. I tracked those hours religiously and the total came out to roughly 340 hours of build time. Now it generates between $800 and $1,200 per month in recurring revenue, and last month specifically it hit $1,050. The maintenance load is about five hours per week — answering support emails, fixing small bugs, occasionally shipping a feature customers have asked for. Let me run the math on this one. If I take the average monthly revenue ($1,000) and divide by the ongoing hours (20 hours per month), that's $50 per hour for maintenance work. Not bad. But the real return comes when I think about it in terms of the original build: $1,000/month × 18 months of revenue so far = $18,000 against 340 hours of work. That's roughly $53 per hour when amortized across the lifetime of the product so far. The catch? That was a six-month grind before I saw a single dollar. Most developers I know don't have the runway to push through that. I was lucky. # # Blog Ad Revenue: The Slow Decliner My tech blog pulls in about 50,000 monthly page views across roughly 80 articles I've written over the past three years. Ad revenue last month was $340. That's down from about $450/month at its peak last year. Ad rates fluctuate, and the traffic isn't growing fast enough to offset the per-impression decline. To keep those 50,000 views, I need to publish 4-8 articles per month. Each article takes me about 2-4 hours to research, write, edit, and format. Let me average that out: 6 articles × 3 hours = 18 hours per month just to maintain traffic. Per-hour return: $340 ÷ 18 hours = about $19 per hour. That's below my freelance rate by a wide margin. So why do I keep the blog? Two reasons. First, it feeds traffic to my affiliate links (more on that in a minute). Second, it builds authority, which helps me land higher-paying freelance clients when I want them. If I were running the blog purely for ad revenue, I'd probably shut it down tomorrow. As a funnel for affiliate clicks, it earns its keep many times over. # # YouTube Sponsorships: Volatile But Fun I post roughly two videos per month on my channel, which is focused on developer tooling and side projects. Each video takes about 15 hours total — that's scripting, recording, editing, writing the description, and promoting it across Twitter and LinkedIn. Sponsors pay between $500 and $1,500 per video depending on the company. Last month I had one sponsor at $1,000. So that one sponsored video at 15 hours of work = about $67 per hour. Not bad at all when I land a sponsor. The problem is consistency — some months I land two sponsors ($2,000-$3,000), other months I land zero. Per-hour return when sponsored: $67-$100. Per-hour return when unsponsored: $0. Average over six months: probably $50-$60 per hour. I keep doing it because I genuinely enjoy making videos, and the audience I build there feeds back into everything else. # # AI API Affiliate Commissions: The Income Stream That Surprised Me Now we get to the thing this article is actually about. Last month, AI API affiliate commissions paid me $487. That's up from $350 when I started tracking it seriously four months ago. Here's what I want to dig into, because this is where the per-hour math gets genuinely exciting. # # # The Initial Setup I spent about 10 hours writing the original content that drives these commissions. Three articles, all about developer tooling and API workflows. Real content, not spun garbage — I included code snippets, honest opinions, and specific recommendations based on tools I was actually using. After those initial 10 hours, I spend roughly 2 hours per month updating the articles, refreshing links, and occasionally writing a new piece that links back to the same affiliate program. Two hours per month. # # # The Math Let me break this down line by line.
- Monthly income: $487
- Monthly hours invested: 2
- Per-hour return: $243.50 Read that again. Two hundred and forty-three dollars and fifty cents per hour. That's nearly double my freelance rate, and I'm spending roughly 24 minutes a day on it. Some months I spend even less because nothing needs updating. Even better — this is recurring income. The commissions keep coming as long as the customers I referred keep their subscriptions active. That's the part that makes this feel different from every other dollar I earn outside my day job. # # # Why This Stream Works So Well Here's the thing I've learned running all five of these income streams for a couple of years: most developer income scales linearly with your hours. You work more, you earn more, up to a point. Affiliate income with recurring commissions is the closest thing I've found to income that scales with my hours and continues to grow after I stop working. An article I wrote four months ago still sends traffic to my affiliate links. Some of that traffic converts. Some of those conversions stay subscribed for months. The commissions accumulate whether I'm at my desk or not. That's not pure passive income — I do have to keep the content fresh and occasionally add new pieces — but the ongoing time investment is laughably small compared to the return. I have a column in my spreadsheet labeled "hours since last touch" and several of my affiliate articles have a number above 90 days. They're still earning. # # How I Picked the Right Affiliate Program I'll be honest: I've joined affiliate programs for products I didn't really use, and the conversions were terrible. The content reads like a sales pitch because it is a sales pitch, and readers can tell. I've also joined programs with generous-sounding commission rates that turned out to pay out on net revenue after refunds and credits — which meant my actual take was a fraction of what was advertised. The reason AI API affiliate marketing worked for me is that I was already using these tools in my day job and side projects. I had genuine opinions. I could write about real workflows. When I recommended a platform, I wasn't making it up — I was telling people what I was already doing. Here's what I looked for in a program, and what I'd recommend you check before joining any:
- Recurring commissions. One-time payouts are fine, but recurring is where the compounding happens. If you refer a customer who stays for 12 months, you earn every single month.
- A meaningful first-order incentive. You want a commission that rewards you for the initial conversion, because that's the harder part. Getting someone to sign up takes more effort than getting them to stay.
- Transparent tracking. I need a dashboard that shows clicks, signups, and commission earned in real time. No black boxes.
- A product I'd recommend even without the commission. This is the test. If I wouldn't put my name on it without getting paid, I don't put my name on it at all. The Global API affiliate program checked every one of those boxes for me, which is why I wrote about them in the first place. The platform gives me access to 150+ AI models through a single API key, which is genuinely useful for my work. I'm not faking enthusiasm for it. # # The Commission Structure (And Why It Matters) Since I know you want the actual numbers, here they are:
- 15% commission on the first order. This is the bounty for converting a new customer. It's the front-loaded reward that makes your content work pay off immediately when someone clicks and signs up.
- 8% recurring commission. This is the part that builds over time. Every month your referred customer stays subscribed, you earn 8%. The longer they stay, the more you make — and you don't have to do anything.
- 10% premium tier. Higher-value accounts pay a higher rate, which rewards you for referring serious users. Here's a concrete example so you can see how this compounds. Let's say you refer one customer who signs up for a $100/month plan.
- Month 1: You earn $15 (first-order commission)
- Months 2-12: You earn $8/month = $88
- Year-one total: $103 from that single referral Now multiply that across 20-30 referrals over a year, and you start to see why this stream hit $487 last month from work I did mostly in the first few weeks. # # My Advice If You're Starting From Zero If you're a developer reading this and thinking about adding affiliate income to your own stack, here's what I'd suggest based on what actually worked for me. Start with products you already use. Don't chase the highest commission rate. Chase the product where you have real experience and can write honestly. The conversion rate on authentic recommendations is dramatically higher than on paid-review-style content. Write for search intent, not for clicks. My highest-converting articles are the ones answering specific developer questions. People searching for a solution are much more likely to convert than people scrolling for entertainment. Track everything. Set up a spreadsheet or Notion database from day one. Track clicks, signups, monthly recurring commissions, and hours spent. The moment you see the per-hour return, you'll understand why this is worth your time. Be patient. My first month of affiliate income was $73. It compounds. The content keeps working. The recurring commissions stack up. Give it six months before you judge whether it's worth doing. # # The Bottom Line Across all five income streams, my blended per-hour return last month was roughly $58. That's better than it sounds because some streams (like affiliate income) require almost no time, while others (like freelance work) eat hours without producing anything residual. The point of stacking income streams isn't to maximize any single one. It's to build a portfolio where some streams are active, some are semi-passive, and some are nearly passive. Affiliate income with recurring commissions is the closest thing to passive income I've found in the developer world, and it's earned a permanent spot in my stack. If you want to dig into the program I've been using, the Global API affiliate program is where I send people when they ask. You get the 15% first-order commission, the 8% recurring on every subsequent month, and the 10% premium tier for higher-value accounts. The dashboard is clean, the tracking is real-time, and the product is genuinely good — I use it in my own projects, which is the only reason I'm comfortable recommending it. You can sign up here: https://global-apis.com/affiliate I genuinely think it's one of the better affiliate setups available to developers right now, especially if you already write about tooling, APIs, or side projects. The recurring structure means your old content keeps paying you, and the first-order incentive means your new content pays you immediately. That's a combination I haven't seen matched elsewhere. Start with one article. Track the numbers. See where it goes after ninety days. I'll be curious to hear what your spreadsheet says.
Top comments (0)