Fintech SDR Discovery: Find the Friction in a Collections Workflow

Collections calls are one of the easiest discovery conversations to ruin. An SDR who hints that a finance team is disorganized, or that customers are dodging invoices, loses the room in the first minute. The fix is not a clever line. It is a set of questions that stay inside the workflow, respect the people who run it, and surface the one handoff that actually causes delay.

Why this conversation goes wrong

Most SDRs walk into a collections conversation with an assumption already baked in, that the prospect's team is behind on invoice follow up and needs a tool to catch up. That assumption leaks into the questions. Asking how a team deals with customers who won't pay turns a routine operational question into an accusation. The controller or finance lead did not build the current process by accident. They built it around constraints you do not see yet, account managers who guard the client relationship, a finance team that owns the money side, and a reporting cadence set by someone above both of them.

The other common failure is scope creep. An SDR hears about a slow paying customer and immediately starts talking about legal escalation, or promises that automation will recover cash faster. Neither claim belongs in a first conversation. You have not seen their data. You do not know their dispute rate. Stating a result you cannot back up costs you credibility the moment the prospect checks it against reality.

There is also a relationship dynamic under the surface. Account managers do not want to damage a client relationship by pushing too hard on payment, and finance does not want a good client to become a bad debt. Neither side is wrong. An SDR who treats this as a simple discipline problem misses that the tension is structural, not a matter of someone not trying hard enough.

How to prepare

Before the call, get clear on the mechanics of a typical accounts receivable process, not so you can lecture the prospect, but so your questions land as informed rather than generic. Know the difference between an invoice that is simply late and one that is disputed. Know that account managers usually own the client relationship while finance owns the ledger, and that friction often lives exactly at the seam between those two roles.

Write down three or four questions that ask about handoffs, not judgments. Who decides an invoice needs a phone call instead of an email. Where does that decision get recorded. What happens when the account manager and the finance team disagree about whether to keep pushing or pause outreach. These questions work because they ask the prospect to describe a process they already know cold. Nobody gets defensive explaining their own workflow.

Look at the company's industry before the call too. A professional services firm collects differently than a subscription software company, and a business with a handful of large accounts manages exceptions differently than one with thousands of small ones. That context tells you which questions to lead with and which to hold for later.

If you want a model for this kind of preparation, read Fintech SDR Discovery Learn From Corporate Card Offboarding, which is a good example at Fintech SDR Discovery Learn From Corporate Card Offboarding. It walks through the same idea in a different operational context, mapping a workflow before you ever suggest a solution.

What to say

Open with a statement that names the pattern you see across finance teams, then hand the floor back immediately. Something like, "I talk with finance teams that are trying to keep invoice follow up visible across finance and the account managers who own the client relationship. Is there one handoff in that process that causes the most delay."

Say the controller answers this way. "Follow up is inconsistent. We send a weekly spreadsheet by email to the account managers, but their responses end up in separate notes, sometimes in the deal system, sometimes in an inbox." That is a specific, concrete answer, and it is worth staying with rather than moving to your next scripted question.

Ask a follow on question that goes one layer deeper. "When an invoice passes its due date, what tells the account manager that outreach is needed now instead of next week." The controller might say, "Nothing tells them automatically. Whoever opens the spreadsheet that week decides what looks urgent." Now you have found the actual gap, no trigger, no owner, no shared record of what happened after contact.

Close the exchange by asking who else feels that gap. "Who besides you deals with the fallout when an account manager misses one of those." If the controller names a person and a role, for example the head of client services who fields complaints about repeated contact, you have your next meeting and a reason for that person to take the call.

Do not end there. Restate what you heard in plain terms and confirm it before you ask for time. Say, "So today the spreadsheet moves the information, but the outcome of each contact does not make it back to one place." When the controller confirms that, ask for a short meeting with the person who owns that record, by name and title if you have it. A precise restatement earns the meeting more than any pitch.

Mistakes to avoid

Do not ask about dollar amounts of overdue invoices or names of specific customers on a first call. That level of detail belongs later, once trust is established, and asking for it early signals that you care more about pipeline data than the problem.

Do not suggest that a dispute should be handled the same way as a simple late payment. They are different paths with different owners, and treating them as one thing tells the prospect you have not listened.

Do not name your product, describe a feature, or imply that automation will fix the gap you just heard about. You are one call in. Your job right now is to understand the workflow well enough that the next meeting has a clear purpose, not to sell a solution to a problem you have only heard described once.

Do not let the conversation drift into cash forecasting or recovery rates. Those are finance leadership topics, not collections process topics, and raising them out of turn makes you sound like you are guessing at value instead of listening.

If the prospect starts naming specific customer accounts or dollar figures tied to a real client, redirect gently. Say that level of detail is not necessary yet and bring the conversation back to the process itself. That protects the prospect's client relationships and keeps the call focused on the workflow, which is what you actually need to plan the next meeting.

How to practice and score it

Run this scenario with a manager or a peer playing the controller, and score three things afterward. First, did the SDR ask about the handoff without implying blame. Second, did the SDR follow a concrete answer with a deeper question instead of moving to the next line on a script. Third, did the SDR end the call with a specific next meeting tied to a named role, rather than a vague request to reconnect.

Score a fourth item too. Did the SDR resist the urge to mention a product or promise a result once the controller described the gap. That moment, right after hearing a real problem, is where most SDRs slip and start selling before they have earned the right to.

A tool like DealSpeak is useful here because it lets an SDR run the same collections scenario repeatedly against an AI counterpart that responds the way a real controller would, including the parts where the prospect gets a little guarded. Reviewing the transcript afterward shows exactly where a question landed as curious and where it landed as judgmental, which is hard to self assess in the moment.

For a broader set of scenarios in this industry, look at the Financial Services practice conversationsor read Fintech SDR Discovery Learn From Corporate Card Offboarding to see how the same disciplined approach applies to a different finance workflow. If your team also sells into companies with more than one entity, Fintech SDR Discovery for Close Calendars Across Multiple Entities covers a related mapping exercise for close calendars.

Close it out

Collections discovery works when you treat the prospect's process as something worth understanding on its own terms, not as evidence of a problem you already plan to solve. Ask about the handoff, follow the concrete answer, and let the prospect tell you who else feels the gap. That is what earns the next meeting.