What positive rate should trigger kill, iterate, or scale decisions?
Use simple gates, then inspect the reason behind the number

Why use positive rate as the main gate?

Positive rate is the cleanest operating signal for outbound decision making because it ties activity to actual buying interest. Opens are noisy. Reply rate can be misleading because a reply is not always commercial intent. Meetings can come too late in the process to help you make early sequence decisions. Positive rate lets you decide sooner whether the market is leaning in or pushing back.

For an operator, the question is not whether a campaign feels promising. The question is whether the campaign has earned more volume. That is why gates matter. They stop a team from throwing more sends at a weak offer, and they stop the opposite mistake, which is killing a good motion before it has enough room to work.

The practical advantage is speed. If you define kill, iterate, and scale thresholds before launch, the team does not need a debate every week. The score tells you what to do next, then the review tells you why.

What thresholds should actually drive kill, iterate, or scale?

The simplest useful framework is the one we use in practice. Under 0.5% positive on sends is a kill. From 0.5 to 1% is iterate. At 1%+ you scale. At 2%+ you pour. These are operating gates, not universal laws of nature. Their value is that they create discipline.

A lot of teams fail because they blur these states together. They treat a weak campaign as a scaling opportunity because a few replies came in. Or they treat an early promising signal as random luck and never lean in. The point of the gate is to turn ambiguity into action.

There is also a useful baseline for humility. A fleet baseline positive rate of 0.05% tells you how ugly broad outbound gets when targeting, offer, or fit are off. If your result lives near that level, you do not have a small optimization problem. You have a relevance problem.

When should you kill instead of tweaking?

Kill when the result is under 0.5% positive on sends and the setup was fair. Fair means the list was not obviously broken, the copy was competently written, the sending environment was stable, and the offer was at least understandable. If those conditions were true and the campaign still missed the mark, more volume is usually denial dressed up as experimentation.

This is where founder ego often gets expensive. A team gets attached to a narrative like enterprise must want this, or this persona should convert, or this category is strategic for us. None of that changes the score. A weak positive rate means the market is not validating the motion yet.

• Kill if the market segment is not responding at all and the message has already had a fair test.
• Kill if replies appear but they are mostly confusion, deflection, or not now with no pattern you can fix quickly.
• Kill if the campaign only works when you hand pick accounts one by one, but fails as soon as you need repeatability.
• Kill if the team keeps rescuing the motion with excuses instead of changing the underlying offer or audience.

Killing a motion is not failure. It is budget protection. It frees attention for the segments and messages that can actually carry pipeline.

What does iterate really mean between 0.5 and 1%?

Iterate means the market is giving you enough signal to keep learning, but not enough proof to scale hard. This middle band is where most useful GTM work happens. You are not trying to celebrate it. You are trying to improve it.

The most common mistake here is changing too many things at once. If a campaign sits in the iterate zone, keep the core market unless the replies clearly say the market is wrong. Then change one level down. Adjust the positioning. Narrow the segment. Change the trigger. Change the ask. Tighten the promise. Do not rewrite the whole system every few days and call it testing.

Another mistake is over-reading reply rate. We have seen weeks with strong reply activity that did not translate to known positive intent. One verified example is a week on the largest account that produced 44,649 emails and 377 replies, for a 0.84% reply rate. That tells you the inbox and message generated responses. It does not tell you the positive count for that week, so you cannot use it as proof of scale readiness.

That distinction matters. A campaign can create conversation without creating demand. Positive rate is the gate because it is closer to the thing you are buying with outbound effort, which is sales interest.

When is it safe to scale at 1%+?

Scale at 1%+ when the result is holding under comparable conditions. Comparable matters more than people admit. If one week used a cleaner list, a hotter segment, or a founder-sourced account set, and the next week uses a broader pool, the same result may not hold. Scaling too early often means you are scaling a pocket of demand, not a repeatable motion.

What you want at 1%+ is operational confidence. The targeting logic is understandable. The offer is repeatable by the team, not just by one excellent operator. The calendar can absorb demand. The handoff into sales will not waste the opportunity.

Calendar discipline is one hidden reason scale breaks. Where calendar discipline is broken, booked meetings die at roughly a 50% show rate. That means you can be right about the top of funnel and still miss pipeline because the system after booking is sloppy. Do not treat scale as a copywriting decision only. It is also an operations decision.

What does 2%+ mean, and why call it pour?

At 2%+ positive on sends, the motion is usually strong enough to justify aggressive resource allocation. I call that pour because the job changes. You are no longer asking whether the campaign works. You are asking how much good volume the market can absorb before quality degrades.

That does not mean remove judgment. Very high performance can come from a narrow pocket, a short-lived trigger, or a founder-led angle that the broader team cannot reproduce. Pour means increase investment with control. Expand adjacent segments. Add capacity carefully. Tighten measurement. Protect what created the result in the first place.

Where do these gates fail?

They fail when teams pretend the number exists outside context. Positive rate is a decision tool, not a religion. If the sample is tiny, the gate can mislead you. If the segment is strategic but very small, the threshold can look harsh. If the sales cycle is long and the ask is intentionally heavy, positive rate can understate future value. If the market is brand new and the message requires education, kill gates may fire before the category has had a fair hearing.

They also fail when attribution is messy. In an allbound motion, outbound may create familiarity while another channel captures the response later. This site owns the arithmetic of channel mix and budget allocation, but deep channel execution belongs elsewhere in the group. If you need detailed email mechanics or multichannel sequencing depth, that is better covered on the sibling properties, not here.

Most importantly, these gates are not for every company. Do not use them blindly if your average deal requires heavy education, if your addressable market is extremely small, or if your outbound motion is primarily account development rather than meeting generation. In those cases, the numbers still matter, but the review layer matters even more.

How should founders and GTM leads apply this in practice?

Set the thresholds before launch. Review on a steady cadence. Separate decision from diagnosis. First decide kill, iterate, scale, or pour from the positive-rate gate. Then inspect the causes. Was the list wrong. Was the offer too soft. Did the copy create replies without intent. Did sales handling waste demand. This order matters because it keeps the room honest.

• Define the target segment and offer before the first send.
• Use positive rate on sends as the primary gate.
• Do not promote a campaign from iterate to scale just because reply activity looks healthy.
• Check operational capacity before increasing volume.
• Write down why a motion was killed, so the team does not repeat the same test with a new name.

If you want the surrounding math, start with pipeline coverage and channel mix before you decide how much budget a good motion deserves. We cover that in the related guides on this site.