How do you set kill gates before a campaign launches?
Decide the stop rules before volume hides the truth

Why set kill gates before launch instead of after results come in?

Because most teams do not kill bad campaigns when the data says stop. They kill them when patience runs out, or when a founder gets embarrassed by a bad week. That is too late. By then, volume, sunk cost, and internal politics have already distorted the decision.

Prelaunch gates force honesty. You write down what success looks like, what failure looks like, how long you will wait, and what happens next. That removes the common excuse loop where every poor result gets explained away as bad timing, list quality, inbox variance, market seasonality, or rep execution.

This matters most in outbound because the top of funnel can generate activity that looks alive without producing real pipeline. Replies can rise while meetings stay flat. Meetings can rise while show rate collapses. Show rate can look acceptable while opportunities never materialize. If the stop rules are vague, weak campaigns linger.

What should a kill gate actually include?

A real kill gate is not just a number. It has five parts. Miss one and the team will argue at the exact moment clarity is supposed to help.

• Primary metric. Pick the signal that decides whether the campaign lives or dies.
• Measurement basis. Define exactly what the metric is calculated on, so nobody swaps definitions later.
• Review window. State when the metric will be judged.
• Owner. Name who makes the call.
• Action. Write the operational consequence of each threshold.

For most launch decisions, the cleanest primary metric is positive rate on sends. It is close enough to the message and list quality to help you diagnose the motion early, but not as noisy as reply count on its own. The verified thresholds are simple and useful. Under 0.5% positive on sends is a kill. 0.5 to 1% means iterate. 1%+ means scale. 2%+ means pour.

The key is to define actions in advance. Kill means stop net new volume into that motion. Iterate means hold or reduce volume while changing one major variable. Scale means increase investment because the campaign has earned it. Pour means the campaign is outperforming enough that budget should move toward it unless another downstream constraint blocks growth.

A practical prelaunch gate template

Which metric should be the kill gate for a new campaign?

For a new outbound campaign, use positive rate on sends as the first gate, then pair it with one downstream protection metric. Do not rely on open rate. Do not rely on total replies. Do not rely on booked meetings alone if calendar discipline is weak.

The reason is simple. You need one early signal and one quality control signal. Positive rate tells you whether the market is engaging in the way that matters. The second metric tells you whether that engagement becomes something commercially useful.

Show rate is a strong second gate in many teams because broken calendar discipline destroys the economics fast. Where calendar discipline is broken, booked meetings die at roughly a 50% show rate. That means campaigns can look healthy in booked meeting screenshots while the real pipeline engine is quietly failing.

If your funnel has a long sales cycle or weak qualification, use opportunity quality instead of show rate. The principle is the same. Do not let a campaign survive on vanity movement at the top.

How do you stop teams from moving the goalposts?

You stop it operationally, not emotionally. Put the gates in the launch brief. Put the review date on the calendar before the first send. Name one decision owner. State what changes are allowed before the gate review and what changes are not.

This matters because teams love to change three things at once when performance is weak. They rewrite the offer, swap the list, alter targeting, and change the sender setup, then claim improvement without knowing what caused it. That destroys the value of your gate.

• Allow one major variable change per iteration window.
• Freeze the definition of positive, so no one broadens it under pressure.
• Separate infrastructure issues from message or market issues.
• Record the exact action attached to each threshold before launch.

You also need context on expected baseline performance so early bad numbers do not get rationalized as normal. Across the fleet baseline, the positive rate is 0.05%. That is not a target. It is a reminder that many campaigns are simply not good enough and should not survive. Operators who refuse to kill weak motion early usually end up subsidizing mediocrity.

How long should you wait before a kill decision?

Long enough to collect a fair read, short enough to avoid protecting bad motion. The right review window depends on setup maturity, audience size, send capacity, and whether infrastructure is still ramping.

This is where founders get impatient for the wrong reason. A campaign can be logically sound and still not be ready for a hard commercial read if the sending environment is not mature. Onboarding is about 21 days, and warm up takes 4 to 6 weeks. If you pretend a fresh setup should behave like a seasoned one, you will make the wrong call.

That said, warm up is not a shield for weak messaging forever. Your review plan should distinguish between infrastructure readiness and campaign viability. Infrastructure asks whether you are in a position to learn. Viability asks whether the market signal justifies more budget.

A simple rule is to set a first formal viability review only when the environment can produce a trustworthy read, then continue with a weekly operator review. If a campaign is materially under the kill threshold once the setup is mature, stop feeding it and diagnose instead of hoping volume rescues it.

What usually breaks kill gates in real teams?

Three things. First, teams use soft language. They say pause and review instead of kill, so nobody actually stops the motion. Second, they choose conflicting metrics. One person cares about replies, another about meetings, another about pipeline, so any campaign can find a defender. Third, they attach prestige to channels or tactics and refuse to admit the market does not care.

There is also a sequencing problem. Some campaigns are judged too early on the wrong variable. Others are judged too late because there is already calendar fill, rep effort, and emotional attachment. Neither is disciplined.

One useful reality check is to compare a live week to your gate language without inventing a story around it. On the largest account, one week produced 44,649 emails, 377 replies, and a 0.84% reply rate. That number alone does not justify scaling because reply rate is not the same as positive rate, and the positive count for that week is not known. This is exactly why the gate definition must be fixed before launch. Otherwise people scale off the wrong signal.

Who should not use this kill gate framework as written?

Do not use it blindly if your campaign is not outbound led, if volume is too low to generate a usable read, or if your definition of positive is inconsistent across segments. The framework is strongest when you have stable measurement, enough activity to judge, and a clear commercial path from response to revenue.

It is also a bad fit for teams still confusing an offer problem with an execution problem. If the market does not want the offer, cleaner gating will only help you stop faster, not fix the core issue. That is useful, but it can feel brutal if leadership expects messaging tweaks to rescue a weak proposition.

And if your real bottleneck is channel execution depth, this site is not the place for a tactical playbook on that. The sibling sites cover channel craft in more depth. Here, the job is to decide whether the motion deserves more budget, less budget, or none.