The working frameworks, published

The most common closing failure is not weak technique at the moment of asking. It is asking when the deal is not decision-ready, then interpreting the resulting hesitation as an objection to overcome.

A deal is decision-ready when, in the prospect’s own words, all nine of these are true:

1. The problem has been named specifically, not as a category ("we lose deals after the proposal", not "sales could be better").

2. The cost of the problem has been stated by the prospect — in revenue, time, risk or opportunity — and is larger than your fee.

3. Urgency has a reason attached to a date or event, not a mood.

4. The decision authority is in the conversation, or the path to it is explicit and scheduled.

5. The money exists: budget confirmed, or its source identified out loud.

6. The alternative paths (do nothing, do it internally, hire a competitor) have been examined together, honestly.

7. The offer has been mapped to the named problem point by point, and the prospect has confirmed the mapping.

8. Every objection raised so far has been answered to a stated "that resolves it" — not to silence.

9. The next step after a yes is concrete: date, owner, first deliverable.

When all nine hold, the close is a summary, not a push. When one fails, the correct move is to return to that condition — not to press harder on the ask.

An objection map is a living document with one row per recurring objection. Building one takes a week of honest listening; maintaining it takes minutes a month. Each row records four things:

1. The objection, verbatim. Write the words prospects actually say, not the category. "We want to think about it" and "I need to run this by my partner" are different rows with different roots.

2. The root. Every recurring objection traces to one of four roots: missing proof, wrong framing, wrong audience, or a real defect in the offer. The root decides the response — and roughly a quarter of the time, the honest answer is to change the offer, not the script.

3. The agreed response. One answer, written down, that every rep gives. Not because uniformity is elegant, but because a written answer can be inspected, improved and drilled. Improvised answers cannot.

4. The prevention point. Most objections are cheaper to prevent than to answer: the moment earlier in the conversation where the topic should have surfaced. "Too expensive" at the close usually means cost-of-problem was never established in discovery.

Review the map monthly. Objections that stopped appearing tell you the prevention is working. New rows tell you the market or the offer moved.

Follow-up fails in two opposite ways: the apologetic drip ("just checking in") and the disappearing act. Both share a root cause — no structure was agreed on the call itself. The cadence starts before the call ends:

1. On the call: agree the next step, its date and its owner out loud. A deal that leaves the call without a scheduled next event is already in limbo; everything after this point is recovery, not follow-up.

2. Same day: a recap in writing. The named problem, its stated cost, the mapped solution, the agreed next step. This is the single most valuable message in the sequence — it converts a conversation into a record both sides can point to.

3. Each subsequent touch carries an artifact, not a nudge. Something with standalone value: an answer to an open question, a relevant framework, a scope clarification. "Just following up" teaches the prospect your messages are skippable.

4. Deadline logic, honestly used. Real constraints (calendar capacity, price validity windows) are stated once, early, and enforced. Invented urgency is a trust withdrawal that costs more than the deal.

5. The clean break. After the agreed sequence completes without a decision, send the break message: the door stays open, the cadence stops, the reason is stated plainly. A clean break preserves more future deals than an infinite drip — and releases your attention to pipeline that can close.

Unscored call review produces adjectives: "good energy", "bit rushed". A scorecard produces evidence. Ours scores six dimensions, each anchored to observable moments with timestamps:

1. Opening frame — was the purpose, agenda and decision context of the call established in the first minutes, or did the call drift into it?

2. Diagnosis quality — did the prospect name the problem and its cost in their own words? Count the moments; do not average an impression.

3. Authority and money — were decision path and budget surfaced as facts, or assumed from enthusiasm?

4. Solution mapping — was the offer mapped to the named problem point by point, with confirmation, or presented as a general tour?

5. Objection handling — was each objection answered to a stated resolution, deferred deliberately, or smoothed over?

6. Commitment — did the call end with a dated, owned next step? A warm ending without one scores zero on this dimension, whatever the mood.

Two rules make the scorecard work. Score from the recording, never from the rep’s memory of the call. And calibrate reviewers on the same call quarterly — a scorecard two people apply differently is an opinion with a grid on it.