Demo Mode - seeded demo workspace, isolated from production bank data
Riverstone Community Bank
Pulaski County, AR · platinum plan · demo mode
Relationship Switch Kit

Move the relationship without losing momentum.

Turn every high-value action into a switch readiness score, treasury implementation plan, customer packet, banker and ops board, risk alerts, and won-value tracker.

Avg readiness
49/100
Expected deposits
$27M
Risk alerts
141
Treasury lanes
275
Selected switch

Southwest Arkansas Surgical Supply

Southwest Arkansas Surgical Supply is a complex switch relationship: 48/100 readiness with 52/100 modeled move difficulty.

Readiness
48/100
Move difficulty
52/100
Expected deposits
$603K
Required products
7
Complex switch: Lead with the switch plan, not a rate: Southwest Arkansas Surgical Supply is a complex switch relationship: 48/100 readiness with 52/100 modeled move difficulty.
Expected deposits
$27,218,500
Deposits tied to a switch plan
Actual balances
$9,160,640
Modeled demo balances tracked against expected
Treasury products
275
Implementation lanes visible to ops
Active risks
141
Funding, payroll, merchant, and treasury gaps
Manager reviews
40
Pricing, waiver, or exception owners

Switch Pipeline

Ranked by expected deposits and switch risk so managers can see where a relationship may open, stall, or fail to fund.

Top switch PDF

Switch Readiness Score

How hard will this relationship be to move?
48/100
Southwest Arkansas Surgical Supply is a complex switch relationship: 48/100 readiness with 52/100 modeled move difficulty.
Treasury complexity
7 lanes
Estimated signers
3
ACH / wire volume
$205K
Move difficulty
52/100
Treasury complexity
7 implementation lanes
Multiple payment, fraud, liquidity, or settlement services may need parallel setup.
Existing lender / credit relationship
Not signaled
No lender handoff is visible from the current action.
Payroll vendor or payroll routing
Needs migration plan
Payroll movement requires timing, prenotes, approval users, and parallel-run planning.
Merchant services / settlement
Not primary
No merchant settlement dependency is visible from the current signal.
Number of signers
3 estimated signers
Signer count is modeled from relationship size, source type, role, and business complexity.
Estimated deposits
$603K
Larger balances usually require pricing discipline, liquidity structure, and manager visibility.
ACH / wire volume
$205K monthly modeled volume
Payment volume drives setup work, approval controls, and treasury operations coordination.
Source and contact confidence
Demo; Internal relationship
Better source proof and allowed contact channels reduce first-call and handoff risk.

Customer Switch Packet

Riverstone Community Bank switch plan for Southwest Arkansas Surgical Supply. Banker sends this after discovery so the customer sees what the bank handles, what the customer provides, and the timeline.

Download branded PDF
This switch packet is a relationship-service planning aid. It is not a credit offer, rate quote, mortgage preapproval, or guarantee of product availability. Final services, pricing, limits, and approvals follow normal bank review.

Treasury Implementation Plan

ACH origination
Treasury Ops - target day 5
Required
Confirm payroll, vendor-payment, and recurring receivable volumes plus authorization users.
Prepare ACH agreement, exposure limit review, originator setup, and file-transmission testing.
Remote deposit capture
Treasury Ops - target day 7
Required
Confirm check volume, deposit locations, scanner needs, and who will approve deposits.
Order or assign scanner, configure user entitlements, and schedule first-deposit test.
Positive pay
Treasury Ops - target day 10
Required
Confirm check issuance process, payee-positive-pay need, and exception decision users.
Set file format, exception cutoff, dual-control users, and first exception review.
Wires
Treasury Ops - target day 8
Required
Confirm wire volume, beneficiaries, approval workflow, callbacks, and dual-control users.
Configure wire limits, approval authorities, callback rules, and user entitlements.
Sweep / ICS / CDARS
Manager - target day 4
Required
Confirm target operating balance, liquidity needs, insurance preferences, and rate sensitivity.
Review liquidity structure, pricing discipline, sweep parameters, and ICS/CDARS eligibility.
Merchant settlement
Treasury Ops - target day 12
Watch
Confirm processor, settlement account, batch timing, chargeback process, and statement contact.
Coordinate merchant boarding or settlement-account change and verify first settled batch.
Payroll routing
Treasury Ops - target day 14
Required
Confirm payroll provider, pay dates, funding account, prenote requirements, and approval users.
Build payroll conversion timeline with parallel run, funding verification, and post-payroll check.
Fraud controls
Treasury Ops - target day 9
Required
Confirm who approves payments, who releases files, and where fraud losses or near misses have occurred.
Bundle positive pay, ACH filters, dual control, wire callbacks, limits, and exception reporting.

