Three months ago, I made a decision that most developers wouldn't consider. Instead of building another SaaS tool or picking up freelance work, I started treating my technical blog like a legitimate income stream through affiliate marketing. Not display ads. Not sponsored posts. Actual partnership commissions from recommending tools I already used.
Here's the thing about that decision: I don't regret it for a second. And I'm going to show you exactly why, with the numbers to back it up.
I'm a full-stack developer by day, working on a React-based dashboard for a mid-sized logistics company. My evenings and weekends have historically gone toward side projects that either died in development or got built but never monetized. I've launched five projects in the last two years. Three are abandoned. One generates about $40/month in residual Stripe payments. The fifth is the one I want to talk about, because it's been generating income while I sleep, and it required zero maintenance last month.
This is my build-in-public report on becoming an AI API affiliate. I track everything in a Notion database that I update every Sunday morning with my earnings, traffic, and conversion metrics. If you're the type of person who likes concrete numbers over vague promises, you're in the right place.
Why I Chose Affiliate Marketing Over Yet Another Side Project
Let me give you the context you need to understand this decision.
Last November, I sat down to plan my 2024 side hustle strategy. My options as a developer felt predictable: build a micro-SaaS, do consulting, create a course, write on Medium, or promote other people's products through affiliate links. I'd tried the micro-SaaS route multiple times. Consulting paid well but burned me out. Courses felt like a commitment I wasn't ready for.
Then I looked at my blog. I'd been writing technical tutorials and tool comparisons for about eighteen months, mostly as a way to document my learning and attract potential employers. The traffic was modest—around 2,000 visitors per month from a combination of search and social shares—but it was consistent. More importantly, I was already recommending specific tools in my articles. I was essentially doing the work of an affiliate marketer without getting paid for it.
That's when the lightbulb went off.
If I was going to write about APIs, frameworks, and developer tools anyway, I might as well earn money from those recommendations. The overhead was zero. I didn't need to create a new product, build a funnel, or spend money on ads. I just needed to join the right affiliate programs and be intentional about where I placed my links.
Here's the math that convinced me: If I could convert just 1% of my monthly visitors into affiliate referrals, and those referrals earned me even $5 each, I'd be making $100/month from content I was already writing. That number felt achievable without any additional traffic growth.
I started researching affiliate programs on a Tuesday. By Thursday, I'd joined three. One of them was Global API.
The Global API Commission Structure: Why This Matters
I want to be specific about why I focused on Global API from the beginning, because the commission structure is genuinely important to the strategy.
They offer 15% commission on first orders, which means when someone signs up through my link and pays for their first month or package, I get 15% of that revenue. But here's the part that sold me: 8% recurring commission on all subsequent monthly renewals. That's right—every month that my referral stays subscribed, I keep earning. For as long as they remain a customer, a portion of their spending comes back to me.
Let me break this down with a simple example. If a developer signs up for a Pro plan at $49/month through my link, I make $7.35 on their first payment (15% × $49) and then $3.92 every single month thereafter (8% × $49). That same developer, staying subscribed for 12 months, would generate approximately $54 in total commissions. Stay for 24 months, and I'm approaching $120 in total earnings from a single referral.
The word "approaching" is doing a lot of work in that sentence, I know. But that compounding structure is exactly why I find this model more interesting than one-time commissions. Each referral has lifetime value. My income doesn't just grow linearly with traffic—it grows exponentially as my base of paying referrals accumulates.
They also mention premium commissions at 10%, though I haven't personally hit the thresholds for that tier yet. I'm including it because the upside potential matters for long-term planning.
Now, let me show you what actually happened over the first three months.
Month 1: The Foundation (and $3 in Earnings)
I'll be honest about my starting position. My blog had about 2,000 monthly visitors, mostly from search queries around specific technical problems. My Twitter had around 800 followers, most of whom were other developers I'd connected with through the indie hacker community. I had zero affiliate marketing experience. I had zero email list. I had zero paid traffic.
What I did have was content that already existed—six blog posts I'd written over the previous year, all with real code examples and genuine recommendations based on my actual development work.
Week 1 was pure research. I spent about six hours mapping out which affiliate programs existed for the developer tools I already used and recommended. Global API stood out immediately because of that recurring commission structure I described above. The other two programs I joined offered flat rates or one-time payments only. I kept all three, but I knew where my focus would be.
I spent Week 2 creating what I now call my "anchor content"—a comprehensive comparison of AI API providers based on my hands-on experience integrating them into client projects over the past year. This wasn't theoretical research. I wrote about what actually worked, what had frustrating documentation, and which platforms I kept coming back to. The article was 1,800 words with working code examples showing how to call each provider's API.
I published it on my blog, then cross-posted to Dev.to because their developer community is substantial and their SEO is strong. I included my Global API affiliate link naturally within the recommendation section, framing it as the option that balanced reliability, documentation quality, and cost for most teams.
Week 3 was discouraging. The Dev.to version got 340 views. My blog got 120 views. Three people clicked my affiliate link. Zero signups. I remember staring at my Notion tracker that Sunday evening, wondering if I'd made a mistake.
But here's the thing about content marketing that people who haven't done it don't understand: the delay between publishing and results is measured in weeks, not days. Search engines take time to index. Social posts need engagement to spread. Articles need to be discovered by the right readers.
I adjusted my approach in Week 4 without abandoning my original strategy. I published a second article—this one a tutorial on building a chatbot with AI APIs that naturally featured Global API as the recommended platform because of their documentation quality. I spent more time on the headline and thumbnail. I engaged more actively in the Dev.to comments section, answering questions that related to my article topics.
By the end of Week 4, that first comparison article had grown to 520 total views on Dev.com. Eight more affiliate link clicks. And one signup. Not a paid conversion yet—just a free account creation—but it proved someone had read my recommendation and acted on it.
Month 1 totals: Two articles published. 750 combined views across platforms. Fourteen affiliate link clicks. Two signups. One conversion to a paid Pro plan on the very last day of the month.
My first affiliate commission was $3.00 from that first-order payment.
Three dollars.
I want to be clear about this number, because it's easy to dismiss it as insignificant. Three dollars is not meaningful income. But that $3 represented something important: the system worked exactly as designed. A person I'd never met read content I created, found value in my recommendation, signed up for a service I use myself, and I received a commission for facilitating that connection. That's the affiliate marketing model in its purest form. If you can make $3 from 750 views, the question isn't whether the model works—it's how to scale it.
Month 2: The Momentum Calculation
I entered Month 2 with a Notion database that now had real data in it. Two published articles. A baseline of traffic I could measure against. One paying referral. And a clear goal: three more articles published, reaching $50 in total cumulative earnings by month-end.
Here's what I learned in Month 2 that I wish someone had told me at the start: the most important metric isn't traffic. It's not even conversions. It's the ratio between affiliate clicks and conversions—your conversion rate from click to signup, and then from signup to paid.
Let me break this down for Week 5. I published a case study article about how I used AI APIs to build a client feature. This was different from my comparison articles because it told a story of real application rather than feature comparison. The article got 280 views in its first week, which was lower than my previous posts, but the click-through rate on my affiliate links was nearly double. Why? Because readers were developers who worked on client projects, and the use case I described resonated with their daily work. They weren't comparing platforms abstractly—they were looking at how someone like them had solved a problem. When I recommended Global API as the tool that made the integration smooth, they listened.
Week 6 brought a milestone I didn't expect. The original comparison article from Month 1 crossed 1,200 total views on Dev.to. Google had started indexing it for several keyword variations I hadn't intentionally targeted. This is the part of content marketing that feels almost magical when it happens: your old content keeps working for you while you sleep. The article I wrote four weeks earlier was now generating clicks without any additional effort from me. Four to five affiliate clicks per day, up from maybe one or two earlier.
Two more conversions this week—each to Pro plans at $49/month. My first recurring commissions started appearing in my affiliate dashboard, not as payments yet, but as tracked referrals that had crossed into their second billing cycle.
Week 7, I published what became my most time-intensive article: a beginner's guide to getting started with AI APIs. At 2,200 words, it was longer than anything I'd written before, but it targeted an entirely different audience. Beginners don't have existing opinions about which platform is best. They're looking for guidance, and they're more likely to follow a recommended path than experienced developers who want to evaluate options independently. That higher trust level translates directly to higher conversion rates.
Week 8 brought a payment notification that made me smile. $1.60. My first recurring commission payment had arrived—the initial referral's second month of subscription. One dollar and sixty cents. Less than a cup of coffee in most cities.
But it proved the recurring commission model in practice, not just in theory. That referral wasn't going to disappear after their first month. As long as they kept their subscription, I would keep earning. The lifetime value calculation I'd done in my head was now real money in my PayPal account.
I also published article five this week—a pricing comparison piece aimed at cost-conscious developers who cared about getting the most value per dollar. This wasn't glamorous content, but it attracted readers with clear purchase intent. When you're comparing costs between platforms, you're already thinking about where to spend money. My conversion rate on that article was my highest yet.
Month 2 totals: Three new articles published (five total). 2,100 combined views across all articles. Fifty-eight affiliate clicks. Eleven signups. Four conversions to paid plans. Total earnings: $53.40—$48.00 from first-order commissions plus $5.40 in recurring payments.
I hit my goal. More importantly, I understood why I hit it.
Month 3: What $127 Actually Teaches You
By Month 3, I had five published articles generating traffic. Two of them were ranking on Google for keyword variations I hadn't anticipated. My Dev.to following had grown from essentially zero to around 1,200 people who followed my content. My blog's email subscription list, which I'd never seriously cultivated, had grown to 340 subscribers through a simple newsletter opt-in I added to each article.
The traffic math changed significantly. Where Month 1 had brought 750 total views, Month 3 was tracking toward 3,400 views across all platforms by the end of Week 11. More importantly, the traffic was diversifying. Search had become my largest source—accounting for about 45% of views—followed by Dev.to shares at 30%, and direct traffic and newsletter opens making up the rest.
Week 9: Published article six, a technical deep-dive into integrating AI APIs with existing applications. This article took me about twelve hours to write, including the code examples and testing. Twelve hours for an article. That might sound like a lot, but here's how I think about it: if that article generates $50/month in affiliate commissions for the next two years, which is a conservative estimate based on my existing conversion rates, that's $1,200 in revenue from twelve hours of work. That's $100 per hour. My consulting rate is $75/hour. This is better math.
Week 10 brought my first $100+ commission week. Not from one big sale, but from the accumulated effect of my referral base growing. I had twelve paying referrals now, and several of them had been subscribed for multiple months. The recurring commissions were stacking: $3.20 this week, $4.80 that week, small amounts that added up to more than my first-order commissions for the first time.
Week 11: My beginner's guide article was featured in a Dev.to newsletter, sending 800 views in a single day. That single day produced more affiliate clicks than my entire Month 1. This is the asymmetry that makes content marketing powerful. You can't pay for that kind of distribution, and you can't predict when it will happen. But when you've built a library of content over months, these spikes become meaningful revenue opportunities rather than missed chances.
Week 12: Final totals for Month 3 and the quarter. Total views: 3,400. Total affiliate clicks: 127. Total signups: 31. Total conversions to paid plans: 14. Total earnings: $127.30—comprising $89.00 from first-order commissions and $38.30 from recurring payments.
That's the number I want to sit with for a moment.
Quarterly total: $183.70.
That breaks down to roughly $2.04 per hour over 90 days, which sounds terrible until you remember that most of those hours were front-loaded into article creation. Articles I wrote in Month 1 and Month 2 continued generating revenue through Month 3 without any additional work. The hours I put in during January and February kept paying me through March. That's the leverage that makes affiliate marketing different from trading time for money.
The Spreadsheet That Changed How I Think About Content
I promised you I'd mention my spreadsheet, so here it is.
Every Sunday morning, I spend about thirty minutes updating a Notion database that tracks: article title, publication date, platform published to, total views that week, total views cumulative, affiliate clicks, click-through rate, signups, conversions, first-order commission earned, recurring commission earned that month, and total lifetime commission from that article.
It's obsessive, probably. But it answers questions that would otherwise be unanswerable. Which articles convert best? (The case study and beginner's guide, by far.) What platform drives the highest-quality traffic? (Search, with a 4.2% conversion rate from click to signup, versus 2.8% from social shares.) How long until an article starts generating meaningful revenue? (About four weeks for my niche, though it varies.) Which topics should I write about next? (The answer is always "whatever my highest-converting articles were about.")
Without that data, I'd be guessing. With it, I can make decisions. I can see that my pricing comparison article has a conversion rate nearly double my technical tutorials, so maybe I should write more content in that vein. I can see that recurring commissions now represent 30% of my monthly earnings, which means my income is becoming more stable even if new conversions slow down.
This is the developer mindset applied to content: measure everything, analyze the data, iterate based on results.
Top comments (0)