A fintech startup has a problem that most software startups do not: the buyer is often regulated, and the regulated buyer has to check you out before it can say yes. A bank that wants to use your product is expected by its supervisors to manage the risk of working with you, and that process starts before the first contract. So the first customers of a fintech startup are won on two things at once: a product that solves a problem, and a package of evidence that you are safe to work with. This page covers how to prepare that package, which first customers are within reach and how to start conversations when nobody knows your name.

What a bank is expected to do about you

In June 2023 the Federal Reserve, the FDIC and the OCC issued a final Interagency Guidance on Third-Party Relationships: Risk Management. According to the agencies' notices, it covers the life cycle of a relationship with a third party: planning, due diligence and third-party selection, contract negotiation, ongoing monitoring and termination. It applies to the banks those agencies supervise, and it replaced each agency's earlier guidance. I am describing the agencies' own summaries, read through search results on 2026-11-20, and the guidance itself is long and detailed. A founder selling to banks should read it, or have a lawyer read it, instead of relying on this paragraph.

What that means in practice is that the bank's vendor management team will send you questions, and the questions will be about you, not only the product: your financial condition, your security practices, how you would continue to serve the bank if something went wrong, who owns what in your company and what happens to the bank's data if the relationship ends. You do not have to have every answer on day one, but you should have a written answer ready and a person who owns it.

Build the evidence pack before you need it

  • A one-page description of the company: who owns it, who runs it, how it is funded, where the staff are.
  • A security summary: how you store and protect data, who has access, and how you handle an incident. If you have an independent security report, such as a SOC 2, include it. If you do not, say when you plan to get one rather than implying you have one.
  • A continuity plan: what happens to the customer if you are down, or if you stop operating.
  • Sample contract terms: data ownership, termination, audit rights.
  • Reference contacts: if you have a pilot customer, ask whether they will speak to others.

This pack has a second use. A prospect who sees it in the first week of a conversation concludes that you understand their world. A startup that sends it unprompted sounds more established than one that scrambles after the question arrives.

Who can be a first customer

Customer Speed What they need to see
Small businesses that use financial tools Fast, weeks That it works and the price is clear
Other fintechs and software firms Moderate An API, documentation, uptime
Community banks and credit unions Slow, months The evidence pack and a champion inside
Large banks Very slow Everything above, plus scale

The speeds are a pattern, not a measurement, and they differ by product. The practical advice is to avoid making a long-cycle institution your only first customer. If your product can serve a faster segment first, the early revenue and the reference you earn make the slower sale easier later.

Starting conversations without a brand

A buyer in finance will not trust a name they have never heard of, so give them a reason to answer that costs nothing: a short note about a specific problem they have, with an offer to show a solution in a call. The first email should be to the person who owns the problem, not to compliance: the head of operations, the head of lending or the product lead. They can become a champion who brings in vendor management when the time comes. Say plainly what you do not do. A fintech that is clear about what it is not, such as not a bank and not holding funds, saves the buyer a round of questions.

Be careful with claims. In financial products, wording about returns, speed or approval can be regulated. Do not state a rate, a savings figure or a result unless you can show it, and ask a lawyer who knows your product to review any email that describes fees or terms.

A design partner before a customer

A first bank or credit union may be more willing to be a design partner, a customer that shapes the product in return for early access, than to sign a standard contract. Startup design partners before product covers how to set that up. A design partner gives you a reference, a case study and the experience of going through one vendor review, which prepares you for the next one.

Count the room, then write

Make a list of 40 institutions of the same type and size, in one region or one segment, and write to the person who owns the problem at each. Count replies, calls and requests for your evidence pack. Learn what they ask for, and improve the pack. Wording about fees or terms can be regulated, so read is cold email legal for the email rules and have a lawyer who knows your product check anything that describes terms.

The founder's job at this stage is the product and the evidence. The list and the first emails can be handed off: Rocketship finds the right people by job title, industry and place, emails them from your own Gmail, follows up, answers replies and books the meeting. You can see the plans, from $12 a month, on the pricing page. Every monthly plan starts with a 7-day free trial, card required, and you can cancel any time before day 8.