Fintech Revenue
Ask the Bank When It Wants the Fintech Live
Quick answer: Ask the bank when it wants the solution live early enough to shape the sales process. The answer reveals urgency, budget timing, stakeholder decisions, diligence, contracting, integration, and implementation dependencies. A vague or distant answer does not automatically kill the deal, but it tells you not to forecast the opportunity as if it has a current decision path.
Many fintech founders will ask a bank about the problem, the budget, the buying committee, and the next meeting.
Then they avoid one of the simplest qualification questions:
When do you want this live?
The question can feel too direct. The founder worries about creating pressure or hearing a date the company cannot meet.
But a desired live date is not a demand. It is a diagnostic.
It helps both sides work backward from the outcome and discover what the decision actually requires.
A live date exposes the difference between interest and intent
A banker can be genuinely interested in the product without having a current plan to adopt it.
That conversation may still be valuable. It may produce market learning, a future opportunity, or an internal introduction.
It should not be forecast like an active deal.
When the bank can discuss a desired outcome date, even as a range, the seller can ask what must happen first. When the bank cannot name any timing or reason for timing, the opportunity may be research rather than procurement.
That distinction protects the founder's attention and the accuracy of the pipeline.
Work backward through the decision
Suppose the bank says it would like the product live before the next planning cycle, renewal, audit period, product launch, or seasonal demand window.
Now work backward.
Ask:
When must implementation begin?
What technical or data work must happen before kickoff?
What vendor, security, risk, compliance, and legal reviews are required?
Who needs to approve the business case and budget?
When do those people meet or make decisions?
What evidence must the fintech provide?
What could move the date?
The conversation turns a general opportunity into a decision map.
It may also show that the original date is impossible. That is useful to learn early, while both sides can reset expectations.
Listen to the reason behind the date
The date itself matters less than the reason.
Strong timing signals can include:
an expiring vendor contract;
a board or strategic priority;
an audit or regulatory commitment;
a new product or market launch;
a staffing or capacity constraint;
a budget window;
rising fraud or loss exposure;
customer experience pressure;
or a major internal project that creates a dependency.
If the bank gives a date but no business reason, keep testing. The date may be aspirational.
If the bank gives a compelling reason but the path is incomplete, the opportunity may be real and need decision support.
Do not use the question as a closing trick
The purpose is not to force urgency the bank does not have.
Do not respond to every answer by insisting on an aggressive timeline. Do not use the desired date to manufacture a false countdown. Do not promise implementation before your own team validates the work.
Use the answer to plan responsibly.
A strong response might sound like this:
If that is the outcome window, we should work backward together. Before we discuss a commitment, let's confirm the internal review, the data and integration path, the people the bank needs involved, and the earliest implementation slot our team can support.
That language respects the bank's process and protects the fintech from overselling.
What vague timing tells you
You may hear:
“Sometime next year.”
“We are just exploring.”
“There is no set date.”
“We need to see what leadership thinks.”
“We have another project ahead of this.”
Do not punish the buyer for being honest.
Re-stage the opportunity.
Identify what would have to change for timing to become real. That could be executive sponsorship, a budget event, completion of another project, clearer proof, or a different first use case.
Then decide whether to nurture, conduct research, complete limited pre-work, or disqualify the current-period forecast.
Ask your own company the same question
The bank is not the only party with timing constraints.
If the institution wants the product live in a defined window, can your team support it?
Confirm:
diligence-response capacity;
legal and commercial availability;
integration resources;
implementation slots;
customer-success ownership;
and support for existing partners.
A deal is not healthy when sales can hit the date only by creating delivery risk.
The desired live date will not tell you everything about an opportunity.
It will expose many of the questions the pipeline has allowed you to avoid.
FAQs
How early should we ask about the desired live date?
Ask after you understand the problem and outcome well enough for timing to be meaningful. Do not wait until the contract stage.
What if the bank's desired date is unrealistic?
Explain the dependencies, validate your own capacity, and build a credible phased timeline. Do not agree to a date before the work is understood.
Does no live date mean there is no opportunity?
Not necessarily. It may be an early research or nurture opportunity. It should not be treated as a current decision-stage deal without stronger evidence.
Work With Stacy
If your pipeline is full of positive conversations but unclear timing, I can help you map the bank's real decision cycle and separate current opportunities from future interest.
Related Reading
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
