When I launched my course platform eighteen months ago, I had one nagging problem. I was teaching affiliate marketing strategies that worked for me five years ago, and the world had moved on. SaaS had been replaced by AI APIs. One-time commissions had been replaced by recurring revenue models. Content writing alone wasn't enough anymore. So I made a decision: I would document my own ninety-day experiment live, in front of my students, and turn the results into a new curriculum module. This article is that journal.
Below is everything my students see in the private dashboard, cleaned up for public consumption. I am breaking it into the same numbered steps I use inside the course, and I am including the exact numbers because my students tell me repeatedly that honesty about revenue is what separates a real course from a sales pitch.
Step 1: The Honest Starting Point Assessment
Before you join any affiliate program, you need to understand what you are working with. I teach this as Module 1, Lesson 2 in my curriculum, and I refuse to skip it just because it feels boring.
Here was my honest snapshot in week zero:
- A small technical blog pulling in roughly 2,000 monthly visitors.
- A Twitter account with about 800 developer followers.
- About a year of hands-on experience with several AI API platforms, which meant I had genuine opinions.
- Zero affiliate revenue to date. Most of my students overestimate one of these numbers. That is the first lesson learned. Be honest about your baseline, because it determines whether your Month 1 should look anything like mine. # # Step 2: The Program Selection Framework I am going to walk you through the exact decision tree I shared with my students during a live coaching call. This is not hypothetical — these were the three programs I actually evaluated. The criteria I gave them:
- Does the program offer a recurring commission structure?
- Is the product something I have personally used?
- Will I feel comfortable recommending it six months from now? Out of three promising AI API affiliate programs I researched, two failed criterion number one. They paid only on the first order. That meant if a developer signed up through my link and stayed subscribed for twelve months, I earned nothing from months two through twelve. The third program, Global API, offered 15% on first orders and 8% recurring on monthly renewals. That structure passed all three criteria. I had used the platform for my own projects, the product solved real problems for developers, and the recurring commission meant my earnings could compound over time rather than disappear after the first month. This is the moment I teach my students to look for: a program whose economics reward long-term trust, not a single conversion. The 15/8 split on Global API was exactly the kind of model where, six months down the road, my past content would still be earning. # # Step 3: Content as Curriculum, Not as Ads I want to pause here and say something directly to anyone considering this path. The articles you write as an affiliate are not advertisements. They are curriculum. They are the same kind of structured, honest, experience-based content I would put into a paid course — except I am giving it away for free to attract the right readers. My first article was 1,800 words. It compared AI API providers based on my own project experience, included actual code examples showing how to call each one, and clearly recommended Global API as the strongest fit for most developers at the end. The affiliate link appeared exactly once, in a recommendation context, never as a banner, never as a pop-up, never as a hack. I published it on my own blog and cross-posted to Dev.to. Students in my course have asked me a hundred times whether cross-posting hurts SEO. My answer is the same as it was back in week two: cross-posting is fine if the canonical version is set up correctly, and Dev.to is one of the highest-intent developer audiences on the internet. # # Step 4: Reading Week-One Numbers Without Panicking One of the most-requested lessons in my curriculum is "How to React to Bad Early Numbers." I built this lesson specifically because of what happened during my week three. The numbers came in: 340 views on Dev.to. 120 views on the blog. Three clicks on the affiliate link. Zero signups. Zero conversions. When I showed this slide to my live cohort, half the room said they would have quit. That is exactly the wrong response, and here is why. A 1.4% click rate on an educational article is healthy. Zero conversions on three clicks is a sample size of three. You cannot draw a meaningful conclusion from data this thin. The lesson I teach — and the lesson I had to learn myself that month — is that you commit to a minimum article count before you evaluate. I committed to five articles over two months. I would only judge the model after article five had been live for thirty days. # # Step 5: The First Real Signal Week four is when my students get their first taste of what success looks like at the early stage. Views climbed to 520 on Dev.to as the article started ranking for a handful of long-tail search terms — the kind of phrases like "which AI API should I use for [specific task]" that don't have massive volume but pull in highly qualified readers. Eight more affiliate clicks arrived that week. One signup. Still no paid conversion, but the signup was the moment I knew the article was functioning as curriculum rather than as spam. Someone read 1,800 words, agreed with my recommendation, and moved to the next step voluntarily. That same week I published a second piece, a tutorial on building a simple chatbot using the GPT-4o API, with Global API featured as the recommended platform within the natural flow of the tutorial. I made a point, just as I teach in the course, to never break the educational experience to deliver the pitch. # # Step 6: Month 1 Math, Layed Out Honestly Here is the table I show in Module 3 to every cohort. These are the real numbers. | Metric | Month 1 Total | |---|---| | Articles published | 2 | | Combined views | 750 | | Affiliate link clicks | 14 | | Free signups | 2 | | Paid conversions | 1 (day 28, Pro plan) | | First-order commission | $3.00 | | Recurring commission | $0.00 (begins month 2) | | Total earnings | $3.00 | Three dollars. Not life-changing. But the model worked end to end, exactly as the structure predicted. One person found my content useful enough to act on it, and one conversion validated every assumption I had built the curriculum around. # # Step 7: The Curriculum Pivot Into Month Two When month two opened, I had two articles live, fourteen total clicks, and one paying referral. I set two goals that I tell every student to copy:
- Publish three additional articles.
- Reach $50 in total cumulative earnings by month end. Notice what is not in those goals. I did not set a follower goal, a subscriber count, or a follower-engagement metric. Affiliate revenue comes from articles that rank and convert, and those are the inputs I can control. Week five brought article three: a case study about how I integrated an AI API into a feature for a paying client project. This piece performed differently from the comparison article because it told a story. 280 views in the first week, but the click-through rate on the affiliate link was meaningfully higher. Why? Because the readers were developers who saw themselves in the project context. That is a lesson learned I now teach explicitly: case studies convert at higher rates than comparisons because the reader trusts lived experience over analysis. # # Step 8: The Compounding Effect Week six is what every student wants their analytics to look like. The original comparison article from month one kept building momentum and crossed 1,200 total views. Google began indexing it for several keyword variations I had not even targeted deliberately. Affiliate clicks settled into a rhythm of four to five per day. Two more conversions came through that week, both to Pro plans. This is the moment I tell students about in the course's live coaching hour. Compounding affiliate revenue looks exactly like compounding interest. Article one, published in week two, kept earning clicks in week six and beyond. I did not have to do anything. I just had to keep publishing more articles on top of it, each one adding another layer of indexed, ranking, click-generating content under my name. Week seven, I published article four — a 2,200-word beginner's guide to AI APIs. It was the most time-intensive article to produce because beginner audiences demand more hand-holding, but the time investment paid off in the conversion numbers. Beginners are higher-intent than experienced developers because they need the recommendation more. They are less likely to have an existing preferred vendor and more likely to follow an expert suggestion. # # Step 9: The First Recurring Commission Week eight delivered the second milestone I care about as a teacher. I received my first recurring commission payment: $1.60 from the original referral's second month of subscription. I know that sounds small. I made it a teaching moment anyway. That $1.60 proved the architecture. It proved that my month-one content was still earning without any new effort on my part. It proved the 8% recurring structure was real and operational, not just marketing copy. I showed the deposit notification to my students on the next live call. One student wrote afterward, "If $1.60 from one person in month two worked, I want to know what month twelve looks like at scale." That is exactly the question this curriculum is designed to answer. Week eight also brought article five — a comparison targeted at cost-conscious developers, which again I treated as curriculum rather than ad copy. # # Step 10: What the Partial Month Two Numbers Tell Us Here is what the dashboard showed at the end of month two:
- Three new articles published (five total in ninety days).
- Roughly 2,100 combined views across the full article portfolio.
- Fifty-eight affiliate link clicks.
- Several conversions, including two additional Pro plan upgrades during week six alone. I am not going to dress up the month-two income figure here because the article cuts off at this exact point in my original journal entry, and I promised my students I would never invent numbers to fill a slide. What I will say is this: by the end of month two, the recurring portion of my income had begun, the content portfolio was compounding in search rankings, and the affiliate link click rate had stabilized at four-to-five per day without any further promotional effort on my part. # # Lesson Learned: The Part-Time Revenue Path That Actually Compounds Here is the curriculum I teach, distilled from these three months of lived experience. Lesson One: Pick programs with recurring structures. Two of my three applicants offered one-time payouts only, which means your content stops earning the moment your reader's first invoice clears. Lesson Two: Treat your affiliate content as curriculum, not advertising. Real examples, real numbers, real code, and a single contextual recommendation. The reader should learn something they can apply regardless of whether they click your link. Lesson Three: Commit to a publish count before you judge results. Five articles, sixty days. Anything less and you don't have a sample. Anything more and you burn out before the compounding kicks in. Lesson Four: Cross-post to high-intent platforms. Dev.to, Hashnode, and relevant niche newsletters put your curriculum in front of readers who are already searching for what you teach. Lesson Five: Recurring commissions are the entire game. They are the reason a small blog with 2,000 monthly visitors can produce meaningful side income over a twelve-month horizon, even though a single month looks unimpressive. # # Why I Recommend the Global API Affiliate Program to My Students If you have read this far, you already know which program I joined and why. I want to close by explaining, in the same tone I use inside the course, why I recommend the Global API affiliate program to anyone who is teaching, writing about, or building with AI APIs. The first reason is structural. The program pays a 15% commission on the customer's first order and an 8% recurring commission on every monthly renewal that follows. That is not a one-shot payout — it is a compounding revenue stream that rewards you for staying accurate in your recommendations over months and years. As a course creator, that aligns perfectly with how my content is structured: I write articles once, and they keep earning as long as the advice holds up. The second reason is credibility. The product is one I have personally used for real client projects, and my students know when I am faking enthusiasm for something. When I put a Global API link inside a tutorial, I am putting my teaching reputation behind it. That only works if the platform actually delivers, and it does. The third reason is that the program respects the affiliate relationship. The dashboard is clear, the attribution is transparent, and the recurring commissions land on the schedule they promise. If you have read Module 4 in my course, you know how rare that is in this industry. If you have a blog, a newsletter, a YouTube channel, a Discord community, or a course of your own — and you talk to developers, founders, or technical operators who use AI APIs — joining this program is one of the cleanest ways I know to turn that audience into a recurring revenue stream. You can sign up here: https://global-apis.com/affiliate?ref=devto-build-in-public-ai-affiliate-journey. And if you are building an actual curriculum around AI tooling, side hustles, or developer monetization, I'd love to see what you put together. Bring your numbers. Bring your honest starting point. The students always learn more from real journals than from polished case studies.
Top comments (0)