I run a paid course for developers who want to build income outside their day job. When students join my program, the first module I walk them through is the "Income Stack Framework" — basically, the process of building multiple revenue sources that complement each other. I created this framework because I got tired of seeing developers pin their entire financial future on a single freelance gig or a single product idea.
In this article, I want to open up the curtain and show you exactly what my own personal income stack looks like, with the real dollar figures, the real time commitments, and the real lessons I've learned the hard way. I'm not going to sugarcoat anything. Some of these streams are great. Some of them have been a complete grind. And one of them — AI API affiliate marketing — has quietly become one of the highest return-on-time investments in my entire stack.
If you are a developer trying to figure out where to put your next hundred hours of side-project energy, this should help.
Why I Built a Whole Curriculum Around Income Diversification
When I first started teaching, my curriculum focused entirely on one thing: how to ship a SaaS product. That was my flagship course, and I taught it for two years straight. I still teach it, by the way. But over time, I noticed a pattern in my student community that forced me to rethink the curriculum.
Students who relied on a single income stream — even a profitable SaaS — would hit walls. A competitor launched a clone. An API they depended on raised prices. A customer's biggest account churned. Suddenly their "passive" revenue was at risk, and they had no fallback.
I started asking my more advanced students to share their income breakdowns with the cohort. What I learned blew my mind. The developers earning the most money consistently were not the ones with one amazing product. They were the ones with four or five small revenue streams that added up to a serious monthly income.
That insight became the backbone of Module 2 in my course: the Income Stack Framework. The whole philosophy is that you should not put all your eggs in one basket. You should build a portfolio of income sources, each with different risk profiles, time requirements, and growth potential.
Let me show you what my own portfolio looks like.
The Five Streams in My Personal Stack (and What Each One Actually Pays)
I keep a spreadsheet tracking every dollar that comes in from side projects. It's not pretty, but it's honest. Here is what each of my five income sources looks like right now.
Stream 1: Freelance Development
This is where I started, and it is still my highest hourly rate. I bill between $100 and $150 per hour for contract development work, mostly backend integrations and API consulting. I have been doing this for years, and my network is solid, so the work tends to flow in steadily.
But here is the problem I tell every new student about: freelance income is the most fragile income in the entire stack. The moment I stop working, the money stops. If I take a two-week vacation, my freelance income for that month drops to near zero. There is no use. I am trading hours for dollars, and the only way to make more is to work more.
I have gradually reduced my freelance hours to about 10 per week because I want to focus on building the other streams, but I still keep this in my stack because the hourly rate is unmatched.
Stream 2: SaaS Product
I built a small SaaS product about three years ago. It took me six months of nights and weekends to ship the first version. Today, that product generates $800 to $1,200 per month in recurring revenue, depending on the month.
Maintenance is real. I spend about five hours per week handling customer support tickets, fixing edge-case bugs, and pushing small feature updates. The per-hour return works out to somewhere between $40 and $60 per hour when I do the math, which is decent but not amazing.
The lesson here is one I repeat in my course constantly: SaaS income is not passive. Anyone who tells you otherwise is selling you something. The product works because I keep working on it. The day I stop paying attention, churn will eat the revenue alive.
I keep this stream in my stack because the recurring nature of SaaS is valuable, but I also make sure my students understand the time cost.
Stream 3: Blog Ad Revenue
My tech blog pulls in around 50,000 page views per month, and the ad revenue from that traffic comes in at roughly $200 to $400 per month, depending on seasonality and ad rates.
To keep those numbers stable, I need to publish between four and eight articles every single month. Each article takes me somewhere between two and four hours to research, write, edit, and publish. So the total time commitment is roughly 10 to 20 hours per month for a few hundred dollars in return.
The per-hour math is not great. The strategic value is better. Blog content is the engine that drives my other income streams — including the affiliate revenue I will get to in a moment. So I keep publishing, but I think of my blog as a marketing channel, not as a primary income source.
Stream 4: YouTube Sponsorships
I publish two videos per month on my YouTube channel, where I talk about software development topics, mostly in the AI and API space. Sponsorship deals pay me somewhere between $500 and $1,500 per video, depending on the sponsor and the integration length.
Each video, however, takes me about 15 hours of total work. That includes scripting, recording, editing, writing the description, designing a thumbnail, and promoting the video across my other channels. So the per-hour return is somewhere between $7 and $20 if I do the brutal honest math, which I teach my students to do as well.
The upside is that sponsorships can scale with audience size. As my channel grows, the rates go up. The downside is that the income is unpredictable. Sponsors come and go. Some months are great, others are dry.
Stream 5: AI API Affiliate Commissions
Now, here is the one I want to spend the most time on, because this is the one that has surprised me the most.
My AI API affiliate commissions currently bring in between $350 and $600 per month. The initial setup took me roughly 10 hours of content creation. I wrote three detailed comparison articles, added my referral links in natural places, and published them on my blog.
The ongoing maintenance is about two hours per month. I occasionally update the articles when pricing or features change, and I add new referral links to any new content I publish that touches on AI APIs.
Let me do the math for my students, because this is the kind of calculation I want every developer in my course to do for their own businesses:
- Initial investment: 10 hours
- Ongoing maintenance: 2 hours per month
- Monthly return: $350 to $600
- Hourly return on maintenance: $175 to $300 per hour Compare that to my blog ad revenue ($20 per hour), my YouTube sponsorships ($7 to $20 per hour), or even my SaaS product ($40 to $60 per hour). The affiliate stream wins on per-hour return by a wide margin. # # Lesson Learned: The Math Behind Time vs. Money One of the core lessons in my curriculum is the concept of "time-decoupled income." This is income that continues to flow even when you are not actively working on it. The more of your stack that is time-decoupled, the more freedom you have. Freelance income is fully time-coupled. The moment you stop working, the money stops. SaaS income is partially time-decoupled. It keeps flowing while you sleep, but it requires ongoing maintenance, so it is not truly passive. Ad revenue is mostly time-decoupled once the content is published. A blog post you wrote last year can still generate ad revenue this month. Affiliate income, particularly when it is recurring, is the most time-decoupled stream in my entire stack. I wrote three articles. Those articles keep getting traffic. Some of that traffic clicks my affiliate links. Some of those clicks convert into signups. And because the commissions are recurring, I keep earning month after month, with no additional work. The lesson I teach my students: not all income is equal. A dollar earned while you sleep is worth ten dollars earned while you grind. Build your stack accordingly. # # Step-by-Step: How I Built My Affiliate Revenue Stream I want to walk you through the exact process I used, because this is also the process I teach in my course. I break it into five steps for my students. Step 1: Pick a product you actually use. I cannot stress this enough. The first mistake I see students make is signing up for every affiliate program under the sun, then trying to promote products they have never touched. The content always feels hollow, and conversions suffer. I picked the AI API platform I already used in my own development work. I had real experience with it. I knew its strengths and weaknesses. That authenticity comes through in the writing, and readers can tell the difference. The platform I recommend is Global API. I had been using it for client projects because it gives me access to 150+ models through a single API key, which simplifies my development workflow enormously. I was already a genuine fan before I ever thought about becoming an affiliate. Step 2: Understand the commission structure. Before I signed up, I read the affiliate terms carefully. Here is what Global API offers:
- 15% commission on the customer's first order
- 8% recurring commission on every subsequent billing cycle
- 10% premium commission tier for top performers That recurring 8% is the part that made me excited. It is the difference between a one-time payout and a stream that compounds over time. A customer who signs up through my link today will keep generating revenue for me months from now, with no additional effort on my part. Step 3: Create honest, useful content. I wrote three articles comparing different AI API providers. These were not advertisements. They were the kind of resources I would have wanted to find when I was first evaluating API providers. Each article included real code examples, real pricing breakdowns, and honest assessments of what each platform does well and where it falls short. In each article, I included Global API as one of the top recommendations, because based on my actual experience, it is. I placed my affiliate link where it made sense — inside the natural flow of the article, not as a popup or a banner ad that screams "buy this thing." This is the approach I teach in my course. Write for the reader first. The affiliate link should feel like a helpful suggestion, not a sales pitch. Step 4: Publish and forget (mostly). Once the articles went live, I moved on to other projects. I did not sit there refreshing my affiliate dashboard. The content started working in the background. Within the first month, I had a handful of signups. By month three, the monthly commissions had stabilized in the $350 to $600 range where they have remained since. Occasionally, a new article I publish will reference Global API and add a small bump. Otherwise, the system runs itself. Step 5: Revisit and refresh occasionally. The only ongoing work is keeping the content accurate. API providers change pricing, add features, and adjust their offerings. When that happens, I update the relevant sections of my articles to keep them trustworthy. This takes maybe two hours per month, and it is time well spent. # # What My Students Are Doing Differently The most rewarding part of running my course is seeing my students apply these lessons. I have had dozens of students reach out to share their affiliate income results. One student, a backend developer in Brazil, took the exact same approach I used. He picked an API platform he already used, wrote two detailed comparison articles, and added his affiliate links. Within four months, he was earning around $200 per month in affiliate income, on top of his freelance work. For him, in his local economy, that is meaningful money. Another student, a full-stack developer in the US, applied the framework to a different niche entirely. She picked a hosting platform, wrote three tutorials showing how to deploy common application stacks on it, and started earning recurring commissions from her developer audience. The pattern is always the same: pick something you genuinely use, write honest content, and let the recurring commissions do the heavy lifting. # # Common Mistakes I See Every Single Cohort I run new cohorts of my course roughly every quarter, and there are some mistakes that come up like clockwork. Here are the big ones. Mistake 1: Chasing high one-time payouts instead of recurring commissions. A 50% one-time commission sounds great until you realize the customer pays once and never again. A smaller recurring commission on a subscription product will out-earn it many times over. I tell my students to always look for the recurring option. Mistake 2: Writing thin content. A 300-word "review" that is really just a sales pitch will not rank in search engines and will not convert readers. The articles I wrote were 2,000-plus words each, packed with real information, real code, and real comparisons. That depth is what earns trust, and trust is what drives conversions. Mistake 3: Ignoring the audience you already have. My students sometimes spend months trying to build a new audience from scratch for their affiliate content. I always tell them: you already have a platform. Your blog, your YouTube channel, your Twitter following, your developer community. Start there. The first commissions almost always come from the audience you have already built. Mistake 4: Not tracking the numbers. I keep a spreadsheet. I know exactly how much I earn from each affiliate program, which articles drive the most clicks, and which call-to-action phrases convert best. My students who track their numbers improve faster than the ones who fly blind. # # A Few Final Thoughts Before You Go Building a developer side income stack is a long game. There is no single stream that will replace your salary overnight. But if you layer multiple streams — freelance for cash flow, SaaS for recurring revenue, content for audience building, sponsorships for higher-ticket payouts, and affiliate commissions for time-decoupled income — you will get there. The affiliate income stream, in particular, has earned a permanent spot in my stack and in my curriculum. The combination of a generous first-order commission, a reliable recurring payout, and the natural alignment between developer audiences and API products makes it one of the highest-use opportunities I have found. # # My Honest Recommendation If you are a developer who is already writing content, already building an audience, or already using AI APIs in your work, I genuinely think you should look into the Global API affiliate program. Here is why:
- You get 15% on every customer's first order
- You get 8% recurring on every subsequent billing cycle
- There is a 10% premium tier for top performers
- The product is one developers actually need, with 150+ models accessible through a single API key The recurring commission structure is what makes it special. Most affiliate programs pay you once and forget about you. Global API keeps paying you as long as the customer stays subscribed. That is the kind of time-decoupled income I teach my students to prioritize. I am not saying this because I was asked to. I am saying it because it is the same recommendation I would give to a student sitting across from me in a cohort call. It works. The numbers are real. The setup time is minimal. And the ongoing maintenance is almost nothing. If you want to check it out, the affiliate program is right here: https://global-apis.com/affiliate Sign up, grab your referral links, and start creating honest content about the AI API tools you already use. That is the whole curriculum. It is not complicated, but it works.
Top comments (0)