What should a forward deployed engineer leave a discovery call with?

THE SHORT ANSWER

The first rows of the eval, labeled by the customer. Salesforce's November 5, 2026 Ask Slackbot column tells an FDE to treat the first answer as a draft, ask 'what happens next' instead of 'why,' bring evidence not opinions, admit what they do not know, and leave with better questions than they brought. The last part is where deployments get found out at go-live. A firm opinion is a compressed story about a pain; the record where the pain happened is the uncompressed version. Ask for three records per opinion, have the customer's expert say on the call what the right answer was, and run the product as it stands against them before the second call. That is how Colin Jarvis's team could say 60 percent at scoping. Run the column's divergence prompt, where the first ask and the final build diverged, on the handshake page rather than on five Slack threads, because my discovery-week ranker buried a three-call theme under a 31-call one and the three were the renewal.

Rows, not questions. Three records per firm opinion, labeled by the customer's expert on the call, and the product's number on them before the second call. The handshake page gives the column's divergence prompt an address.

The three artifacts and the rewritten prompt are in Salesforce's FDE Slackbot Says Leave the Call With Better Questions. Leave It With Rows.. The eval rule and Colin Jarvis's sequence are in The FDE Writes the Eval: Almost Right Has a Number, and the page itself in In the Room, Not on the Quota: Who Owns the FDE Promise.

SOURCES

THE LONG VERSION

RELATED ANSWERS

Last reviewed 2026-11-05 · 1 min read