Quick answer: Agree on the evaluation step before the demo, then ask whether the bank has enough information to take it. If it does not, identify the missing evidence. A compliment about the product is engagement; an agreed decision with an owner is more useful evidence of progress.
Watch the video
The Next Responsible Decision
Ask for the next responsible decision
In the companion video, I ask: “What would the next responsible decision be from here?” The answer may be involving the business owner, checking data availability, or defining a narrow proof of concept. It may also be that there is no decision to make yet. That answer helps you stop treating interest as a step you can control.
The short version
- "So, what did you think?" asks a buyer to review your product. You need them to advance a process.
- Ask instead: "Based on what we covered today, do you have enough information to take the next step we identified?"
- That question only works if you established a next step before the demo started.
- Positive feedback is an engagement signal. Stakeholders, due diligence, and documented requirements are progress signals. Forecast on the second kind.
I have been on both sides of this meeting.
Early in my career I was the banker sitting through the demo. For the 23 years after that I was the vendor giving it, and eventually the revenue leader reviewing why deals in my team's pipeline had gone quiet. The pattern I saw from the leadership seat was consistent. The demos that died were rarely the bad ones. They were the ones that ended warm and vague.
The demo is not the main event
Founders treat the demo as the moment the deal is won. It is one input into an institutional decision that involves people who were never in the room.
A bank is not deciding whether your software works. It is deciding whether it can absorb your company. Those are different questions, and the second one takes longer.
That reframe changes what you show, what you ask, and what has to be true when the meeting ends.
What happens after you leave the room
This is the part most founders underestimate, so it is worth naming the actual machinery.
The agencies’ 2023 guidance describes principles for managing third-party relationships through their life cycle. The 2024 community-bank guide provides practical considerations. These sources help explain the institution’s evaluation work; they are not a universal sales timetable.
You do not need to quote regulation back at your buyer. You need to understand that your champion is walking into a process with defined stages, documentation requirements, and people whose job is to slow things down on purpose.
When you ask "what did you think," you are asking someone for a personal reaction to an institutional problem.
The question you should ask instead
Here is what "So, what did you think?" usually produces:
- "It looks really interesting."
- "I like what you showed us."
- "We should discuss this internally."
- "Send me some information and we'll circle back."
None of those are buying signals. A buyer can admire your product for eighteen months and never sign.
Ask this:
"Based on what we covered today, do you have enough information to take the next step we identified?"
It does three things at once. It ties this meeting to a process both sides already agreed to. It forces the room to name anything still missing. It opens the conversation about what happens next without you having to pitch for it.
If the answer is yes, you move. If the answer is no, you have just learned what is blocking the deal while everyone is still on the call. That is worth more than six weeks of checking in.
The next step has to exist before the demo starts
You cannot ask about "the next step we identified" if you never identified one.
Set it in the meeting before. It sounds like this: if the platform meets the business requirements we discussed, what happens after this demo?
Depending on the institution and the stage, that next step might be:
- Bringing in the CIO, COO, or the business line executive who owns the P&L.
- Opening an information security or vendor risk assessment.
- Reviewing integration requirements with the core team.
- Introducing compliance, legal, or procurement.
- Building the internal business case.
- Scheduling technical discovery.
- Reviewing pricing and commercial terms.
Which one matters less than having one. Without it, the meeting ends in "we'll talk internally," and you leave without knowing what has to be true for the deal to move.
Discovery decides which demo you give
If you are giving the same demo to every institution, the problem is upstream.
A multibillion dollar regional bank and a $500 million credit union can be looking at the same product for completely different reasons. Two credit unions of identical size can have different cores, different risk appetites, and different approval chains.
Before I decide what deserves demo time, I want answers to:
- What triggered this evaluation now?
- What happens if they do nothing?
- How is the problem handled today, and where does it break?
- Which outcome matters most, and how will they measure it?
- Who evaluates, and who approves?
- What internal reviews are required?
- Is there a target implementation date, and what could push it?
Discovery is not the thing you finish so you can finally demo. Discovery tells you which demo to give.
Then build the demo around the institution's priorities rather than your feature list:
If a credit union tells you member onboarding abandonment is the problem, fifteen minutes of unrelated admin functionality does not strengthen your case. It dilutes it. Three capabilities that map to their stated problem beat twenty that do not.
Engagement signals are not progress signals
This is the distinction I wish more founders learned early. People can love your product and still never buy it.
Engagement signals:
- Detailed product questions
- Requests for another demo
- Compliments on the interface
- Longer meetings
- Interesting use case discussions
Progress signals:
- The right stakeholders have joined the evaluation
- Security or vendor due diligence has started
- Integration requirements are being documented
- The business case is being built
- Budget has been identified
- Procurement or legal has entered
- Both sides committed to a specific next action with an owner and a date
Track engagement. Forecast on progress. Most fintech pipelines I review are inflated because the two got mixed together.
Your champion has to sell this without you
You get an hour. Your champion may spend two months explaining your solution to executives, IT, compliance, procurement, finance, and risk, most of whom never saw the demo.
Give them clear answers to three questions:
- Why change? What is no longer acceptable about the current state.
- Why this? Why your approach fits their environment better than the alternatives, including doing nothing.
- Why now? Why this project beats the dozen others competing for the same budget.
If your champion cannot make those three points in a hallway without you, your deal is more fragile than your CRM says it is.
The seven-step sequence
- Reconfirm the problem you heard in discovery.
- Reconfirm the outcome they want and how success gets measured.
- Confirm what this specific meeting needs to accomplish.
- Show only the workflows connected to those priorities.
- Answer the buying questions appropriate to this stage, not every stage.
- Ask what the team still needs to understand.
- Confirm the next step, the participants, the owner, and the date.
That turns a product presentation into a decision-making meeting.
Where this does not apply
I work with community banks, credit unions, and the fintech founders selling into them, including through core and digital banking channel partners. That is the lens here.
The largest national banks and non-US institutions run materially different processes. If you are selling through a core provider's marketplace or a sponsor bank arrangement, the evaluation path changes again, and your real buyer may not be the institution at all. The principle holds. The stages do not.
Final word
Banks and credit unions do not buy because the demo impressed them. They buy when enough of the right people believe the problem is worth solving, the economics work, the risk is acceptable, and the organization can actually implement it.
Change three things this quarter:
- Stop measuring demos by reaction. Measure whether the opportunity advanced.
- Show less product and more relevance.
- Never end without a defined next step.
Then stop asking what they thought. Find out whether you gave them what they needed for their next decision.
Frequently asked questions
What should a fintech founder include in a bank demo?
Only the workflows that address the problem the institution named in discovery. Show how the current process changes, answer the buying questions relevant to this stage, and give the team enough to decide whether to move forward.
How long should a fintech demo for a bank or credit union be?
There is no universal answer. A focused 30 minutes that answers this stage's buying questions beats a 60 minute feature tour. Length is a symptom. Relevance is the variable.
Why do fintech sales cycles with banks take so long?
Because the decision is distributed. Business leadership, IT, information security, compliance, risk, legal, procurement, and finance may all have standing in the process, and regulatory guidance expects institutions to run structured due diligence on third parties. The specific path varies by institution and by how critical your solution is to their operations.
How can fintech founders shorten bank sales cycles?
You cannot remove legitimate review. You can remove avoidable delay: strong discovery, early stakeholder identification, a defined next step after every meeting, and due diligence materials prepared before anyone asks for them. That reduces avoidable delay; it does not guarantee a particular sales-cycle length.
What should I ask at the end of a fintech demo?
"Based on what we covered today, do you have enough information to take the next step we identified?" If the answer is no, find out exactly what is missing before the call ends.
What is the biggest mistake fintech founders make when selling to banks?
Reading product interest as purchase intent. A buyer can like your technology and still lack the budget, authority, urgency, internal alignment, or risk approval to buy it.
Guidance context, October 12, 2026: The agencies’ 2023 third-party relationship guidance and 2024 community-bank guide are the background for this discussion. In September 2026, the agencies issued proposed revisions; the OCC describes those revisions as proposed, with application when final. Do not treat a proposal, this article, or a vendor checklist as a binding rule.
Sources
- Stacy’s next-responsible-decision video
- Interagency third-party relationship guidance
- Community-bank guide
- OCC September 2026 proposed revisions
Continue the conversation
For help translating your product and sales process into a bank-ready decision, explore working with Stacy. For ongoing practical guidance, subscribe to Selling Fintech.
Adapted from Stacy Bishop’s original posts and newsletter with AI-assisted editing. Cover portraits were generated from Stacy’s reference photographs. Illustrative exercises are labeled.
