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

Framework for fintech founders diagnosing why community bank deals stall after interested conversations

Stacy Bishop

What to Do When a Bank Goes Quiet After a Strong Fintech Sales Call

Quick answer: When a bank goes quiet after a strong sales call, the founder should diagnose the internal stall before pushing harder. Silence may mean the champion lacks language, the product has no clear owner, risk or IT raised concerns, urgency is weak, the business case is incomplete, or the next step was too vague. The right follow-up should help the bank resolve the stall, not simply ask for an update.

A bank sales call can feel strong and still go quiet.

The banker was engaged. The questions were thoughtful. The problem seemed real. The founder left the meeting confident.

Then nothing.

No next meeting. No clear objection. No hard no.

Just silence.

Founders often read that silence as disinterest. Sometimes it is. But often, something happened inside the bank that the founder cannot see.

The worst response is to keep sending generic check-ins.

“Just following up” does not solve an internal stall.

Diagnose before you push

Before you follow up, ask what may have stalled.

There are six common possibilities.

1. The champion did not have the language

Your champion may have tried to explain the product internally and struggled.

If the product requires too much translation, the champion can lose confidence.

The fix is not another demo. The fix is clearer language, a tighter problem statement, and a forwardable summary.

2. No one owned the problem

The banker may like the idea but not know where to route it.

If the product does not clearly belong to an internal owner, the bank has no natural path for the decision.

Your follow-up should help identify the likely owner and suggest who should be involved next.

Fintech Revenue

How to Make Fintech Implementation Feel Realistic to a Community Bank

Stacy Bishop

How to Make Fintech Implementation Feel Realistic to a Community Bank

Quick answer: To make implementation feel realistic to a community bank, fintech founders must explain the first phase, internal resource requirements, data and system touchpoints, support model, timeline, risk review, and what the bank does not have to do. Community banks are often interested in innovation, but they buy when the lift feels manageable.

Community banks do not reject fintech because they dislike innovation.

Many are actively looking for better ways to serve customers, reduce manual work, improve efficiency, and compete with larger institutions.

But interest is not the same thing as capacity.

A community bank may like your product and still hesitate because the team is thinking:

Who is going to implement this?

That question can stall a deal if the founder does not answer it clearly.

Lean teams evaluate lift early

A large bank may have dedicated teams for innovation, vendor management, procurement, information security, project management, compliance, implementation, and operations.

A community bank may have a much smaller group of people wearing several of those hats.

That changes the buying conversation.

The bank is not only evaluating the value of the product. It is evaluating whether the organization can absorb the work.

Explain the first phase

Do not describe implementation as one large event.

Break it into phases.

The first phase should answer:

  • What happens first?

  • Who needs to participate?

  • What information is needed?

  • What systems are involved?

  • How long does it usually take?

  • What does success look like at the end of this phase?

When implementation is phased, it feels more manageable.

Fintech Revenue

How to Choose the First Use Case for a Bank Pilot

Stacy Bishop

How to Choose the First Use Case for a Bank Pilot

Quick answer: The best first use case for a bank pilot is narrow, owned, measurable, urgent, and operationally realistic. It should solve a real bank problem without requiring the institution to redesign too many processes at once. Founders weaken first deals when they try to prove the entire platform instead of one decision-ready use case.

Your first use case inside a bank should not be the biggest possible version of your product.

It should be the easiest meaningful version to approve.

That distinction matters.

Founders often want the bank to see the full vision. They want to show every capability, every workflow, every future expansion path.

I understand why.

But inside a bank, a broad first use case can create more risk than momentum.

The bank is not only asking whether the product is useful. It is asking whether this first step is safe, clear, and manageable.

Choose a problem someone owns

The first use case needs an internal owner.

If no one inside the bank clearly owns the problem, the deal will drift.

Ownership matters because someone has to sponsor the evaluation, answer internal questions, coordinate stakeholders, defend the business case, and push the next step.

If your use case touches five departments but belongs to none of them, it may sound strategic and still go nowhere.

Choose a problem the bank can measure

A pilot should create evidence.

That evidence might be reduced manual time, fewer exceptions, faster review, better completion rates, lower error volume, stronger visibility, improved customer experience, or clearer compliance oversight.

If the bank cannot measure the improvement, the pilot becomes subjective.

Subjective pilots are harder to turn into contracts.

Choose a problem with enough urgency

Useful is not enough.

The bank has to care now.

Look for timing pressure:

  • Audit findings

  • Staffing constraints

  • Vendor renewal

  • Board priority

  • Customer complaints

  • Operational backlog

  • Fraud exposure

  • Compliance concerns

  • A strategic initiative already in motion

The best first use case connects to a clock the bank already watches.

Fintech Revenue

Framework for fintech founders diagnosing why community bank deals stall after interested conversations

Stacy Bishop

What to Do When a Bank Goes Quiet After a Strong Fintech Sales Call

Quick answer: When a bank goes quiet after a strong sales call, the founder should diagnose the internal stall before pushing harder. Silence may mean the champion lacks language, the product has no clear owner, risk or IT raised concerns, urgency is weak, the business case is incomplete, or the next step was too vague. The right follow-up should help the bank resolve the stall, not simply ask for an update.

A bank sales call can feel strong and still go quiet.

The banker was engaged. The questions were thoughtful. The problem seemed real. The founder left the meeting confident.

Then nothing.

No next meeting. No clear objection. No hard no.

Just silence.

Founders often read that silence as disinterest. Sometimes it is. But often, something happened inside the bank that the founder cannot see.

The worst response is to keep sending generic check-ins.

“Just following up” does not solve an internal stall.

Diagnose before you push

Before you follow up, ask what may have stalled.

There are six common possibilities.

1. The champion did not have the language

Your champion may have tried to explain the product internally and struggled.

If the product requires too much translation, the champion can lose confidence.

The fix is not another demo. The fix is clearer language, a tighter problem statement, and a forwardable summary.

2. No one owned the problem

The banker may like the idea but not know where to route it.

If the product does not clearly belong to an internal owner, the bank has no natural path for the decision.

Your follow-up should help identify the likely owner and suggest who should be involved next.

Fintech Revenue

How to Make Fintech Implementation Feel Realistic to a Community Bank

Stacy Bishop

How to Make Fintech Implementation Feel Realistic to a Community Bank

Quick answer: To make implementation feel realistic to a community bank, fintech founders must explain the first phase, internal resource requirements, data and system touchpoints, support model, timeline, risk review, and what the bank does not have to do. Community banks are often interested in innovation, but they buy when the lift feels manageable.

Community banks do not reject fintech because they dislike innovation.

Many are actively looking for better ways to serve customers, reduce manual work, improve efficiency, and compete with larger institutions.

But interest is not the same thing as capacity.

A community bank may like your product and still hesitate because the team is thinking:

Who is going to implement this?

That question can stall a deal if the founder does not answer it clearly.

Lean teams evaluate lift early

A large bank may have dedicated teams for innovation, vendor management, procurement, information security, project management, compliance, implementation, and operations.

A community bank may have a much smaller group of people wearing several of those hats.

That changes the buying conversation.

The bank is not only evaluating the value of the product. It is evaluating whether the organization can absorb the work.

Explain the first phase

Do not describe implementation as one large event.

Break it into phases.

The first phase should answer:

  • What happens first?

  • Who needs to participate?

  • What information is needed?

  • What systems are involved?

  • How long does it usually take?

  • What does success look like at the end of this phase?

When implementation is phased, it feels more manageable.

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.