Fintech SDR Discovery: Finding the Break in a Purchase Order Handoff

A purchase order call sounds simple until the SDR asks the wrong question first. The prospect owns a process with several people touching it, and a rep who guesses where the break sits before asking will either flatter the finance team or imply their controls are sloppy. Neither approach earns a second call. The path that works is narrower. You name a moment the prospect already recognizes, you ask what happens next, and you let the answer tell you who belongs in the room.

Why this conversation goes wrong

You can fail this call in one of two ways. The first is leading with a diagnosis before you have evidence. You hear "plant managers sometimes order direct" and jump straight to "so you have a control gap," which puts the controller on the defensive and ends discovery before it starts. Nobody wants to admit their process has a hole to a stranger on a cold call, especially a stranger trying to sell them something.

The second failure is staying so vague that the prospect cannot engage. Questions like "walk me through your process" or "what challenges do you face with purchase orders" ask the prospect to do your job for you. A controller has a dozen ways to answer that and no reason to pick the one that matters to you.

Purchase order handoffs cross departments by design. A request starts with a buyer or a plant manager, moves through a purchasing coordinator, gets matched against an invoice by accounts payable, and sometimes needs a receiving confirmation before anyone releases payment. Four people can each hold a piece of the answer and none of them owns the whole picture. Ask the wrong person the wrong question and you get a partial answer that feels complete.

How to prepare

Before you pick up the phone, decide on the one moment you will use to open the conversation. The moment should be something the prospect has lived through, not a hypothetical. An invoice that lands without a purchase order reference works well because almost every finance team has hit it at some point, and naming it does not accuse anyone of anything.

Know the roles before you ask about them. In most companies the chain runs from requester to approver to purchasing to accounts payable, with a receiving check for physical goods. Write down which title in this company probably plays each role, based on the industry and company size, so you recognize it when the prospect names it back to you.

Prepare three possible causes for a stuck invoice and hold all three loosely. The purchase order was never created. The number exists but nobody can find it. Someone still needs to confirm the goods or services arrived. Each cause points to a different owner, and your job on the call is to let the prospect tell you which one applies, not to guess out loud.

Rehearsal matters here because the questions have to sound natural under pressure, not read off a script. Reps who practice this kind of call against a realistic counterpart handle the unexpected answer better than reps who only read about it. DealSpeak's Financial Services practice conversations give a rep a place to run this exact scenario before it happens on a real prospect.

What to say

Picture an SDR calling a controller at a distribution company. The controller mentions, almost in passing, that regional managers sometimes send orders straight to a supplier instead of routing them through the requisition system.

The SDR does not react to that as a problem. Instead the SDR asks, "When an invoice shows up without the reference number your team expects, what has to happen before it can move forward?" That question accepts the scenario the controller just described and asks for the mechanics, not a judgment.

The controller answers that an accounts payable specialist emails the regional manager to ask what the charge was for, the manager searches a shared inbox for the original request, and the purchasing coordinator eventually updates a tracking spreadsheet once everyone agrees on the details. Three people, three separate steps, no single owner.

The SDR follows with a question aimed at the decision, not the whole process. "Does the invoice usually wait because the request was never logged, because the reference number cannot be found, or because someone still needs to confirm the order arrived?" The controller says it is almost always the second one, the number gets lost between the manager's inbox and the coordinator's spreadsheet.

The SDR closes the loop with a plain recap. "It sounds like AP starts the search, but purchasing is the one who can actually close it out. Is that a fair way to put it?" Once the controller agrees, the SDR has earned the right to ask whether the purchasing coordinator and someone from accounts payable would be worth including on a short call about the handoff.

Mistakes to avoid

Do not propose a fix during discovery. Saying "we can stop those missing POs" turns a fact finding call into a pitch, and the prospect has not confirmed the fix solves their actual problem yet. Stick to naming what you are trying to understand, something closer to "I am trying to see where this handoff creates extra work."

Do not stop at the first person who answers the phone. A controller can describe the process from a distance but may not be the person who feels the pain of it daily. If the purchasing coordinator is the one updating spreadsheets by hand, get that person on the next call even if you never spoke with them directly.

Do not treat one story as the whole pattern. A single anecdote about a regional manager ordering direct tells you the shape of one incident. Ask whether it happens often, ask about the last time it happened, and ask if it is the same two or three people every time. That turns an anecdote into evidence you can bring into a meeting.

Do not ask closed questions when you want detail. "Does that ever cause delays" invites a one word answer. "What has to happen before it can move forward" invites a sequence, and a sequence tells you where to focus.

How to practice and score it

Score four things when you listen to this call. Did the rep name a specific, recognizable moment instead of asking an open ended question. Did the rep avoid diagnosing the problem before the prospect described it. Did the rep identify at least two people who touch the process, not just the person on the phone. Did the rep end the call with a specific ask, a short meeting with named roles, rather than a vague promise to follow up.

Score the recap line separately. A rep who repeats the sequence back accurately and gets a "yes, that's right" from the prospect has earned trust that a rep who skips the recap has not. That single line often decides whether the prospect agrees to a next call.

Reps improve fastest when they run this scenario more than once against different versions of the same prospect, some cooperative, some guarded, some who ramble. A related scenario worth rehearsing is Fintech SDR Discovery Use a Revenue Recognition Handoff as a Hypothesiswhere the rep has to test an assumption rather than build one from scratch. Another good pairing is Fintech SDR Discovery Ask How Subsidiaries Report Spendwhich covers a related handoff problem across business units. Running variations of the same call inside DealSpeak lets you compare how a rep handles a cooperative controller against a guarded one, with a score that gives both of you something concrete to work from.

The break in a purchase order process is rarely dramatic. It shows up as a small gap between two people who each assume the other has it, and a good discovery call finds that gap without insulting anyone who works there.