Banker + Ops Task Board

Banker
Confirm decision makers and switching trigger
Day 0
Validate 3 modeled signers, current account routine, and why the relationship should move now.
Send customer switch packet
Day 1
Send the branded packet after discovery and record products proposed for ROI attribution.
Record won value and attribution
Day 14
Track expected deposits, actual balances, products activated, loans/referrals, and source attribution back to Core Intelligence.
Treasury Ops
Open treasury implementation lane
Day 2
7 required products: ACH origination, Remote deposit capture, Positive pay, Wires, Sweep / ICS / CDARS, Payroll routing, Fraud controls.
Schedule first-file and first-settlement tests
Day 7
Confirm ACH, RDC, positive pay, wire, merchant, payroll, and fraud-control tests before declaring the switch complete.
Branch / Platform
Prepare operating account opening
Day 3
Collect signer documentation, entity documents, beneficial ownership details, online access, and debit/card needs.
Manager
Review pricing, fee waiver, or referral split
Day 1
Manager review required before pricing exceptions, treasury fee waivers, or split attribution are discussed externally.

Conversion Risk Alerts

Payroll not moved after 14 days.
Payroll is in the required implementation plan; conversion is incomplete until payroll funding or routing is verified.
Active P1
Owner: Treasury Ops. Day 14. Next: Confirm provider, next pay date, funding account, prenote requirements, and parallel-run owner.
Merchant settlement still going to prior bank.
Merchant need is not confirmed, but settlement should be asked in discovery.
Watch P2
Owner: Treasury Ops. Day 12. Next: Collect processor statement, settlement-account instructions, and first-batch verification date.
Deposits opened but treasury not activated.
A funded account without treasury activation leaves the relationship vulnerable and under-attributed.
Active P0
Owner: Banker. Day 10. Next: Hold a banker and treasury ops checkpoint before calling the relationship fully converted.
High-value relationship stalled before funding.
$603K expected deposits are modeled; unfunded openings should escalate before the relationship cools.
Active P0
Owner: Manager. Day 7. Next: Escalate to manager, confirm opening deposit date, and document blocker in CRM.

Won Relationship Value Tracking

Expected deposits
$603K
Actual balances
$277K
Fee income activated
$3K
Products sold
2/7
Funding variance
-$326K
Loans/referrals opened
0 of $0 potential
Tracking status
Needs funding follow-up
Source attribution
Sanitized core relationship extract - Bank-owned internal data - Demo

Owner Accountability

Morgan Avery
20 switch plans
50/100 readiness
$14M
Jordan Lee
10 switch plans
44/100 readiness
$7M
Priya Nair
6 switch plans
48/100 readiness
$3.9M
Alex Chen
4 switch plans
59/100 readiness
$2.7M

Compliance Guardrails

This switch kit is a relationship-service workflow, not a credit decision, rate quote, or product guarantee.
Do not imply the bank knows a private competitor relationship unless a sourced record explicitly proves it.
Customer-facing packet language stays operational: what the bank will handle, what the customer provides, and the timeline.
Account numbers are never stored in DepositLeads; internal attribution should use hashed identifiers only.