Fintech Revenue

Fintech Founders: Win More Deals By Solving The Category Conundrum

Illustration for Stacy Bishop article about solving the Category Conundrum in fintech bank sales

Quick answer: The Category Conundrum is what happens when a bank likes a fintech product but cannot place it into a familiar internal category. Without a category, there is no obvious owner, budget, review path, or buying committee route, so the deal stalls even when the meeting feels positive.

You polish the deck. You nail the demo. The banker across the table is nodding, engaged, saying things like "this is exactly what we need." You leave the meeting confident.

Then nothing happens.

You follow up. They say they're "still evaluating." You follow up again. They say "let's circle back after Q1." You refine the pitch, book more meetings, and the exact same thing happens — new bank, same outcome.

Most founders run the standard diagnostic at this point: unclear pitch, wrong ICP, bad timing. So they rewrite the deck. They narrow the target. They wait for a better quarter. And the pattern repeats.

Here's what I want to tell you, because I've watched this loop play out across dozens of FinTech founders: you're solving the wrong problem. The issue is not your pitch. It's not your timing. It's not your ICP.

It's a placement problem. And until you diagnose it correctly, you'll keep optimizing inputs in a broken system.

Watch me explain it in this video.

For the complete framework, read the full guide.

What the Category Conundrum Actually Is

I call this the Category Conundrum.

It happens when a genuinely novel FinTech product enters a market that is institutionally built around categories that don't include it. Banks and credit unions are not free-form buyers making intuitive decisions. They operate through a structured internal sequence before any purchase can move forward.

When your product doesn't map to a category they already recognize, that sequence breaks. Not slows. Breaks. And the result isn't a "no" — it's an indefinite suspension of forward movement that looks, from the outside, exactly like a timing issue or a pitch problem.

This distinction matters enormously. A pitch problem responds to iteration. A placement problem doesn't. If you're iterating on a placement problem, you're doing precision work in the wrong direction.

The Institutional Buying Machinery

To understand why this happens, you need a clear picture of how institutional buying actually works. I model it as three sequential steps, and every step has to complete before the next one starts.

Step

What It Requires

What Breaks When Category Is Missing

1. Categorize

The institution must be able to answer: what is this?

Banker attempts to translate, fails quickly, disengages rather than ask

2. Assign Ownership

Once categorized, the institution routes it to a team, budget line, and internal champion

No category = no natural owner = no one raises their hand internally

3. Evaluate

With a category and owner, the institution can compare, score, and justify the decision

No category = no comparison set = no evaluation rubric = no mechanism to say yes

When a banker encounters your "next-gen orchestration layer" or your solution "redefining real-time decisioning," they don't reach out for clarification. They attempt a rapid internal translation: Is this fraud? Is this data? Is this core banking adjacent? When no answer surfaces in the first few seconds, they don't flag confusion. They nod. They engage. They say "that's interesting." And the meeting ends warmly for both parties.

You leave thinking it went well. The banker leaves not knowing what you do.

This is the Category Conundrum in action — and it's invisible while it's happening because the feedback signals look positive.

The Misdiagnosis That Keeps Founders Stuck

Here's why the Category Conundrum is underdiagnosed: it produces symptoms that look exactly like three other problems.

It looks like a pitch problem because deals stall after meetings. But if you've improved the pitch and deals still stall at the same point, the pitch isn't the variable.

It looks like a timing problem because you keep hearing "let's circle back" and "we're not ready yet." But if circling back never produces movement, it wasn't timing.

It looks like an ICP problem because no segment seems to convert. But if every segment endorses the product and points somewhere else as the right buyer — large banks say try community banks, community banks say try credit unions, credit unions say try regional banks — that circular pointing pattern is category evidence, not customer profile evidence.

The difference between those three problems and the Category Conundrum is this: pitch problems, timing problems, and ICP problems respond to iteration. The Category Conundrum doesn't. It requires category creation work — and that has to happen before or alongside selling, not after you've exhausted every other explanation.

