coolfluxLast March, I was three weeks behind on rent and pretending I was "strategically scaling back" on my...
Last March, I was three weeks behind on rent and pretending I was "strategically scaling back" on my freelance workload. The truth was uglier. I had one client ghosting me on a $400 invoice, another paying me $75 an article with a "trial period" that had stretched into four months, and a third who kept promising a retainer that never quite materialized.
Sound familiar?
I had been freelancing full-time for almost three years at that point, and I was exhausted. Not the kind of tired a vacation fixes. The kind where you realise the math never works in your favor. $150 per article, three articles a week, minus taxes, minus the hours I spent pitching and following up, minus the software I bought to "streamline" my workflow. After expenses, I was netting maybe $2,400 a month, and that was a good month. A slow month looked a lot like eviction notices.
This is the story of how I stumbled into affiliate marketing for AI tools, why it felt like a totally different game from the per-article grind, and how I made my first recurring commission with zero audience to speak of. If you're a writer stuck in the same hamster wheel I was on, I hope this saves you the year it took me to figure it out.
Freelance writing pays you once. You write the piece, you submit it, you wait 30 to 60 days for the invoice to clear, and then you start over. That cycle is brutal because the work is never compounding. Every dollar you earn requires another hour of your time, and there's a hard ceiling on how many hours one person can sell.
I tried to break out of it the "right" way. I built a portfolio site. I cold-pitched editors at publications I admired. I even landed a few higher-paying clients, including one SaaS company that paid me $500 per piece to write their blog content. It felt like I'd made it. Then I got an email saying they were "restructuring" and my contract wouldn't be renewed.
That's when it hit me: even a retainer is just a slightly fancier version of trading time for money. The client can leave. The budget can shrink. The entire model is built on someone else deciding your income each month.
I started reading everything I could about passive income for writers. I tried creating an online course, but I didn't have the audience to sell it. I tried self-publishing a Kindle book, which earned me $14 in six months. I tried Medium's partner program, which paid me literal cents. Nothing clicked.
Then a friend who works in developer relations mentioned that his company had just launched an affiliate program. He said the commissions were recurring. I almost scrolled past it, but I asked him what "recurring" actually meant, and he told me that some AI tool companies pay you a percentage every single month that the person you referred stays subscribed.
That one word — recurring — is what changed everything for me.
Here's the math that made me stop and pay attention. Say you refer a customer to a platform that pays a 15% commission on the first order and 8% on every renewal after that. If that customer spends $100 a month, you earn $15 the first month and $8 every month after that. If they stay for a year, you've made $15 plus 11 times $8, which is $103. From one referral. From one piece of content you wrote once.
Compare that to a freelance article. You write it once, you get paid once, and you never see another cent from it. The blog post sits on someone else's domain, driving their traffic, building their SEO, and the only thing you got out of it was that single payment.
Affiliate revenue flips that. The article you write is an asset. It works while you sleep. It works while you pitch new clients. It works on a Sunday morning when you're still in your pajamas. And because the commission is recurring, every new referral is like planting a tree that pays you for years.
I know "passive income" is one of the most overused phrases on the internet, and most of the people selling courses about it are full of it. But this specific model — writing content that ranks in search engines, recommending tools you actually use, and earning a percentage of the revenue those recommendations generate — is the closest thing to it I've ever found. And you can do it without a single follower.
My biggest mental block was the audience question. I had read dozens of affiliate marketing guides, and almost all of them started with "build an audience first." Grow your Twitter. Start a newsletter. Launch a YouTube channel. But I'm a writer, not a performer. The idea of building a personal brand on social media made me want to lie down.
Here's what I wish someone had told me: you don't need an audience. You need search traffic.
Search traffic is fundamentally different from an audience. An audience is a group of people who follow you around the internet and care about your opinions. Search traffic is a stream of strangers who type a question into Google and click whatever looks most helpful. They don't know who you are. They don't care about your newsletter. They just want an answer.
Every single day, thousands of people search for things like "best AI API for my startup," "how to add AI to my app," "AI tool recommendations for developers." Those people are actively looking for recommendations. If you can create a piece of content that shows up when they search, they will click your link and read your article. You don't need to have any relationship with them beforehand.
I know this works because I did it. My first affiliate sale came from a stranger in Bangalore who had never heard of me. He found my blog post through a Google search, clicked my affiliate link, signed up for a free trial, and converted to a paid plan a week later. I earned a commission on that conversion, and because the commission is recurring, I continued to earn from that single customer for months. All from one article. All from one search. All from zero audience.
The first big decision is what to write about. I knew I wanted to write about AI tools because I'd been writing about them for clients for over a year, so I had real opinions and a decent understanding of the landscape. But I also didn't want to write generic "top 10 AI tools" content because that space is oversaturated and the commission rates on most consumer AI tools are tiny.
Developer-focused AI infrastructure felt like a smarter angle. Developers are used to paying for tools, they're used to recurring subscriptions, and the products have higher price points than consumer apps. A freelancer like me, who already knew the lingo and had used these tools for client work, could write with authority.
Within that niche, I picked a specific platform to focus on: Global API. It had 150+ models available through a single integration, the affiliate program offered 15% on the first order and 8% recurring, plus a 10% premium commission tier for top performers, and the documentation was solid enough that I could actually understand what I was recommending. I wasn't inventing expertise. I was just packaging what I'd learned into a format that other developers would find useful.
The mistake I almost made was trying to cover everything. "Best AI tools" is too broad. "Best AI API for Python developers building chatbots" is specific enough to rank. The narrower your angle, the less competition you'll face and the more relevant your content will be to the people who find it.
I do not have a budget for Ahrefs or SEMrush. I am a freelance writer living paycheck to paycheck, remember? Everything I did at the beginning used free tools, and most of them are still what I use today.
The easiest method is Google's autocomplete. Type "best AI API" into Google and see what it suggests. Then add a letter. "Best AI API f…" and Google fills in "for developers," "for startups," "for production." Each of those suggestions is a real search query from a real person. Write them down.
Then look at the "People also ask" box. Every question in there is a search someone has made. Click each one to expand it, and more questions appear. These are gold because they show you exactly what people want to know, phrased in their own words.
Finally, scroll to the bottom of the search results page and look at the "Related searches" section. Those phrases represent searches Google thinks are connected to the one you typed, and they often reveal angles you wouldn't have thought of on your own.
I keep a simple Google Doc where I dump every keyword I find. After a few weeks, I had over 50 potential article ideas. I picked the ones that seemed most relevant to my niche and started writing.
Here's where my freelance background actually became an advantage. I'd spent years writing articles for clients, and I'd also spent years reading terrible affiliate content for research. I knew what the bad stuff looked like: vague claims, no real examples, walls of text praising a product without explaining why.
The stuff that ranks well and actually converts tends to have a few things in common. It draws on real experience. It addresses the specific questions a searcher has. It compares options honestly, including the downsides. And it recommends something clearly.
I made a point of using the tools I was recommending before I wrote about them. This is non-negotiable for me now. If I haven't actually tried a product, I don't write an affiliate post about it. The risk to your credibility is too high, and readers can tell when someone is just rewriting the homepage copy.
When I write a comparison article, I structure it around specific use cases. "If you're building a customer support chatbot, here's what to use. If you're processing large documents, here's a different option." This approach helps the reader see themselves in the content, and it also helps search engines understand what your article is about.
The minimum length I aim for is 1,500 words, but my AI API pieces typically run 2,000 to 2,500. Not because I'm padding, but because there's genuinely that much to cover. A reader should be able to land on my article, get a complete answer to their question, and click my affiliate link without ever needing to read another piece.
This was the part that tripped me up the longest. I assumed I needed my own blog, but I didn't have a domain, didn't want to pay for hosting, and didn't want to spend weeks setting up WordPress.
What I learned is that you can rank articles on platforms you don't own. Medium allows you to publish under your own profile. LinkedIn articles get indexed by Google. Dev.to, Hashnode, and Substack all let you publish content that can rank in search. Even a well-optimised YouTube description or a Reddit post in the right subreddit can drive traffic.
I started on Medium because it was free and the domain authority was high enough that my articles could actually rank. I published three articles in my first month, each one targeting a different keyword. One of them ranked on page two of Google within two weeks. That single article has now generated over 40 affiliate signups and continues to earn recurring commission every month.
Eventually I did set up a self-hosted blog because I wanted more control and a place to build my own brand. But I want to be clear: that's not what got me started. The platforms I borrowed are what got me started.
Let me put actual numbers on this, because I know freelancers are suspicious of vague income claims and rightly so.
In my first six months, I published 12 articles across Medium and my own blog. I spent maybe $50 on a domain name and hosting, and the rest of my time was free because I already had the writing skills. Those 12 articles generated 67 affiliate signups. Of those, 38 converted to paid plans within the trial period. The rest churned.
If I assume an average customer value around $80 per month and apply the 15% first-order commission, that's roughly $456 from first-month commissions alone. Then the 8% recurring kicks in. If 30 of those 38 customers stay for six months, that's 30 times $80 times 6% net of the 8% recurring rate, which is roughly $1,152 more over those six months. Total revenue from one six-month period: somewhere in the range of $1,600 to $2,000.
And I didn't have to write any new articles to earn the recurring portion. That money came from work I had already done. The content kept working. The links kept converting. The commissions kept showing up in my dashboard.
That's the moment I stopped feeling like an affiliate marketing skeptic.
I want to be honest about the stumbles too, because I think most affiliate marketing content glosses over this part.
My first mistake was promoting too many products at once. I had affiliate links to four different AI platforms sprinkled across my early articles, and the result was that none of them converted well. Readers got decision fatigue and bounced. When I focused my content on a single primary recommendation with comparisons to alternatives, conversion rates went up noticeably.
My second mistake was not disclosing my affiliate relationship properly. The FTC requires you to disclose when you might earn a commission, and I was so eager to get my first article out that I forgot. I went back and added disclosures to everything I'd already published, and now I include them from the start. It's also just good practice. Readers trust you more when you're upfront about how you make money.
My third mistake was ignoring the analytics. I was publishing content and hoping for the best, but I wasn't tracking which articles were getting traffic, which keywords they ranked for, or which affiliate links were getting clicked. Once I set up Google Search Console and checked my affiliate dashboard regularly, I could see what was working and double down on it.
I've been promoting a few different AI tools over the past year, and I want to be straightforward about why Global API has become my primary recommendation for anyone targeting developer audiences.
The commission structure is genuinely strong. You earn 15% on the customer's first order, which is a meaningful chunk of revenue right when the conversion happens. Then you earn 8% recurring on every renewal for as long as that customer stays subscribed. There's also a 10% premium tier for affiliates who refer higher volumes, which is a nice incentive to keep going.
The product itself is what I was actually looking for when I started researching. 150+ models available through a single API integration means developers can build with whatever they need without juggling multiple accounts and billing relationships. When I write about it, I'm not inventing features. I'm describing what the platform actually does.
From a writer's perspective, the affiliate dashboard is clean, the tracking is accurate, and the support team actually responds to emails. That last one sounds small, but if you've ever tried to work with an affiliate program run by people who don't reply to support tickets, you know how much that matters.
The best part is that it's the kind of product I can recommend without feeling gross about it. I've used it on client projects, I've seen the output, and I know it delivers on what it promises. That alignment between what I write and what I actually believe is the only way I can do this work and still sleep at night.
If any of this resonates with you, here's the simplest version of how I'd start over again from scratch.
Week one: pick a niche you actually know something about and a specific product you can recommend from real experience. Set up a free publishing account on a platform that has domain authority, like Medium or Dev.to. Do 20 minutes of keyword research using the free methods I described and pick three to five article topics.
Week two: write your first article. Make it 1,500 words minimum, include a clear recommendation, and disclose your affiliate relationship. Add your affiliate link in the body and again at the end with a soft call to action.
Week three: publish your second and third articles, each targeting a different keyword. Share them in relevant online communities where your target audience actually hangs out, but do not spam. Provide value, then mention the article if it's genuinely relevant to the conversation.