sales-sales-engineer

Start with a one-sentence problem statement, define written pass/fail success criteria with the buyer before starting, scope aggressively to one critical use case, and set a two-to-three-week timeline with a midpoint review. End with a GO/NO-GO decision gate at the final readout.

Quantify the buyer's problem first using discovery specifics, show the end-state outcome before explaining how it works, then reverse into architecture and setup. Close with a customer reference mirroring the buyer's situation, and plan the narrative to peak at one clear aha moment.

FIA stands for Fact, Impact, Act: state an objectively true fact about the competitor, explain why it matters to the buyer's business, then define the specific talk track or demo moment to use. It keeps positioning fact-based instead of emotional.

Decode the real concern behind the stated question first. Scale questions usually mean past vendor failures, so respond with benchmark data from a comparable customer. On-prem requests may signal security policy or sunk infrastructure cost, which require completely different conversations.

Never trash competitors, because it raises buyer defenses and damages credibility. Instead acknowledge the competitor's genuine strength, then reframe around the buyer's specific priority where your approach delivers more long-term value.