A prospect sends a spreadsheet with forty rows and three columns marked yes, no and partial. He wants it completed by Friday.
Half the rows describe capabilities that have no bearing on what his business is trying to do. Several describe one competitor's product in terms only that competitor uses. Three things that will genuinely determine whether this works for him are not on the list at all.
Completing it honestly produces a middling score against a framework designed by somebody else. Completing it dishonestly wins an evaluation that will unravel during implementation.
Script 1: ask what the list is for
What is the business trying to achieve, and what happens if it does not. This is the question nobody asks, and asking it changes the conversation immediately.
Script 2: answer the list honestly anyway
Complete it, including the noes. Refusing reads as evasion, and an honest completion with commentary is considerably more credible than a column of unqualified yeses.
Script 3: mark the partial answers precisely
Say exactly what is and is not supported rather than claiming partial and hoping nobody asks, which is where most evaluations produce later disputes.
Script 4: name the rows that do not matter
Respectfully, with the reason. Telling a buyer which of their own criteria are irrelevant to their situation is genuinely useful and rarely done.
Script 5: add what is missing from the list
Three things that will actually determine success. This is how a vendor changes the framework without appearing to dodge it.
Script 6: handle the requirement you do not meet
Directly, with a workaround or an honest no. A buyer who discovers a gap themselves trusts nothing else on the sheet.
Script 7: the capability that exists differently
Frequently the answer is that the same outcome is achieved another way, which is a yes to the problem and a no to the row.
Script 8: the item that only one competitor has
Naming it plainly, explaining what it does and why it may or may not matter, is more persuasive than pretending not to know where the row came from.
Rule 1: never complete it with a sales person alone
Somebody who knows the product properly should verify every row, since an optimistic yes on a spreadsheet becomes a contractual expectation.
Rule 2: date and keep a copy
Evaluations resurface at renewal and during disputes, and what was claimed is remembered precisely by one side only.
Rule 3: separate today from planned
Which is the honesty required in early customer questions a startup cannot answer yet, and which a spreadsheet column rarely allows for.
Rule 4: record what buyers keep asking for
Because a row that appears on every evaluation is a genuine market signal, which is the ground in roadmap and feature request questions from early users.
Rule 5: be honest about availability generally
The same discipline applies to anything a customer wants and cannot have today, as in out of stock medication questions.
Answer the list and change the question
An assistant that responds to capability questions consistently, states plainly what exists and what does not, explains where the same outcome is reached differently and asks what the buyer is actually trying to achieve turns a spreadsheet scored against somebody else's product into a conversation about the problem. The matching logic is set out in ai shopping assistant product fit. See features, start at try, and the sector view sits under startups.