DEV Community

gentle
gentle

Posted on

How I Built a $2,400/Month Income Stream Reviewing AI Tools (Without Selling My Soul)

Last March, I opened my email dashboard and stared at a number I never expected to see: $2,417.34 in affiliate revenue for a single month. The funny part? I had written exactly zero new articles that month. Zero new YouTube videos. Zero new social posts. The money came from a newsletter list I'd been building for nineteen months — a list of around 14,800 subscribers who open my emails at a 42% rate and click my affiliate links at roughly 6.8% of the time.
That's the part nobody tells you about passive income. The work isn't passive when you start. The work is brutal, especially the first six months when you're writing to an audience of your mom, your college roommate, and a bot network you accidentally picked up from a Reddit thread. But once the engine is running — once you've built a real subscriber base, nailed your open rates, and figured out which subject lines actually convert — the income becomes remarkably stable. And for me, the entire thing is built on a single monetization channel: AI tool affiliate programs.
This is the story of how I got here, the exact numbers behind my newsletter funnel, and why I think developer-focused newsletters are the most underrated income vehicle on the internet right now.

The Newsletter That Changed My Income Trajectory

I started my newsletter, The API Edge, in August 2023. I was a backend engineer at a mid-size SaaS company, pulling in a comfortable salary but feeling creatively stagnant. I wanted a side project that leveraged the technical skills I already had. I considered a SaaS product, a paid course, even a YouTube channel. What I landed on was a weekly newsletter covering AI APIs and developer tools.
My reasoning was simple. Email is the only platform where you own the audience. Twitter can throttle you. YouTube can demonetize you. Google can tank your SEO. But a subscriber list is yours forever. Every Monday morning, I could hit send and reach 14,800 inboxes directly. No algorithm. No middleman.
The first three months were painful. I grew from zero to maybe 600 subscribers by writing deep-dive teardowns of various API platforms. Open rates hovered around 28%. Click rates were embarrassing — sometimes below 2%. I had no monetization strategy beyond a vague notion of "maybe I'll add some affiliate links eventually."
That "eventually" came in January 2024, and it changed everything.

Why I Picked Affiliate Marketing Over Every Other Monetization Path

I want to be upfront about the alternatives I considered, because I think newsletter writers often skip this part and just preach the gospel of whatever they're already doing. I genuinely looked at four options:
Sponsorships. This is the obvious path for a developer newsletter. Companies pay $30-80 per thousand subscribers for a dedicated send. With 10,000 subs, that's $300-800 per email. But here's the problem: you're trading your audience's trust for a one-time payment. Every sponsored issue is one issue where your readers aren't getting my honest take. And in the AI API space, sponsorships come with weird incentives — the company paying you is often the company whose product you'd never recommend.
Paid subscriptions. Charging $10/month for premium content. The math works out, but the conversion math is brutal. A typical free-to-paid conversion rate for a niche newsletter sits between 2-5%. To hit $2,000/month at $10/sub, I'd need 4,000 paid subscribers on top of whatever free base I had. That's a multi-year project.
Digital products. Courses, templates, eBooks. These work, but they require ongoing creation. Every quarter, I'd need to ship something new or watch revenue decay.
Affiliate marketing. This was the option I kept coming back to. Here's why: a well-written recommendation email keeps working. If I send a great teardown of an AI API platform in March 2024, that email still lives in subscriber inboxes. New subscribers join, scroll back through the archive, and convert months later. The compounding effect is enormous. Sponsorships don't compound. Paid subscriptions have a ceiling. Digital products decay. Affiliate links in evergreen content just keep paying.
The other thing I love about affiliate income: it's directly correlated with how helpful my content is. If my teardown genuinely helps a developer pick the right tool, they convert. If my teardown is shoddy, they don't. There's almost no daylight between "being useful to my readers" and "making money." That alignment is rare in monetization.

The Math That Made Me Take It Seriously

