Last month, my affiliate income hit $537. That's not a typo. I didn't launch a new product, land a big client, or work 80-hour weeks. I simply kept creating content around tools I was already using — and let compound interest do its thing.
Today, I'm sharing everything. Every stream of income, every struggle, every number. This is what build-in-public actually looks like when you strip away the highlight reels and show the messy middle where real money gets made.
Why I Started Tracking Everything Publicly
Eighteen months ago, I was exhausted. I was working as a senior developer, building side projects at night, and watching my bank account hover around the same number regardless of how hard I pushed. I was trading time for money, and time was running out.
Something clicked when I stumbled onto the build-in-public movement. Developers sharing their revenue dashboards. Writers posting their monthly income breakdowns. Everyone being radically transparent about what was working and what was flopping. It felt like a breath of fresh air in a space where everyone usually keeps their numbers hidden behind vague claims of "side income" and "passive revenue."
So I started doing the same thing. Every dollar I earned, I documented. Every stream of income, I tracked. And slowly, I started seeing patterns that completely changed how I thought about my earning potential.
My Complete Income Stack (The Real Numbers)
Let me be straight with you. Here's exactly what hit my bank account last month:
Freelance Development Work: $2,400
My hourly rate sits at $125. Last month I landed a small React project that paid $2,000 and a quick backend fix that added another $400. Not bad, right?
Here's the problem nobody talks about: freelance income is completely parasitic. The moment I stop taking calls, reviewing code, and pushing commits, the money stops. I took a weekend off last month for my cousin's wedding. That weekend cost me roughly $500 in potential earnings. Every vacation day is a choice between memories and money.
SaaS Product: $940
I built a small developer tool two years ago. It took me about seven months of evenings and weekends to ship the initial version. Now it generates between $800-$1,200 monthly, depending on new signups and churn.
But let me tell you what that $940 doesn't show you. I spent 12 hours last month on customer support emails. I fixed a critical bug that kept three customers up at night. I updated my Stripe integration because their API changed. I answered feature requests in my Discord server. This "passive" income requires roughly 6-8 hours of active attention every single week.
Blog Ad Revenue: $312
My tech blog pulls about 52,000 monthly page views. At roughly $6 per thousand impressions, that's what I get. I publish 5-7 articles monthly, each taking 3-5 hours to research, write, and optimize.
The frustrating part? Traffic is finicky. Google rolled out a small algorithm update in February and my organic traffic dropped 15% for three weeks. I'm still recovering. Ad rates also fluctuate — I remember making $450 monthly with only 40,000 views when CPMs were higher. The sustainability here is questionable.
YouTube Sponsorships: $1,100
I publish two developer-focused videos monthly. Each takes about 18 hours total — researching, scripting, recording, editing, thumbnail design, and promotion. My last sponsor paid $550 per video, and I had two sponsors last month.
But sponsorships are unpredictable. Some months I can't find any sponsors willing to work with my niche. Other months I have to turn deals down because the product doesn't align with my audience. The inconsistency is stressful, and I've had months where YouTube income was zero.
AI API Affiliate Commissions: $537
And here we are — the star of today's show.
Last month, my affiliate income hit $537. The month before that, it was $481. Three months ago, I crossed $400 for the first time. This stream has been growing steadily without any additional effort on my part, and it's now my third-largest income source.
Let me break down exactly how this works.
The Affiliate Model That's Actually Worth Your Time
I want to be specific about what I'm promoting and why. After years of experimenting with different affiliate programs, I found one that actually makes sense for developers.
The program I'm part of offers tiered commissions that reward ongoing relationships:
- 15% commission on the first order from any referred customer
- 8% recurring commission on all their future orders
- 10% premium tier for high performers Think about what that means in practice. When someone signs up through my link and spends $100 in their first month, I get $15. But if they stay for six months and spend $600 total, I receive $15 plus 8% of every subsequent payment. A customer spending $200 monthly is worth $15 + $16 + $16 + $16 + $16 + $16 = $95 over six months. Compare that to a one-time 10% affiliate program where that same customer would only be worth $20. That's the magic of recurring commissions. The math compounds in your favor. Every customer you refer becomes a monthly annuity, and annuity income is what separates struggling freelancers from builders who are actually building wealth. # # How I Set This Up (My Exact Process) I want to walk you through exactly what I did because I've had DMs from developers who tried "affiliate marketing" and made $0. It's because they treated it like a get-rich-quick scheme instead of a legitimate business model. # # # Step 1: I Only Promoted Things I Actually Used I wasn't about to become one of those tech bloggers recommending random tools for affiliate checks. I only promote products I have real experience with, platforms I've personally integrated into projects, and services I would pay for myself. When I started exploring AI APIs for a client project, I went deep. I tested multiple providers, dealt with their documentation, hit rate limits, and figured out their quirks. I wasn't looking for an affiliate opportunity — I was looking for the right tool. One platform kept coming up in my testing: Global API. It offered access to 150+ models through a single API key, which simplified my stack significantly. Instead of managing five different API integrations, I had one. The documentation was solid, the performance was reliable, and the pricing made sense for production use. I didn't become an affiliate first. I became a user first. # # # Step 2: I Created Genuinely Useful Content Once I had real experience with the platform, I started writing about what I learned. Not promotional content. Not sponsored posts. Genuinely useful technical content that solved problems I had actually encountered. My first article was about building a multi-model AI pipeline. I walked through exactly how I structured the integration, showed real code examples, and discussed the tradeoffs between different approaches. The article wasn't "hey check out this great product." It was "here's how I solved this specific problem, and part of that solution involved using this platform." Somewhere in that article, naturally and contextually, I mentioned Global API. I included my affiliate link where it made sense — not as a pop-up, not as a banner, but as a resource link where readers who wanted to try the tool could do so easily. The key word is "naturally." Nobody wants to read an obvious advertisement. They want to read content that helps them, and if your content genuinely helps them, mentioning the tools you used is just good documentation. # # # Step 3: I Built Content Pillars, Not One-Off Posts One article isn't a business model. It's a blog post. I created a content strategy around AI API usage. My pillar pieces covered integration patterns, error handling strategies, cost optimization techniques, and use case walkthroughs. Each article naturally referenced the tools I used, including Global API where relevant. Over six months, I published 14 articles in this content cluster. Each one attracted search traffic, social shares, and newsletter subscribers. Each one included affiliate links where they made contextual sense. Then the compounding started. My first article continued ranking. My third article started pulling traffic. My seventh article hit a viral spike when someone shared it on Reddit. The aggregate effect was significant — I went from occasional clicks to steady referral traffic. # # # Step 4: I Tracked Everything and Optimized I don't just dump links and hope for the best. I track every affiliate link through UTM parameters. I see which articles drive the most clicks, which calls-to-action convert best, and which traffic sources produce actual signups. My "Getting Started with Global API" article converts at 3.2%. My "Multi-Model Architecture" article converts at 2.1%. My "Error Handling Patterns" article barely converts at all — it attracts researchers but not potential customers. This data tells me where to invest my next piece of content. More of what converts, less of what doesn't. It's basic marketing, but it's amazing how many people skip this step entirely. # # The Numbers Behind This Income Stream Let me get specific about the financial reality of this approach. Time Investment:
- Initial setup and first content cluster: ~15 hours
- Monthly content creation (1-2 articles): ~6-8 hours
- Link maintenance and optimization: ~2 hours monthly
- Total time last month: 8 hours Revenue Generated:
- $537 in affiliate commissions
- 12 new referred customers
- Average customer value: $44.75 per month in referral fees Per-Hour Return: At 8 hours monthly generating $537, that's $67 per hour. That's better than my freelance rate when you factor in that the content I created last month will continue generating revenue for months and years to come. The Compounding Effect: Three months ago, my monthly affiliate income was $312. Last month, it was $537. That's a 72% increase in three months without any additional content creation. The customers I referred months ago are still spending money, and I'm still earning 8% on their bills. If this trend continues, I'm projecting $800-$1,000 monthly by year-end from this single income stream. That's on top of everything else in my stack. # # The Struggles Nobody Tells You About I want to be honest about the ugly parts because that's what build-in-public means. The Waiting Game: I spent four months creating content before my first affiliate conversion. Four months of publishing articles, watching traffic grow, and seeing zero dollar signs. Many developers would have quit. I almost did. The people who succeed in affiliate marketing are the ones who can delay gratification and trust the process. The Content Grind: Creating genuinely useful technical content is hard work. It's not spinning articles or using AI to auto-generate garbage. It's researching, testing, failing, trying again, and finally writing something that actually helps people solve their problems. The bar for quality is high, and the bar keeps rising. The Impostor Syndrome: Who am I to be recommending developer tools? I'm not an AI researcher or a platform expert. I'm just a developer who tried some things and documented the results. But here's what I learned: expertise isn't about credentials. It's about solving problems for your audience. If your content genuinely helps someone, you're qualified to write it. The Algorithm Anxiety: My first pillar article got 3,000 views in its first week and then vanished into search result obscurity. My second pillar article took eight months to hit 1,000 views. The inconsistency is maddening. Some content soars. Some content flops. You can't predict which is which, so you just keep creating and hope the averages work out. # # What This Means for Your Side Hustle Stack Here's my honest assessment after 18 months of build-in-public income tracking: Most side hustle advice is garbage. People tell you to freelance more hours (terrible advice when you're already stretched thin), build a SaaS (great idea but requires significant capital and time), or "monetize your expertise" (vague and useless). The one genuinely underrated opportunity is creating content around tools you already use and joining their affiliate programs. You don't need to build anything new. You don't need to find clients. You don't need to launch a product. You just need to document your existing work and point people toward tools that helped you succeed. The use is real. You create content once, and it earns money indefinitely. You build trust with your audience, and affiliate conversions happen naturally. You compound your efforts over time, and the income stream grows even when you take a vacation. # # The Numbers Don't Lie Let me leave you with one final breakdown. This month, I'll spend roughly 10 hours on content creation and affiliate optimization. If the current trend holds, I'll make $550-$600 in affiliate commissions. That's roughly $55-$60 per hour. But here's what that number doesn't capture: the hours I worked this month on freelance projects will never pay me again. The hours I spent on customer support for my SaaS are gone forever. The hours I poured into YouTube editing are sunk costs unless I keep producing videos. The hours I spent writing articles last month? They're still working. They generated income in March, they'll generate income in April, and they'll generate income a year from now without any additional effort on my part. That's the fundamental difference between trading time for money and building use. One burns out. The other compounds. # # Ready to Start Your Own Affiliate Journey? If you've read this far, you're probably a developer who wants to stop trading all your time for money. You want something that scales beyond your hours. You want to build an income stream that works while you sleep. I've been exactly where you are, and I can tell you definitively: joining an affiliate program for a tool you actually use is the lowest-friction path to creating used income. If you're already using AI APIs in your projects, consider the affiliate program I participate in. Here's why I genuinely recommend it: The commission structure is exceptional. 15% on the first order plus 8% recurring means every customer you refer becomes a long-term revenue stream, not a one-time payout. A developer who signs up and spends $200 monthly generates $16 per month in perpetuity. Referring ten developers like that is $160 monthly, forever. The product is genuinely useful. With access to 150+ models through a single API key, it's the platform I actually use for my own projects. I'm not recommending something I don't use. I'm recommending the tool that simplified my own development workflow. The conversion rates are solid. Because the product works and developers actually want it, the affiliate conversions happen naturally. I'm not fighting an uphill battle trying to sell something nobody wants. If you're ready to start building affiliate income, here's my referral link: https://global-apis.com/affiliate I'm not going to tell you this will make you rich overnight. It won't. I spent four months creating content before my first sale. But the compound effect is real. My affiliate income has grown 72% in three months, and I expect it to keep climbing as my content library expands. The developers who will win in this space are the ones who start creating now and trust the process. Not tomorrow. Not next month. Now. Build in public. Share your numbers. Document your journey. The transparency isn't just good ethics — it's good marketing. People trust creators who show their work, and trust converts into clicks, signups, and affiliate commissions. Your turn. --- This post is part of my ongoing build-in-public series where I track every dollar I earn. Previous income reports are archived on my blog. Yes, the numbers are real. Yes, I have the bank statements to prove it.
Top comments (0)