Turn an AI shortlist into a qualified sales conversation

A shortlist is the start of discovery

A buyer arrives with a polished comparison of your offer and two competitors. They may already have a preferred option, a proposed budget, and a list of questions produced with AI. That preparation can make the conversation more useful. It can also carry incorrect prices, stale scope descriptions, or assumptions nobody has checked.

Your job is to connect the comparison to the buyer’s actual situation. Begin with curiosity: “What prompted the search, and what are you hoping will be different if this works?” Do not spend the first ten minutes defending a ranking whose method you cannot verify.

Reconstruct the brief with the buyer

Ask which problem they gave the assistant, what constraints they included, and what they changed during the search. A prompt for the cheapest provider produces a different brief from one for a team that can complete a regulated integration. The buyer may discover that an important requirement never made it into the comparison.

Confirm the desired outcome, current workaround, people affected, timing, and decision process. Ask permission before reviewing or retaining their AI transcript. They can summarize the relevant points instead of sharing private business information.

Sort the comparison into facts and assumptions

Use three columns in your notes: verified fact, buyer preference, and unresolved question. A published service scope is a fact you can check. A preference for weekly meetings belongs to the buyer. An assumed integration or delivery date is a question until someone confirms it.

Correct inaccuracies with a current source and a plain explanation. “That page describes our earlier package; this is the current scope, including what it excludes” is more helpful than blaming the assistant. If the misunderstanding came from your own website, assign an owner to fix it after the call.

Make fit visible with a bounded next step

In an illustrative example, a founder asks for an “AI sales system” because an assistant recommended automation. Discovery shows that leads reach the wrong person and nobody agrees on qualification criteria. A sensible first step may be mapping the handoff and testing a routing rule, before discussing a larger implementation.

Write the proposed next step in five lines: the decision it will support, inputs required, deliverable, who reviews it, and what happens afterward. State the price or pricing process accurately. Make it easy to conclude that the work is not a fit. A clear disqualification can save both parties effort.

Send a recap that survives another AI summary

Organize the recap under recognizable headings: agreed problem, success criteria, scope, exclusions, dependencies, unresolved questions, and next action. Include the relevant current links. Avoid implied commitments in vague phrases such as “full support” or “seamless integration.” Name what those terms mean in this engagement.

If you use an assistant to draft the recap, give it your approved notes and ask it to flag missing facts. Review every price, date, deliverable, and commitment before sending. Do not let a fluent draft turn an open question into an agreement.

Measure conversation quality

Track whether the inquiry matched the offer, whether the buyer understood the scope, and whether both sides agreed on the next action. If you ask how the buyer found you, record their answer as self-reported attribution. An AI mention is not proof that the assistant caused the sale.

For your next practice session, take a fictional AI comparison and role-play five minutes of discovery. The goal is to identify one missing constraint and one unverified claim without making the buyer feel foolish.

Review the AI buyer shortlist test, then use the next conversation to turn a plausible recommendation into a clear shared decision.