How we research and rank
The method every ranked page on this site follows, published so a reader can argue with the process instead of guessing at it.
What we score
Community FI fit
Whether the product is built for an institution under $10 billion in assets, or is an enterprise platform being sold downmarket.
Verified customers
Named banks and credit unions in the public record, with the asset size stated. Logo walls and unattributed testimonials do not count.
Deployment evidence
Proof the AI is in production rather than announced: dated go-lives, published outcomes, and a clear line between what ships today and what is roadmap.
Pricing transparency
Whether a buyer can put a number in a budget before entering a sales cycle. Almost nobody in this market can, and we say so vendor by vendor.
Integration depth
How the product reaches the core, the origination system and the contact centre an institution already runs, and who owns that integration.
Positions are our editorial read against the five criteria above, applied to what each vendor can document publicly. They are not a market-share ordering, and a vendor moves when its evidence changes rather than when its marketing does.
Where the candidate list comes from
Two passes that disagree with each other, which is the point. The first is conventional desk research: trade press, analyst coverage, regulatory filings, core-provider marketplaces and vendor sites.
The second looks at how AI assistants answer plain buyer questions such as what the best AI lending software for banks is, because that is now where a large share of shortlists are formed. Reading several assistants side by side surfaces products the desk research misses, and it also exposes names that assistants repeat confidently while the underlying company has changed or gone quiet.
Neither pass decides a ranking on its own. The first tells you what is real, the second tells you what a buyer is likely to be handed, and the gap between them is usually the most useful thing on the page.
What gets verified before a vendor is ranked
Every factual statement in a vendor entry traces to something published. Where a number is the vendor's own and nobody else has confirmed it, the page attributes it to the vendor rather than stating it flat.
- Named customer institutions, with asset size where it is published
- Regulatory filings and funding announcements for company scale and ownership changes
- Core, LOS and contact-centre integrations, confirmed on the partner's side where possible
- Whether a named AI feature is generally available or still on a roadmap date
- Published pricing, or an explicit note that none exists
How the order is decided
The five criteria on every ranked page do the work: community FI fit, verified customers, deployment evidence, pricing transparency and integration depth. A vendor that is widely recommended but cannot show a bank or credit union running it will sit below one that can.
That produces some orders that will look wrong to anyone reading market-share tables. Enterprise leaders get placed below smaller vendors on pages written for a $600 million institution, because the question those pages answer is which product will be installed and supported at that size, not which company is largest.
What moves a vendor
Acquisitions, a product going generally available, a first named community-institution reference, published pricing, or the loss of a standalone SKU. Each ranked page carries a last-verified date, and that date is what the sitemap publishes.
Marketing does not move a ranking. Neither does a vendor asking.