You are in the sales call to find the truth, not to close the deal

An FDE in a pre-sales conversation has a different job from everyone else in the room. Your credibility comes from being the person who says what will not work, and spending it to close a deal you cannot deliver is the most expensive mistake available to you.

13 MIN

TL;DR: In a sales conversation you are the only person whose credibility depends on being right rather than on winning. That asymmetry is the entire value you add, and it disappears the moment you start selling.

Where you are. First lesson of the flagship course. Foundations began after the deal existed. This one begins before it does, because the constraints that decide your engagement are usually set in a room you are only sometimes invited to.

Why you are in the room

An account executive brings an engineer into a customer conversation for one reason: the customer will believe things from you that they will not believe from the salesperson. That belief is an asset, it was extended to you before you said anything, and it is spent in one of two ways.

Spend it saying yes to everything and it converts into a signed deal and an engagement that cannot be delivered. You will be the one delivering it.

Spend it saying accurately what will and will not work, including in front of your own colleague, and you become the person the customer calls when they want a real answer. That relationship is worth more than any single deal, and it is the reason experienced buyers ask for the engineer to be present.

The trap is subtle because nobody asks you to oversell. The pressure is ambient: the meeting has momentum, the customer is enthusiastic, a hedge would be awkward, and the specific sentence that would introduce doubt is one you could reasonably leave for later. Later is where the doubt becomes a slipped date.

The pressure also has a season. A technical discovery call scheduled for the last week of the quarter is not discovery. It is a signing ceremony with questions.

The three questions worth asking

Pre-sales discovery is short, and you will get a handful of technical questions before the conversation moves on. These three buy the most.

Where does that data live today? The answer is rarely the system they name. It is that system plus a nightly export plus a spreadsheet somebody maintains. You are listening for how many hops away the data is from a place you could reach, because that number is your timeline.

Has anyone here said no to something like this before? Phrased neutrally, this finds the gatekeeper months before the security review. It also surfaces the previous failed attempt, which almost always exists and which nobody volunteers. Knowing that a similar project died last year, and why, is worth more than the rest of the meeting.

If this works, whose job changes? If nobody in the room can name that person, adoption has no owner and the pilot is a science project with a budget. This question is uncomfortable, which is why it is useful.

Saying no without losing the room

The skill is separating the impossible from the expensive, out loud, in real time.

Most things a customer asks for are not impossible. They are expensive, or slow, or they require a decision somebody in the room does not want to make. Saying "no" to those is inaccurate and makes you the obstacle. Saying "yes" is worse.

The useful shape is a price rather than a refusal. That is possible, and here is what it costs: doing it inside your network means a security review, which the last one took about six weeks, so it belongs in phase two rather than the pilot.

That sentence does three things at once. It keeps the answer honest, it hands the decision to the person whose decision it is, and it does not spend your colleague's deal on your caution. Most account executives will take that trade every time, because a slipped delivery costs them the renewal.

When something genuinely will not work, say it once, plainly, with the reason, and then stop talking. The pause after is uncomfortable and you should let it happen. Filling it is how a clear no becomes a maybe.

What to write down afterwards

Send a short note to your own team, same day, before memory smooths it out. What they asked for, what you heard about the data, who was named as a blocker, what you committed to, and what you deliberately did not commit to.

That last line is the one that matters. Months later, when the scope conversation happens, the difference between "we discussed it" and "we said it was out of the pilot" is written down or it is not.

Do this before moving on

Take a feature request you have received, from any context. Write the honest price for it in one sentence: what is possible, what it costs, and what it displaces. Then read it aloud. If it sounds like a refusal rather than a decision handed back, rewrite it until it does not, because that gap is exactly what makes engineers sound obstructive in customer meetings.

Go deeper

Requirements discovery is the technique underneath the three questions, in more depth.
Explaining trade-offs is how a no becomes a price the customer can decide on.
Stakeholder management covers the gatekeeper you just found and what to do with them.
Four people decide your deployment is the Foundations lesson this one assumes.
Why customer-facing engineering? is worth answering again now that you have seen the pre-sales half.

Key takeaways

Your credibility in a sales call was extended before you spoke, and it is spent either on closing or on being right.
Three questions do most of the work: where the data lives, who has said no before, and whose job changes if this works.
Convert an impossible into a price rather than a refusal, then hand the decision to the person whose decision it is.
Write down what you did not commit to, the same day. That is the line the scope conversation turns on later.

Check yourself

Answer before you look. Recalling it is what makes it stick; recognising it does not.

1A customer asks whether the system can run entirely inside their network. It can, but it means a security review that historically takes six weeks. What do you say?
2Why ask whether anyone has said no to something like this before?
3Nobody in the room can name the person whose job changes if the project succeeds. What does that tell you?