Fintech Revenue
The "This Isn't for Us" Loop: Why FinTech Founders Keep Getting Redirected (and What It Actually Means)
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:
What the Banker Says | What Founders Hear | What's Actually Happening |
|---|---|---|
"We're not the right size for this" | Sizing problem — adjust ICP | Placement failure — they can't categorize it internally |
"Let's circle back next quarter" | Timing problem — follow up in Q2 | Routing failure — no one knows who owns it internally |
"This is better for larger banks" | Wrong segment — target upmarket | Categorization failure — they can't place it, so they redirect |
"We'd need to see more traction" | Proof problem — get more case studies | Evaluation failure — they have no framework to assess it |
"We love it but we're in the middle of a system migration" | Bad timing — wait it out | Avoidance — they're using a real constraint as an exit |
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.
Why Bankers Redirect Instead of Admitting Confusion
Understanding the mechanism makes this pattern less maddening.
Banks and credit unions are process-driven institutions staffed by professionals who are evaluated on their judgment. Admitting that you don't understand what a vendor is selling is not something institutional buyers do comfortably in a meeting — particularly when their colleagues are present or when the founder is clearly knowledgeable and credible.
So when a banker encounters your product and can't categorize it — can't answer the internal question "what is this and who at our institution should own it?" — they don't say "I don't understand." They say something that sounds like a thoughtful, considered response. "Your product is really designed for institutions at a different stage than us." "We'd need to see this proven at a few reference customers first." "Our technology roadmap is locked through next year."
These aren't lies. They may even be partly true. But they're functioning as exits from a categorization problem, not as honest assessments of fit.
What makes this particularly hard to diagnose is that these responses feel specific. They contain information. Founders record them as objections, analyze them for patterns, and build responses to overcome them. They practice handling the "not the right size" objection. They develop proof points to address the "we need more traction" concern.
And none of it helps, because none of it addresses what's actually happening: the banker couldn't place the product in a category, and rather than surface that confusion, they redirected.
The Common Mistake: Optimizing the Wrong Variable
The most expensive version of this mistake looks like this:
A founder gets the "not ready for this yet" objection from six mid-size banks. They conclude that community banks are the better ICP. They retarget entirely. They spend the next quarter building a pipeline of community banks, get the same warm reception, and hear "this is really more of a fit for the regionals — they have more flexibility."
They've spent six months refining their ICP and are now back to targeting the segment they started with.
This is the loop in full expression. And it consumes not just time but credibility — internally, with investors, and with founders themselves. After a year of this, founders start questioning whether the market wants the product at all. They don't. The market actually does want it. The market just can't operationalize wanting it because no institutional category exists for it.
The mistake is accepting "this isn't for us" as feedback about who the customer is, when it's actually feedback about how the product is understood.
What to Do When You Recognize the Loop
If this pattern is happening in your pipeline right now, here's the shift to make.
First: stop optimizing the ICP until you've changed your approach in the meeting itself. More qualified prospects will produce the same outcome if the categorization problem is present in the meeting. Narrowing the funnel does not fix what's happening inside the conversation.
Second: before your next meeting, identify one familiar process. Not a feature. Not a category claim. A specific process that the institution already runs — something they do today, in their current state — that your product connects to. Open with that. "You currently process X applications manually through Y workflow. That's where this sits." Watch whether the conversation shifts.
Third: name the internal owner before they have to figure it out. One of the reasons "this isn't for us" is so common is that bankers genuinely don't know which team would own the evaluation. If your product sits across compliance, operations, and risk, who runs the internal process? You need to tell them. "This typically sits with the operations team, though risk is usually a key stakeholder in the evaluation." That one sentence routes the conversation internally — which is what has to happen before any deal can progress.
This is the third signal in the Category Conundrum diagnostic, and it has a specific remedy. You can read the full approach in the step post on how to make internal ownership obvious before they ask.
You can also read about Signal 1 — the language gap that creates confusion before the objection ever appears — in the post on why your language only makes sense to you.
What Forward Movement Actually Looks Like
Here's a useful calibration: genuine deal progression in a sales cycle has observable markers. Next steps are defined with names and dates. Implementation timelines come up. Procurement questions surface. Someone asks about contracting.
When "this isn't for us" is the recurring pattern, none of those markers appear. The meeting ends with warmth and vague next steps. The follow-up gets a polite response and no action. The prospect eventually goes quiet.
If you've never had a meeting that ended with a specific named next step — "let's get a call on the calendar with our operations lead" or "can you send over your standard agreement so we can get legal to take a look" — that is diagnostic information. You are not in a sales cycle. You are in a market education cycle, and the "This Isn't for Us" loop is one of its clearest expressions.
Learn about the market education cycle and how to diagnose which one you're in.
Recognizing the Pattern Is the First Step Out of It
The "This Isn't for Us" loop is disorienting precisely because it feels like useful feedback. Bankers give you segment recommendations. You follow those recommendations. The pipeline stays busy. It feels like progress.
It is not progress. It is a diagnostic signal. And once you recognize it as one, the path forward changes completely — not toward a different set of institutions, but toward a different way of showing up in the conversation you're already having.
The institutions you've been meeting with are not wrong for you. They may not be able to buy you yet — not because they don't want to, but because they don't have the internal infrastructure to categorize what you are, route it to the right owner, and evaluate it against a framework they recognize. Build that infrastructure for them, and the loop stops.
This is Part 3 of a 7-part series. Start from the beginning.
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
