In fintech the buyer is regulated, so every purchase that touches money, customer data or a license passes through risk, compliance and security, and each of them can stop it. A fintech rep can have an enthusiastic product owner and a signed-off budget and still lose the quarter to a vendor risk review nobody booked.
This page applies the deal risk guide to fintech teams selling to banks, credit unions, lenders, insurers and other financial firms. The examples are invented; we do not publish customer outcomes by industry.
Selling to banks, lenders and insurers
A fintech deal carries two kinds of risk for the buyer. The usual one: will the product solve the problem? And the regulated one: what happens to the buyer's license, audit or customers if the vendor fails? The second question has its own owners, its own documents and its own calendar, and the rep rarely meets those owners early.
So fintech reps lose deals in a pattern. The business case is strong, the champion is keen, and the deal reaches "contract" before anyone in vendor risk has seen it. Then it waits. The quarter ends with the deal still "on track".
Four pressure points
| Pressure point | Coach on the live deal | Evidence it is working |
|---|---|---|
| Buying group | Who in risk, compliance, security and procurement must approve, and whether the rep has met them | Each approver named, with a date the rep will speak to them |
| Cycle length | The approval path, mapped back from the close date | A written sequence of reviews with owners and dates, agreed with the champion |
| Missing evidence | What the buyer said the problem costs, and who outside the champion has said it | The cost in the buyer's words, from someone who can sign |
| Method | The decision process and paper process in the team's method | The rep can describe each review the deal must pass, in order |
The buying group has risk and compliance in it
In a fintech deal, the people with a veto often do not use the product. A head of payments wants it; the chief risk officer, the compliance lead and the information security team decide whether the bank can take it on. Each asks different questions and needs different evidence.
Coach the full list of approvers, and the question the rep will ask each one. The manager listens for whether the rep has heard from anyone outside the champion. One question does this job: who besides your champion has said this must be fixed this quarter?
A rep who has this covered has asked the champion who ran the last vendor risk review, and has a meeting with that person before the security questionnaire arrives.
The cycle is long, and deals slip on approvals
Fintech deals run long because the reviews run in sequence: security before risk, risk before legal, legal before procurement. A close date that ignores that sequence is a guess.
- 01Security review
- 02Risk review
- 03Legal
- 04Procurement
Here the manager coaches the approval path, written backwards from the close date. For each review: who owns it, how long it usually takes at this buyer, and what the rep must hand over to start it. A deal with a mapped path can be forecast honestly, which is how coaching improves the number. The forecast accuracy piece covers the forecast call.
The sign it is working: the champion has agreed the path in writing and the rep has started the longest review first.
The evidence most fintech deals lack
The common gap is a cost the buyer has stated. Fintech buyers are cautious, and a cautious buyer with no stated cost of inaction will wait. Without a stated cost, the risk team weighs the vendor risk against nothing, and nothing wins.
In the 1:1, the manager asks what the buyer said the problem costs (fraud losses, manual reconciliation hours, a delayed product launch, an audit finding) and who said it. If no one has, they work out the question the rep will ask next.
Aim for a cost stated by someone senior enough to weigh it against the vendor risk.
Running the method through the approval path
Most methods name this part. MEDDPICC calls it the decision process and the paper process; the MEDDPICC page describes both. Gap Selling asks for the buyer's current state and the cost of staying there. The ValueSelling Framework® asks for the buyer's view of value and access to power. The method is only useful in fintech if the manager coaches those elements on every deal, because those are the elements a regulated purchase tests hardest.
The coaching target is the weakest element of the team's method on this deal, worked into the rep's next call.
Good here means the rep names the weakest element unprompted and has a question ready for it.
The claims a rep makes have to survive review
Everything a fintech rep says on a call can end up in a risk file. A loose sentence about uptime, data location or regulatory status gets written down by the buyer, checked by their security team, and asked about again in legal. A rep who overstates once spends the next month walking it back, and the risk team now reads every answer with more suspicion.
The opposite failure is just as common. A team that trains compliance and never coaches selling ends up with reps who are careful and still lose. The manager coaches both at once, on the live deal.
In the debrief after each buyer call, the manager asks the rep which claims they made about security, data handling or compliance, and whether each one is in the company's approved answers. Anything that is not goes to the right internal owner before the buyer's questionnaire asks about it. Then the manager coaches the selling part: did the rep ask the risk lead what a failed vendor would cost them, or only answer questions?
Over time the rep makes fewer, plainer claims, each one already documented, and spends the saved time asking the approvers about their own concerns. "I'll confirm that in writing with our security team" is a strong answer on a fintech call.
Example: a fraud screening deal (illustrative)
The deal is made up. Dev sells a fraud screening API to a regional bank. The deal is forecast for this quarter at "commercial terms". The champion is the head of digital payments.
What the dashboard shows. The conversation intelligence tool marks the deal at risk: no executive engaged, and the last two calls were with the same person.
The call with Caty. Dev calls Caty and talks the deal through. She asks what the head of payments said the problem costs. Dev says chargebacks are rising, but has no figure. She asks who besides the champion has said this must be fixed this quarter. Nobody. She asks for the approval path. Dev knows legal has the contract and does not know who does vendor risk.
What Caty finds. The deal is missing a stated cost, a second voice and a mapped path. She prepares the next call with Dev: ask the champion to walk through how the last fintech vendor was approved, by whom, and how long each review took; ask what the chargeback trend cost last quarter; ask whether the chief risk officer has seen the case, and offer to brief her.
The next call. The champion says vendor risk takes about six weeks at this bank and has not started. The close date moves to next quarter, honestly, with a path behind it. The champion books a 30-minute call with the chief risk officer. The forecast is now one deal smaller and one deal more accurate.
From a risk flag to the next step
Revenue intelligence tools are good at telling a manager which deals are at risk. Gong and Clari flag risk; the question a fintech manager still has to answer is what the rep does about it this week. The deal risk score vs deal coaching piece compares the two jobs, and our post on why a risk score is not a fix makes the argument.
Our AI sales experts pick up where the flag stops. Each rep's deals are staged by buyer evidence, the expert names what each deal is missing, and one click puts the rep on a call with Caty to prepare the next conversation with the approvers. The rep describes the deal out loud and Caty works it in the team's method. Typing is there when talking is not possible. Drive deal execution shows how managers see it across the team. For a fintech deal stuck in review, talk to us.
FAQ
How is coaching fintech sales reps different from coaching SaaS reps?
Fintech buyers are regulated, so risk, compliance and security can each stop a deal, and their reviews run in sequence. A fintech manager coaches the approval path and the approvers on every deal, as well as the business case. A SaaS manager can often coach the champion and the budget owner and expect the rest to follow.
Why do fintech deals slip at the end of the quarter?
Most slip because a review nobody mapped starts late: vendor risk, information security or legal. The rep forecast the deal on the champion's enthusiasm and the commercial terms. Mapping the approval path back from the close date, with owners and durations, catches this weeks earlier.
How do you coach a rep selling to banks?
Coach the deal the bank will run internally. Ask who approves vendors, who owns risk, what the last approval took, and what the buyer said the problem costs. Then prepare the rep's next call so they ask for the missing piece, and meet the approvers before the paperwork reaches them.
Should fintech sales teams use a sales methodology?
Yes, fintech sales teams should use a named sales methodology, because it gives the manager and rep shared words for what a deal is missing. MEDDPICC's decision process and paper process fit regulated buying well, and Gap Selling and the ValueSelling Framework® both force the cost conversation. Pick the one the team will coach to every week.
What is the difference between a deal risk score and deal coaching?
A deal risk score tells a manager which deals look unhealthy, based on activity and engagement signals. Deal coaching works out what a specific deal is missing and prepares the rep's next conversation to fix it. The score points at the deal; coaching changes what happens on the next call.