Home › Blog › How fintechs land their first bank pilot, and why most pilots stall
How a fintech lands its first bank pilot: find a budget owner, keep scope out of 'critical', start vendor risk early, and agree the path to contract.
By Moe Alhosni · Published 29 October 2026 · 9 min read
Short answer: A fintech lands its first bank pilot by finding a business owner with a live problem, scoping the pilot small enough to stay out of the bank's "critical" tier, and starting vendor risk in parallel instead of after the demo. Agree written success criteria and the path from pilot to contract before the pilot starts. Most pilots that stall were never designed to convert.
I have seen this from both sides. At Moody's in London, from October 2019 to April 2024, I sold into Tier 1 banks, asset managers and, as Assistant Director, Sales, into central banks and financial institutions across Central and Eastern Europe plus Portugal, Malta and Cyprus. Then, from April to December 2024, I was Sales Director at Coinshift, a Web3 treasury management company, where I was the young vendor asking finance teams to trust a newer product. The lessons below are the general ones. No former employer's data, no client names, no deal figures.
This is a B2B guide: a fintech selling software or services to a bank. It is not about consumer lending or retail investment products.
The word covers three different things, and confusing them is the first way pilots go wrong.
| Type | What happens | Who pays | Does it go through vendor risk? |
|---|---|---|---|
| Proof of concept | You show the product works on test or sample data, often in a sandbox | Usually nobody | Light, or not at all |
| Paid pilot | A real team uses the product on real work, for a fixed period, with success criteria | The bank, often a small fee | Yes, scaled to what data you touch |
| Production contract | Live use, usually with an option to expand | The bank, full price | Yes, the full review |
A proof of concept is easy to get and easy to forget. The innovation team that ran it may have no budget for what comes next. A paid pilot is harder to get and far more valuable, because the bank has already put you through some of its vendor process and a business line has already spent money. If you can choose, aim for a small paid pilot over a free proof of concept.
From what I saw on both sides, stalled pilots usually share one of these causes.
Every one of these can be designed out before the pilot starts.
Founders often assume a bank cannot work with a company that has two years of accounts and twenty staff. The published US guidance says otherwise.
The Interagency Guidance on Third-Party Relationships: Risk Management, issued by the Federal Reserve, FDIC and OCC in June 2023, expects that a bank may not get all the information it wants. It gives the example that the third party "may not have a long operational history". In that case, the guidance says the bank should "identify and document any limitations" of its due diligence and consider alternatives, such as getting other information, adding controls or monitoring, or using a different provider. The Federal Reserve's cover letter also says the guidance covers relationships with fintech companies.
So being young is a risk the bank has to manage, not a rule that excludes you. Your job is to make that management easy. Offer the alternative evidence before they ask: founder and investor backgrounds, insurance, a clear security posture, references from other regulated customers if you have them, and an exit plan that shows the bank can leave you cleanly.
In the EU, DORA, Regulation (EU) 2022/2554, has applied to banks and payment institutions since 17 January 2025. If you provide an ICT service, even a pilot contract is expected to carry certain terms, such as a description of the service, where data is processed, and termination rights. The heavier terms apply when your service supports a critical or important function. In the UK, the PRA's SS2/21 sets the expectations for outsourcing and third-party risk at banks and building societies.
This is general information, not legal advice; check with your compliance team or counsel.
Every framework above scales scrutiny to how important your service is. A first pilot that stays in the lighter tier moves faster. Here are the design choices that help.
| Choice | Why it helps |
|---|---|
| One team, one use case | A narrow scope is easier to approve and easier to measure |
| Synthetic, anonymised or public data where possible | Less personal data means a lighter data protection and security review |
| No dependency in a live process | If you fail, the bank carries on, so you are not a critical service |
| Fixed term, usually a few months | A clear end date makes approval a smaller decision |
| A small fee | It puts the pilot in a budget, and turns "interesting" into a purchase |
| Written success criteria | Two or three measures the sponsor agrees to in advance |
| A pre-agreed path to contract | What happens, and at what price, if the criteria are met |
The last row is the one most founders skip. Before the pilot starts, ask the sponsor: "If this works, what happens next, who signs, and what do they need to see?" Write the answer down and send it back. That email is your conversion plan.
Ask for the due diligence questionnaire as soon as the sponsor says the word "pilot". In my experience, even a large, well-known provider goes through the bank's vendor onboarding. A start-up certainly will.
The US guidance lists the areas a bank typically looks at, including financial condition, business experience, key personnel, information security, operational resilience, incident reporting, reliance on subcontractors and insurance. Build your answers once and keep them current:
Send the pack with the pilot proposal. A sponsor who can forward a complete vendor file to their risk team looks good internally, and that matters to them.
Innovation teams and labs are easy to meet and can be good partners. But check early whether they own a budget or hand successful pilots to a business line. If they hand off, find the business line owner now, not at the end.
The best first contact is usually the head of the function your product changes: treasury, payments operations, credit, compliance, finance. They feel the problem every week, and they have a reason to push your file through risk. Add a second contact in a neighbouring team so the pilot survives a reorganisation. My longer guide to bank buying committees, who signs and who blocks, is in how to sell to banks.
Consider where you start. Smaller banks and credit unions often have shorter committees and a sponsor at C-level. Non-bank finance firms, such as payment companies and lenders, can be a faster first logo that still proves you can pass a regulated firm's review.
Many first bank meetings come from introductions: investors, advisers, a former colleague. That is fine, and you should use every one you have. Outbound adds meetings you choose, on a schedule you control, with people your network does not reach.
For bank outbound, three things matter more than in other markets.
Cold B2B email to banks is ordinary B2B marketing, but the rules on email differ by country. Germany, for example, treats advertising by email without the addressee's prior express consent as an unacceptable nuisance under UWG section 7. The jurisdiction-by-jurisdiction version is in is cold email legal for financial services.
We book meetings with business owners at the institutions you choose, and you pay per qualified meeting that took place. Here is the honest position on proof: ROI Maximizer has not run a finance campaign yet. Our published results are in PR, not finance. PR Noir got 27 leads, 10 qualified meetings and a $90K deal, and P1 Communications, a hospitality PR agency, got 20+ qualified meetings. What I add for fintechs is the buyer-side knowledge on this page.
Prices: a setup fee of $1,000–$3,000, then $200–$500 per qualified meeting that took place, or a flat $5,000 a month. No minimum term, and nothing for a no-show. More on the offer for fintechs is on fintech lead generation, and the wider offer on the financial services page. What should count as "qualified" when the buyer is a bank is in pay per meeting for fintech.
Usually through a small, paid pilot with a business-line sponsor who has a budget, scoped to avoid critical processes and live customer data. Start the bank's vendor risk review at the same time as the pilot proposal, and agree in writing what happens if the pilot succeeds.
Yes. The 2023 US interagency guidance expects some vendors "may not have a long operational history". It tells banks to document the gap and manage it, for example with extra information, controls or monitoring. Make that easy by offering the evidence up front.
Only if the next step is clear. A free proof of concept is easy to agree and easy to forget. A small paid pilot puts you in a budget and through part of the vendor process, which makes conversion to a contract much more likely.
Long enough to hit the success criteria and no longer, usually a few months. Agree the end date and the criteria in advance, and allow for the time it takes to get data and system access.
If you pay anyone to book bank meetings, us included, get three things in writing first.
Then put your pilot fee, contract value and conversion rate into the ROI calculator to see what a bank meeting is worth to you.
If you are working towards your first bank pilot and want a second view on scope, sponsor or sequence, book 30 minutes or email moe@roimaxi.com.
Moe Alhosni, founder, ROI Maximizer (M Ventures LTD, 4 Beau Street, Bath BA1 1QY).
About the author: Moe Alhosni, founder of ROI Maximizer. Before that he spent four and a half years in sales at Moody's in London, most recently as Assistant Director, Sales, working with banks, asset managers and private equity firms. He runs the campaigns behind the first-hand data on this site. LinkedIn
Or run the free GTM teardown on your own site for the ICP, cold email and numbers specific to your company.
ROI Maximizer is a trading name of M Ventures LTD, registered in England and Wales, company no. 15554493. Registered office: 4 Beau Street, Bath BA1 1QY, United Kingdom. moe@roimaxi.com
© 2024–2026 M Ventures LTD. Privacy notice