The package a community bank can actually buy from.

Start with the CBO view. This is not a static calling list; it is the morning operating system for deposit growth. The first screen answers three questions: what changed overnight, who owns the work, and what should the team do before lunch.

Before a bank trusts the leads, it has to trust the facts. The audit gate blocks real rates, bank names, company data, contacts, dates, and verified labels unless source proof is attached. This is how we keep a demo from feeling like a black box.

A BDO does not need another spreadsheet. They need the next best call, a reason to call, contact confidence, territory ownership, and a compliant opener. The workflow moves from signal to action in under two minutes.

This is the intelligence moment. The profile explains why the business matters, which public relationships are connected, what products may fit, what evidence supports it, and what not to say. That is the difference between a lead and a relationship strategy.

Treasury officers get a different queue. They see ACH, payroll, RDC, wires, sweeps, merchant settlement, and fraud-control signals. Deposit executives can also review public rate movement without relying on unsourced anecdotes.

This is the renewal conversation before the pilot starts. We track calls, bad numbers, meetings, accounts opened, deposits won, treasury products, loans, and ROI by source, county, banker, and product line.

The ask is a contained 30-day pilot: defined counties, suppression upload, banker invites, daily digest, weekly QA, and a board-ready readout. Pilot terms are released after confirming fit, source expectations, and buyer stakeholders.