Why Innovation Specifically Causes This

I need to address something counterintuitive here, because it's the part founders push back on most: the more genuinely innovative your product, the harder the institutional sale.

Not because banks dislike innovation. They don't. They'll sit in meetings, express genuine enthusiasm, and mean every word of it.

The problem is that genuinely novel products break the institutional buying machinery at all three steps simultaneously. There's no bucket for them. There's no obvious internal owner. There's no comparison set for evaluation. The institution doesn't have the mental models, the ownership structures, or the evaluation criteria to act on interest in something with no precedent.

Incremental products — the ones that are slightly better versions of something banks already use — move through the machinery easily. Categorization is immediate. Ownership is obvious. Evaluation criteria already exist. The deal progresses.

Your genuinely innovative product gets stuck at step one and never moves.

This is not a reason to make your product less innovative. It's a reason to do category creation work alongside your sales motion — to give the institutional buying machinery what it needs to process your product.

What to Do About It

The Category Conundrum has three targeted remedies, each designed to intervene at a specific breakpoint in the institutional buying machinery:

Remedy 1: Lead with what's familiar, not what's different. Categorization has to come before evaluation. If you open with differentiation, you're asking the buyer to evaluate something before they can place it. Start with a process they already run, a problem they already feel. Give them a way to categorize your product before you show them what makes it new. Read the full breakdown of familiar-first positioning.

Remedy 2: Tell them who should own it. Founders wait for the prospect to figure out internal ownership. The prospect waits for someone internally to raise their hand. No one does. Fix this by naming the owner explicitly: "This typically sits with your operations team." That one sentence converts a routing problem into a partnership conversation.

Remedy 3: Build the scorecard before they ask for it. Without a category, there's no evaluation infrastructure. Buyers don't move forward not because they've decided against you, but because they have no mechanism to decide at all. Build the decision apparatus for them: what two to four things could you replace, what does 90-day success look like, what two criteria matter.

The Diagnosis Comes First

None of the remedies work until you've correctly identified the root cause.

If you're in a Category Conundrum and you keep improving your pitch, you'll produce better meeting energy with the same deal outcomes. That's worse in some ways — the positive feedback makes it harder to see the real problem.

The first step is accurate diagnosis. The three signals that confirm you're in it: your language produces nodding but no comprehension, every prospect redirects to a different segment as the right buyer, and every meeting requires re-explaining the problem from scratch. When all three are present, you're not in a pitch problem. You're in a placement problem.

Name it correctly. Then solve the right thing.

Key Takeaways

  • The Category Conundrum is a placement problem, not a pitch problem. When banks can't categorize your product, they can't buy it regardless of how clearly you explain it.

  • Institutional buying follows a three-step sequence: categorize, assign ownership, evaluate. Category-creating products break all three steps simultaneously.

  • The symptoms look like pitch failure, timing failure, and ICP failure — which is why most founders iterate on those variables and stay stuck.

  • Genuine innovation is a sales obstacle in regulated institutional markets specifically because novel products have no existing category, no natural owner, and no evaluation framework.

  • The three remedies — familiar-first positioning, naming the owner, building the scorecard — are targeted interventions for each of the three breakpoints. They only work after the root cause is correctly identified.

This is Part 1 of a 7-part series. Click here to start from the beginning and read the full guide.

Stacy Bishop author image for fintech-bank partnership articles

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

Stacy Bishop

How to Build a Bank-Ready Fintech Pitch Deck

Quick answer: A bank-ready fintech pitch deck is not an investor deck. It exists to help a banker explain your product to everyone who must approve the decision: the internal owner, the risk team, IT, operations, and leadership. The strongest decks name the bank problem first, show a realistic implementation path, answer risk and compliance questions before they are asked, and end with a clear next step the bank can say yes to.

I have worked across banking and fintech for more than 28 years, including 23 years inside Jack Henry, and I have sat in more bank vendor presentations than I can count. I can usually tell within the first three slides whether a deck was built for investors or built for a bank. Investor decks sell a vision. Bank decks sell a defensible decision. If you want to sell your technology or service to banks, you need the second kind.

