Pavone
SIGN IN

Discovery Call Questions for Fintech Sales

Fintech buyers combine the speed of a software company with the regulatory weight of a financial institution. These discovery questions are written for selling into payments, lending, banking-as-a-service and wealth platforms: they cover transaction volume, unit economics and the compliance stack, and they map a decision process that runs through engineering, risk and finance at once.

Want one built around your product? Use the Discovery Call Question Generator.

What Fintech buyers care about

The buyer at a fintech is typically a head of operations, risk, compliance or product, a VP of engineering for anything in the transaction path, or a growth or revenue leader for anything touching acquisition. Their world is transactions and the margin on them: payment volume, loan originations, accounts opened, and the take rate or interest spread on each. They operate under licenses or partner bank relationships that impose rules, and they scale fast enough that last year's manual process is this year's bottleneck.

They are judged on transaction volume, take rate or net interest margin, customer acquisition cost against lifetime value, fraud and chargeback rates, default rates in lending, onboarding conversion and the regulator's or partner bank's view of their controls. Operations leaders are measured on cost per transaction and on how many customers each support or compliance agent can handle. Investors and boards ask about unit economics and the path to profitability, so every spend is justified in those terms.

They are wary of vendors who do not understand their regulatory obligations, who cannot pass a security and compliance review, or who cannot integrate through an API without a long professional services engagement. They are often engineers at heart and will evaluate on documentation and sandbox quality. They respect reps who ask about volume, fraud, compliance workload and the partner bank, and who are concrete about integration effort.

Situation questions

Payments, lending, neobanking, wealth and infrastructure fintechs have different economics, regulators and bottlenecks, and the buyer will assume you do not know the difference until you prove otherwise. Establish the model, the volume, the licensing structure and the stack before you ask about pain.

  1. How would you describe the business: payments, lending, banking, wealth, infrastructure, or a mix, and what is the core unit of volume you track?
  2. Roughly what monthly volume are you processing, and how fast is it growing?
  3. How are you licensed or structured: your own licenses, a partner bank or sponsor, a program manager, and what does that relationship require of you?
  4. What does the stack look like for the area we are discussing: in-house, vendor, or a mix, and how is it integrated?
  5. What is driving this conversation: scale, a regulatory or partner bank requirement, a fraud or loss problem, a cost target, or a product launch?

Pain questions

Fintech pain shows up as manual review queues, fraud losses, onboarding drop-off, compliance findings and engineering teams stuck on maintenance instead of product. Ask about specific queues, rates and incidents; operations and risk leaders can quantify them precisely.

  1. Where are manual reviews piling up, whether onboarding, transactions, disputes or compliance alerts, and how is the team keeping up?
  2. What are fraud, chargeback or default rates doing, and where did the last significant loss come from?
  3. Where in onboarding do customers drop off, and how much of that is friction you control versus requirements you do not?
  4. What was the last finding from a regulator, auditor or partner bank, and what did it take to close it?
  5. How much engineering time goes to maintaining this part of the system rather than building product?

Impact questions

Fintech leaders think in basis points on volume and in cost per transaction, so the arithmetic is fast once they engage. Tie pain to take rate, loss rates, conversion and cost to serve in their own figures. A few basis points at their volume is a number they will defend to the board.

  1. What is a basis point of loss or margin worth at your current volume, and at the volume you expect next year?
  2. If onboarding conversion improved by a few points, what does that mean in accounts and revenue over a year?
  3. What does the manual review queue cost in headcount today, and what does it look like if volume doubles without a change?
  4. What would a regulatory or partner bank finding in this area cost in remediation, restrictions or delayed launches?
  5. If unit economics stay where they are, what does that do to the next fundraising or profitability conversation?

Decision process questions

