Fintech SDR Discovery: Ask How Subsidiaries Report Spend

When a fintech SDR gets a prospect that manages three or four subsidiaries, the discovery call can go sideways fast. The instinct is to talk about consolidation, real time visibility, or a single dashboard for every entity. But the prospect did not call because they want a new dashboard. They called because someone in finance spends hours every quarter chasing down numbers from regional offices that do not report spend the same way. The job in this call is to find that handoff, name it plainly, and let the prospect decide if it is worth fixing.

Why this conversation goes wrong

Most SDRs open with an assumption. They ask whether the parent company wants central control over subsidiary spend, or they ask if local teams have a formal process. Both questions push the prospect toward a yes or no answer that tells you almost nothing. A finance leader who says yes to central control might still run three completely different reporting processes underneath that answer. A regional manager who says they have a process might mean a shared spreadsheet that gets updated once a quarter under pressure.

The real problem is not whether a process exists. It is what happens when the parent team needs a number from a subsidiary and the subsidiary has to translate its own records into something the parent can use. That translation step is where time gets lost, where errors creep in, and where finance teams start looking for a new tool. If you skip past that step and ask about goals or priorities instead, you miss the one detail that makes your pitch specific instead of generic.

How to prepare

Before the call, learn how many entities the company runs and how they are structured. A distributor with three regional offices reporting into one parent finance group has a different problem than a holding company with a dozen unrelated businesses. Read anything public about the company's structure, including investor materials or press mentions of acquisitions, so you are not asking questions the prospect has already answered elsewhere.

Write down two or three questions about the reporting handoff itself. Do not write questions about tools, budgets, or timelines yet. Those come later once you understand the workflow. The goal in preparation is to know enough about the company's shape that your first question sounds informed rather than generic.

Also decide in advance what you will not ask. Do not ask for actual transaction values, account numbers, or anything that touches real financial data. This is a discovery call, not an audit. You are trying to understand a process, not collect numbers you have no reason to hold.

What to say

Picture a distributor with three regional entities. Each regional manager reviews local purchasing, and the parent finance group assembles a quarterly view across all three. The SDR opens with, "When the parent team asks a region about a spend line, where does the regional manager look first?"

The prospect answers, "It depends on the region. Two of them pull from a local report that matches our chart of accounts. The third one does not have that report set up yet, so their controller builds a spreadsheet by hand after we ask."

That is the moment worth following. The SDR says, "That sounds like it creates a different amount of back and forth depending on which region you are asking. Which one of these causes the most delay when you are trying to close the quarter?"

The prospect says, "Honestly, the manual one. We usually wait two or three extra days for that region alone, and half the time the categories do not match what the other two use, so someone on my team has to reconcile it by hand."

Now the SDR has a specific handoff, a named cause of delay, and a person doing unnecessary manual work. That is enough to propose a next step. The SDR says, "It sounds like getting that third region onto a comparable report could save your team real time every quarter. Would it help to get the person who owns your parent level reporting in a room with someone from that region, so we can look at what a matching report would take?"

Notice what the SDR did not do. The SDR did not promise a consolidated view, faster closes, or better accuracy. The SDR asked about the calendar that matters, in this case the quarter close, and about which records need to be comparable across entities. The SDR did not ask for actual numbers from any spend line. The invitation names the problem plainly and leaves the prospect free to say no.

Mistakes to avoid

The most common mistake is asking a closed question early, one that lets the prospect answer in a single word without describing anything. Asking whether headquarters wants control, or whether local teams follow a process, invites a yes or no that ends the thread instead of opening it.

Another mistake is reacting to the phrase "every region is different" as if it were bad news, or worse, treating it as an objection to overcome. That phrase is an opening. A prospect who says every region is different is telling you there is variation worth mapping. The right response is to ask which difference costs the most time or causes the most rework, not to reassure them that your product handles all regions the same way.

A third mistake is jumping to a pitch before you have a specific example. If the prospect describes a general frustration without naming a region, a report, or a delay, ask a follow up question before offering anything. An SDR who proposes a meeting based on a vague complaint sounds like they are selling a demo, not solving a problem.

Finally, avoid asking for real transaction data or account level detail during discovery. It is not necessary to diagnose a reporting gap, and asking for it early makes the prospect defensive about a relationship that has barely started.

How to practice this call

Reporting handoffs like this one are hard to get right the first time you try them live, which is why rehearsal matters more than reading about it. Run this scenario with a manager or a peer playing the prospect, and have them throw out a vague answer like "every region is different" on purpose, so you practice asking the follow up question instead of moving on. Score the rehearsal on three things. Did the SDR ask an open question about the handoff instead of a yes or no question about process or control. Did the SDR follow up on a vague answer with a question that surfaces a specific example. Did the SDR propose a next step that names the problem without promising an outcome the product has not earned yet.

DealSpeak builds this kind of rehearsal into a practice conversation with an AI counterpart that can play a distracted or vague prospect and score how well the SDR handles it. If you manage a team that sells into companies with multiple entities, this scenario is worth running before reps take it live, not after a real call goes flat. You can find more scenarios built around Financial Services practice conversationsincluding a related one on Fintech SDR Discovery for Treasury Access Reviews that covers a similar handoff problem in a different part of finance. Teams rolling out a new system across entities may also want to look at Implementation Managers Building a Cutover Communication Plansince the same multi entity coordination shows up again after the deal closes.

Close

The subsidiary spend conversation is not about proving your product can consolidate everything into one view. It is about finding the one handoff that costs a finance team real time every quarter and naming it clearly enough that the prospect wants to keep talking. Practice the open question, practice the follow up, and let the prospect's own example do the selling.