Table of Contents

  • Why Investor Decks Fail in Bank Sales

  • The Job Your Deck Actually Has

  • The Eight Slides a Bank Deck Needs

  • What to Cut From Your Current Deck

  • How to Test Whether Your Deck Is Bank-Ready

  • FAQ

Why Investor Decks Fail in Bank Sales

An investor deck answers the question "how big can this get?" A bank deck answers a different question: "is this safe, useful, and realistic for our institution right now?"

I have watched founders present market size, growth curves, and disruption language to community banks, and I have watched the room cool in real time. The banker is not buying your upside. The banker is buying a change to their operation, and every change carries risk they will have to own.

I wrote about how this plays out before the meeting even happens in Why FinTech Founders Lose Bank Deals Before the Demo. The deck is one of the first places a bank decides whether you understand them.

Fintech Revenue

Stacy Bishop

How Banks Evaluate Fintech Vendors Before the Demo

Quick answer: Banks start evaluating a fintech vendor long before the demo. Bankers first decide whether the product fits a real institutional problem, whether it can be routed to an internal owner and budget, whether the vendor looks mature enough to survive due diligence, and whether implementation seems manageable for their team. If those answers are unclear, the demo either never gets scheduled or never matters.

I spent 23 years inside Jack Henry and more than 28 years across banking and fintech, and I can tell you that the most important evaluation in a bank deal is the one founders never see. It happens in hallway conversations, in a quick scan of your website, in the forwarded email your champion sends to a colleague with the note "worth a look?" By the time you get demo time, the bank has already formed a working opinion. Your job is to make sure that opinion is built on the right signals.

Table of Contents

  • The Invisible Evaluation

  • Question 1: Is This a Problem We Care About?

  • Question 2: Who Would Own This?

  • Question 3: Would This Vendor Survive Our Review?

  • Question 4: Can We Actually Implement This?

  • What Your Website and Collateral Need to Prove

  • How to Make the Demo Easier to Approve

  • FAQ

The Invisible Evaluation

Founders treat the demo as the start of the evaluation. Banks treat it as a checkpoint in an evaluation that is already underway. I know because I watched those evaluations happen for years.

Before a demo gets approved, someone inside the bank has to spend political capital to put it on calendars. That person is making a quiet calculation: "If I bring this vendor in, will I look smart or will I waste everyone's time?" Everything the bank can see about you before the demo feeds that calculation.

This is a different problem from losing the deal after a strong demo, which I covered in Why FinTech Founders Lose Bank Deals Before the Demo. This is about what gets measured before you are ever in the room.

Fintech Revenue

Stacy Bishop

The First Bank Deal Playbook for Fintech Founders

Quick answer: The first bank deal closes when a founder stops selling novelty and starts selling a defensible path to adoption. That means choosing a bank whose priorities actually match your product, narrowing the first use case until it is easy to approve, bringing proof that does not depend on bank logos you do not have yet, designing a pilot the bank can execute, and preparing for due diligence before it starts.

I have spent more than 28 years in banking and fintech, including 23 years inside Jack Henry, and I have watched the first bank deal break more founders than any other milestone. Not because the products were weak, but because founders ran the first deal like a normal sale. It is not a normal sale. The first bank deal is structurally different, and it deserves its own playbook.

Table of Contents

  • Why the First Bank Deal Is Different

  • Step 1: Choose the Right First Bank, Not the Most Excited One

  • Step 2: Build Proof That Does Not Require Logos

  • Step 3: Narrow the First Use Case

  • Step 4: Prepare for Due Diligence Before Outreach

  • Step 5: Design a Pilot Built to Convert

  • Step 6: Protect the Deal From Your Own Promises

  • FAQ

Why the First Bank Deal Is Different

In your first bank deal, the bank is not just evaluating your product. It is evaluating whether being your first bank customer is a safe place to stand. Every later deal can point to the bank before it. The first one cannot. I have watched that calculation up close for decades, and I can tell you the banker feels the exposure personally.

