Home › Blog › Pay per meeting for fintech: what "qualified" should mean when the buyer is a bank
When a fintech pays per meeting and the buyer is a bank, define qualified as function, institution fit, a live project and held, not booked.
By Moe Alhosni · Published 29 October 2026 · 7 min read
Short answer: When a fintech pays per meeting and the buyer is a bank, a "qualified" meeting should mean four things: the right function at the right seniority, an institution you can actually sell to, a live project or budget line, and a meeting that took place. A curious VP with no project is a conversation, not a qualified meeting. Write the definition before the first email, because whoever controls it controls the invoice.
I am Moe Alhosni, founder of ROI Maximizer, and we sell pay per meeting. We have not run a finance campaign yet, so nothing below is a fintech result of ours. It comes from the buying side of the table I sat across for years: Account Manager on Tier 1 banks and asset managers at Moody's in London, then Assistant Director, Sales, covering central banks, financial institutions, asset managers, PE and VC across Central and Eastern Europe plus Portugal, Malta and Cyprus. After that I was Sales Director at Coinshift, selling Web3 treasury management. Before Moody's I worked in settlements and customer due diligence at BLOM Bank France in London. I have been the seller trying to turn a first bank meeting into a second one.
This page is B2B only: a fintech or service provider selling to banks, credit unions and other financial institutions.
Our standard definition of a qualified meeting has six parts: seniority, company size and sector, budget authority, expressed need, held not booked, and no-show handling. It is in what counts as a qualified meeting, and it works for most B2B sales.
Banks break two of those parts.
So the bank version replaces "budget authority" with "is there a project", and makes "expressed need" mean something specific.
Here is the clause I would put in a fintech's contract. Change the words to fit your product, but keep the shape.
The person runs, or is the direct deputy of the person who runs, the function your product changes. For a payments product, that might be the head of payments operations. For a data product, the head of the team that uses the data. Name the titles that count and the ones that do not.
Analysts and associates do not count by default. They can be the right first contact in a big bank, so if you want them, say so, and agree whether they count as a full meeting.
The institution is one you can sell to today:
That last point costs fintechs the most. A meeting with a global bank you cannot onboard with is a nice slide and nothing else.
This replaces "budget authority". The meeting counts when the person said, in their own words, one of these:
Write down what they said. "We are reviewing our reconciliation tooling next year" is a project. "Interesting, send me something" is not.
The meeting took place, with the person named in the booking or someone you accept in their place. A bank meeting that moves three times and then dies is not a meeting.
Not charged. Rebooked at the agency's cost. If the prospect sends a junior in their place, you decide whether it counts, and say so within two working days.
After each meeting, you approve it or reject it against the clause, with a one-line reason. Rejected meetings stay off the invoice. That is how we bill: you approve each meeting.
| Meeting | Qualified? | Why |
|---|---|---|
| Head of payments operations at a regional bank, says they are reviewing their payments hub vendor next year | Yes | Right function and level, sellable institution, live project in their own words |
| VP of innovation at a Tier 1 bank, "always keen to see new fintechs", no project | No | Interest, not need. A conversation worth having, not one to pay for |
| Treasury analyst at a credit union, standing in for the CFO, who asked them to look at options | Your call | Junior, but a project exists and the CFO sent them. Decide in advance whether a delegated meeting counts |
The third row is the one to argue about before the campaign, not after.
Bank sales are long. The first meeting is the cheapest step for the buyer. In my experience the real filter is the second meeting, where the sponsor brings their team and names the project.
That has two consequences for pay per meeting.
First, a bank meeting is worth more than most B2B meetings, because deal sizes are larger, but fewer of them turn into deals. Price the meeting against what it is worth to you: deal size times the share of qualified first meetings that become deals. Put your own numbers into the ROI calculator.
Second, you will not know whether a campaign worked for months. If you pay a retainer, you pay throughout. If you pay per qualified meeting, you pay only for meetings that met the clause, and you can see the trend early from how many pass your approval.
How institutions run these processes is in how to sell to banks, and the special case of landing a first one is in how fintechs land their first bank pilot.
Our 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. Nothing for a no-show. Where a meeting sits in the range depends on how hard the buyer is to reach. A Tier 1 bank's head of a function is at the top end. A credit union CFO is lower.
Other agencies price differently. As of October 2026, Belkins' fintech page shows a starter package "from $5,000" with a 3-month pilot and "100 guaranteed appts/year" (Belkins). Compare its definition of an appointment with the clause above before comparing the price. A full table is in fintech lead generation agencies compared, and the general pricing models are in pay per meeting lead generation pricing.
One more line belongs in a fintech contract: the outreach itself must be lawful where it lands.
Selling a B2B product to a bank is ordinary B2B direct marketing, not a financial promotion. The email rules still apply. In the UK, PECR's email consent rule covers individual subscribers (PECR reg 22), and the ICO says "You can email or text any corporate body" (ICO guidance). In the US, CAN-SPAM "makes no exception for business-to-business email" (FTC guide). In Canada, CASL needs express or implied consent (CASL s6).
A meeting booked by breaking those rules is not one you should pay for, and not one a bank's compliance team will forgive. The full version, country by country, is on the financial services hub.
This is general information, not legal advice; check with your compliance team or counsel.
We have not run a finance campaign. Our published results come from PR agencies. PR Noir, a New York PR agency, went from 27 leads to 10 qualified meetings and a $90K deal. P1 Communications, a UK hospitality PR agency, got 20+ qualified meetings. Both started from a written definition of "qualified", and that is the part that carries over to a bank campaign. The numbers do not.
If you need a fintech or bank case study before you sign, pick an agency that has one. If you would rather pay only for meetings that pass a clause like the one above, we are built for that. More on how we approach the sector is on the selling to banks page.
Get three things in writing before you pay any agency, including this one.
If you want me to pressure-test your qualification clause against how banks actually buy, book 30 minutes or email moe@roimaxi.com.
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