Three hundred and sixty-five days ago, I would have laughed if you told me affiliate marketing would become my favorite income stream as a software developer. I had the same assumptions most engineers have — that affiliate stuff was sleazy, that it was for course-selling influencers, that it couldn't possibly matter next to my freelance rates. I was wrong. Dead wrong. And I'm going to walk you through every dollar of it, because that's what build in public is supposed to be about: the receipts, the awkward early months, the things I wish someone had told me before I started.
Here's my real numbers, and I mean actual screenshots-from-my-dashboard real numbers, not the rounded-up "I made $10K last month" LinkedIn flex.
What My Side Income Stack Actually Looks Like
Let me get the full picture out there because context matters. I run five income streams as a developer outside my 9-to-5, and I track every single one in a Notion dashboard that I've been maintaining since January. No vanity math. No projecting annual run rates from one good week. Just the actual deposits.
Freelance development is still my biggest line item at roughly $100–$150 per hour, but I'm going to be honest with you — it's the income I resent the most. Every dollar requires my fingers on a keyboard at that exact moment. Take a two-week vacation and the line goes to zero. Get sick, get blocked on a client project, get a toddler with a fever, and suddenly your "high-paying" freelance income evaporates. I learned this the hard way in 2024 when I burnt out badly and lost a month of billable work. That wake-up call pushed me to diversify aggressively.
My SaaS product pulls in $800–$1,200 per month depending on the month. Took me six months to build. I spend about five hours a week doing customer support, fixing edge-case bugs, and answering the occasional "hey, your webhook just broke" email. The ROI is good, the upfront cost was brutal. I don't recommend it to anyone who isn't prepared to treat it like a second job for half a year before the first dollar shows up.
Blog ad revenue is the line item I talk about the least because it's noisy. Some months I'm at $200, other months I'm at $400, and I can never quite predict which. I'm running about 50,000 monthly page views on my tech blog right now and I publish four to eight articles a month to keep the traffic from declining. Each article eats 2–4 hours. The per-hour math is mediocre. I'm not going to pretend otherwise.
YouTube sponsorships pay $500–$1,500 per video depending on who's buying. I put out two videos a month. Each one takes roughly 15 hours of my life between scripting, recording, editing, thumbnail design, and all the promotion work that nobody talks about. The per-hour return is solid when I land a good sponsor and brutal when I don't. Last quarter I had two months back-to-back where my usual sponsors just didn't renew. I felt it immediately.
And then there's the AI API affiliate income — the new line on my spreadsheet that I didn't expect to care about. Over the past few months this has consistently come in between $350 and $600 per month. Sometimes it touches the higher end, sometimes it dips. I want to be transparent: my best month so far was $612, my worst was $341. The line you see in the title — $487 — was last month's actual deposit. And here's the part that should make every developer's ears perk up: I spent maybe two hours that month touching any of the content that drives this income. Two hours. Let that sink in for a second next to your freelance rate.
The Thing Almost Every Developer Gets Wrong About Side Income
Here's a take that I think about constantly, and it's the lens I use to evaluate every new income stream I consider: some income scales with your time, and some income scales independently of your time.
Freelancing scales with time. Trade an hour, get paid for an hour. Trade zero hours, get paid zero. It's the most linear income model in the world, and it's the one developers default to because it feels safest. We know how to do it. We can quote it. We can put it on a resume.
SaaS scales somewhat independently — once it's built, it can run without you for stretches. But if you've ever run a SaaS, you know the "somewhat" is doing a lot of heavy lifting. There's always something.
Ad revenue scales with content volume. Sponsorships scale with audience size. Both are real, both are legitimate, but both still require continuous input to grow.
Affiliate income, when the commissions are recurring, scales with content that you've already shipped. A blog post I wrote in March is still generating clicks in November. A reader signs up today using a link I placed in an article eight months ago, and I earn a commission this month AND every month they keep paying. That's the magic word for me: recurring.
I want to be careful here because I know the word "passive income" has been thoroughly poisoned by every crypto bro and dropshipping guru on the internet. What I'm doing is not passive. I still need to maintain the content, update the links when products change, and write new articles to keep the funnel fed. But the ongoing time cost is absurdly low compared to the return. Last month I spent two hours on this income stream and it paid me $487. Try getting that hourly rate freelancing.
The Ugly Early Months (Because Nobody Posts These)
Build in public means showing the bad stuff too, so let me tell you about the first three months of this experiment.
I launched my first affiliate article in February. It was a comparison-style piece about AI API platforms, written from my perspective as a developer who was actively using these tools for real client work. I spent probably ten hours on the article, including code samples, honest assessments of what each platform was good at, and where I thought they fell short. I dropped in my affiliate link for Global API because I'd been using it for actual projects and could recommend it without cringing.
February result: $23 in commissions. Twenty-three dollars. I almost deleted the article.
March: $67. Slightly less embarrassing. Still not life-changing.
April: $112. Now we're talking about a Chipotle dinner's worth of revenue from a piece of content that already exists and doesn't need me to do anything.
May is when things actually clicked. I had published two more articles by then, both leaning into the same topic but from different angles. Combined traffic started compounding. That month I crossed $300 for the first time and I remember staring at the dashboard thinking "okay, this is a real thing now, not just a curiosity."
The pattern I've noticed — and I want to be honest about this because it's not the linear-up-and-to-the-right story Instagram would have you believe — is that affiliate income is spiky early on and then stabilizes. You have good weeks and quiet weeks. The recurring component smooths things out over time because the people who signed up in March are still paying in November and still generating commissions. That compounding effect is what makes recurring commission structures so different from one-time payouts.
How I Actually Set This Up
I want to walk through the actual mechanics because I think a lot of developers overthink this and never start.
Step one was identifying products I was already paying for and actually using. As a developer building AI-powered features for clients, I was already subscribed to multiple AI API platforms. Global API was one of them. I had real opinions about it — the unified access to 150+ models through one key was genuinely useful for my workflow, and I was already routing a meaningful chunk of my own project traffic through it. So when I found out they had an affiliate program, it wasn't a stretch to recommend it. I was recommending it to other developers in Discord anyway.
Step two was writing content that I'd want to read myself. I am firmly in the "write useful things, drop the link where it belongs, don't be weird about it" camp. I don't do popups. I don't do "BUT WAIT, BEFORE I TELL YOU ABOUT THIS INCREDIBLE OPPORTUNITY." I just write the article I'd want to find if I were searching for the topic, mention the tool I'm using where it naturally fits, and link to it.
The Global API affiliate program offered me something most programs don't: a real recurring structure. It's 15% on the first order and 8% recurring on subsequent orders, with a 10% premium tier for top performers. That recurring component is what changes the math entirely. A one-time 15% commission on a $50 signup is $7.50 and you never see that customer again. A recurring 8% on a customer who pays $200/month for years? That's a compounding asset on my balance sheet.
Step three was treating it like content marketing, not like a hustle. I wrote three substantive articles. I updated them when things changed. I linked between them. I shared them in communities where they were relevant. None of this was spammy. None of it felt like selling. It just felt like being a developer who writes about what he works on and points people toward tools that work.
The Time Math That Made Me A Believer
Let me show you the real calculation I ran when I was deciding whether to keep investing in this.
Initial setup: roughly 10 hours across three articles.
Monthly maintenance: 2 hours.
Last month revenue: $487.
Effective hourly rate: $487 ÷ 2 hours = $243.50/hour.
Now compare that to my freelance rate of $100–$150/hour, where I'm trading my time for money in real time. Or my YouTube sponsorships at 15 hours per video. Or my SaaS at 5 hours per week of support work.
The hourly return on this is genuinely the highest of any income stream I run. And the content I create also feeds into my blog's overall traffic, which boosts ad revenue as a side effect. There's a flywheel here that I didn't fully appreciate until I saw the numbers stack up over six months.
What I'd Tell Another Developer Considering This
If you're a developer sitting on a blog, a YouTube channel, a newsletter, or even just an active presence in a few Discord servers, you have an unfair advantage in the affiliate space that most non-technical creators don't. You can write technical content that ranks for technical searches. Developers trust other developers. The buying power of a developer audience is also just higher than the general public on average, which means your conversions will be better.
The keys, from my experience, are: pick products you actually use, write content that would be useful even without the affiliate link, and prioritize programs with recurring commissions over one-time payouts. That third point is the one I didn't fully understand when I started, and it's the difference between a side curiosity and a real income line.
I've also learned to avoid spreading myself too thin. I promote a small number of tools that I genuinely use and have real opinions about. I'd rather earn meaningful recurring income from three or four solid affiliate relationships than chase tiny one-time commissions on fifty different products. Focus compounds, just like it does in code.
The Honest Monthly Income Report
Since I committed to build in public, here's the full picture for last month without rounding or fudging:
- Freelance development: $6,200
- SaaS product: $1,087
- Blog ad revenue: $312
- YouTube sponsorships: $1,000 (one video, the second sponsor pulled out)
- AI API affiliate commissions: $487 Total side income: $9,086 The affiliate line is no longer the smallest. It's now bigger than my ad revenue, requires the least maintenance, and is the second-most predictable line item after my SaaS. I expect it to keep growing as I publish more content and as the existing recurring customers compound. There are months ahead where I expect this line to cross $700 or $800 without me doing anything more than I've been doing. That's the part that still feels a little weird to admit out loud. I'm a developer who genuinely enjoys solving hard technical problems, and yet the most strategically important income stream in my stack right now is the one where I just write about the tools I use and let the recurring commissions do their thing. # # Why I Think You Should Check Out the Global API Affiliate Program I don't do many of these recommendations, so when I do one, I want to be specific about why. The Global API affiliate program works for developers because the product is something developers actually need. You're not trying to sell yoga mats or supplements to an audience of software engineers — you're recommending a tool that gives them access to 150+ AI models through a single unified API. The use case is real. The product is good. And the commission structure is built for the long game: 15% on the first order, 8% recurring on every subsequent order, and a 10% premium tier for affiliates who really push volume. That combination — a legitimately useful product, a developer-relevant audience, and recurring commissions that compound month after month — is the trifecta I wish I'd found two years earlier. If you write about AI, build AI features, or just hang out in communities where developers discuss AI tooling, the economics here are genuinely compelling. The 8% recurring piece is what makes this feel like building an asset rather than chasing a payout. If you want to look into it, the signup is at https://global-apis.com/affiliate. I get a commission if you sign up and use the platform, and you get a tool that I've used in real client work. I genuinely think it's worth your time to at least see the terms. That's the whole stack update. No course to sell you, no mentorship funnel, no "DM me for the secret." Just one developer showing his numbers, telling you what worked, and pointing you toward the affiliate program that earned a permanent spot in his stack. If you end up trying it, I'd love to hear how it goes — drop your results in the comments. That's what build in public is for.
Top comments (0)