The ICP Gate: Filter Guests Before You Invite

Most shows pick guests on how well they will interview, and that one habit is why a full calendar produces no revenue. We run invite led outbound for 50 plus B2B companies at a 4.6% reply rate, against the 3.43% average Instantly measured across billions of cold email interactions, and almost all of that edge is decided before a word of copy gets written. Below, the gate that decides who earns an invite, the 5 checks it runs, the filters worth deleting today, and how to tell when you have set it too tight.

What Is an ICP Gate for Podcast Guests?

The gate is not a scorecard and it is not a vibe. It is a sentence you could hand to a stranger, and the stranger would return the same verdict you would on the same 100 names.

That is the whole test. If 2 people reading your criteria disagree on a row, you do not have a gate yet, you have an opinion with bullet points under it.

ICP Gate

A binary fit rule run on every name before an invite is sent. Output is pass or fail plus one line of reasoning, stored on the row so the decision is auditable later.

Pull Parameter

A countable filter set at list build time in Apollo or a similar tool. Headcount, revenue band, geography, seniority, keyword. These belong in the query, never in the gate.

The distinction between those 2 is where most guest lists quietly break, and it is worth more than any wording change you will make to the invite itself. How you build the guest list sets what reaches the gate. The gate decides what survives it.

Why Does a Written Gate Beat Judgment on Every Name?

Judgment does not scale and it does not hold still. Reviewed on a Monday, a mid market operations lead is a strong fit. Reviewed on a Thursday, with 400 rows left to go, the same person is a maybe, and maybes get invited because deleting a row feels like losing progress.

Volume settles the argument. At 10,000 invites a month nobody is reading 10,000 profiles, so either the standard is written down and runs the same way every time, or the standard is whoever was reviewing rows at 4pm.

There is a second reason, and it is about who is actually on the other end. Gartner puts the typical B2B buying group at 6 to 10 decision makers, with 77% of buyers describing their last purchase as complex or difficult. A guest list built on impressive titles invites 6 people who each own a slice of the decision. A guest list built on a gate invites the 1 who owns the problem.

That person is usually less senior than the title you were reaching for and far more useful, which is the same finding behind defining an ICP for cold email and what an ideal customer profile actually is.

What Belongs in the Gate and What Belongs in the Query?

The query holds everything countable. The gate holds everything that needs a judgment call written down once. Mixing the 2 is the most common way a list gets thin without anyone noticing.

Here is what that looks like in practice. Your Apollo query already restricted the pull to companies of a certain size, in certain regions, at certain seniority levels. Every row that reaches the gate has cleared those. Write those same limits into the gate prose and the grader starts rejecting rows the query already approved, usually because a headcount estimate on the enrichment text disagrees with the one in the database.

You paid for that filter once at pull time. Restating it charges you a second time, in rows you never see, and the shrinkage shows up as a list that ran dry a month early.

So the gate never mentions company size or revenue. It asks a different kind of question entirely: does this person sit at a desk and own the problem we solve. The desk part sounds trivial and it is not. A buyer who works a computer as part of the job reads email, replies to email, and can join a recorded conversation from a quiet room. A buyer who spends the day on a job site does none of those things, regardless of how well the company matches on paper.

The rest of the row is context for that judgment, which is why enrichment runs before the gate rather than after it.

What Are the 5 Checks Every Name Has to Pass?

In the order they should run, cheapest first.

1. Do they own the problem you solve. Not adjacent to it, not interested in it. It is their number, their team, or their quarter that suffers when the problem goes unsolved.
2. Can they decide on spend. Either they sign, or they are the person whose recommendation ends the conversation. Anyone who has to build an internal case from scratch is a longer road than a guest seat can carry.
3. Do they sit at a desk. Reachable by email during the workday, able to join a recording without leaving a site. This single check replaces every industry blacklist we used to keep.
4. Is the company visibly operating. A live site, recent activity, a real team page. Dead companies are the largest source of silent list decay, and they never announce themselves.
5. Would you take the sales conversation if it booked tomorrow. The honest one. If the answer is no, the invite is a favor you are doing your calendar, and the recording will confirm it 45 minutes at a time.

Check 5 is the one people skip, and it is the only one that catches a name that passed the first 4 on technicalities. Run it last, run it every time, and the rest of the funnel gets easier. Qualifying guests before you invite them covers the mechanics underneath each check.

Which Filters Should You Delete From Your Gate Today?

Most gates carry inherited filters that feel responsible and do damage. These 4 are the ones we removed and never rebuilt.

The follower count one deserves a sentence on its own. The seat you are handing out is the scarce asset, not the guest's reach. Podchaser's guest pitching data puts the median acceptance rate at 5% when publicists pitch shows for a slot, which is what the market looks like from the other side of the table. You are holding the thing everyone is chasing, so spend it on someone who can buy, not someone who can broadcast.

How Do You Run the Gate on 10,000 Names?

One model call per row, reading the enrichment text already sitting on that row. It returns a verdict and one line of reasoning. Nothing more elaborate is needed, and every extra layer we have tried added spend without moving the verdict.

1. Write the gate in one file. One paragraph of ideal buyer prose, no numbers in it. Version it, date every change, and treat an edit as a decision rather than a tidy up.
2. Grade in a single call per name. Pass or fail, plus the reason in the model's own words. The reason is what makes the gate auditable 3 weeks later when somebody asks why a name was dropped.
3. Append the verdict, never overwrite the row. New columns on the right of the file, original data untouched. A gate that destroys its input cannot be re-run when the criteria change.
4. Hand audit 50 rows a week. 25 passes and 25 rejects. If you disagree with more than 5, the gate prose drifted from what you actually want, and the prose is what needs the edit.
5. Re-run the borderline rows. Grading is probabilistic, so a name at the edge can land either way on a given pass. Re-running the near misses recovers real buyers at almost no expense.

The list tooling underneath this is ordinary. Clay against Apollo covers what each does well, and building a list from scratch covers the pull that feeds the gate in the first place.

How Do You Tell If the Gate Is Set Right?

Watch 3 numbers and cohort every one of them by gate verdict.

A pass rate over 60% means the gate is descriptive prose rather than a rule, and it is approving names on general resemblance. A pass rate under 15% usually means the pull query was wrong upstream, and the gate is quietly doing work that belongs in list segmentation.

Reply rate tells you whether the invite landed with someone it should have landed with. If replies look fine but almost no recording turns into a sales conversation, the gate is passing the wrong seniority, and the reply rate benchmarks will look healthy the whole time it happens.

False negatives are the expensive half and they are invisible by design. Nobody complains about a buyer you never invited. Pull 100 rejects a month, read the reasons, and look for a pattern the gate is not built to see yet.

The volume math sits on top of all of this. How many invites it takes to book one recording tells you how much a narrower list has to earn back, and guest no show rate tells you how much of what you booked survives to the room.

The Practitioner Take on ICP Gates

A guest list is a revenue decision that looks like a data task, which is why it gets handed to whoever has the afternoon open. The gate is where you decide, once, in writing, who is worth 45 minutes of your show and the sales conversation that follows it.

Shows that never write the gate down end up with a calendar full of pleasant recordings and nothing to sell into. The episodes are fine. The guests are interesting. Not one of them could have bought anything.

We measure client work in recorded conversations for this reason. 30 recorded conversations with your ideal buyers in 90 days, or your money back, where ideal buyer is the phrase the gate is holding up. Drop the gate and that number is still reachable, and it stops meaning anything, which is the version of this failure nobody catches until quarter end.

Write the gate before you write the invite. The copy can only reach the people your list decided to reach, and by then every decision that mattered has already been made.