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

If Almost Every Bank Could Buy Your Fintech, Your Market Is Still Too Broad

Quick answer: “Banks” is not a useful first target market. Even when nearly every bank or credit union could technically use your product, only a smaller group will have the right problem, internal owner, urgency, budget, systems, and capacity to act now. Start with the segment where those conditions overlap, then use real sales evidence to expand.

A founder recently asked a question I hear often:

If almost every bank or credit union could use what we built, where do we start?

It sounds like a good problem. The market is large. The product appears relevant. The founder does not want to exclude a bank that might buy.

But “almost every bank could use this” is not a market strategy.

It is a statement about technical possibility.

A useful target market tells you where the problem is sharp enough, owned clearly enough, and urgent enough to create a buying process. If you cannot make that distinction, every account looks promising, every conversation teaches something different, and the sales team never gathers comparable evidence.

Possible is not the same as probable

A community bank, regional bank, credit union, and sponsor bank may all be able to use the same technology. That does not mean they will evaluate it for the same reason.

They may have different:

  • strategic priorities;

  • customer segments;

  • operating models;

  • technology environments;

  • risk tolerances;

  • budget cycles;

  • implementation capacity;

  • and internal owners.

Fintech Revenue

Stacy Bishop

You Have Spent a Year Selling to Banks. Is Banking Still the Right First Market?

Quick answer: After a year of weak bank traction, do not ask only whether the product solves a real problem. Ask whether your company has the credibility, access, proof, implementation readiness, and urgency needed to enter banking through that problem. Banking may remain the right long-term market while another financial-services segment becomes the better first place to build evidence.

One of the hardest founder questions is not, “How do we sell this better?”

It is, “Are we selling it to the right market at all?”

A team can spend a year pursuing banks, hear that the problem is real, hold encouraging conversations, and still create very little movement. At that point, the founder often reaches one of two conclusions.

Either the sales team is failing, or the product has no market.

Both conclusions can be premature.

The product may solve a real problem and still be a poor first entry into banking for this company, at this stage, through this use case.

Separate problem validity from company-market fit

Start with two different questions.

Question one: Is the problem real?

Does it create measurable cost, risk, delay, friction, or missed revenue? Do buyers recognize it without being coached? Are they trying to solve it today?

Question two: Is your company well positioned to solve it for banks now?

Can you reach the owner? Does the team have relevant credibility? Can the product pass the expected review? Can you support implementation? Do you have evidence strong enough for a regulated buyer?

A “yes” to the first question does not guarantee a “yes” to the second.

Fintech Revenue

Stacy Bishop

Your Fintech Use Case Is Real. It May Still Be the Wrong One to Lead With.

Quick answer: A use case can be valid and still fail as your lead bank offer. The best lead use case is not merely useful. It has a clear owner, current urgency, credible proof, manageable implementation, a defensible competitive position, and a next decision the bank can make. If those conditions are missing, reposition or demote the use case instead of trying to explain it harder.

Founders often defend a use case with one sentence:

“But the problem is real.”

They are often correct.

The bank does experience the problem. The current process is inefficient. The product can improve it. Someone inside the institution may even agree.

Yet the deal still does not move.

That does not always mean the bank failed to understand. It may mean the use case is valid but weak as the first reason to buy from your company.

“Real problem” is only the first test.

A lead use case has a bigger job

Your lead use case has to do more than demonstrate product utility.

It has to create a workable entry into the institution.

That means it must help the bank answer:

  • Who owns this problem?

  • Why does it matter now?

  • Why should we trust this company?

  • What changes if we say yes?

  • What work will implementation require?

  • What evidence will support the next decision?

A use case can fail any one of those tests while remaining technically sound.

Run the six-part lead-use-case test

Fintech Revenue

Stacy Bishop

If Almost Every Bank Could Buy Your Fintech, Your Market Is Still Too Broad

Quick answer: “Banks” is not a useful first target market. Even when nearly every bank or credit union could technically use your product, only a smaller group will have the right problem, internal owner, urgency, budget, systems, and capacity to act now. Start with the segment where those conditions overlap, then use real sales evidence to expand.

A founder recently asked a question I hear often:

If almost every bank or credit union could use what we built, where do we start?

It sounds like a good problem. The market is large. The product appears relevant. The founder does not want to exclude a bank that might buy.

But “almost every bank could use this” is not a market strategy.

It is a statement about technical possibility.

A useful target market tells you where the problem is sharp enough, owned clearly enough, and urgent enough to create a buying process. If you cannot make that distinction, every account looks promising, every conversation teaches something different, and the sales team never gathers comparable evidence.

Possible is not the same as probable

A community bank, regional bank, credit union, and sponsor bank may all be able to use the same technology. That does not mean they will evaluate it for the same reason.

They may have different:

  • strategic priorities;

  • customer segments;

  • operating models;

  • technology environments;

  • risk tolerances;

  • budget cycles;

  • implementation capacity;

  • and internal owners.

Fintech Revenue

Stacy Bishop

You Have Spent a Year Selling to Banks. Is Banking Still the Right First Market?

Quick answer: After a year of weak bank traction, do not ask only whether the product solves a real problem. Ask whether your company has the credibility, access, proof, implementation readiness, and urgency needed to enter banking through that problem. Banking may remain the right long-term market while another financial-services segment becomes the better first place to build evidence.

One of the hardest founder questions is not, “How do we sell this better?”

It is, “Are we selling it to the right market at all?”

A team can spend a year pursuing banks, hear that the problem is real, hold encouraging conversations, and still create very little movement. At that point, the founder often reaches one of two conclusions.

Either the sales team is failing, or the product has no market.

Both conclusions can be premature.

The product may solve a real problem and still be a poor first entry into banking for this company, at this stage, through this use case.

Separate problem validity from company-market fit

Start with two different questions.

Question one: Is the problem real?

Does it create measurable cost, risk, delay, friction, or missed revenue? Do buyers recognize it without being coached? Are they trying to solve it today?

Question two: Is your company well positioned to solve it for banks now?

Can you reach the owner? Does the team have relevant credibility? Can the product pass the expected review? Can you support implementation? Do you have evidence strong enough for a regulated buyer?

A “yes” to the first question does not guarantee a “yes” to the second.

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.