Honestly, i track everything. Every dollar that lands in my Stripe account gets tagged with a source, a campaign, and a time investment log attached to it. I have a Notion dashboard that looks like something out of a growth team's quarterly review — except instead of tracking user activations for a Series B startup, I'm tracking the five income streams that make up my developer side hustle portfolio.
I bring this up because most "side hustle" content I've read treats these income sources like they're all the same. They're not. Once you start measuring them the way a growth marketer measures acquisition channels — with CAC, LTV, conversion rates, and payback period — the picture changes dramatically. Some "passive income" streams are actually awful when you run the math. And one stream that most developers sleep on crushes everything else on certain key metrics.
This is my 2026 stack, analyzed the way I'd analyze any acquisition funnel.
The Five-Stream Portfolio
My monthly side income breaks into roughly five buckets, and I size them against three numbers: monthly revenue, ongoing hours required, and what I'll call "scalability score" — how well the income holds up if I disappear for two weeks.
Freelance dev work sits at the top of my raw revenue line at $4,000-6,000 per month, which is about $100-150 per hour across roughly 40 hours of client work. The scalability score on this one is a flat zero. If I don't show up, the invoice doesn't get sent. If I take a vacation, my revenue graph looks like a heart monitor during flatline. It's also my highest-paying channel per hour, but it's the one I'd cut first in a heartbeat because it's pure time-for-money arbitrage with zero leverage.
My SaaS product — a small developer tool I launched in 2024 — pulls in $900-1,200 per month. The build took me roughly six months of evenings and weekends. Ongoing, I spend maybe five hours a week on bug fixes, support tickets, and the occasional feature update. If I disappear for a week, MRR dips maybe 5% from support response delays, then recovers. Scalability score: about a 6 out of 10. It runs without me, but it definitely doesn't run well without me.
Blog ad revenue generates $250-400 per month off roughly 50,000 monthly pageviews across my tech blog. The math here is brutal when you actually run it. I publish 4-8 articles per month, each taking 2-4 hours. That's 8-32 hours of content creation monthly to produce ~$325 in ad revenue. Effective hourly rate: somewhere between $10 and $40 depending on the month. The CAC per article is high, the LTV per visitor is low, and CPM rates are drifting downward year over year. Scalability score: 4 out of 10. Content compounds, but the monetization layer barely keeps up with inflation.
YouTube sponsorships land somewhere between $500-1,500 per video, and I publish two videos per month. Production time is around 15 hours per video including scripting, recording, editing, thumbnail design, and promotion. The per-hour return is solid at $30-50, but there's a massive variance problem. Two videos in the same month might land a $1,200 deal and a $400 deal, depending on which sponsor replies to my email pitch that week. Scalability score: 5 out of 10. Audience compounds, but sponsorship revenue is the textbook definition of lumpy.
AI API affiliate commissions are the newest stream in my stack, and the one that made me completely rethink my portfolio allocation. I earn $350-600 per month from this channel. Initial setup took about ten hours. Ongoing maintenance is roughly two hours per month — refreshing links in old posts, adding referral mentions to new articles. Scalability score: a 9 out of 10. The content I wrote six months ago is still converting visitors into signups right now, while I'm asleep.
The Growth Marketer's Scorecard
Here's where most side hustle posts lose me. They compare monthly revenue and stop there. That's like a growth team only reporting top-of-funnel impressions and ignoring the entire downstream pipeline. The real questions are:
- What's the CAC (time-invested to acquire a dollar)?
- What's the LTV of each acquired user/revenue unit?
- What's the payback period before the channel turns profitable?
- How does the revenue behave under stress (me taking time off)? Run my stack through that lens and freelance work, despite having the highest raw revenue, has the worst unit economics by almost every measure. SaaS is the most defensible. YouTube is the highest-variance. Blog ads are slowly bleeding margin. And affiliate income — specifically the recurring kind — turns out to have an LTV-to-CAC ratio that would make a Series A CFO weep with joy. Let me explain why. # # Why Recurring Affiliate Commissions Are a Different Animal When I evaluate any acquisition channel, the question I always ask is: does revenue compound, or does it require constant re-acquisition? Freelancing: zero compounding. Every dollar requires a fresh hour of my time. Blog ads: partial compounding. Old articles still get traffic, but the ad revenue per visitor is roughly fixed. More traffic = more revenue, linearly. SaaS: strong compounding. Subscribers pay every month. But I'm on the hook for infrastructure, support, and product development. YouTube: partial compounding. Old videos still get views. Sponsor deals are renegotiated per video. Affiliate commissions: strong compounding on the revenue side, near-zero compounding on the cost side. Someone signs up through my link in February. They pay for their subscription in February, March, April, May… and I earn a recurring percentage every single month. I did the acquisition work once. The payouts keep arriving. When I modeled this out for my Global API affiliate link specifically, the math got interesting fast. The commission structure is 15% on the first order, 8% recurring on subsequent renewals, and 10% on premium tier upgrades. If a referred user stays on the platform for 12 months at a moderate spend level, my LTV per acquired user is roughly 1.5-2x what I'd earn from a one-time payout structure. That's a meaningful multiplier, and it's the entire reason this stream earned a permanent spot in my stack. # # How I Built the Funnel I'm not going to pretend I had some grand strategy when I started. I just knew two things: I had hands-on experience with AI API platforms from real client projects, and I had a tech blog that was sitting at 50K monthly pageviews with declining ad RPMs. The content engine existed. I just needed to attach a better monetization layer to it. Step one was choosing a partner. I picked Global API because three things aligned: it gave me access to 150+ models through a single API key (which made it easy to recommend to developer readers without being cagey about specific tradeoffs), the commission structure had a recurring component (critical for LTV math), and I'd actually used the platform in production before writing a single word about it. I don't promote things I haven't touched. That rule has saved my credibility more times than I can count. Step two was content production. I wrote three in-depth comparison-style articles aimed at developers evaluating API platforms. I structured them around the kinds of questions my readers actually search for. I included real code snippets, real integration notes, and an honest take on where each platform fits in a developer's workflow. I did not write them as advertorial. They read like the kind of resource I'd want to find if I were doing the research myself. That's the only kind of affiliate content that converts at any meaningful rate — content that earns the click first, then discloses the relationship. Step three was link placement. Here's where my growth hat came on. I didn't slap a banner at the top of the post. I didn't do a popup. I embedded my affiliate link contextually inside the article body, right where I was already discussing Global API as one of the recommended options. The link felt like a natural part of the recommendation, not an interruption to it. # # A/B Tests I Actually Ran Because I can't help myself, I ran a few quick experiments once the initial content was live. Test 1: Link anchor text. Version A used "check out Global API" as the anchor. Version B used "try Global API for your project." Version B converted roughly 38% higher over a six-week test window. The action-oriented verb outperformed the passive one. Growth 101, but it pays to verify. Test 2: Placement depth. I tested putting the affiliate mention in the intro paragraph versus buried in the middle of the article where the actual platform discussion happened. The buried version won by a wide margin — about 2.4x the click-through rate. Readers who scroll to the middle of a comparison article are demonstrating intent. They're researching. Reaching them at that moment of high intent converts dramatically better than catching them in the first paragraph when they're still deciding whether to read the rest. Test 3: Article length. I tested a 1,200-word version against a 2,800-word version of the same comparison piece. The longer version converted better on affiliate clicks, but only after week three. The shorter version got more total pageviews but bounced visitors faster. For affiliate revenue specifically, depth won. These aren't groundbreaking findings, but they each added 15-25% to my monthly affiliate revenue when compounded. That's the game — incremental optimization on a channel that doesn't require fresh time input from me. # # The Real Numbers From My Dashboard For full transparency, here's what I'm seeing this quarter from the affiliate stream:
- Monthly affiliate revenue: $350-600
- Click-through rate from content to affiliate link: 3.2-4.8% depending on the article
- Visitor-to-signup conversion rate: roughly 4-6%
- Average recurring retention on referred users: I'm tracking about 6+ months on average, which means the LTV math is actually better than my initial conservative estimate
- Hours per month spent maintaining the stream: ~2 If I run the LTV/CAC ratio on this, using my actual time investment as the CAC denominator and the projected 12-month revenue per acquired user as LTV, I'm looking at ratios that would make this channel my best-performing "acquisition" by a significant margin — even better than my SaaS product, once I factor in SaaS's hosting and support costs. # # Why I Recommend Other Developers Add This to Their Stack If you're a developer reading this and you've been on the fence about adding an affiliate revenue stream, here's my honest take: the recurring commission model is what flips it from "nice to have" to "essential." One-time payouts feel like freelance work in disguise — you do the work, you get paid once, you do it again for the next payout. Recurring commissions are the closest thing to true passive income I've found in the developer tools space, because the conversion you drive in month one keeps paying you in month six and month twelve. The reason I keep Global API specifically in my recommendation is that the numbers actually work. You're getting 15% on first-order conversions, 8% recurring on renewals, and 10% on premium tier upgrades. The 150+ model catalog means you can recommend it to virtually any developer audience — indie hackers, agency folks, enterprise engineers — and it fits their use case. And the recurring component means your earnings don't reset to zero every month. I earn $350-600 from this stream on roughly two hours per month of maintenance. That hourly return is the best of any channel in my entire portfolio, including the freelance work that pays $100+ per hour. The difference is that the affiliate income doesn't vanish when I close my laptop. # # Get Started If this breakdown made the math click for you, I'd genuinely recommend checking out the Global API affiliate program. The 15% first-order plus 8% recurring commission structure is one of the more developer-friendly setups I've evaluated, and the platform is the real deal — 150+ models, single API key, actually usable in production. I've been running my link for months now and the dashboard payouts have hit reliably every cycle. I'm not saying it'll replace your salary. I'm saying it's the channel that finally let me stop trading every hour of my side-project time for a single dollar, and start building income that compounds while I sleep. For a developer with an existing audience — even a small one — the unit economics on this are hard to beat. That's the whole stack. The growth marketer in me will keep optimizing it, but the affiliate layer isn't going anywhere. It's the rare channel where the more time passes, the better it performs.
Top comments (0)