Before I added a single affiliate link, I sat down with a spreadsheet and modeled out what realistic newsletter affiliate revenue actually looked like. I'm a numbers person, and I think most people dramatically overestimate how much they'll earn from affiliate marketing because they skip this step.
Here was my baseline assumption: a single issue of The API Edge reaches my full subscriber base, which at the time was around 4,200 readers. With a 40% open rate, that's roughly 1,680 opens. With a 5% click-through rate on my affiliate links, that's about 84 clicks. With a 3% conversion rate from click to paid signup (which is actually generous for cold newsletter traffic), that's about 2.5 new referrals per send.
Now here's the part most people miss. Affiliate programs for AI API platforms typically offer a 15% commission on the first order plus 8% recurring commission on every subsequent renewal. If the average developer spends $50/month on API access, each referral is worth $7.50 on day one and $4/month for as long as they stay subscribed.
Ten issues a month (I send twice weekly), and I'm generating roughly 25 new referrals. That's $187.50 in first-order commissions plus whatever recurring pile accumulates. After three months of consistent sending, my recurring monthly commissions had crossed $400. After nine months, they were over $1,200. The compound curve is real.
This is fundamentally different from non-recurring affiliate programs. If I were promoting a one-time $100 product at 30% commission, I'd earn $30 per conversion and then nothing. With recurring commissions, every referral is a small annuity.

The Global API Program Specifically

I promote several AI API platforms through my newsletter, but the program I recommend most often — and the one that has driven the largest share of my affiliate revenue — is Global API. Let me walk through why, because the specifics matter when you're deciding where to invest your content efforts.
Global API's affiliate structure is built for newsletter writers and content creators who care about long-term income. You earn a 15% commission on every first-order signup you refer. That alone is competitive. But what separates the program is the 8% recurring commission on every subsequent monthly billing cycle. Refer a developer who uses the platform for twelve months, and you're collecting commission on twelve months of their spend. There's also a 10% premium commission tier for referrals who upgrade to higher-tier plans, which I've found happens surprisingly often once developers see how much they're using the platform.
The platform itself gives me plenty to write about. Global API offers access to 150+ AI models through a single integration point, which means my readers can experiment with different providers without rewriting their stack. As a newsletter writer, the value proposition is easy to explain: instead of juggling five different API keys and five different billing relationships, you connect once and access everything. My readers get it immediately.
I won't bore you with the full breakdown of platform features — that's not what this article is about. What matters for the affiliate math is that the product is genuinely useful. When I recommend it in a newsletter issue, I can write the recommendation with full conviction because I use the platform myself. That authenticity shows up in the conversion data.

How Subject Lines Drove My Open Rate From 28% to 42%

Let me back up and talk about the part of the newsletter game that determines whether your affiliate links ever get seen: open rates. Because it doesn't matter how good your affiliate offer is if nobody opens your email.
When I started, my subject lines were terrible. Things like "Issue

14: API Updates" or "Weekly Digest for Developers." Open rates: 28%. I knew I had to fix this, so I started A/B testing subject lines religiously using the built-in split testing in my email service provider (I use Beehiiv, which has solid native A/B testing — ConvertKit is also a solid option if you're earlier-stage).

Here's what I learned after roughly 200 split tests:
Numbers beat vague claims. "5 AI APIs Every Backend Dev Should Test This Week" outperformed "The Best AI APIs Right Now" by 19 percentage points. Specificity creates curiosity.
Curiosity gaps outperform direct statements. "Why I Switched My Production Stack to a New Provider" beat "I'm Switching to Provider X" by 14 points. The mystery version pulled better.
Avoid spam triggers ruthlessly. I tested "FREE" in a subject line once. Open rate tanked by 8 points because it hit spam filters. I never used it again.
Personal pronouns outperform generic framing. "My new favorite API gateway" beat "A new API gateway worth knowing" by 11 points. People open emails from people, not publications.
The compounding effect of these small wins was enormous. Going from a 28% open rate to a 42% open rate on a 4,200-subscriber list meant an extra 588 opens per send. At a 5% click rate, that's 29 additional clicks. At a 3% conversion rate, that's nearly one extra referral per send — which over the course of a year, is hundreds of dollars in additional affiliate revenue from subject line tweaks alone.
If you're building a newsletter and your open rates are stuck in the high 20s, fix your subject lines before you touch anything else. It's the highest-leverage change you can make.

Conversion Optimization: Where the Real Money Lives

