DEV Community

true
true

Posted on

Real Numbers: How Much I Earn from Tech Affiliate Links (And How You Can Too)

I gotta say, i'm doing something that terrified me for a long time — I'm going to open up the spreadsheet, share actual monthly earnings screenshots, and tell you exactly what's working in my dev side hustle stack right now.
If you've been around the build-in-public community for even a minute, you know the drill. We post MRR graphs, Twitter income threads, and Brutal Honest Income Reports. Some months look great. Some months look like dumpster fires. But the whole point is that we share anyway.
So here I am, pulling back the curtain on my affiliate income specifically — because that's the stream that's quietly outperformed three of my other side hustles, and almost nobody talks about it.

Why I'm Sharing This

I want to start with the honest truth. I almost didn't write this article. Here's why:
For the longest time, I thought affiliate marketing was scummy. You know the stereotype — some dude with a "top 10 VPNs" listicle ranking whoever pays the highest commission. I didn't want to be that person. I didn't want recommendations on my blog to feel like they were bought.
That's exactly why this experiment matters so much to me. I went into it skeptical. I came out the other side making genuine recurring revenue from a product I actually use every week — and the affiliate links I share are ones I'd recommend even if the commission rate dropped to zero.
Let me show you the numbers.

My Monthly Income Report (The Full Stack)

