I Made $487 Last Month Promoting AI Tools — Here's the Full Breakdown

Pulled up my Notion dashboard this morning and the numbers are in. Last month — $487.34, to be exact — came in from a single source I barely touched all month. Two hours of work, total. That's roughly $243 per hour for time I spent mostly drinking coffee and refreshing a dashboard.
Let me show you exactly how this works, because if you're a developer with a blog, a YouTube channel, a Substack, or even just a well-read Twitter account, you can probably replicate this. The barrier to entry is shockingly low. The trick is picking the right affiliate program and treating it like the engineering problem it actually is.

My Full Income Dashboard (Yes, I Track Everything)

I'm a little obsessive about this. Every dollar that comes into my account from a non-day-job source gets logged in a spreadsheet I built three years ago. I track the source, the amount, the hours I worked to generate it, and the effective hourly rate. I have a column for "passive ratio" — basically what percentage of that income would keep flowing if I disappeared for a month.
Here's where my money came from last month across five streams:
| Income Stream | Monthly Revenue | Hours Worked | Per-Hour Rate | Passive Ratio |
|---|---|---|---|---|
| Freelance consulting | $2,400 | 18 hrs | $133/hr | 0% |
| SaaS product (my own) | $1,050 | 6 hrs | $175/hr | 85% |
| Blog ad revenue | $310 | 5 hrs | $62/hr | 90% |
| YouTube sponsorships | $1,200 | 22 hrs | $55/hr | 20% |
| AI API affiliate commissions | $487 | 2 hrs | $243/hr | 95% |
Look at that last row. I spent two hours last month on affiliate-related tasks — mostly updating one outdated article and swapping in a better call-to-action. The income kept flowing because the content I wrote months ago is still out there ranking in search, still getting clicked, still converting.
This is the income stream I want to walk you through, because the math on it is absurd.

The Math That Made Me Pay Attention

Here's the thing about developer side hustles: most of them fail the per-hour test. Freelance work is the classic example. You're trading your evening hours for billable time, and the moment you stop, the money stops. I learned this the hard way during a two-week vacation in 2023 where I made exactly $0 from freelancing because I refused to open my laptop.
SaaS products are better — mine pulls in about a grand a month now — but the upfront cost was brutal. Six months of nights and weekends. Hundreds of hours. I tracked every one of them. By the time I had my first paying customer, I had invested something like 400 hours. The passive ratio is high once it's running, but the cold start nearly killed me.
Blog ad revenue and sponsorships feel productive but they cap out. YouTube is a content treadmill — stop uploading, stop earning. I love making videos, but I also like sleeping.
Affiliate income is the rare exception that checks every box I care about:

