Prove Core Intelligence can launch without a data team.
A CBO should not hear “custom integration project.” This readiness desk shows the exact extract, guardrails, owners, and first 10 minutes required to turn bank-owned core data into banker action queues.
Riverstone Community Bank can preview Core Intelligence in one working session: upload a sanitized Jack Henry extract, verify source controls, and produce banker-owned deposit defense queues in about 10 minutes.
Assign retention calls before Friday
Route ACH/wire accounts to treasury
Review outside payment-provider leakage
Create 30/60/90-day banker queue
Show who owns the first core-data actions before the meeting ends.
Approve the first banker queues and use the routing preview as the day-one Core Intelligence proof artifact.
Call balance-decay relationships before any rate-only offer is discussed.
Proof: Uses 90-day balance trend and 30-day average balance from the sanitized extract.
Review ACH/wire volume and prepare one treasury product-fit conversation.
Proof: Uses monthly credits/debits and active treasury-products flag; no transaction descriptions are required.
Create a relationship-depth call, not a mass prospecting task.
Proof: Uses average balance and active product count only.
Manager review required before mass outreach.
Build renewal calendar tasks and assign follow-up dates.
Proof: Uses maturity date fields; exact payoff/maturity data remains labeled internal and source-dated.
Convert the preview into approved banker work without losing audit control.
Core Launch Center readiness export with QA, routing, suppression, and access-log proof.
Approved for relationship-service banker workflow after suppression and source-proof checks pass.
Approved for relationship-service banker workflow after suppression and source-proof checks pass.
Manager review is required before broad outreach because this queue contains high-value or strategic relationships.
Approved for relationship-service banker workflow after suppression and source-proof checks pass.
Core extract QA preview shows required fields, row count, raw-identifier findings, and suppression readiness.
DNC, opt-out, existing-product, and review statuses are checked before any task or export.
4 action(s) are assigned across 4 queue(s) with SLA and proof.
Core Launch PDF includes source-safe QA, routing preview, approval orders, and guardrail language.
Give the deposit team its first approved workday from the core extract.
Which approved core-data tasks must be completed before noon, and which manager reviews are blocking relationship-service outreach?
Friday proof requires completed banker dispositions, treasury reviews, renewal follow-up dates, manager approvals, and the Core Launch approval PDF.
Open a retention call task for each shrinking relationship and record whether the balance movement is seasonal, operational, or relationship-risk.
Proof: CORE-01 approval note, source-safe queue proof, suppression status, and banker outcome note.
Create treasury review tasks with ACH, wire, RDC, positive pay, sweep, or ICS/CDARS fit noted before banker outreach.
Proof: CORE-02 approval note, source-safe queue proof, suppression status, and banker outcome note.
Assign a senior relationship-depth conversation and require manager review before any broad call list or export.
Proof: CORE-03 approval note, source-safe queue proof, suppression status, and banker outcome note.
Create renewal calendar tasks with maturity window, assigned banker, and next documented follow-up date.
Proof: CORE-04 approval note, source-safe queue proof, suppression status, and banker outcome note.
Turn a core extract into first signal QA without waiting on a data team.
Approve the first-signal preview and schedule the production cutover owner.
Jack Henry sample extract accepted through secure browser upload.
Artifact: Transfer receipt with row count and checksum
Guardrail: Encrypted transfer only; raw files expire after validation.
10 of 11 launch fields mapped to banker-readable labels.
Artifact: Sanitized field dictionary
Guardrail: Unknown fields stay out of queues until reviewed.
Opt-out, DNC, and existing-product suppression files are loaded.
Artifact: Suppression load receipt
Guardrail: No customer appears in a call queue before suppression checks pass.
GLBA acknowledgement and audit log are enabled for every view/export.
Artifact: Access log sample and GLBA acknowledgement
Guardrail: Every internal insight is relationship-service workflow, not credit decisioning.
Preview queues reconcile balance decay, treasury fit, maturity radar, and outside payment-provider patterns.
Artifact: First-signal QA worksheet
Guardrail: Signal counts are preview-only until a bank admin approves production routing.
Named bank owner can approve the first production banker queues.
Artifact: Go-live signoff and demo-isolation attestation
Guardrail: Demo workspace remains seeded and isolated from production bank data.
Core Provider Runbooks
A community bank should not need a data team to launch. Pick the core path, collect the artifact, and show the banker outcome in the same session.
Export the standard deposit account, balance history, ACH/wire activity, maturity, and assigned-officer fields into the sanitized launch template.
Ops uses a saved report/export path; DepositLeads maps banker-readable fields and rejects raw account numbers automatically.
First Balance Decay, High-Balance Low-Product, Maturity Radar, and Treasury Upsell queues can be previewed in the launch session.
Artifact: Sanitized field dictionary, transfer receipt, row count, checksum, and GLBA acknowledgement.
Drop the sanitized daily or weekly extract to the bank-controlled SFTP folder with account hash, product, balance, trend, ACH/wire, and officer fields.
DepositLeads consumes the scheduled extract contract; bank IT only manages credentials and folder access.
Daily internal opportunity queues refresh without a manual spreadsheet after the pilot proof is approved.
Artifact: SFTP connection receipt, field dictionary, suppression load receipt, and access-log sample.
Schedule the sanitized relationship extract with hashed account IDs, customer segment, county, balances, maturity windows, and transaction-volume fields.
The bank provides the ordinary ops extract; DepositLeads handles mapping, QA, suppression, and preview routing.
Deposit defense, rate sensitivity, and treasury depth actions route to the assigned banker without SQL work.
Artifact: Field dictionary, sample extract approval, suppression receipt, and production cutover signoff.
Send sanitized account-opened, maturity, and transaction-summary events to the core webhook receiver after the preview extract reconciles.
API-enabled cores use a prebuilt event contract; no custom analyst query is needed for the first banker queues.
Account-opened attribution, maturity radar, and internal signal changes update inside the banker workflow.
Artifact: Webhook credential receipt, event contract, audit-log sample, and preview-to-production approval.
Use the DepositLeads sanitized template when the bank cannot yet automate a core-specific extract.
A bank operations user can launch the pilot from a template while IT works on a later scheduled feed.
The CBO still sees first-signal value in the first session without waiting on an integration project.
Artifact: Template validation receipt, raw-identifier block result, suppression receipt, and demo-isolation attestation.
Core Extract QA Preview
Bank ops can validate the sanitized extract before activation: required columns, raw identifier blocks, suppression readiness, and first banker queues from the same preview file.
Validate a sanitized extract before anyone sees a queue.
Paste a CSV or upload a file. DepositLeads blocks raw identifiers, checks required fields, confirms suppression status, and previews banker-owned internal signals.
Assign same-day retention calls before any rate quote is approved.
Route ACH, wire, and operating-balance accounts to treasury for product-fit review.
Create relationship-depth calls for high-balance customers with shallow product usage.
Build 30/60/90-day renewal queue for assigned bankers.
Next ops action: Approve this preview for controlled Core Intelligence routing and show the first banker queues in the same session.
QA stores source-safe extract facts only. It blocks raw identifiers, labels outputs as banker workflow, and keeps preview queues out of customer-facing exports until admin approval.
QA API endpointAssign same-day retention calls before any rate quote is approved.
Uses 90-day balance trend and 30-day average balance from the sanitized extract.
Route ACH, wire, and operating-balance accounts to treasury for product-fit review.
Uses monthly credits/debits and active treasury-products flag; no transaction descriptions are required.
Create relationship-depth calls for high-balance customers with shallow product usage.
Uses average balance and active product count only.
Build 30/60/90-day renewal queue for assigned bankers.
Uses maturity date fields; exact payoff/maturity data remains labeled internal and source-dated.
Sanitized Core Extract Template
Give bank operations a safe starting file: hashed IDs, relationship-level balances, treasury indicators, suppression status, and no raw account numbers.
Template accepts hashed IDs and relationship-level facts only. It excludes raw account numbers, SSNs, tax IDs, card numbers, and customer-level transaction rows.
Download CSV template