Quick answer: FinTech founders often lose bank deals before the demo because the banker cannot categorize the product quickly enough to route it internally. If the banker cannot explain what the solution is, who owns it, which budget applies, and how vendor management should review it, the deal stalls even when the meeting feels positive.

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

• The Case Study: 40 Discovery Calls, Zero Conversions

• Why Anchoring Is the Answer

• The Five Anchors Framework

  • Anchor 1: The Pain Anchor

  • Anchor 2: The Task Anchor

  • Anchor 3: The Technology Anchor

  • Anchor 4: The Process Anchor

  • Anchor 5: The Emotion Anchor

• The Core Rule: Anchor to the Present, Not the Future

• Three Practical Steps Before Your Next Bank Meeting

• Key Takeaways

• FAQ

• Related Reading

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.

Quick answer: The five-point self-diagnostic helps innovative FinTech founders determine whether stalled bank deals are caused by a category problem rather than a pitch, pricing, or product problem. If bankers are interested but cannot identify the owner, category, budget, or internal route for your solution, you are likely facing the Category Conundrum.

Not every stalled FinTech sales cycle has the same root cause. The framework I've built around the Category Conundrum — where placement failure, not pitch failure, is killing your deals — applies to a specific type of founder in a specific situation. Before you spend another quarter refining your deck, here is how to know whether you are actually that founder.

Watch me explain this live

The Framework Doesn't Apply to Everyone

If you're selling a FinTech product that has a clear, established category — lending software, fraud detection, payments infrastructure — and you're losing deals, the problem probably is the pitch, the pricing, or the targeting. The Category Conundrum framework is not for you.

But if you're selling something genuinely novel — something that doesn't have a clean home in an existing technology category, something that bankers look at and say "I've never quite seen this before" — the problem is almost certainly structural. Not pitch-level. Structural.

The Category Conundrum happens when an institutional buyer encounters a product that doesn't fit their internal machinery. Banks and credit unions operate through a three-step process: categorize the solution, assign internal ownership, evaluate it against existing frameworks. When your product breaks step one, steps two and three never happen. No evaluation. No champion. No deal.

For the complete framework on what this is and how to work your way out, read the full guide.

What I want to focus on here is who this happens to — specifically. Because most founders in this situation have been misdiagnosing their problem for twelve to eighteen months, and it's costing them deals they should be winning.

Quick answer: The “This Isn’t for Us” loop happens when bankers keep redirecting a FinTech founder to another type of institution, department, or buyer because they cannot categorize who should own the product. The objection sounds like fit, but the real issue is usually internal ownership ambiguity.

You've been here before. You get the meeting. The banker is engaged. They ask good questions. They say something like "this is really interesting, but honestly, I think you'd be better served talking to community banks. We're a bit too large for this stage of the product."

Or maybe they say the opposite: "We're actually a smaller shop — have you talked to any of the regionals? They have more appetite for this kind of thing."

You follow up. You shift your outreach. You talk to the community banks, who tell you credit unions are more nimble. The credit unions tell you to go back to the regionals. The regionals tell you they'd need to see more traction with smaller institutions first.

You've met with thirty financial institutions. Everyone agrees your product is a good idea. Not one has moved to next steps.

This is the "This Isn't for Us" loop — Signal 2 of what I call the Category Conundrum. And here's what I want you to understand: this is not an ICP problem. It is not a targeting problem. Refining your prospect list will not fix it. It is a categorization failure in disguise, and until you recognize it as that, you will keep running the same cycle with different institution names.

Watch me explain this live — this pattern came up repeatedly when I walked through the Category Conundrum framework.

For the complete framework, read the full guide.

What the "This Isn't for Us" Pattern Actually Looks Like

The misdirection objection comes in several forms. Founders hear all of them and file them under different diagnoses:

That last column is the diagnosis most founders never reach. They accept the surface-level objection, adjust the variable the banker named, and run the same cycle again. The cycle repeats because they changed the wrong variable.

The Circular Pointing Trap: A Diagnostic Pattern

When every segment endorses the product and redirects to another segment, that is not ICP signal. That is category signal.

Here's the distinction: if your product were an ICP problem, you'd see a pattern where specific segments consistently reject it while other segments show genuine traction. One type of institution would say no with specificity ("your product doesn't integrate with our core," "your pricing model doesn't work for our revenue structure") while another type showed real forward movement.

What actually happens in a Category Conundrum is different. Enthusiasm is universal. Redirection is universal. No one says "this is wrong for us" — they say "this is right for someone else." And the "someone else" is always whoever is not currently in the room.

This matters because it completely changes the action you take. If the problem were ICP, the fix is narrowing your outreach and qualifying harder before the meeting. If the problem is category, the fix is working on how you establish what your product is before you ask them to decide whether they want it.

One of those paths moves you toward closed deals. The other moves you toward a more refined version of the same loop.