A community bank or credit union is one of the most procedure-driven businesses in the country. Every product has a written procedure, every loan type has an operations checklist, every department has a training manual, and a compliance team keeps a library of policies that examiners read line by line. Around that sits the daily traffic: loan officers emailing borrowers and underwriters, branch staff asking operations how to handle an odd deposit, the IT help desk, the vendor-management file.
The labs' interest in this work is on record. Invisible says it draws reinforcement learning tasks from banking. Mercor names finance and insurance with statements and underwriting files as examples, and micro1 names financial services. Financial managers and customer service representatives in finance are GDPval occupations.
Banks also hold the most closely guarded customer information of any industry here, along with records that regulators treat as confidential by rule. So the operating library, the part least tied to any one customer, is the only sensible place to begin: procedures, loan operations SOPs, credit memo templates, training, vendor-management workflows and help-desk history. Raise every customer or member record, every examination document and every core processor agreement with the licensing company before anything is exported.
Worth
What a institution's data may be worth
Pre-set for a typical institution: 90 staff and 20 years of records. No buyer publishes pricing by industry, so industry does not move the band. Our estimate, not a buyer quote.
Buyers
Which buyers want this data
Each reason is the buyer's own published statement about the tools, data or industries it takes, matched to how community banks and credit unions work.
Featured partners
micro1
Names financial services and lists SOPs, playbooks and knowledge bases, which is what a bank's procedures library is.10,11
- $100K to $2M+, micro1 says7
Watch out for: Says it removes personal details only "when relevant", so ask exactly how.12
Polyshares
Names financial services and buys tickets, email and spreadsheets, with a third-party partner scrubbing PII before licensing.13,14,15
- $100K to $2M+, Polyshares says8
- None, Polyshares says16
- An offer in 1 to 2 weeks, then paid in 30 to 60 days17
Watch out for: Exclusive by default, and every deal it lists is exclusive with no end date.18,19
Everyone else we reviewed
By score, with full reviews. We have no referral agreement with these companies, so we do not link out to them.
Buyer demand
How buyers' own tools rate community banks and credit unions
No buyer publishes a price list by industry. These are settings inside buyers' and brokers' own estimators and intake forms, read from their public pages on 2026-10-14. They show how each company sorts industries, not what any institution was paid. The category shown is the one a institution would most likely pick; that match is ours.
| Company | Its category | How it rates the industry |
|---|---|---|
| Troveo | Financial services, banking or fintech | Tier 1 of 4: "Buyers pay a premium for data from your industry." Price factor 1.3 in its estimator.27 |
| Polyshares | Financial services and fintech | Marked premium in its intake list28 |
| VMS | Finance | Higher weight in its estimator (factor 1.30)29 |
| Ventra | Legal, healthcare, financial services or accounting | Says it cannot take these industries right now30 |
Size rules buyers publish
Checked against 90 staff, the typical institution size this page's calculator is set to. Ask each buyer whether contractors and part-time staff count.
Polyshares
No headcount rule; the length and texture of the record matter more31
Mercor
None stated32
Troveo
No minimum stated; its estimator starts at 2033
Nyne
20+ US W-2 employees and 3+ years34
Handshake AI
20+ full-time employees and 3+ years35
micro1
Pewter
20+ staff and 3+ years38
Endless
Roughly 30+ employees39
Ventra
30+ US employees and 3+ years of records40
Supersoniq
50+ employees and 5+ years41
What buyers value
What in a institution's records buyers value
The column on the right is not legal advice: it lists what to raise with the buyer before anything is exported.
| Data | Where it lives | Why a buyer values it | Raise with the buyer |
|---|---|---|---|
| Procedures and policy library | SharePoint, policy management software | Written procedures for every product and department, kept current for examinations. | Any document that is part of an examination file or marked confidential supervisory information. |
| Loan operations checklists | Loan origination system, shared drive | Boarding, documentation and post-closing steps for each loan type, with exception handling. | Borrower names and account numbers on completed checklists. |
| Credit memo templates and credit policy | Word, loan origination system | How the institution argues for and approves a commercial or consumer loan. | Completed memos about real borrowers. |
| Staff training and onboarding materials | Learning management system, intranet | How tellers, member service reps and lenders are taught to handle situations, in the institution's own words. | Nothing specific |
| IT and operations help-desk tickets | ServiceNow, Freshservice, email | Branch questions to operations and IT, answered thousands of times. | Tickets that include account or member details. |
| Vendor-management workflow | Third-party risk software, email | How the institution reviews and monitors vendors, a long, documented process. | Vendor agreements that restrict disclosure. |
A week of records
A week of data at a institution
- Monday: loan operations boards 40 new loans from the checklist and logs 6 exceptions.
- Tuesday: branch staff send 120 questions to the operations help desk; most are answered from the procedures library.
- Wednesday: the compliance officer updates a deposit procedure after a regulatory change and pushes training to staff.
- Thursday: credit committee reviews three commercial memos from the standard template.
- Friday: the vendor-management team completes an annual review of a technology provider.
Process
How it works with each buyer
In each buyer's own published words. Where a buyer publishes nothing, we say so rather than guess.
micro1
- Internal docs, SOPs and playbooks, knowledge bases, project management workflows, internal comms, templates, CRM and workflow metadata, task histories11
- 30 to 200 employees37
- $100K-$2M+ per data package; over $1M for unique data7
- PII removed "when relevant"12
- The company keeps ownership of its data and reviews samples before release42
- Not published
Polyshares
Selling or closing
Selling or closing your institution? License its data first
When community banks and credit unions merge, the combined institution usually keeps one core system and one procedures library and retires the other. The retired library is written institutional knowledge that nobody prices. If a merger or conversion is coming, ask each licensing company whether procedures, training and operations SOPs can be licensed before the old systems are shut off, with every customer record left to the licensing company's review. Buyers already approach companies around deals: Mercor went to Warmly after HubSpot acquired it.3
FAQ
Banks and credit unions: questions, answered
Repeated, well defined ones, which is what micro1 says it looks for: loan boarding, account maintenance, disputes intake, help-desk answers to branch questions. Each runs from a written procedure many times a day.47
No buyer prices banks on their own. Published ranges mostly run $100K to $2M, as the buyers' own claims: micro1 states $100K-$2M+, Ventra $100K-$2M and Jottings $1M+ for rare data. Endless says regulated data lowers its range, so describe an operations-only package as exactly that from the start.7,50,51,52
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
We do not answer legal questions. Ask the licensing company: their team reviews this with you before anything is signed.
Before you sign
Legal questions go to the licensing company
We do not answer legal questions. Ask the licensing company before you sign: their team reviews these with you.
Questions for this kind of business
- How does your review treat GLBA nonpublic personal information and our privacy notice?
- How will confidential supervisory information and BSA records be identified and kept out?
- Does OCC, FDIC, NCUA or state regulator guidance on third-party relationships apply to this deal?
- Do our core processor and vendor agreements limit exports?
- Who owns this data: the company, an estate, or someone else?
- How do CCPA, GDPR, UK GDPR and state privacy laws apply, and is de-identified data still personal information?
- Do customer, vendor or platform contracts, NDAs or API terms restrict this?
- Do professional rules apply (AICPA, IRC 7216, HIPAA, ABA Model Rule 1.17, insurance agency contracts, adviser rules, state boards)?
Questions for any buyer
- Is the license exclusive, and for how long?
- Can you sublicense the data, and to whom?
- Which AI labs will receive it, and will you tell us?
- How long do you keep it, and how is it deleted?
- What is your liability cap, and who indemnifies whom?
- Will the contract ban re-identification of people in the data?
- Who removes personal data, by what method, and do we approve it first?