By Junaid Ahmed
When we sat down to figure out the marketing budget for PodGlue, the
math went like this. We could spend a few thousand dollars a month on
Google Ads, watch the click-through rate, A/B test the landing pages,
and hope to convert 1–3% of traffic into trials. That's the standard
playbook. Everyone does it. Nobody loves it.
Or we could pay that money to the people who already use the product
and would already recommend it.
We picked the second one.
The PodGlue affiliate program pays 15% recurring commission to
Engage subscribers and 30% recurring commission to Amplify
subscribers. Recurring means: every month your referral stays
subscribed, you get paid. Not one-time. Not "first year only." For as
long as they're on a paid plan.
No earning ceiling. No qualification process. No special tier you have
to apply for. Open Settings → Affiliate in the app. Your unique
referral link is already live. Done.
There's a reason it's structured this way, and it isn't generosity.
Most podcast tools we looked at do one of two things. Either there's no
affiliate program at all, and the company spends that money on cold
ads to people who've never heard of them, or there's a token program
that pays you 10–20% on the first month and nothing after. The second
version is worse than the first because it pretends to align incentives
without actually doing it.
If I pay you $7.90 once for sending me a customer who stays for three
years, I've underpaid you by every metric that matters. That customer
generated $2,800 in revenue. You did the work that made them show up.
You should get paid the whole way through.
So that's how we built it. The 30% number on Amplify isn't a launch
discount or a promotional thing. It's the rate. It compounds with every
referral you send.
Here's what 30% recurring actually looks like.
Five active Amplify referrals at $79/mo = $118.50 per month, every
month they stay. Ten = $237. Twenty = $474. The post-launch price is
$99, which makes those numbers $148.50, $297, and $594. None of this
makes you rich. All of it shows up in your account on the first business
day of every month.
For a podcaster who already talks about the tools they use, on the
show, in newsletters, in show notes, in the Slack groups they're in, this isn't a side hustle. It's residual income on a conversation you
were going to have anyway.
The ones who do best with it aren't influencers. They're hosts who
interview other creators. Course instructors who teach podcasting.
People with newsletters about the craft. Community moderators. Anyone
who's already a node in the "what tool do you use?" conversation.
A few things worth knowing.
The commission rate is based on your active plan, not the plan your
referral signs up for. So an Amplify subscriber who refers an Engage
customer earns 30% on that Engage subscription. The tier you sit on is
the tier you earn at.
Commission cookies last 30 days from first click. If someone clicks
your link, doesn't sign up, and comes back a month later directly, you
still get credit.
Payouts go out on the first business day of each month, calculated
on the previous month's active referrals. You set the payment method in
Settings → Affiliate → Payout Method. USD only for now.
The full guide is at Affiliate Program docs
if you want every detail.
The honest version of this post is short. We'd rather give the money to
the people who use PodGlue than to Google. If you're already telling
other podcasters about the workflow, even casually, turn on your
affiliate link before you do it again.
Sign in. Settings → Affiliate. Copy the link. That's it., Junaid
Ready to make every episode compound?
PodGlue is the operating system for relationship-driven podcasters.
Get Started FreeRelated reading
I Wanted to Invite 50 People to a Call
What started as a weekly beta call invite turned into rebuilding how PodGlue tracks people. The smallest tasks reveal the most about what you actually need.
From 642 Megabytes to Nine
Our admin app deploy was uploading 642MB. The container only needed 9MB. The fix was one config file — and a question I'd been avoiding.
The Deploy That Never Deployed
Our CI had been silently rejecting every edge function deploy for months. I only noticed because something I shipped didn't appear.