Quick answer: After a strong first bank meeting, fintech founders should send a champion packet, not a generic thank-you email. The packet should include the bank-specific problem, the use case in plain language, likely internal owners, risk and implementation notes, relevant proof, suggested next participants, and a short forwarding note the champion can reuse.
A good first meeting with a bank can feel like momentum.
The banker asked smart questions. They understood the problem. They said the product was interesting. They may have even said, “I can see how this would help us.”
Then the founder sends the usual follow-up:
Thank you for the time. Great conversation. Attached is the deck. Looking forward to next steps.
Thank you for the time. Great conversation. Attached is the deck. Looking forward to next steps.
That is polite, but it is not enough.
Inside a bank, the next sale usually happens without you. Your champion has to explain the opportunity to someone else: risk, IT, operations, finance, executive leadership, or another business owner.
If you only send the deck, you make the champion do the translation work alone.
A thank-you email is a receipt. A champion packet is a sales asset.
The follow-up should help the champion sell internally
Your post-meeting follow-up should help the banker answer three questions:
- What problem are we trying to solve?
- Why does this vendor seem worth evaluating?
- Who should be involved next?
What problem are we trying to solve?
Why does this vendor seem worth evaluating?
Who should be involved next?
That is different from summarizing the call.
A summary looks backward. A champion packet moves the deal forward.
1. Start with the bank-specific problem
Do not start with your product.
Start with what you heard.
Example:
Based on our conversation, the main issue seems to be manual exception review in the onboarding process, especially when volume spikes and operations has to pull in compliance for clarification.
Based on our conversation, the main issue seems to be manual exception review in the onboarding process, especially when volume spikes and operations has to pull in compliance for clarification.
That kind of summary does two things. It shows the banker you listened, and it gives them language they can reuse internally.
2. Translate the use case into bank language
A champion cannot sell internal stakeholders on vague platform language.
Do not say:
Our platform uses AI to automate workflow intelligence.
Our platform uses AI to automate workflow intelligence.
Say:
This would help the operations team reduce manual review time while giving compliance clearer visibility into exceptions.
This would help the operations team reduce manual review time while giving compliance clearer visibility into exceptions.
Banks buy what they can route. Plain bank language travels farther inside the institution than founder language.
3. Identify the likely internal owners
Tell your champion who should be involved next.
Depending on the product, that might include:
- Operations
- Digital banking
- Lending
- Compliance
- Information security
- Vendor management
- Finance
- Executive leadership
Operations
Digital banking
Lending
Compliance
Information security
Vendor management
Finance
Executive leadership
Do not make the champion guess.
If the next step requires a business owner and a technical reviewer, say that. If risk can wait until after use-case fit is confirmed, say that too.
4. Answer the obvious risk and implementation questions
A champion cannot move a deal if they know the first internal question will stop them.
Give them short answers to the issues most likely to surface:
- What data is involved?
- What systems are touched?
- What does implementation require?
- What does the bank team need to provide?
- What documentation is ready?
- What is the lowest-risk first step?
What data is involved?
What systems are touched?
What does implementation require?
What does the bank team need to provide?
What documentation is ready?
What is the lowest-risk first step?
You do not need to answer every due diligence question in the first follow-up.
You do need to show that the process is not vague.
5. Include proof the bank can evaluate
If you have bank logos, use them carefully. If you do not, be direct.
Proof can include:
- Pilot results
- Workflow data
- Customer outcomes
- Implementation examples
- Security readiness
- Founder experience
- Comparable use cases
Pilot results
Workflow data
Customer outcomes
Implementation examples
Security readiness
Founder experience
Comparable use cases
The worst move is inflated proof.
Banks can sense when a founder is trying to look bigger than they are. Credible proof beats exaggerated proof.
6. Give the champion a forwarding note
This is the piece most founders skip.
Give the champion a short note they can forward internally.
I spoke with [company] about [problem]. They appear relevant because [reason]. The first evaluation step would be [next step]. I think [teams] should review because [why].
I spoke with [company] about [problem]. They appear relevant because [reason]. The first evaluation step would be [next step]. I think [teams] should review because [why].
You are not manipulating the process. You are making it easier for the champion to be accurate.
Champion Packet Checklist
After the first strong meeting, send:
- Bank-specific problem summary
- Plain-English use case
- Internal owner map
- Risk and implementation notes
- Proof or pilot evidence
- Suggested next meeting participants
- Forwardable internal summary
- Clear next step
Bank-specific problem summary
Plain-English use case
Internal owner map
Risk and implementation notes
Proof or pilot evidence
Suggested next meeting participants
Forwardable internal summary
Clear next step
A bank champion does not need more enthusiasm.
They need useful material.
Your job after the first meeting is not to celebrate interest. Your job is to equip the person who has to carry the deal when you are not there.
FAQ
Should I send the champion packet as an email or a document? Usually both. Put the high-level version in the email and attach a one-page packet the champion can forward.
How long should the champion packet be? One to three pages. If it gets longer, it becomes homework.
Should pricing be included? Only if the conversation is ready for it. If pricing will create internal debate before value is clear, keep it separate.
Work With Stacy
I help fintech founders build the sales materials their bank champions can actually use inside the institution.
‹ How to Design a Bank Pilot That Can Become a Paid Contract
What Your Fintech Website Must Prove Before a Bank Books the Demo ›
