Fintech Revenue
Why FinTech Founders Lose Bank Deals Before the Demo
You've done the discovery call. The banker was engaged, asked real questions, said things like "we could really see this fitting into what we're trying to do here." You walked away thinking the deal was warm.
Then nothing. A follow-up email. A polite response. A slow fade.
If that pattern is familiar, I want to offer you a diagnosis that has nothing to do with your pitch, your demo, or your pricing.
The problem is categorization. And until you solve it, every meeting you take will produce the same result.
I spent 23 years inside Jack Henry, and the last six working alongside FinTech founders trying to sell into community banks and credit unions. In that time, I've watched brilliant products stall at the exact same point — not because they weren't good enough, but because the banker couldn't sort them. No shelf, no deal. It doesn't matter how impressive the technology is.
This post is about what that problem actually is, why it persists even among sophisticated founders, and the five-part framework I use with clients to solve it.
Table of Contents
What the Category Conundrum Actually Is
Bankers don't evaluate vendors from scratch. They sort them.
The moment a FinTech walks into a meeting — or clicks into a video call — the banker's brain is already working through a checklist, consciously or not. Where does this go? What budget line does it come from? Who internally owns this category? What does vendor management need to do with it? What examiner category does it fall under?
This is not a flaw in the way bankers think. It is an entirely rational response to the volume of vendor outreach they receive and the complexity of the institutions they manage. They are running organizations with fiduciary obligations, examiners, boards, and communities depending on them. Mental categorization is a survival skill.
The problem for FinTech leaders is that the most innovative products — the ones that should theoretically win — are also the hardest to sort. They don't fit neatly into core IT. They're not a loan product or a payments product or a compliance tool or a CRM. They're genuinely new. Which is also why they stall.
When a banker can't sort you, they don't reject you. Bankers are almost universally polite. They smile, engage, ask thoughtful questions, and tell you they'll follow up. What they're actually doing is parking you. The deal sits in a mental holding queue that never converts to action because there is no internal pathway for it. No budget owner to bring it to. No vendor management process to initiate. No champion who knows what to call it.
Being interesting to a banker is not the same as being understood by one and interesting does not get you to a contract.
The Case Study: 40 Discovery Calls, Zero Conversions
A founder I worked with had done everything right. He had a genuinely strong product. He had done the outreach, booked the meetings, and conducted approximately 40 discovery calls with community banks and credit unions. By every external measure, those calls went well. Bankers liked him. They asked real questions. They said things like "this is really interesting" and "we could see this fitting into what we're doing."
Zero conversions. No next steps. No timelines established. No deals in motion.
He came to me convinced the problem was his demo. He wanted to tighten his messaging, add a case study, adjust the ROI slide. He had done the rational thing a founder does when they're not closing — look at the pitch and try to improve it.
My diagnosis was different. His product didn't fit neatly into any existing category at the banks he was pitching. It wasn't core IT. It wasn't a lending product. It wasn't compliance software. It wasn't a CRM. It was genuinely innovative — sitting at the intersection of two or three categories without owning any of them completely.
That was the problem. Not the demo. Not the messaging. Not the ROI slide.
The bankers he spoke with couldn't answer the internal questions that would move a deal forward: What budget does this come from? Who owns it? What do I call it when I bring it to my vendor management committee? Without answers to those questions, the most natural path is to do nothing. And that's exactly what they did.
The sale doesn't happen at the demo. It happens when the banker finally understands what you are. If that moment never comes, no demo will save you.
Why Anchoring Is the Answer
In 2001, Apple launched the iPod. The device contained a one-and-a-half inch micro hard drive capable of storing and playing back compressed audio files at variable bit rates through a proprietary digital interface. None of that was in the launch copy.
What Apple said was: "A thousand songs in your pocket."
Four words. No specs. No architecture diagram. No feature breakdown. Just a shelf built around a frustration people already had — the CD binder, the cassette case, the limited soundtrack you could carry through an airport.
Nobody needed to understand how the iPod worked. They just needed to feel the relief of not carrying that binder anymore. The anchor did the work before the product had to.
The same mechanism applies in every bank meeting you walk into.
Before you explain a single feature, you have one job: give the banker a shelf to put your product on. Root your solution in something they already understand, already feel, or already live with every day. Not because bankers are unsophisticated — they're not. Because every buyer, in every industry, needs a mental category to take the next step. When they can't categorize you, they park you.
Most FinTech founders believe their job in a bank meeting is to explain what they built. It isn't. Their job is to do the translation work the banker shouldn't have to do.
Anchoring is not dumbing it down. It is earning the pitch.
The Five Anchors Framework
There is not one kind of anchor. There are five, each targeting a different buyer profile and requiring a different kind of homework. Understanding which anchor to use — and when — is what separates founders who close from founders who keep getting "this is really interesting."
Five Anchors Framework diagram — five labeled boxes (Pain Anchor, Task Anchor, Technology Anchor, Process Anchor, Emotion Anchor) each connected to a specific buyer type (Strategic Buyer, Operational Buyer, CIO/CTO, Multi-Stakeholder Deal, Internal Champion) arranged around a central "Anchor Before You Pitch" hub
Upload ImageGenerate with Imagen 4Edit prompt
Anchor Type | Best Used With | What It Names | Requires |
|---|---|---|---|
Pain Anchor | Strategic / executive buyers | What the institution is actively losing | Specific, quantifiable cost data |
Task Anchor | Operational buyers | What their team does manually every week | Specific task, time estimate, department knowledge |
Technology Anchor | CIOs, CTOs, technology owners | How current tools are being misused | Honest assessment of their existing stack |
Process Anchor | Multi-stakeholder deals | Where their buying process stalls for solutions like yours | Deep familiarity with institution procurement |
Emotion Anchor | Any buyer — when used carefully | What the banker feels but hasn't said aloud | Extensive banker conversations, not inference |
Anchor 1: The Pain Anchor
The most common anchor type, and also the most commonly misused.
There is a version of the pain anchor that works, and a version that sounds like a press release. Most FinTech leaders use the one that sounds like a press release.
The one that doesn't work: "Banks are facing increasing pressure from digital-first competitors and need to modernize their infrastructure to remain competitive." Every banker has read this sentence in every deck they've seen this quarter. It signals nothing except that you watched the same industry webinar they did.
The version that works: "You're losing approximately X percent of your deposit base to digital-first players every year. Not because you have a bad product — because the friction at account opening is costing you the relationship before it starts."
The difference is specificity and ownership. The pain has to be theirs, not the industry's. It has to be real, not theoretical. It has to be something they already feel — even if they haven't put a number on it yet.
When you get the pain anchor right, you'll know. Bankers nod before you've told them what you do. That nod means you're in. You've earned the next sentence.
Anchor 2: The Task Anchor
Operational buyers at banks do not respond to strategy language. They respond to someone who can name their Tuesday.
The task anchor works because it starts exactly there. Before you introduce your product, you describe a specific thing their team does manually every week — the task everyone on the floor hates, the one that takes forever, the one that only exists because there hasn't been a better option.
Here is what this sounds like in practice: "Your ops team spends 40 hours a month reconciling vendor documentation. That's a full week per quarter, every quarter, just on reconciliation."1
You have not told them what your product does. You have told them you know their life. That is a fundamentally different kind of credibility — and it opens a door that a feature walkthrough cannot.
This anchor is also a diagnostic for your own preparation. If you cannot name a specific, real task — with time attached and department ownership clear — you have not done enough homework to use it. The anchor is earned, not assumed. Do the homework. Then name the task.
Anchor 3: The Technology Anchor
Bankers hear a remarkable number of pitches about new technology. They almost never hear someone tell them the truth about their current technology.
The technology anchor works by doing exactly that. You start not with what you've built, but with how they're currently using existing tools — and specifically how those tools are being pushed beyond what they were designed to do.
The framing: "You're asking your core system to do something it wasn't built to do. It technically works, but it creates a lot of downstream problems."
This is effective with CIOs and CTOs for reasons that go beyond positioning. It signals that you've done real work before walking in. You understand their stack. You're not pitching blind. And you're being honest in a way that most vendors aren't — naming a limitation that's real rather than selling around it.
That honesty builds immediate trust. It makes the banker more receptive to what follows because they've just heard something true, which is rarer than it should be in a vendor meeting.
Anchor 4: The Process Anchor
This is the most underused anchor in the framework and, in multi-stakeholder deals, often the most powerful.
The process anchor doesn't start with the banker's pain or their team's workload. It starts with how decisions get made inside their institution — and specifically where the buying process tends to stall for solutions in your category.
The framing: "Here's how a new vendor typically moves through a buying committee at an institution like yours. At this stage, deals usually stall — here's why, and here's how we make that stage easier for you."
When you can map their internal procurement process back to them before they've described it, you demonstrate a level of institutional knowledge they didn't expect. Most vendors only know the outside of the door. You're showing them you know what happens inside the building.
But this anchor has a second function that makes it strategically distinct from all the others: it equips your internal champion.
In most bank deals, the person you're sitting across from is not the decision-maker. They're the person who will carry your deal into rooms you'll never be in, to stakeholders who have never heard of you. If they can't explain you clearly — if they don't have crisp language for what you are and why you're worth bringing forward — your deal dies in those internal conversations.
The process anchor gives your champion exactly what they need. You're not just selling to the person in front of you. You're writing their script for the conversations you can't attend.
Anchor 5: The Emotion Anchor
This one requires care. When it lands, it is often the most powerful anchor in the set. When it doesn't, it can derail a meeting immediately.
The emotion anchor starts with how the banker feels in their current world — not what they're losing, not what their team is doing, not how their technology is performing. How they feel.
This sounds like: "Every banker I talk to tells me they feel behind. They know the landscape is shifting — AI, embedded finance, changing customer expectations. They don't know if their institution is moving fast enough, and they don't have a clear picture of what fast enough even looks like."
When you name what someone is feeling before they say it out loud, something shifts. They begin to trust you differently — not as a vendor running a pitch, but as someone who genuinely understands their world.
The critical constraint: this only works if it's real.
Do not guess at banker emotions. Do not use language that sounds empathetic but is generic. If you haven't spoken to enough bankers — enough times, deeply enough — to genuinely know what the people in your ICP are feeling, do not use this anchor. It will read as performance. And banking audiences are exceptionally sensitive to performance.
These are tools, not gimmicks. The emotion anchor is earned through conversations, not through reading industry reports.
The Core Rule: Anchor to the Present, Not the Future
Everything I've described above depends on a single underlying principle that is easy to state and harder to internalize.
Anchor to the present. Not the future.
FinTech founders have a natural tendency — understandable, often well-intentioned — to lead with what's coming. The AI-driven future. The embedded finance revolution. The competitive landscape two years from now. They frame their product as the way to get ahead of what's next.
The problem: if you sound like the future, you sound like risk.
Bankers are not slow or conservative or backward-looking. They are managing institutions with fiduciary obligations — to depositors, to examiners, to boards, to the communities that depend on them. When a FinTech arrives using unfamiliar terms, revolutionary framing, and category-creating language, the banker doesn't think "wow, this is exciting." They think: expensive, uncertain, hard to defend to my examiner. How do I write this up for the board? How do I explain it to my audit committee? What happens if this doesn't work?
When you show up anchored to their present — naming their friction, speaking their language, rooting your solution in something they already recognize — they hear something entirely different: of course, this makes sense.
That is the reaction you are optimizing for. Not amazement. Not awe at the technology. Not validation that you've built something revolutionary.
"Of course, this makes sense."
The "wow, this is revolutionary" reaction strokes the founder's ego. The "of course, this makes sense" reaction fills the pipeline. These are not the same thing, and they should not be confused.
Three Practical Steps Before Your Next Bank Meeting
The framework above only produces results if it's applied. Here are the three pre-meeting disciplines I use with every founder I work with.
Step 1: Name Your Category
Before you walk into any bank meeting, you must be able to answer one question in a single sentence: What shelf does this sit on?
Not your shelf. The banker's shelf. The one that corresponds to a budget line, a department head, a vendor management classification, and an internal conversation they've already had.
If you can say "we're a compliance workflow tool for institutions managing third-party risk" or "we sit inside your digital banking layer and reduce friction at account opening" — you have done something most FinTech leaders never do. You have made yourself sortable.
If your answer requires a paragraph to make sense, you are putting the work of categorization onto the banker. They will not do that work. They will smile, say this is interesting, and move on.
Creating the category is your job. Come in with the shelf. Put yourself on it. Then — and only then — explain why you're better than what's already there.
Step 2: Find Who Owns That Category Before You Pitch
This step prevents one of the most common and costly mistakes I see founders make.
Once you've named your category, you need to know where that category lives inside the specific institution you're meeting with. Vendor management, for example, might sit in risk at one institution, operations at another, compliance at a third, and legal at a fourth. The same is true for most categories.
Walking into the wrong room will get you a warm response. Bankers are unfailingly polite. But there will be no follow-up. The champion you need — the person who has the authority and the internal relationships to move your deal — must be in the room you're sitting in.
Pre-call research into org structure is not optional. It is the step that determines whether a great conversation leads anywhere.
Step 3: Make It Understandable Before Making It Compelling
Understandable before compelling — every single time.
You cannot sell someone the value of something they haven't been able to categorize yet. The ROI slide means nothing if the banker doesn't have a mental model for what you do. The case study doesn't land if they can't map your solution to a problem they already recognize.
Simplicity travels. Complexity parks your deal.
This is the sequencing rule that underlies everything else in this framework. Anchoring earns the pitch. Once the anchor is set — once the banker has a shelf and your product is on it — then you can go deeper. Then you can introduce the differentiation, the architecture, the case study, the ROI. In that order.
Never in reverse.
Key Takeaways
Bankers sort vendors into mental categories. When they can't sort you, they don't reject you — they park you. This is the category conundrum.
"This is really interesting" is not a buying signal. It is a parking signal. If your meetings consistently end there, the problem is categorization, not pitch quality.
The sale doesn't happen at the demo. It happens when the banker finally understands what you are.
Anchoring means rooting your solution in something the banker already understands, feels, or lives with — before you explain a single feature.
There are five distinct anchor types: pain, task, technology, process, and emotion. Each targets a different buyer profile and requires different preparation.
The technology anchor is uniquely powerful because it requires truth-telling about the banker's current stack — something most vendors never do.
The process anchor equips your internal champion with language to use when you're not in the room. In multi-stakeholder deals, this is often the decisive variable.
The emotion anchor is the most powerful and the most dangerous. Use it only if you've earned it through genuine banker conversations.
Anchor to the present, not the future. Revolutionary framing reads as risk. Present-anchored framing reads as "of course, this makes sense."
Make it understandable before making it compelling. Simplicity travels. Complexity parks your deal.
FAQ
Why do bank meetings go well and still not convert?
Because "going well" and "moving forward" are two different things. Bankers are polite, intellectually engaged, and genuinely curious about the FinTech ecosystem. A warm meeting means they found the conversation worthwhile. It does not mean they have a mental category for you, a budget pathway, an internal champion, or a reason to initiate a vendor management process. When those structural elements are missing, even excellent meetings produce no forward movement.
What does "anchoring" mean in a sales context?
Anchoring means starting your pitch inside the banker's world before introducing your own. You begin with something they already know — a cost they're already carrying, a task their team already does, a technology they're already misusing, a process that already frustrates them, or a feeling they're already experiencing. You establish that you understand their present reality before you explain how your product addresses it. The anchor earns the pitch.
Which anchor type should I use?
That depends on who is in the room and what you know about their specific situation. Pain anchors work well with strategic and executive buyers. Task anchors are designed for operational buyers. Technology anchors are most effective with CIOs and CTOs. Process anchors are built for multi-stakeholder deals and the activation of internal champions. Emotion anchors require the most preparation and carry the most risk, but can be the most powerful when done authentically. In most pitches, a combination of two anchors — one structural, one emotional — will outperform any single anchor used alone.
What is the difference between the category conundrum and a bad pitch?
A bad pitch fails to communicate value. The category conundrum is upstream of that — it's a failure of categorization that happens before value can even be communicated. You can have a brilliant pitch for a product the banker cannot sort, and it will still park. The category conundrum is not a messaging problem. It is a positioning problem. Solving it requires you to give the banker a mental shelf before you start the pitch, not during it.
How do I know if my product has a category conundrum problem?
There are two reliable signals. The first is the consistent "this is really interesting, let us think about it" response with no follow-up. The second is the inability to answer, in one sentence, what budget line your product comes from and who would own it internally at a specific institution. If you can't answer that, you have a category conundrum problem.
What does "present-anchored" mean and why does it matter?
Present-anchored means your pitch begins with the banker's current reality — what they're doing today, what it costs them today, what frustrates them today — rather than with a vision of the future. It matters because future-framed pitches read as risk to banking audiences. When you lead with the future, bankers hear: expensive, uncertain, hard to defend. When you lead with their present, they hear: "of course, this makes sense." That reaction — not amazement, not excitement about the future — is what moves deals forward.
What is the "champion activation" strategy and why is it important?
In most bank deals, the person you meet with is not the final decision-maker. They are the person who will carry your deal into rooms you'll never be in. Champion activation means equipping that person with language — specifically the language to describe your solution to stakeholders who weren't in the original meeting. The process anchor is the primary tool for this. When you can map the institution's internal buying process back to them — naming the stage where deals typically stall and explaining how you make that stage easier — you give your champion a script they can use without you. In multi-stakeholder deals, this is often the variable that determines whether a promising meeting ever becomes a signed contract.
Can I use multiple anchors in a single pitch?
Yes — and in practice, the most effective pitches typically combine two anchor types. A strong opening might pair a task anchor with a technology anchor: you name what their team is doing manually, then name the existing tool they're misusing to do it. This creates a layered credibility effect — you understand both their workflow and their technology environment before you've said a word about your own product. The key is sequencing: anchor first, pitch second. Do not try to anchor and pitch simultaneously. The anchor is not an introduction to your product. It is proof that you understand their world.
About the Author: Stacy Bishop
I spent 23 years inside Jack Henry — one of the largest core banking technology providers in the country — before stepping out to work directly alongside FinTech founders. In the six years since, I've worked with leaders at every stage: from founders making their first community bank calls to teams that have been in market for years and can't figure out why the pipeline isn't moving.
The category conundrum is the most common problem I diagnose. And it is almost never the one founders come in thinking they have.
If you want to pressure-test your positioning — to find out whether bankers have a clear mental model for what you do and a credible path to internal ownership — I work with a small number of founders on exactly this. Book a strategy call and we can walk through your current approach together.
about the author
Stacy Bishop
Stacy Bishop leverages 30 years of community banking experience and $100M+ in deal exposure to coach fintech founders through the complex institutional sales process. From mapping out internal buying committees to navigating strict FDIC and OCC scrutiny, Stacy helps founders de-risk their pitches and close high-stakes bank deals faster.
You May also like
