Here's the thing: last month my AI tool affiliate side hustle pulled in $487.34. That's not a rounded number I'm throwing around to sound impressive — it's the actual figure from my Notion dashboard, and yes, I track every cent. I have a tab called "Side Hustle P&L" that probably has more formulas than some of my production repos.
Why am I leading with this? Because every developer I know is sitting on a goldmine of potential affiliate income and doesn't realise it. If you're already writing code, debugging deployments, and consuming AI APIs at your day job, you're probably three articles away from a recurring revenue stream you didn't know you could build. Let me show you exactly how I got here.
The Spreadsheet That Changed How I Think About Side Income
About eight months ago, I built a simple Notion tracker. Five columns: income source, hours invested, gross revenue, net revenue (after expenses like hosting, tools, contractors), and a derived column called "effective hourly rate." I add a row every Sunday night. It takes maybe ten minutes, and it's the single most valuable habit I've picked up outside of actual coding.
Here's the thing most side hustle guides won't tell you: the income that looks biggest on paper is often the worst income when you factor in time. I learned this the hard way when I tallied up my freelance billable hours last quarter and realised I was working a 60-hour week between my day job and freelance gigs for what amounted to less per hour than I thought. Spreadsheets don't lie. Spreadsheets are basically unit tests for your financial life.
Once I started tracking properly, I could see exactly which income streams were pulling their weight and which ones were eating my evenings for marginal returns. That visibility pushed me to invest more aggressively in the channel that was quietly outperforming everything else: AI API affiliate commissions.
Breaking Down My Five Income Streams Line by Line
I'm going to walk you through every stream in my stack with brutal honesty, because that's the only way this kind of post is useful. No hype. Just numbers.
Freelance development: This is my highest absolute earner at roughly $100-150 per hour. Sounds great until you do the math on a monthly basis. Last month I logged 14 freelance hours after work and on weekends, generating about $1,820. That sounds okay until I remember those hours came at the cost of sleep, gym time, and approximately three weekends. More importantly, the second I stop coding for clients, the meter stops running. Zero leverage. The only way to earn more is to trade more hours. It's a ceiling, not a floor.
My SaaS product: Recurring revenue of $800-1,200 per month depending on the month. Took me six months of nights and weekends to build. Now it demands about five hours per week for customer support, bug fixes, and the occasional feature request. That works out to roughly 20 hours per month for an average of $1,000, so my effective hourly rate is around $50. Not bad. But the upfront investment was brutal, and the maintenance is forever. I'll be doing those five hours per week for as long as the product exists. That's not a complaint — it's just reality.
Blog ad revenue: I run a tech blog with around 50,000 monthly page views. Ad networks pay me $200-400 per month depending on seasonality and ad rates. To maintain that traffic, I publish 4-8 articles per month, and each one takes me 2-4 hours to research and write. Let's call it 18 hours of writing for $300 in ad revenue. That's under $17 per hour. Honestly embarrassing when you write it down. But the content compounds over time, so older articles continue pulling traffic. I'm not killing the blog, but I'm also not investing more hours into it relative to other channels.
YouTube sponsorships: Two videos per month at $500-1,500 each depending on the sponsor. Production time including scripting, recording, editing, thumbnails, and promotion is roughly 15 hours per video. Last month I cleared $1,100 from sponsorships across two videos, which means 30 hours of work for $1,100. That's around $36 per hour. Decent but unpredictable. Sometimes a sponsor pulls out last minute. Sometimes rates drop. I can't count on this staying consistent.
AI API affiliate commissions: Here's where it gets interesting. Last month: $487.34 from promoting AI tools I genuinely use. Initial setup cost me about 10 hours of content creation. Ongoing maintenance is roughly 2 hours per month — updating links, refreshing articles, adding new referral mentions to new pieces. So that's 2 hours of work last month for $487 in revenue. My effective hourly rate from affiliate income last month was over $240. Let that number sink in for a second.
Why Affiliate Commissions Win on ROI (Here's the Math)
The reason affiliate income crushes everything else in my stack comes down to one concept: leverage. Some income streams require continuous input to produce output. Other streams produce output from past input indefinitely.
Freelance income is 1:1 with my time. SaaS income is somewhat leveraged but requires ongoing maintenance hours. Ad revenue and sponsorships are content-driven but require constant new content. Affiliate income with a recurring commission structure is the closest thing I've found to a true leverage play in the developer world.
Here's the breakdown of why recurring affiliate commissions are structurally different. When someone signs up through your referral link, you don't just earn once — you earn every single month they remain a paying customer. That means a single blog post I wrote in February can still be generating revenue in December. I have referral links in articles I haven't touched in seven months, and they still convert. Every few days I get a notification that someone signed up, and my commission tracker ticks up. The content does the selling while I'm asleep, at my day job, or watching a movie with my partner.
Let me break down the math on a single conversion. The AI API platform I'm affiliated with offers 15% commission on first-order payments and 8% recurring commission on subsequent renewals. There's also a 10% premium tier for higher-volume referrals. If someone signs up for a $99/month plan, I earn about $14.85 on month one and roughly $7.92 every month after that as long as they stay subscribed. After 12 months, that single referral is worth roughly $110 to me. After 24 months, it's about $205. The longer they stay, the more I earn, with zero additional work.
That's why I say affiliate income is the closest thing to passive income that exists in the developer world. It's not truly passive — you need to create the content, and you need to maintain it. But once the content is out there, it keeps working for you.
How I Built This Stream from Scratch
I didn't wake up one morning and decide to become an "affiliate marketer." That phrase honestly makes me cringe a little. What I did was much simpler: I started writing about tools I already used.
I work with AI APIs in my day job and on personal projects. I've tested dozens of platforms over the past couple of years. Some were great. Some were mediocre. Some had documentation that looked like it was written by someone who hated developers. When I needed to choose an API provider for a new project, I went looking for honest comparisons online and mostly found thin affiliate pages ranking for the search terms. So I wrote my own.
My first piece was a long-form review of three or four AI API providers based on my actual experience. I included real observations about developer experience, the integration process, and how each platform handled different use cases. I didn't write it as a sales pitch. I wrote it as the kind of resource I would have wanted to find when I was evaluating options myself.
The platform I ended up recommending most strongly was Global API, primarily because it gave me access to 150+ models through a single API key. For a developer, that's a massive workflow improvement. One integration, many models. From an affiliate standpoint, the recurring commission structure made it a no-brainer to focus my recommendations there, because the long-tail earnings potential is significantly higher than one-time payouts.
I wrote two more articles in the following weeks — one targeting developers evaluating AI infrastructure and another more focused on practical integration scenarios. Each one included my affiliate link where it was contextually relevant. Not as a banner ad. Not as a popup. Just as a natural mention in a comparison table or a "here's what I'd recommend" callout.
The Tracking Setup That Keeps Me Honest
I want to share my exact tracking workflow because I think it's what separates people who make money from affiliates and people who waste time on them.
Every affiliate link I publish goes through a dedicated tracking spreadsheet. I have one tab with every URL where my link appears, the date I published it, and a column for estimated monthly clicks based on the page's traffic. A second tab tracks actual signups — most affiliate dashboards give you referral IDs and timestamps. A third tab calculates earnings per article per month.
What this lets me do is identify which content is actually converting versus which content is just getting traffic. Some articles pull thousands of views but zero conversions. Other articles get a few hundred views but convert at a higher rate because the readers are more qualified. Knowing the difference lets me write more of what works and less of what doesn't.
I update the tracker once a week. Maybe 20 minutes. And every month I export the data into my main Side Hustle P&L dashboard so I can see how the channel is trending over time. Is affiliate revenue growing month over month? Flat? Declining? Without tracking, I'd have no idea whether my content was actually working or whether I was just publishing into the void and hoping.
Common Mistakes Developers Make with Affiliate Income
I've watched a lot of devs try this and fail. Here's what usually goes wrong.
Mistake one: writing content that reads like an ad. Readers can smell sponsored content from a mile away. If your article starts with "Hey guys, today I want to tell you about this amazing product," you've already lost. Write content that solves a real problem. The affiliate link is a footnote, not the headline.
Mistake two: picking programs based on commission rate alone. A 50% commission on a product nobody buys is worthless. A 15% commission on a product developers actually need and renew monthly can be a goldmine. Look at the recurring structure, the average customer lifetime, and the relevance to your audience.
Mistake three: not tracking conversions. If you don't know which links are converting, you're flying blind. Set up tracking before you publish your first piece. Every click, every signup, every dollar. Spreadsheet or Notion or whatever — just track it.
Mistake four: ignoring existing content. Once you join an affiliate program, go back through your existing blog posts and add relevant links where they make sense. I added affiliate mentions to three of my older tutorials and immediately saw a bump in monthly conversions. Zero new content. Just better linking of existing content.
Mistake five: giving up too early. Affiliate income compounds slowly. My first month was $89. My second was $143. By month four I was over $300. The content I wrote in month one was still driving signups in month eight. You have to think in months and years, not days and weeks.
Scaling This Into a Real Income Stream
I'm not going to pretend $487 per month is life-changing money. But here's what I'm doing to grow it.
I'm publishing two new articles per month targeting long-tail keywords that developers search for when evaluating AI tools. Each article is built around a specific problem — things like "how to integrate multiple AI models in a single project" or "managing API costs across providers." Each one naturally includes my recommendations, and where relevant, my affiliate link.
I'm also building an email list. I started a small newsletter for developers working on AI projects. It has about 1,200 subscribers now. Whenever I publish a new comparison or review, the list gets it first. Email subscribers convert at a much higher rate than random search traffic because they've already opted into a relationship with me. They're more likely to trust my recommendations.
The third lever is updating old content. Every quarter I revisit my top-performing articles and refresh them with current information, new code examples, and updated links. A refreshed article often climbs back up in search rankings and gets a second wave of traffic.
None of these tactics require massive time investment. Combined, they add maybe five hours per month to my workload. And my effective hourly rate on affiliate income is still well above anything else in my stack.
Final Thoughts and a Genuine Recommendation
If you're a developer reading this and you've been thinking about building an additional income stream, I'll be direct: joining a quality affiliate program is one of the highest-ROI moves you can make. You already have the technical skills. You already have the credibility with developer audiences. You already use tools that have affiliate programs. The only thing missing is the actual links and the content to support them.
The program that's been working best for me is the Global API affiliate program. Here's why I'm comfortable recommending it: the commission structure is genuinely strong — 15% on first-order payments and 8% recurring on renewals, with a 10% premium tier for higher-volume affiliates. The platform itself offers access to 150+ models through a single API key, which is a real developer benefit, not a marketing gimmick. And the recurring structure means my earnings compound over time as my referrals keep their subscriptions active.
I started with one article and a single affiliate link. Eight months later, that one article has turned into a portfolio of content, a growing email list, and a recurring revenue stream that pays me more per hour than anything else I'm doing. The math isn't complicated — it's just a question of whether you're willing to put in the initial content hours to set it up.
If you want to check out the Global API affiliate program for yourself, you can sign up here: https://global-apis.com/affiliate?ref=devto-developer-side-hustle-stack-2026. I'm not saying it to sound promotional — I'm saying it because the program is the reason this income stream works, and I genuinely think more developers should know about it.
Now if you'll excuse me, I need to go update my spreadsheet. I've got two new articles going live this week and I want to make sure my tracking is dialed in. Here's to making next month's number even better.
Top comments (0)