The kill or scale decision
Gate arithmetic for outbound sequences

What does kill or scale actually mean in outbound?

Most teams do not have a sequence problem. They have a decision problem. They let weak campaigns run because a few replies feel encouraging, or they shut down a test after a bad pocket of sends even though the audience and offer are still learning.

Kill or scale is a simple operating rule. Every sequence sits inside a gate. The gate decides whether you stop it, adjust it, or give it more volume. That sounds obvious, but most outbound teams still decide based on anecdotes, sales pressure, or the founder spotting one reply in Slack.

The point of gate arithmetic is not precision theater. The point is to create a shared threshold that sales, marketing, and revops can use without arguing every week. Once the thresholds are explicit, you can inspect the real issue, market fit, targeting, list quality, deliverability, messaging, or follow through.

Which metric should decide the gate?

Use positive rate on sends. Not opens. Not total replies. Not booked meetings. Not revenue from one lucky deal. Positive rate on sends is the cleanest early signal for whether a sequence is creating real buying interest from the audience it touches.

The gates we use are straightforward. Under 0.5% positive on sends is a kill. 0.5 to 1% is iterate. 1%+ is scale. 2%+ is pour.

These gates are useful because they force consistency. Two operators can look at the same sequence and reach the same action. That matters more than having a complicated model no one trusts.

One warning here. Do not swap metrics mid decision. If you are gating on positive rate, stay on positive rate. A lot of bad decisions come from mixing total replies, meetings, and pipe stories into one muddy judgment.

Why not use reply rate or meetings booked?

Reply rate is useful, but it is not the same thing as positive rate. Replies include noise, objections, unsubscribes, and dead ends. We have one verified data point from the largest account, one week produced 44,649 emails and 377 replies, a 0.84% reply rate. That tells you activity and response environment. It does not tell you the positive rate, so it cannot decide kill or scale on its own.

Meetings booked are even further downstream. They reflect sequence quality, but also SDR behavior, routing speed, calendar management, and rep discipline. Where calendar discipline is broken, booked meetings die at roughly a 50% show rate. If you use meetings as the first gate, you risk blaming messaging for an ops problem.

Revenue is the worst early gate for most teams. It arrives late, is lumpy, and can make a weak sequence look strong because one account happened to close. Revenue belongs in channel allocation and pipeline planning. It is not the first test of sequence health.

When should you kill fast, and when should you iterate?

Kill fast when the sequence had a fair shot and still failed the gate. Fair shot means the list fits the ICP, the offer is understandable, the infrastructure is stable, and the follow up was actually sent. If all of that is true and you are under 0.5% positive on sends, do not get sentimental. Stop it.

Iterate when the signal is mixed or the setup is not yet clean. The 0.5 to 1% range is where operator judgment matters. Something may be working, but not enough to trust with more budget or more domains. This is where small changes can matter, narrower targeting, a sharper problem statement, a stronger proof point, or a different call to action.

• Kill if the audience is right, the send quality is acceptable, and the sequence still lands under 0.5% positive on sends
• Iterate if the sequence sits between 0.5 and 1% positive on sends and you can name a specific fix to test
• Scale at 1%+ only if operational capacity can absorb the extra responses
• Pour at 2%+ only if quality holds after volume increases

What I do not recommend is endless micro editing of copy before you face the gate. Teams often rewrite intros, tweak subject lines, or argue about tone while avoiding the harder question, should this market, message, and offer combination continue at all.

What has to be true before the gate arithmetic is trustworthy?

The gates only help if the environment is stable enough to produce signal. If your sending setup is young, your numbers can mislead you. Onboarding is about 21 days, and warm up usually takes 4 to 6 weeks. If you rush the judgment before the system is ready, you can kill a decent sequence for the wrong reason.

You also need consistency in audience selection. If one batch is founder led software companies and the next is enterprise teams with a very different buying process, the gate is no longer measuring one thing. It is measuring a moving target.

Operational discipline matters too. If leads are not worked promptly, positive responses do not become meetings. If calendars are unmanaged, meetings do not show. If ownership of follow up is fuzzy, the sequence will be judged on a downstream mess it did not create.

Who should not follow this advice as written?

Do not use these gates blindly if you are very early in category creation, selling a complex enterprise motion, or running such low volume that every response swings the picture. In those cases, qualitative evidence matters more and you may need a longer learning window before making the call.

This framework is also not a substitute for channel mix decisions. If the real problem is that outbound should not be carrying the whole target, the answer is not to force a better sequence. We cover the budget side in the GTM math pieces, including how to think about channel mix and allocation.

If you need deep execution detail on list building, copy structure, or multichannel choreography, that belongs on sibling properties inside the group, not here. This site owns the arithmetic and the operating rules, because that is where most teams actually lose money.

How should an operator use this every week?

Run a weekly review with one sheet and three possible outcomes, kill, iterate, or scale. Start with positive rate on sends for each live sequence. Do not let the meeting drift into personal opinions until the gate is assigned.

• Label each sequence with its current gate
• Write one sentence on why it earned that gate
• Name the single next action, stop, test, or expand
• Check whether sales capacity and calendar discipline can support any scale decision

This sounds simple because it is simple. Simplicity is the point. The fleet baseline positive rate is 0.05%, which is a useful reminder that weak outbound can stay alive for a long time if no one imposes a hard threshold. A sequence does not deserve budget because it exists. It deserves budget because it clears the next gate.

If you want help diagnosing whether your issue is market, message, infrastructure, or follow through, the closest thing we have to a standard method is our GTM audit approach.