A fintech purchase goes through engineering for integration, risk and compliance for approval, security for review, finance for unit economics and often the partner bank for anything in the regulated path. The sponsor cannot sign alone. Map every gate, because the partner bank review is the one reps forget.

  1. Who sponsors this, and who in engineering, compliance, security and finance would need to approve it?
  2. Does the partner bank or sponsor need to review or approve vendors in this area, and how long did that take last time?
  3. What does your vendor security and compliance review look like, and what documentation do you need from us up front?
  4. How is integration effort estimated and prioritized against the product roadmap, and who makes that call?
  5. Is there budget in the current plan, or would this need to displace a vendor or an internal build?

Next step questions

Fintech buyers want to see the API, the documentation and the compliance posture before they commit time. Propose a technical and compliance review in parallel, with named owners, scoped to a specific flow, and agreed success criteria for a sandbox or pilot.

  1. Would it make sense to get an engineer into the sandbox and a compliance lead into our documentation at the same time, so both reviews run in parallel?
  2. If we scoped a pilot on one flow or one segment, what would you need to see in loss rate, conversion or review volume to proceed?
  3. Who else needs to be in the next conversation, including anyone from the partner bank side?
  4. What is a realistic timeline given your roadmap, your review process and any regulatory or launch deadlines?
  5. Is there anything in your regulatory setup or your architecture that you think would rule this out?

Red flags on a Fintech discovery call

  • The company is raising a round or has just had a down round, and all vendor decisions are on hold until the money is in or the cuts are done.
  • The sponsor has not spoken to compliance or the partner bank and assumes they will be fine with it.
  • Engineering has no capacity for integration this quarter, and the sponsor cannot move it on the roadmap.
  • They cannot describe their loss rates, review volume or onboarding conversion, which means nobody owns the problem.
  • They are seriously considering building it in-house and are using your call to scope the internal project.

Tips for running the call

  • Understand the regulatory structure before the call: licensing, partner bank, program manager. Asking about it early shows you know the industry.
  • Establish the business model and the unit of volume first. Payments, lending and banking have different economics.
  • Ask about queues, rates and findings, specifically. Fintech operations and risk leaders have precise numbers.
  • Frame impact in basis points on volume and cost per transaction, at current and projected scale.
  • Run engineering, compliance and security reviews in parallel. Sequential reviews at a fintech take two quarters.
  • Ask about the build versus buy question directly. Fintechs have strong engineering teams and the internal build is your real competitor.

Frequently asked questions

What questions should I ask a fintech company on a discovery call?

Ask what the business model is and what unit of volume they track, how they are licensed or which partner bank they use, where manual reviews are piling up, what fraud or loss rates are doing and where onboarding drops off. Then ask what a basis point is worth at their volume and who in compliance, engineering and the partner bank must approve.

How do I sell to fintech startups?

Be technically concrete and compliance-ready. Fintech buyers evaluate on API documentation, sandbox quality and security posture, and they will compare you against building in-house. Tie value to unit economics and loss rates, and run engineering and compliance reviews in parallel to shorten the cycle.

What metrics do fintech buyers care about?

Transaction or origination volume, take rate or net interest margin, fraud and chargeback rates, default rates, onboarding conversion, customer acquisition cost against lifetime value, cost per transaction and the status of regulatory and partner bank controls. Ask for the real numbers for the flow you are discussing.

How long is the fintech sales cycle?

Two to six months for operational tools outside the regulated path, longer for anything in the transaction flow or that the partner bank must approve. Engineering roadmap capacity is often the real constraint. Fundraising and regulatory deadlines can accelerate or freeze the cycle without warning.

What is the biggest mistake reps make selling into fintech?

Forgetting the partner bank and the build-versus-buy question. Reps who get a sponsor excited and skip compliance discover a bank review in month four, and reps who do not ask about internal builds lose to the engineering team. Ask about both on the first call.

More discovery call questions by industry

Start practicing in minutes

AI Roleplays for any scenario

  • Build a roleplay from your scenario
  • Practice with AI, voice to voice
  • Get instant, structured feedback after practice
  • Free to start — no credit card required