Never resend the rejected proposal. Remove the constraint that killed it, cut the scope or reshape the terms, so the buyer decides on a new offer instead of reversing their verdict on the old one.
They looked at your proposal and said no. A month later you are about to send it again with a friendlier cover note.
Go back with a different offer, not the same one. Remove the constraint that killed it, cut the scope, reshape the terms or change the order of the work. The problem you solve stays the same. What they are asked to approve changes, and that lets them decide again without anyone in the room having been wrong the first time. Sending the same document back asks them to reverse themselves.
Deepak Malhotra's conditional concession, as Katie Shonk reports it for Harvard's Program on Negotiation. Two moves. The price is final, but the question can be reopened if the other side changes some of its demands. Extra support is available, but only against a commitment to buy named additional services. In both, a closed question reopens because a term on the buyer's side moves, not because the seller asks again.
Scotwork's payment-terms example, from August 2026. A rejected payment term comes back as two different shapes: thirty-day payment if the annual price drops by a stated amount, or forty-five days at the current price plus a commitment to quarterly volume forecasts. Every movement carries a condition, so the buyer chooses between structures instead of refusing the same one twice.
What sales publishes instead. No sales source publishes the wording for re-offering after a rejection. The nearest thing is the win-back play, such as ZoomInfo's from December 2023, which fires ninety days after the deal was marked lost and opens with a subject line asking whether the buyer has found a solution. It changes the message and the timing. It does not change the offer.
Nobody has tested it. No study compares sellers who went back with a changed offer with sellers who went back with the same one.
How often a no comes after a yes. G2 surveyed 1,038 B2B software decision-makers in June 2026 for its buyer report and announced that 49% said their CFO had vetoed an already-approved software purchase in the past twelve months. G2 sells to the software market it surveyed. The figure says how common the situation is, not what works once you are in it.
The nearest measured thing, from a vendor. Proposify's State of Proposals 2026 covers 742,137 proposals sent through its own platform in 2025, with an average close rate of 34%. Close rates were 18% higher after one round of revisions the buyer asked for, 28% after two and 45% after three. Proposify sells proposal software, and there is no comparison group. A buyer asking for changes has not rejected anything, so the likeliest reading is that deals going well are the ones that collect revisions. Other sites repeat these figures as 37%, 42% and 50%, which the report does not say.
The field study the move comes from. Henry Mintzberg, Duru Raisinghani and André Théorêt followed 25 strategic decisions for their 1976 paper in Administrative Science Quarterly. Formal approval came up in 14 of them, 33 times in all, and it was all or nothing: the whole solution was accepted or rejected, and a rejection led either to dropping it or to reworking it. They counted 13 cases where a failure sent the process back, to remove a constraint or to change the solution from an earlier point. In their words, "a previously rejected alternative was reintroduced under the new conditions". They also give the order organisations followed: remove the constraint first, change the solution if that fails, design a new one if that fails, and only at the end accept something they had called unacceptable.
The nearest experiment points the other way. Daniel O'Keefe and Scott Hale pooled 88 tests with 7,780 people on the door-in-the-face tactic: make a large request, get refused, then make a smaller one. Overall the effect was small. For commercial requests it was close to zero, and where any time passed between the two requests, more than five minutes in their coding, it turned slightly negative. The size of the concession made no difference. Going back smaller works between strangers in one conversation for a good cause, which a rejected proposal never is.
The direct evidence is a 1976 study of managers deciding inside their own organisations, not of a supplier trying to get back in. The closest experiment stops working once the request is commercial or once days pass. The only sales numbers belong to a company selling proposal software. Nobody has compared a changed offer with a resent one in a real pipeline.
Change something real before you go back, say what changed, and let the buyer decide on a new proposal instead of reversing their verdict on the old one. Start by removing the constraint that killed it, which is what organisations tried first in the field study. Treat the changed offer as the price of a second hearing, not a promise of one.