I have a Notion page that I treat like a religion. Every dollar that hits any of my side income accounts gets logged within 48 hours. Every hour I spend on side work gets tracked with a timer. I've been doing this for about 18 months now, and last weekend I sat down to figure out which of my income streams are actually worth the effort. Some of the results surprised me. One of them — tech affiliate marketing — has quietly become my favorite line on the entire sheet.
Let me break this down the way I'd break down a production cost analysis. We're going line by line, and I'm going to show you the real numbers, not the polished LinkedIn version.
The Five Streams Running Through My Spreadsheet
Right now I have five distinct income sources. They're all developer-friendly, and they all run alongside my day job as a backend engineer. Here's the full picture.
Freelance contract work. This is the obvious one most devs try first. My hourly rate sits at $120 (I round to that for easy math). On a good month I'll bill maybe 40-50 hours of freelance work on top of my full-time job. That's $4,800-6,000 per month. Sounds great until you do the time math. Forty hours of freelance on top of a 40-hour day job means I'm working 80-hour weeks. My per-hour return is solid, but my quality of life is trash. I capped freelance at 50 hours per month because anything more and I start making mistakes in my day job code. And here's the brutal part — if I get sick, take a vacation, or just don't feel like opening my laptop on a Saturday, that income hits zero. This is a time-for-dollars equation with zero use.
The SaaS tool I built. A niche scheduling product for small dental clinics. MRR hovers between $800 and $1,200 depending on the month. Sounds nice, but let me show you the build cost. I spent roughly six months of weekends and evenings getting it to a launchable state. If I amortize that build time at my freelance rate, the product "cost" me about $28,000 in opportunity cost. Now it needs maybe five hours per week for support tickets, bug fixes, and the occasional feature request. The per-hour return on the maintenance side is decent — somewhere around $40-60 per hour when you divide MRR by monthly hours invested. But the upfront capital (time capital) was enormous. I'd need to keep this product running for years just to break even on what I spent building it.
Display ads on my tech blog. About 50,000 monthly page views generate somewhere between $200 and $400 per month, depending on the season and which programmatic ad network is having a good quarter. To keep those page views flowing, I need to publish between four and eight articles per month. Each article eats 2-4 hours of my time (writing, editing, screenshots, SEO). Let's do the math: six articles at three hours each is 18 hours per month to maintain that $300 average. That's roughly $17 per hour. Worse than freelance. And the ad rate has been declining year over year as more advertisers pull back from programmatic display.
YouTube sponsorships. I get $500-1,500 per sponsored segment depending on the brand. I push out two videos a month, and each one takes about 15 hours of total production time (scripting, recording, editing, thumbnail, promotion). At one video per month with a $1,000 average sponsor, my per-hour rate looks like roughly $33. Not bad. The catch? Sponsorship income is wildly inconsistent. Some months I get three inbound requests, other months I get none. I never know what I'm going to earn, which makes it impossible to budget around. I treat it as bonus money.
Tech affiliate commissions. This is the new kid on the block in my stack, and it's the one that made me want to write this article. Current run rate: $350-600 per month, and trending up. Initial content investment: roughly 10 hours of writing and linking. Ongoing maintenance: maybe two hours per month updating articles, refreshing links, adding new comparison pieces. Let me do the per-hour math on this one. I'll use a conservative 12-month average: $475 per month. Total hours invested across those 12 months: 10 (initial) + 2 per month (24 hours) = 34 hours. So $475 × 12 = $5,700 / 34 hours = $167 per hour. That's higher than my freelance rate, and most of those hours were spent in month one. The pure maintenance cost is more like $237 per hour if you just look at the ongoing work. Here's the part that still feels weird to type: this income keeps coming in even when I'm on a beach in Portugal not thinking about it at all.
Why Affiliate Income Is the Line I Keep Staring At
Let me explain the framework I use for evaluating side income, because I think a lot of devs get this wrong. I score every income stream on three axes: time intensity, use, and durability.
Time intensity is just hours per dollar. Freelance is high time intensity. Display ads are high time intensity. SaaS maintenance is medium. Affiliate income is low — once the content is up, the clock stops ticking on most of it.
Leverage means how well the income scales independently of your direct effort. Freelance has zero use. The minute you stop coding, the money stops. Display ads have moderate use because old content keeps earning. SaaS has high use once built. YouTube has moderate use. Affiliate income — specifically recurring affiliate income — has the highest use of anything in my stack. A blog post I wrote in February can still be earning me commissions in November.
Durability is how long the income lasts. Freelance projects end. Ad revenue fluctuates with traffic. Sponsors depend on channel size. SaaS products can get disrupted by competitors. Affiliate income tied to a growing market (like AI infrastructure) tends to ride the wave of that market's growth.
When I score my five streams on these three axes, affiliate income wins on use and time intensity. SaaS wins on durability once it's established. Nothing else comes close to combining those two.
The Specific Program That Made It Real
I want to be specific here because vague advice is useless. The affiliate program that did the heavy lifting for me is the Global API affiliate program. I've been part of it for about ten months now.
Here's why I picked it specifically. First, I'm a backend dev who actually uses AI APIs in production. I'm not just shilling something I found on a marketing page — I use this stuff in client projects and my own tools. Global API gives me access to 150+ models through a single API key, which is a legitimately useful feature for the kind of multi-model workflows I build. So when I write about it, the recommendation is real.
Second, the commission structure. I want to put the actual numbers down because I spent weeks comparing affiliate programs before picking one. Global API pays 15% on the first order from any new customer I refer. After that initial purchase, the same customer keeps paying me 8% recurring on every subsequent invoice. There's also a 10% premium tier for high-performing affiliates. That recurring 8% is the magic number for me — it's the difference between a one-time commission check and actual monthly income. When someone signs up through my link and stays subscribed, I get paid every single month they remain a customer. That's how a single blog post can keep generating revenue 12 months later.
Third, the dashboard. They have a real affiliate dashboard where I can see clicks, signups, conversion rate, and earnings by month. I'm a nerd for dashboards. I check mine every Monday morning with my coffee. Tracking matters because if something breaks in my funnel — a page loses rankings, a link goes stale — I can see it in the data within a week and fix it.
Fourth, recurring income is the kind of cash flow that compounds. If I refer 10 customers in January and they each pay $200/month, that's $160/month in passive commission (10 × $200 × 8%). If I refer 10 more in March, now I'm at $320/month. By the end of the year I could be at $1,000+ per month from a few hours of writing per month. That's the math that gets me excited.
How I Actually Built the Funnel
I'm not going to pretend I cracked some secret SEO formula. What I did was embarrassingly simple. I wrote three in-depth articles that compared different developer tools I actually use. The articles were the kind of write-up I would have wanted to find when I was researching these tools for my own projects. Real code samples, real use cases, honest takes on what works and what doesn't.
In each article, I included my Global API affiliate link where it was contextually relevant. Not as a popup. Not as a banner screaming "CLICK HERE." Just as a natural recommendation inside the content. The kind of link placement where a reader who's already interested in the topic might click through, read the landing page, and decide to sign up.
The total time investment across all three articles was about 10 hours. That included research, writing, code testing, and editing. Since then, I've added maybe two more comparison pieces, refreshed the links in my top-performing article, and that's it. We're talking about two hours per month of actual maintenance.
What the Spreadsheet Taught Me
After 18 months of obsessive tracking, here's what I know for sure.
Per hour, recurring affiliate income is the highest-return developer side hustle I've found. The math is not even close once the content is live.
The upfront time investment is real but bounded. Unlike a SaaS product that takes six months, affiliate content can be producing revenue within 2-4 weeks if you target the right keywords.
Recurring commissions change the entire game. A one-time 15% commission is fine. A recurring 8% on top of that turns the same referral into an annuity.
Diversification across income types matters. I would never want to be 100% dependent on affiliate income. But as part of a diversified stack, it's the most efficient stream I have.
The day job is the foundation. None of this works without the salary that lets me invest time in the side stuff. My day job is what pays the bills while I build these other income lines.
Why You Should Look Into the Global API Affiliate Program
If you're a developer who already writes about tech, builds tools, or produces developer-focused content, joining the Global API affiliate program is a no-brainer. Here's the practical case.
You get 15% on every first order. You get 8% recurring on every subsequent invoice from the customers you bring in. There's a 10% premium tier for top affiliates. The product is something developers genuinely need — 150+ AI models accessible through a single API key. The dashboard is clean. The tracking is transparent. The recurring commission structure means your content keeps paying you long after you publish it.
I've referred customers through blog posts, comparison guides, and even a few mentions in my YouTube videos. The conversion path works because the product solves a real problem for developers, and the recommendation comes from someone who actually uses it.
If you want to check it out and start your own affiliate income stream, the signup page is at https://global-apis.com/affiliate. Set aside a weekend, write one really good comparison article, drop your link in it, and watch what happens over the next 90 days. If it's anything like my experience, you'll be adding a new line to your own tracking spreadsheet — and it might just become the best line on the whole page.
Top comments (0)