Fintech Revenue
How to Sell Fintech to Banks Without Discounting
Quick answer: Discounting does not fix the real reason most bank deals stall. When a bank is not moving, the cause is usually unclear urgency, weak internal ownership, perceived risk, or an unproven business case. A price cut does not solve any of those, and it often makes the risk question worse. The alternative is to strengthen the business case, equip the internal champion, reduce perceived risk, and use scope and pilot structure instead of price as your flexibility.
After more than 28 years in banking and fintech, including 23 years inside Jack Henry, I have seen what happens inside a bank when a vendor suddenly drops their price. It is rarely what the founder hopes. The banker does not think "now we can move." The banker thinks "why was the first price wrong, and what else is soft?"
Table of Contents
Why Founders Reach for Discounts in Bank Deals
What a Discount Actually Signals to a Bank
The Four Real Reasons the Deal Is Stuck
Strengthen Urgency Without Pressure
Show Value by Stakeholder
Use Scope and Pilot Structure Instead of Price
What to Say When the Bank Asks for a Lower Price
FAQ
Why Founders Reach for Discounts in Bank Deals
The quarter is ending. The board wants logos. The bank has gone quiet, and price is the one lever the founder fully controls. So the founder pulls it.
I understand the pressure. But in 28 years of bank deals, I can count on one hand the times price was the real blocker. A discount is a solution to a problem the bank does not have, paid for with margin you will not get back.
What a Discount Actually Signals to a Bank
Banks are professional risk evaluators. I have watched surprise discounts land in bank deals, and I can tell you the signals they send are not the ones the founder intends:
The vendor may be desperate, which raises viability questions in due diligence
The original price was inflated, which damages trust in everything else you said
Future pricing is negotiable forever, which trains the bank for renewal battles
There is a worse one. If the bank's real hesitation is risk, a discount confirms it. Risky and cheap is not more attractive to a bank than risky. It is less.
The Four Real Reasons the Deal Is Stuck
Unclear urgency. The bank agrees the problem exists but has not decided it matters this year. No discount creates urgency.
No internal owner. Nobody inside the bank owns the decision, so it routes nowhere. I wrote about this pattern in Why Community Banks Say "Interesting" But Never Move Forward.
Perceived risk. Someone in the approval chain is not yet convinced this is safe: data, vendor viability, implementation, or regulatory optics.
Unproven business case. The bank cannot defend the spend in numbers it trusts. The deal is not too expensive. It is unjustified, which feels the same but has a completely different fix.
Diagnose before you negotiate. Ask your champion directly: "What would have to be true for this to move forward this quarter?" In my experience, the answer almost never contains the word price.
Strengthen Urgency Without Pressure
Manufactured urgency backfires with banks. Real urgency comes from connecting your product to clocks the bank already watches: exam cycles, board priorities, budget season, a competitor's visible move, rising losses in a measurable line.
Show the cost of waiting in the bank's own measures. "Every quarter this stays manual costs roughly X hours and Y exceptions" moves a bank. "This pricing expires Friday" insults it.
Show Value by Stakeholder
A stalled deal often means one stakeholder sees the value and four do not. Operations needs to see workload relief. Finance needs a conservative, defensible return. Risk needs to see exposure going down, not up. Executives need a story they can repeat to the board.
When each stakeholder can state the value in their own terms, price stops being the conversation. When they cannot, price becomes the excuse. Equipping your champion to run these conversations is the highest-leverage work in the deal.
Use Scope and Pilot Structure Instead of Price
When a bank genuinely needs a smaller commitment, give them a smaller commitment, not a cheaper one:
Narrow the initial scope to one use case or one workflow
Structure a paid pilot with defined success metrics and a contract path, like I described in How to Turn a Community Bank Pilot Into a Paid Contract
Phase the rollout so spend follows demonstrated value
Adjust payment timing rather than total value
Every one of these preserves your pricing integrity while honestly meeting the bank's need to start smaller. That is a real difference, not a framing trick: the bank gets less risk, and you keep your margin and your credibility.
What to Say When the Bank Asks for a Lower Price
First, treat the question as information. "Help me understand what's driving that. Is it budget, or is it confidence in the return?" The answer tells you whether you have a finance problem, a risk problem, or a champion problem.
Then trade, never give. If movement on price truly becomes necessary, exchange it for something real: a longer term, a reference commitment, a case study, expanded scope later. A concession with nothing in return resets the bank's expectations for the life of the relationship.
FAQ
Should I ever discount for a first bank customer?
Prefer narrowing scope over cutting price. If you do trade pricing for being early, name it explicitly as a founding-customer arrangement with defined terms, so it does not silently become your price.
What if a competitor is cheaper?
Banks rarely buy the cheapest option in a risk-bearing category. If you are losing on price alone, the bank does not see a difference in value or safety. That is the actual problem to fix.
Is end-of-quarter pricing ever effective with banks?
Bank buying timelines are driven by committees, exams, and budgets, not your fiscal calendar. Quarter-end pressure mostly teaches banks to wait for it.
If discounting has become your closing strategy, the deal is missing a business case someone inside the bank can defend. I help fintech founders build that case instead of paying for its absence. Let's talk.
about the author
Stacy Bishop
Stacy Bishop brings 28+ years across banking and fintech, including 23 years inside Jack Henry and $100M+ in bank-related deal exposure. She helps fintech founders translate innovative products into bank-ready categories, stakeholder priorities, risk answers, and buying committee language so deals can move through internal review.
You May also like