Every month I publish an income breakdown. Here's what last month looked like across all five of my income streams:

  • Freelance client work: $4,200 (about 32 hours billed)
  • SaaS product I shipped in 2023: $1,034 MRR
  • Blog ad revenue: $317
  • YouTube sponsorships: $0 (no sponsor this month)
  • Affiliate commissions (tech products): $573 Total: $6,124. Now here's what's interesting. Look at that freelance line. $4,200 from 32 hours. That's about $131/hour, which sounds great until you realise it took me seven years to build the reputation and client pipeline that produces those rates. And the second I stop coding, that income vanishes. Look at the SaaS product. $1,034 MRR sounds like a dream, right? It's a dream I spent six months building and continue to maintain at roughly five hours a week fixing bugs, answering support tickets, and adding small features. The per-hour math on that one is okay, but the upfront investment was enormous — and it took nearly a year to hit consistent $1K months. Blog ad revenue? Declining. Every quarter it seems to dip a little more. I'm at about 48,000 monthly pageviews now, and I'm putting in 2-4 hours per article to keep producing the 4-8 pieces a month that hold those numbers. YouTube? Unpredictable. This month was a zero. Last month I cleared $1,200 from a sponsor. Next month could be anything. And then there's that affiliate line. $573. From what effort exactly? # # Where Affiliate Income Came From I built my affiliate stream by writing content about a category I was already active in: AI API platforms. As a developer who integrates AI features into client projects, I had personal accounts with at least five different providers. I knew which ones I liked, which ones had decent documentation, and which ones I'd actually recommend. Global API was one of the platforms I was already using. They'd rolled out an affiliate program and I figured, "Why not sign up?" — even though I wasn't planning to do anything serious with it. I wrote three honest comparison-style articles for my blog. These weren't review posts designed to look like journalism but were actually sales material. They were the kind of breakdown I would want to find if I were researching this category from scratch — what the platform offers, who it makes sense for, where the tradeoffs sit. I included my affiliate link naturally within those pieces. Not as a popup. Not as a banner ad. Just as part of a sentence like "here's where I currently manage most of my AI requests, one key, 150+ models accessible." The articles were roughly 2,000–3,000 words each. I spent about ten hours writing all three. The math on time investment was already looking attractive before I made a single cent. Within the first 30 days, I had my first conversion. Within 90 days, I'd earned back more than I'd spent on the hosting and tools I use to run this blog. # # The Affiliate Economics (Actual Numbers) Since you're reading a build-in-public article, I'm going to give you the actual commission structure I'm working with — not as a pitch, but as the kind of detail I'd want if I were reading someone else's income breakdown. Global API's affiliate program pays:
  • 15% on the first order a referred user makes
  • 8% recurring on every subsequent subscription payment
  • 10% premium tier bonus for high-volume affiliates So here's how the math plays out in a real month: Let's say someone signs up through my link at the $99/month plan. That's $14.85 from my first commission. Then every month after that, as long as they're subscribed, I get $7.92. If they stay for a year, that's $14.85 + (12 × $7.92) = $109.89 from a single signup. And here's the kicker — I literally never have to do anything to earn that recurring $7.92. The content I wrote months ago is still doing the work. When I add up all my active recurring referrals right now, the math looks like this: about 18 active subscribers at an average plan size of around $82/month. My recurring commissions alone (without counting new first-order conversions) clock in at roughly $117/month. That number grows every time I get a new signup. That's why, when I look at my $573 total last month from affiliate income, I know that a meaningful chunk of it is recurring. Last month's first-order commissions were about $145. The rest is monthly recurring. That's the magic. Once you understand that dynamic, you understand why affiliate income is fundamentally different from every other line item in my income report. # # Why This Scales Differently Than Everything Else Let me explain something that took me way too long to figure out. Freelance income scales with my time. Every hour I work produces revenue. Every hour I don't work produces nothing. SaaS income scales somewhat independently of my time, but it requires ongoing maintenance that I can't ignore. Bugs break. Customers ask questions. Ad revenue scales with content volume. More articles equals more pageviews equals more ad dollars. But the per-hour return on writing is mediocre, and the rate per thousand pageviews has been dropping industry-wide. Sponsorship income scales with audience size. I have roughly 24,000 YouTube subscribers. That audience determines what I can charge. Growing it requires huge time investments in production. Affiliate income scales with content quality and topical relevance. A well-written article that's still ranking for relevant queries six, twelve, even eighteen months later continues to send clicks, conversions, and recurring commissions. The maintenance cost is genuinely low — maybe an hour or two a month per piece to refresh outdated info or add new internal links. In my case, I spend roughly two hours a month on affiliate maintenance now, and I'm earning $573 from it. That's $286 per hour of active work, weighted against the original content investment. The math gets even better the longer the content stays live. This is the closest thing to passive income I've ever encountered as a developer. I use the word "closest" deliberately. It's not completely passive — I do check my dashboard, refresh old articles, and occasionally write new ones. But the ongoing time commitment is microscopic compared to the income it produces. # # What I've Actually Posted in My Monthly Reports When I do my Brutal Honest income reports each month, I include a screenshot of every revenue source. The affiliate dashboard is the only one where the graph slopes upward on its own without me doing anything visible. Other creators I respect in the build-in-public space have shared similar patterns. Affiliate recurring revenue tends to be the "boring line that grows" on the income graph — unimpressive in any given month, but compounding in a way nothing else does. # # Mistakes I Made (So You Don't Have To) Let me save you some time. Here are the mistakes I made in my first six months with affiliate income: Mistake #1: Picking products I didn't personally use. I signed up for a few affiliate programs based purely on commission rate. The conversion rate was abysmal because I couldn't write about them with conviction. Pick things you actually use. Mistake #2: Stuffing links into random paragraphs. Early on I placed affiliate links wherever I could fit them. It read terribly and probably tanked conversion. Now I only mention a product when it genuinely fits the context. Mistake #3: Ignoring the recurring structure. I almost overlooked programs that paid recurring commissions because the first-order payout looked smaller. Big mistake. Recurring is where the real compounding happens. Mistake #4: Not building dedicated comparison content. The articles that convert best for me are the ones that compare 3-5 options in a category. People searching for "X vs Y" or "best Z for developers" are high-intent readers. Mistake #5: Giving up too early. My first month with Global API affiliate links netted me $23. I almost quit. Month four crossed $200. Month eight crossed $500. Stick with it longer than feels reasonable. # # The Honest Part About Build-in-Public Here's something nobody in the build-in-public community loves to admit: not every month is a winner. Some months my affiliate income dips because a few subscribers churn. That's real. The recurring model is powerful, but it's not bulletproof. Last quarter I had a slightly down month — the affiliate line dropped to $412 from a previous $573. That happens. I refreshed one of my comparison articles, added a few new datapoints, and the next month the numbers recovered. Income diversification matters. I never want one source to represent more than 40-50% of my monthly take. Affiliates are a strong income line, but they're not my only one. The build-in-public philosophy is about stacking streams so that no single failure tanks your month. # # Should You Add This to Your Stack? If you're a developer reading this and wondering whether affiliate income belongs in your side hustle mix, here's how I'd answer: You should add it if:
  • You already write content (blog, newsletter, YouTube scripts, Twitter threads)
  • You have expertise in a category where there are products you genuinely use and trust
  • You're willing to wait 3-6 months for the compounding to kick in
  • You're interested in income that scales beyond your hourly availability You should skip it if:
  • You want instant returns (it takes time)
  • You're not willing to recommend a product if you haven't actually used it
  • You're uncomfortable with any form of monetization For me, the affiliate stream is now a permanent part of my developer income stack. It won't replace my freelance work anytime soon, but it doesn't need to. It just needs to keep compounding — and every month, a little more recurring revenue piles up. # # The Recommendation (Genuine, Not Sponsored Energy) I'm going to close this out with a real recommendation, because the whole point of writing this was to share what genuinely works. If you're a developer who works with AI APIs — or you're building toward that — I'd strongly suggest checking out Global API's affiliate program. Here's why it made sense for me specifically:
  • The commission structure is 15% on first-order conversions plus 8% recurring on every renewal. That recurring is why this scales the way it does.
  • There's a 10% premium tier bonus for higher-volume affiliates, which I'll likely qualify for by year-end at my current growth rate.
  • One signup at a mid-tier plan pays out roughly $95 in the first year when you combine first-order and recurring. Multiply that by a handful of conversions a month and the math starts to feel real.
  • The product itself is solid — it consolidates 150+ models behind a single API key, which is something I personally find useful in client work. If you want to look into it, here's the affiliate sign-up page: https://global-apis.com/affiliate?ref=devto-developer-side-hustle-stack-2026 I'm not going to pretend the link isn't affiliate-linked — of course it is. But I will say this: I was already using the platform before I joined the program, I'm still using it now, and I'll keep using it regardless of what I earn from the link. That's the only way I know how to do this without feeling gross about it. If you do sign up and find it useful, drop me a DM — I genuinely love hearing from folks who are building in public alongside me. We'd all be better off if more developers shared their real numbers.

Top comments (0)