That means the bank carries extra risk, and the banker who champions you carries extra personal exposure. Your entire playbook should be built around lowering that exposure.

Fintech Revenue

Stacy Bishop

How to Build a Bank-Ready Fintech Pitch Deck

Quick answer: A bank-ready fintech pitch deck is not an investor deck. It exists to help a banker explain your product to everyone who must approve the decision: the internal owner, the risk team, IT, operations, and leadership. The strongest decks name the bank problem first, show a realistic implementation path, answer risk and compliance questions before they are asked, and end with a clear next step the bank can say yes to.

I have worked across banking and fintech for more than 28 years, including 23 years inside Jack Henry, and I have sat in more bank vendor presentations than I can count. I can usually tell within the first three slides whether a deck was built for investors or built for a bank. Investor decks sell a vision. Bank decks sell a defensible decision. If you want to sell your technology or service to banks, you need the second kind.

Table of Contents

  • Why Investor Decks Fail in Bank Sales

  • The Job Your Deck Actually Has

  • The Eight Slides a Bank Deck Needs

  • What to Cut From Your Current Deck

  • How to Test Whether Your Deck Is Bank-Ready

  • FAQ

Why Investor Decks Fail in Bank Sales

An investor deck answers the question "how big can this get?" A bank deck answers a different question: "is this safe, useful, and realistic for our institution right now?"

I have watched founders present market size, growth curves, and disruption language to community banks, and I have watched the room cool in real time. The banker is not buying your upside. The banker is buying a change to their operation, and every change carries risk they will have to own.

I wrote about how this plays out before the meeting even happens in Why FinTech Founders Lose Bank Deals Before the Demo. The deck is one of the first places a bank decides whether you understand them.

Fintech Revenue

Stacy Bishop

How Banks Evaluate Fintech Vendors Before the Demo

Quick answer: Banks start evaluating a fintech vendor long before the demo. Bankers first decide whether the product fits a real institutional problem, whether it can be routed to an internal owner and budget, whether the vendor looks mature enough to survive due diligence, and whether implementation seems manageable for their team. If those answers are unclear, the demo either never gets scheduled or never matters.

I spent 23 years inside Jack Henry and more than 28 years across banking and fintech, and I can tell you that the most important evaluation in a bank deal is the one founders never see. It happens in hallway conversations, in a quick scan of your website, in the forwarded email your champion sends to a colleague with the note "worth a look?" By the time you get demo time, the bank has already formed a working opinion. Your job is to make sure that opinion is built on the right signals.

Table of Contents

  • The Invisible Evaluation

  • Question 1: Is This a Problem We Care About?

  • Question 2: Who Would Own This?

  • Question 3: Would This Vendor Survive Our Review?

  • Question 4: Can We Actually Implement This?

  • What Your Website and Collateral Need to Prove

  • How to Make the Demo Easier to Approve

  • FAQ

The Invisible Evaluation

Founders treat the demo as the start of the evaluation. Banks treat it as a checkpoint in an evaluation that is already underway. I know because I watched those evaluations happen for years.

Before a demo gets approved, someone inside the bank has to spend political capital to put it on calendars. That person is making a quiet calculation: "If I bring this vendor in, will I look smart or will I waste everyone's time?" Everything the bank can see about you before the demo feeds that calculation.

This is a different problem from losing the deal after a strong demo, which I covered in Why FinTech Founders Lose Bank Deals Before the Demo. This is about what gets measured before you are ever in the room.

Fintech Revenue

Stacy Bishop site footer image for fintech-bank partnership consulting

Ready to Build Your Bridge?

If you’ve made it this far, you probably care about more than just closing the next deal. You care about building something sustainable: a partnership that works for both sides.

That’s the work I’ve been doing for nearly three decades, and it’s what I’d love to do with you.

Let’s start with a conversation. I guarantee you’ll walk away with value, clarity, and practical next steps—even if we don’t end up working together.