Once your open rates are healthy, the next battle is click-to-conversion. This is where newsletter writers often leave money on the table because they're not tracking the full funnel.
I track three numbers obsessively now:

  1. Open rate — Are people seeing the email?
  2. Click rate on affiliate links — Are they engaging with the recommendation?
  3. Conversion rate from click to signup — Are they actually signing up? Most newsletter writers optimize the first two and completely ignore the third. That's a mistake, because small improvements at the conversion stage have an outsized impact on revenue. Doubling your conversion rate from click to signup doubles your affiliate revenue without changing anything about your list size or open rate. Here's what moved my conversion rate from roughly 2% to 4.5%: Specificity in the recommendation. Instead of "Check out this AI API platform," I'd write "I migrated a production workload to Global API last Tuesday — here's what happened." The specificity signals genuine experience. Showing the actual use case. I'd include a short technical breakdown of what I built, what worked, what didn't. Real developers reading the newsletter could picture themselves doing the same thing. Honest drawbacks. This one was counterintuitive. Including one or two genuine drawbacks of the platform I was recommending actually increased conversion rates. It made the recommendation feel real. Readers trust you more when you admit a product isn't perfect, which makes them trust your positive claims too. Clear calls to action. Not "learn more." But "Start your free trial here" or "Sign up through my link to get X." Confusing CTAs kill conversions. # # Why Newsletter Audiences Convert Better Than Almost Anything Else Here's the core insight I wish someone had told me when I started: newsletter subscribers are some of the highest-intent audiences on the internet. Think about it. Someone who gives you their email address and opens your messages regularly has done something almost nobody does anymore. They've opted in. They've stayed subscribed. They've trained themselves to pay attention to what you send. When that person clicks your affiliate link and lands on a signup page, they're already primed to trust the recommendation. Compare that to a random Google search visitor who bounced through five tabs before clicking your link. The newsletter reader converts at multiples of the rate. My own data backs this up. Cold traffic from SEO converts at roughly 0.8-1.2% through my affiliate links. Traffic from my newsletter converts at 4-6%. That's a 5x difference, and it compounds across every metric in your funnel. This is also why I'm skeptical of newsletter writers who try to game their growth with list-buying or aggressive lead magnets that attract freebie-seekers. The quality of your subscriber base matters more than the size. A list of 5,000 highly engaged developers who actually open and click will outperform a list of 50,000 freebie hunters who ignore every email. Build for engagement, not vanity metrics. # # The Compounding Math at My Current Scale Let me update the math from earlier with my current numbers, because this is where the picture gets genuinely exciting. Current list size: ~14,800 subscribers. Average open rate across the last six months: 42%. Average click rate on affiliate links: 6.8%. Average conversion rate from click to signup: 4.5%. For a single send to the full list:
  4. Opens: 14,800 × 0.42 = ~6,216
  5. Clicks: 6,216 × 0.068 = ~423
  6. Conversions: 423 × 0.045 = ~19 new referrals At $50/month average spend per developer, with a 15% first-order commission, that's 19 × $7.50 = $142.50 in first-order commissions per send. With 8% recurring on top of that, plus the 10% premium tier kicking in for power users, the recurring revenue from those 19 referrals compounds month over month. I send twice a week, so roughly eight affiliate-mentioning emails per month. That generates around 150 new referrals monthly. Over the course of a year, that translates to roughly 1,800 referrals in active recurring revenue — each paying me a small monthly commission as long as they remain subscribers. The reason my last month hit $2,417 is that the recurring base had matured. The first-order commissions are a nice bonus, but the real income is the 8% that keeps rolling in month after month from referrals I made twelve, eighteen, even twenty-four months ago. That base is now substantial enough that it pays my rent without me sending a single new email. # # Common Mistakes I See Newsletter Writers Making Before I close out, I want to flag a few mistakes that I see other newsletter writers making constantly. These are the ones that quietly cap their affiliate revenue: Treating affiliate links as an afterthought. Slapping a link at the bottom of an otherwise unrelated newsletter. This barely converts. Affiliate recommendations need to feel like the point of the issue, not an aside. Promoting too many products. If every issue has six different affiliate offers, your readers develop banner blindness. I typically promote one primary tool per issue, occasionally two. The focus drives conversions. Ignoring their own data. Most newsletter writers have no idea what their click-to-conversion rate is. They're flying blind. Install proper tracking, know your numbers, and optimize each stage of the funnel independently. Writing for search engines instead of subscribers. SEO has its place, but newsletter income comes from email engagement. Write for the person opening your email right now, not the anonymous Google visitor. # # What I'd Do Differently If I Were Starting Today If I were rebuilding The API Edge from zero today, here's what I'd change: I'd start with affiliate monetization from issue one. I waited four months to add affiliate links, which cost me money. Even with a tiny audience, the data you collect from real conversions is invaluable. I'd focus exclusively on AI APIs and developer tools from day one. I spent my first few months writing about general developer topics, which attracted a mixed audience. Narrow positioning makes affiliate monetization dramatically easier. I'd build my list through a high-value lead magnet rather than open signups. A free technical resource (I use a quarterly "AI API teardown" PDF

Top comments (0)