Win-Loss Interview Script

Reconstruct the Decision

The reason recorded in a sales note is usually the last reason spoken. It may not be the reason that moved the decision. “Too expensive” can follow weak urgency, “missing integration” can conceal fear of adoption, and a win can depend on founder attention that will not survive the next ten customers.

Use this interview after a prospect buys, chooses an alternative, delays, or ends the evaluation without a decision. The aim is to reconstruct how the choice developed, then decide what deserves another test. It is not a disguised attempt to reopen the sale.

Prepare the Opportunity Trace

Before the conversation, make a one-page trace from the evidence you already have: how the prospect arrived, the job and urgency they described, participants and their roles, alternatives mentioned, demonstrations or trials completed, proposal and price, objections, significant pauses, and final outcome. Keep dated events separate from your interpretation.

Choose a respondent who saw the decision form. A user can explain workflow fit; a buyer can explain value and budget; an approver can explain risk. One person may not know what happened in another room. Record whose account you heard rather than blending several perspectives into an imaginary company opinion.

Invite candor with a clear boundary:

Hi [Name],

Thanks again for considering [product/offer]. I am trying to understand how
the decision developed, including where our approach helped or fell short.
I am not asking you to reconsider it.

Would you be open to a candid 15-minute conversation? There is nothing to
prepare, and direct criticism is useful.

For a won opportunity, replace the boundary with: “This is not an expansion call. I want to understand why the product was worth trying now, without assuming the reason I heard during the sale was the decisive one.”

Follow the Evaluation

Begin before your product became an option. You need the event that made evaluation worth the effort and the standard every option had to beat.

What was happening when you first decided the current approach might need to change?
What would have happened if you had left it alone?
What options did you consider at the beginning, including an internal workaround or doing nothing?
Who first wanted a change, and who still needed convincing?

Then walk through the evaluation in order. Do not start by asking for a ranked list of criteria; people often describe the decision more neatly after it is over than they experienced it. Ask for events, comparisons, and changes of mind.

What did you do first to compare the options?
When did [product] become a serious possibility, if it ever did?
What did you see or learn that increased confidence?
What reduced confidence?
Was there a moment when the likely outcome changed? What happened?
Which concern was hardest to resolve, and who owned it?

When the answer becomes a label—price, security, usability, integration, support—return it to the decision. Ask what the label meant in practice, what it was compared with, who was affected, and what evidence would have resolved the concern. A requirement matters differently when it blocks the core job, delays procurement, or merely appears on a preferred-feature list.

Locate the Commitment

The formal outcome and the real commitment may happen on different days. Find the point after which the organization stopped evaluating in earnest.

Who made the final call, and whose view carried the most weight?
What was the last unresolved question before the decision?
What finally settled it?
When did the decision feel effectively made, even if it was communicated later?
How was it explained internally?

Follow the Outcome

Now follow the branch that matches the outcome.

For a win, ask what the customer believes they bought, what nearly prevented the purchase, and what must happen next for the choice to look wise. Separate repeatable product value from a relationship, concession, custom promise, or deadline peculiar to this deal.

For a competitive loss, ask what the chosen option made easier to approve and what trade-off the buyer knowingly accepted. The useful comparison is not a feature inventory; it is why one complete choice felt safer, faster, more credible, or more valuable in that setting.

For a delay, ask what work or event must happen before the evaluation can resume, who owns it, and whether a date or budget actually exists. “Next quarter” without an owner, trigger, or cost of waiting is closer to no decision than to pipeline.

For no decision, ask what made the status quo preferable to the effort and risk of change. A product can beat every named competitor and still lose because the problem is tolerable, the buyer lacks authority, or adoption would consume more attention than the result warrants.

Close with counterfactuals only after the history is clear:

What would have had to be different for another outcome to make sense?
Which part could a vendor realistically have changed?
What kind of organization would have made the opposite decision?

Treat these answers as hypotheses. Buyers can describe a plausible alternate world without revealing what they would actually have done in it.

Turn the Account into Evidence

Immediately afterward, write the trace in sequence: trigger, cost of staying put, options considered, evaluation events, changes in confidence, decisive concern, commitment point, outcome, and expected aftermath. Mark each statement as an observed event, the respondent’s account, another participant’s reported view, or your inference.

Then choose the smallest implication the evidence supports. Test positioning when qualified prospects enter with the wrong expectation or cannot connect the offer to an urgent job. Test proof when they understand the value but cannot justify the risk. Reconsider product scope when the same necessary workflow fails across well-matched opportunities. Revisit qualification when the buyer lacks the urgency, authority, operating conditions, or support capacity the product requires.

Do not count every mention as a vote. A concern that changed the decision deserves more weight than a preference supplied after the fact. One account can expose a claim you should correct or an obstacle you can verify; it rarely proves a roadmap or segment change. Compare traces across similar opportunities by trigger, participant role, alternative, commitment point, and decisive evidence.

The interview has done its work when you can explain how the decision changed over time, distinguish the stated reason from the event that settled it, identify which evidence is direct, and name the next claim to test without turning one outcome into a product strategy.