I Wanted to Invite 50 People to a Call

By Junaid Ahmed

---

The task was small.

PodGlue has 50 hosts in the beta and another stack on the waitlist. I wanted to send all of them an email every Thursday saying come hang out on Zoom at 11am Pacific. Simple weekly invite. A sentence about what we'd be covering.

That was the whole project. A weekly email.

It took two days, three pull requests, and a complete rebuild of how PodGlue tracks people.

---

What the task actually was

The first complication was easy to see: I needed to know who to send the email to. Some people on the list are on the waitlist. Some have signed up. Some are mid-trial. Some have an active subscription. Some have canceled. Each group probably wants slightly different language, or at least the option to be addressed differently.

The second complication is the one I almost missed: those categories don't sit still.

Someone joins the waitlist this week. Gets an invite the week after. Signs up. Starts a trial. Upgrades to paid. Five weeks, five categories.

A weekly email isn't a weekly email. It's a snapshot of a moving population.

---

The system that fell out of it

I ended up building lifecycle stage tagging across the whole platform.

Five stages, waitlist, active user, in trial, paid, canceled, each mapped to a tag in our email tool. Triggers in the database fire whenever someone's lifecycle state changes. A background worker syncs that change to the email tool inside a minute. The weekly call invite sends to the union of waitlist + user. The conversion drip sends to trial. The welcome sequence sends to user. The winback sequence sends to canceled. None of those broadcasts ever hit the wrong audience, because the audience is always current.

I didn't sit down to build a lifecycle system. I sat down to send an email.

The lifecycle system was the floor underneath the email.

---

What my mother knew

My mother taught me this lesson, though I didn't know that's what was happening at the time.

Growing up in Riyadh, we didn't have YouTube or a hardware store you could just drive to. When something needed fixing, she fixed it. She'd take a door off its hinges, lay it across the dining table, and trim the bottom with a jigsaw because it was dragging on the carpet. She'd set up a booth at school festivals, Pakistani Independence Day, August 14th, and we'd sell whatever we'd sourced or made.

The interesting thing was never the one door, or the one booth.

It was that after she trimmed one door, she had the setup, the jigsaw out, the surface clear, the technique figured out. The second door was twenty minutes. The fifth one she barely thought about. After the first booth she had the table, the inventory system, the change box, the cousin who'd help her set up. The work she'd done once was running underneath every door and every booth after that.

I watched all of that without understanding what I was learning. The thing that was getting installed in me was the belief that small tasks are usually carrying a foundation along with them.

The weekly email is the door. The lifecycle tagging is the jigsaw, the surface, and the technique. Once it's there, it runs underneath everything next.

---

How to tell when to build the foundation

The tricky part is being honest about the difference between building the foundation and over-building.

Over-building is real. Building a 12-month roadmap for a 1-week problem is something founders do all the time. The trap is dressed up as foresight. I've fallen into it.

The way I've started telling the difference is one question: would this foundation make my next ten weeks easier?

Lifecycle tagging passed that test. I have welcome emails to write, trial conversion sequences to test, winback sequences to run, and probably three more cohort-specific things I haven't thought of yet. All of them need the same foundation. Building it once and reusing it for the next ten weeks is good math.

If the answer is no, this only helps with this one task, you're over-building. If the answer is yes, the next ten things I want to do all need this, you're laying the kind of foundation my mother laid when she pulled the jigsaw out of the closet.

---

What this looks like in your show

The same logic applies to podcasting.

I've recorded over 700 episodes of Hacks & Hobbies. Every one of them, every single one, followed the same shape underneath. Outreach, scheduling, pre-call notes, recording, edit, publish, asset delivery, follow-up. By the time I had done it 100 times, the dance was muscle memory. By 300 it was automatic. By 700 I had built the system in my head over and over again, but I hadn't built it in software.

So every guest still cost me the same amount of energy. The 700th guest was almost as expensive as the first.

That's the trap most podcasters never see. You don't build a guest CRM because you want to remember one guest's email. You build it because the next thirty guests are going to ask the same questions, want the same intake form, need the same follow-up cadence, and benefit from the same relationship records.

The first guest is the door. The system that holds the next thirty is the workshop you set up to handle every door.

Most podcasters never set up the workshop. They send the email manually to the first guest. And the second. And the fifteenth. By the fiftieth, they're exhausted and they don't know why.

The reason is that they kept solving the same problem from scratch. The work that should have run underneath every guest was never built. That's the whole reason PodGlue exists, I lived inside that gap for 700 episodes before I built the workshop.

---

PodGlue is in beta with 50 hosts. Every Thursday they get an email from me inviting them to the call. It comes through Kit. It's tagged automatically by their lifecycle stage. The whole thing took two days to build and will send for the next two years without me touching it again.

That's the math that justified building the foundation. That's the math my mother taught me, before I had any idea I was being taught.

Junaid Ahmed is the host of Hacks & Hobbies and the founder of PodGlue.