Skip to content

Objections and questions — [Use case]

Rules for using this:

  • Answer the question that was asked, then stop. A long answer to a short question reads as evasion.
  • If the answer is "it doesn't do that", say so first, then say what it does do. Never lead with the workaround.
  • Everything here is checkable in a public repository. If you are not sure, say "let me check" and check — you can, live, in front of them.

"[The competitive question — why would we move?]"

""

"[The capability the demo cannot show]"

Answer the limitation first.

""

"Where are the credentials?"

""

"Is it really idempotent?"

""

"What happens when it breaks?"

""

"Who can launch this?"

"What does this cost us to run?"

"Can I have it?"

Questions to ask them

After [beat]:

Before the close: -

Things not to say

-