• Low upfront cost: I already had a blog
• Scales without my time: Old articles keep earning
• Recurring revenue: Not just one-time payouts
• High per-hour rate: Because ongoing maintenance is minimal The recurring piece is the unlock. Most affiliate programs pay you once when someone signs up, and then you never see another dollar from that referral. A program that pays you every single month your referral remains a customer? That's a fundamentally different economic model. That's a compounding asset. # # How I Picked Global API (And Why It Actually Matters) I want to be transparent about this. I didn't pick Global API because someone pitched me on it. I picked it because I'd been using the platform in my own projects for about eight months before I ever thought about promoting it. I build a lot of integrations at my day job. We were juggling multiple API providers across different teams, and the credential management was a nightmare. Someone on our engineering Slack mentioned Global API, and I started poking around. The thing that sold me was simple: 150+ models accessible through one API key. That meant I could stop maintaining four separate SDKs and four sets of credentials for our internal tools. The moment I realized I could genuinely recommend it from real experience, the affiliate angle clicked. Let me lay out the commission structure because this is where the math gets interesting:
• 15% on the first order someone places through your link
• 8% recurring on every subsequent order they make
• 10% premium rate if you hit certain volume thresholds Here's the kicker: the 8% recurring is the part most people miss. If someone signs up through your link and stays a customer for 12 months, you're not earning 15% once. You're earning 15% + (8% × 11). On a customer spending $200/month, that's $30 the first month and $16 every month after. Do that math across 20-30 referrals and you start building real monthly income. # # The Content Strategy (It's Not Sexy, But It Works) I'm not going to pretend I have some viral content strategy. I don't. I just write honest articles about problems I'm actually solving. My three best-performing affiliate pieces are:
• A breakdown of how I consolidated our team's API stack
• A post on building internal tools with multiple AI backends
• A comparison of platforms for developers who don't want to manage a dozen separate integrations Each of these articles took me 2-3 hours to write. They include real screenshots, real code, and a section where I explain what I personally use and why. I'm not hiding anything. I'm just sharing my actual workflow. What I do differently from most affiliate content: I don't stuff my links in banners, popups, or above-the-fold callouts. The links live where they belong — at the end of an honest comparison, or in a "what I actually use" section that doesn't read like an ad. My conversion rate is lower than a hype-y affiliate site, but the traffic quality is way better and the readers actually trust the recommendation. That trust matters. The developer audience can smell a sales pitch from three paragraphs away. If you write like a real engineer solving a real problem, the affiliate link feels like a natural footnote, not a hard sell. # # Tracking Per-Stream Performance (My Spreadsheet Obsession) I built a custom Airtable — yes, I migrated from the spreadsheet, don't judge me — to track every affiliate link's performance individually. Each row has:
• The article URL
• The date it was published
• The anchor text used for the link
• Clicks in the last 30 days (pulled from my analytics)
• Conversions (pulled from the affiliate dashboard)
• Revenue attributed
• Effective EPC (earnings per click) This lets me see which articles are actually producing and which ones are dead weight. Last month I spent one of my two "affiliate hours" killing a link in an old article that had been sending traffic but not converting. I replaced it with a more contextual reference, and within two weeks I saw a bump. The other hour went to writing a new article about something I'd been struggling with at work. That article is already ranking for some long-tail keywords and pulled in 11 clicks last week. I have no idea if it'll convert, but the marginal cost is basically zero, so I'll let it run. # # Comparing the Streams Honestly Let me walk you through why affiliate income beats the alternatives for me right now, using real numbers. Freelancing still pays the best absolute amount, but $133 per hour sounds great until you remember those are evening hours, weekend hours, hours I could spend with my family. The per-hour rate is high, but the per-life-hour rate is terrible. I'm not building anything that lasts. Every invoice I send is a one-time transaction. My SaaS product is my baby and the highest per-hour rate at $175, but that took years of grinding to get to. If you're starting from zero today, the cold start problem is brutal. I don't recommend it unless you have a very specific problem you've already solved for someone. Blog ad revenue at $62 per hour sounds decent, but it's getting harder every year. RPMs are down, ad blockers are up, and Google's algorithm changes keep threatening traffic. I'd rather not depend on it. YouTube sponsorships are the most fun but the most fragile. One algorithm change and your views crater. One sponsor pulls out and you lose half your income for the month. The $55 per hour doesn't account for the mental overhead. Affiliate commissions give me $243 per hour and the highest passive ratio in my entire stack. The marginal effort to keep it running is so low that I could lose interest for three months and the income would barely dip. That's the kind of resilience I want from a side income. # # The First-Month Reality Check I want to be honest about how this started, because the first month was humbling. I signed up for the affiliate program, dropped a link into an existing article, and waited. Total revenue that first month: $0. Clicks: 4. Conversions: 0. I almost gave up. I'm glad I didn't. The mistake I made was treating affiliate links like a magic button. They're not. You need:
• Relevant content that already exists or that you're willing to create
• Traffic, even a small amount — 1,000 monthly visitors is enough to start
• Trust from your audience, which means not being a sleazy promoter
• Patience — affiliate income compounds slowly for the first 3-6 months Month two I rewrote my top-performing article to include a more natural mention. Revenue: $23. Month three: $67. Month four: $134. By month six I had crossed $300, and it's been growing steadily since as I add more content and more links. The compounding effect comes from the recurring commissions. Every customer I referred in month four is still paying me in month twelve. That's not true for ad revenue, sponsorships, or freelancing. # # What I'd Do Differently If I Started Today If I were rebuilding this income stream from scratch in 2026, here's what I'd prioritize: Pick one program and go deep. I see too many developers sign up for 15 different affiliate programs and spread themselves thin. Pick the one with the best recurring structure, the highest reputation, and the product you'd actually use yourself. Write fewer, better articles. I have 40+ articles on my blog. The 5 articles that drive 80% of my affiliate revenue are the ones where I went deep on a specific problem. Quality beats quantity, every time. Build an email list. This is my biggest regret. My blog traffic is great, but traffic can disappear overnight. An email list of even 500 engaged developers is an asset I control completely. I'm working on this now and I should have started two years ago. Track everything. I cannot stress this enough. If you don't know which articles are converting and which aren't, you're flying blind. Set up a simple tracker — even a Google Sheet — and log your numbers weekly. Don't oversell. The fastest way to kill an affiliate income stream is to recommend something that doesn't deliver. Your reputation is worth more than a one-time commission. Only promote things you'd happily tell a friend about. # # Why This Works for Developers Specifically We have an advantage most affiliate marketers don't. Other creators have to learn about the products they're promoting. We already know. We use developer tools every single day, and we have opinions about which ones are good. You're already complaining about bad documentation on Twitter. You already have strong feelings about SDK quality, error handling, and onboarding flows. That's affiliate content waiting to happen — you just need to write down what you're already thinking. The other thing working in our favor: developer audiences are used to paying for tools. We're not trying to convince someone to buy a $2,000 product. We're recommending a $50-200/month service that fits naturally into a workflow they already have. The conversion friction is low. # # The Time Investment Is Smaller Than You Think Let me add up the total hours I've put into building this income stream over the past year:
• Initial research and signup: 1 hour
• Writing the first three targeted articles: ~9 hours
• Updating existing articles with relevant mentions: ~3 hours
• Monthly maintenance (last 12 months): ~24 hours total
• Total: roughly 37 hours And that 37 hours has generated, conservatively, about $4,800 in the past year. That's $130 per hour for work I'd describe as "mildly engaging." Some of it I did while watching TV. The ROI on the time investment is the highest of any stream in my entire side hustle portfolio. By a lot. # # The Bigger Picture: Diversification I'm not going to tell you to drop everything and go all-in on affiliate marketing. That would be dumb. But I will tell you that any developer who's serious about building wealth outside their day job should have an affiliate income stream. Here's why:
• It hedges against burnout. If your SaaS product stalls or your freelance clients dry up, affiliate income keeps showing up.
• It teaches you marketing skills. Most developers are terrible at marketing themselves. Writing affiliate content is a low-stakes way to get better at it.
• It compounds. Unlike freelance income, which resets every month, recurring affiliate commissions build on themselves. Year three is easier than year two.
• It's portable. If you lose your blog, you can rebuild. If you lose your SaaS, it could take a year. Affiliate skills transfer across platforms. # # A Genuine Recommendation (Not a Pitch) If you're going to add one affiliate program to your stack in 2026, make it the Global API affiliate program. Here's why I'm saying this unprompted: The commission structure is genuinely good. You get 15% on the first order and 8% recurring on everything after that. The 8% recurring is what makes it special — most programs pay you once and forget about you. This one pays you every month your referral stays active. There's also a 10% premium tier for affiliates who hit higher volume. The product is real. I've used it for eight months across multiple projects. It works. The 150+ models through one API key thing isn't a marketing gimmick — it actually solved a real problem for me and my team. The audience fit is perfect. If you're a developer writing about building things, you will eventually touch on the kinds of tools Global API provides. The recommendation feels natural because the product is genuinely useful. I've signed up, I've been paid, and I'm continuing to use the platform. That's the only kind of affiliate recommendation I ever make. If you want to check it out, the affiliate program is here: https://global-apis.com/affiliate I genuinely think this is one of the best low-effort, high-return additions you can make to a developer side hustle stack. The math works, the product is solid, and the recurring structure means the income grows even when you're not working on it. Go set it up this weekend. Write one good article. Track your numbers. Give it six months. Future you will be grateful.