Ask about their process before you talk about your product

Start functional and technical discovery with how the buyer works today. Ask about roles, workflows, systems and bottlenecks before you describe a single feature. Their answers decide what your demo shows and what it leaves out. Without them you are guessing, and the buyer can tell.

The situation

Say you have a first call with a new account. Sales promised "a quick look at the product". The buyer's team joins and expects a tour. Your demo is ready, and the pull to start it is strong.

The handbook rule is blunt. Never run a demo without discovery first. A demo before discovery is like a doctor handing out medicine before checking what is wrong. It comes too early and can even do harm.

Why process questions work on buyers

Process questions are easy to answer. Nobody has to defend a budget or admit a weakness to describe how an order moves through their team. That lowers the guard a sales call usually raises.

They also change who the expert is. When you ask how the work runs, the buyer teaches and you learn. The chapter describes this as your edge: trust grows while you explore their goals, and the demo that follows becomes more personal.

Buyers grade you in this phase too. A seller who can describe their environment, culture and challenges accurately stands out from the others. Feature talk never earns that, because it is about you.

The first sales calls usually stay with broad goals. The functional and technical discovery (FTD) that follows often decides whether the deal succeeds or fails. It is where the sales discovery (opens in a new tab) turns into something you can build a demo on.

What to do

Book 25 minutes for the first FTD session. The handbook recommends that length. It fits a full calendar and shows you respect their time. Ask for the people who do the work, not only the person who signs.

Run the eight phases in order

1. Open the conversation. Ask about their role and how they got there. It shows interest and loosens the room.
2. Map the organisation. Team sizes, roles, and who hands work to whom.
3. Ask about workflows and systems. Which tools run today, and how do they connect? This is where your product must integrate.
4. Look at the operations. Find the dependencies, bottlenecks and weak points.
5. Find the pain. Learn where it hurts most and what it costs them.
6. Widen the view. Neighbouring teams may feel the same problem. Extra value often hides there.
7. Check culture and adoption. Ask how they took up the last new tool. Your plan has to fit that pattern.
8. Close with their vision. Ask where they want to be. It confirms you agree and sets up the next meeting.

Phrasing that keeps it on process

Exact questions help when nerves push you toward the product. Try these, in your own words:

• "Walk me through what happens from the moment a request comes in until it is done."
• "Where does that step wait for someone else?"
• "What did you do the last time it went wrong?"
• "Which system holds the answer, and who copies it from there?"
• "If this worked well a year from now, what would be different for your team?"

The "last time" question does the most work. It replaces a general complaint with a real example you can later show in the demo. When an answer stays thin, ask why again. The 5 Whys method goes one level deeper each time, until you reach the root cause.

Reflect back what you heard before you move to the next phase. "So the order sits in the inbox until finance approves it. Did I get that right?" A correction here is cheap. The same correction in front of their team during the demo costs you the room.

What you leave with

You leave with four things. A filled-in Opportunity Scoping Document (opens in a new tab). A list of gaps ranked by impact and urgency. The raw material for your demo story. And a next step the customer agreed to. Without that last one, you had a nice chat. You did not have a discovery.

Then send a short summary of your findings and ask them to correct it. The handbook calls this step feedback and validation. If it shows gaps, go back and dig deeper before you build the demo (opens in a new tab). The full method and the cheat sheet are in the functional discovery chapter (opens in a new tab). The FTD template is on the templates page (opens in a new tab).

What can go wrong

The buyer insists on the product

Sometimes the demo request is firm. Do not refuse it. Give a short overview of what the solution can do, or a look-and-feel demo of the interface. When detailed questions come, acknowledge them and offer a closer look after a full discovery. You can also ask probing questions inside the demo, so it works as discovery too.

This is the strongest argument against the whole play, and sometimes it wins. A technical evaluator with a shortlist may only want to see whether your tool does the job. Then a short early demo can earn you the discovery session. Keep it brief and end it with one question: "How does this step work for you today?"

Thin or guarded answers

Clients often give the broad picture without depth. Some hold back because they fear a pitch. Say why you ask and what you will do with the answers. Then listen before you present. Ask for a recent example instead of a general description.

The room disagrees

In a large organisation, people name different primary problems. Treat that as information, not as a failure. Talk to several stakeholders and adapt your questions to each role. In a smaller company, one person may run the whole process, and one good session can be enough. In a large account, plan one session per team that touches the workflow.

Too little time

A rushed session misses things, and you only understand part of their needs. Plan two shorter sessions instead of one cramped interview. Be patient with their schedule. A real dialogue beats a hurried questionnaire.

The signals to watch

It is working when the buyer starts sharing their own screen or sketching the flow. It is failing when you have spoken more than they have, or when your notes list features instead of steps. If you catch yourself describing your product, look at the list and ask the next question.

For more questions by role, read the key questions every presales professional should ask (opens in a new tab). For why buyers pull back from a pitch, read buyers do not hate salespeople, they hate being sold to (opens in a new tab).