Retail Council
Retail banking strategy and operations
- 1.
**The council should now govern Mantl as an implementation path, not a vendor debate.** The strongest current signal is a pending Mantl contract and an Aug. 11 implementation-timeline meeting. The useful conversation is owner, bank-side critical path, 3.5-4 week UAT, go-live range, support model, and first-90-day measures.
- 2.
**Bottle Rocket must stay in its lane: experience definition, not a second account-opening engine.** Aug. 13 SteerCo and Aug. 14 final readout created expectation risk. The clean line is: Mantl opens and funds accounts; Bottle Rocket defines the customer and employee experience; no build SOW without scope, cost band, kill criteria, and a sequencing page.
- 3.
**Salesforce trust is now a Retail issue.** Regional Bank Council and Salesforce prep kept returning to field confidence, owner clarity, and release lead times. A 1776 campaign into a frustrated banker base would harden resistance rather than deepen relationships.
- 4.
**Enlight/Mesh is still a proved-versus-not-proved gate.** The acceleration thesis may reduce ambiguity and speed handoff, but the open gates remain production-code readiness, non-functional requirements, SOC 2 coverage, tech-lead confidence, and staffing decisions. Do not let contractor reductions outrun validation.
- 5.
**Retail still lacks the single operating scorecard it needs.** Useful fragments exist: 8-minute median account-opening speed in Enlight, turnover improvement from 38.0% to 34.7%, maintenance pilot turnaround around 12 minutes versus up to two days, and industry deposit growth context at 4.5%. The gap is one trusted view of open, fund, activate, support, deepen.
- ›Enlight median speed to open an account: about **8 minutes**, versus a prior **15-minute** target.
- ›Retail turnover improved from **38.0% to 34.7%** in recent prep.
- ›Maintenance pilot timing cited around **12 minutes** versus up to **two days** previously.
- ›Industry deposit growth context in the Aug. 13 FUB intelligence brief: annual deposit growth around **4.5%** in Q4 2025, near the 2011-2019 CAGR of **4.7%**. This is industry context, not FUB performance.
- ›Community Bank presidents were previously cited as holding approval authority in roughly **98.9%** of treasury exception cases, but the current packet did not recover a fresh update.
- ›new-account openings versus target
- ›online versus Community Bank opening mix
- ›abandonment by OAO step
- ›funded-account conversion
- ›activation quality in the first 30 days
- ›NIB mix and quality by market
- ›treasury attachment within 30 days
- ›referral conversion from lending into retail and treasury
- ›customer-care contacts per new account
- ›Mantl contract was pending approval in the Aug. 10 internal reporting scan.
- ›Mantl/FUB implementation timeline was on the Aug. 11 calendar.
- ›Previous packet frame still holds unless reversed: Consumer first, Business second, kickoff around Labor Day, Consumer target around Thanksgiving, Business before the annual meeting, and employee-assisted opening in scope.
- ›UAT should be treated as **3.5-4 weeks**, not compressed to the vendor default without FUB-specific risk review.
- ›Aug. 13 SteerCo and Aug. 14 readout should not become implied build authorization.
- ›The account-opening engine must stay clear: Mantl opens and funds; Bottle Rocket clarifies journey, experience, and handoff.
- ›Before any follow-on spend, require: named owner, scope, cost band, out-of-scope list, kill criteria, and a sequencing page across Mantl, Enlight, Bottle Rocket, Salesforce servicing, Q2/Gro sunset, Customer Care, training, marketing, and compliance.
- ›Salesforce is the customer-relationship layer, not a document-heavy workflow engine.
- ›The field needs top five 90-day priorities, single owners, release lead times that LOBs can train against, and Banking-owned communications.
- ›Open seats and owner gaps remain in the Salesforce/SLWE operating model.
- ›Case & Complaint redesign has four vendor RFP responses pending decision.
- ›The 1776 campaign should not be pushed harder until servicing and pipeline trust are visibly ready.
- ›Mantl reduces opening friction.
- ›Enlight reduces maintenance friction.
- ›Salesforce should support next-best relationship motion and follow-up.
- ›Customer Care has to support employee-assisted and digital-originated customers without orphaning the relationship.
- ›Treasury and lending referral tracking determine whether small-business relationships deepen or stall.
- ›Can a customer open digitally and still be connected cleanly to a Community Banker?
- ›Can Customer Care answer status and support questions without swivel-chair work?
- ›Can the Community Bank see what happened, who owns the follow-up, and whether funding/activation occurred?
- ›Can Retail tell after 90 days whether the relationship deepened?
- ›Mesh may accelerate design, workflow definition, UI artifacts, endpoint documentation, test artifacts, and handoff packages.
- ›That does not by itself prove production-code readiness.
- ›August governance should distinguish what was proved from what was not proved.
- ›production-code quality
- ›non-functional requirements
- ›SOC 2 coverage for Studio components
- ›key tech-lead confidence
- ›impact on Enlight architecture and delivery
- ›contractor-reduction sequencing
- ›December 2026 core development / February 2027 deployment assumptions
- ›open the relationship cleanly
- ›maintain it without customer-visible confusion
- ›deepen it with timely lending, treasury, and service follow-up
- ›make Community Bank teams more relational and less administrative
- 1.**Mantl operating owner and control plan.** Name owner, dates, UAT assumption, go-live range, support model, and first-90-day metrics.
- 2.**Bottle Rocket disposition.** Confirm experience-layer role and block any build SOW until scope, cost band, sequencing page, and kill criteria are written.
- 3.**Salesforce/1776 readiness.** Decide whether 1776 proceeds, narrows, or pauses based on field trust, servicing readiness, and owner clarity.
- 4.**Enlight/Mesh governance gate.** Separate demo proof from production proof before staffing or date assumptions change.
- 5.**Retail operating scorecard.** Require one scorecard across open, fund, activate, support, deepen, NIB quality, referrals, and treasury attachment.
- 6.**Opening-to-activation owner.** Name one accountable owner for the customer journey after opening, spanning Retail, Customer Care, Community Bank follow-up, lending referrals, and treasury attachment.
- ›**Meeting cadence:** Aug. 13 Retail Council occurred; this Aug. 16 packet appears off-week/post-meeting. Next live event not recovered.
- ›**Mantl contract:** pending approval as of Aug. 10 digest; final signature not recovered.
- ›**Section 1033 flexibility:** Legal should review Mantl contract terms before signature given open-banking uncertainty.
- ›**Bottle Rocket expectation risk:** strong readout could accidentally reopen custom-build assumptions.
- ›**Salesforce trust:** 1776 into weak field confidence would damage adoption.
- ›**Case & Complaint redesign:** four vendor RFP responses were in hand as of Aug. 14 research digest; decision not recovered.
- ›**Enlight/Mesh validation:** contractor and date decisions should wait for gate evidence.
- ›**Scorecard gap:** current record still lacks aligned OAO abandonment, funded conversion, NIB quality, treasury attachment, referral conversion, and support-contact definitions.
- 1.Ask Layna/Jack to bring the Mantl control plan: owner, dates, UAT, launch range, support model, employee-assisted scope, and 90-day measures.
- 2.Ask the Bottle Rocket team for a one-page disposition: experience layer output, no-build assumptions, dependencies, cost band, and kill criteria.
- 3.Ask Salesforce/SLWE owners for a 1776 readiness call: proceed, narrow, or pause.
- 4.Ask the Enlight/Mesh team for a proved/not-proved gate summary before any staffing cuts.
- 5.Ask Albert/council owners to publish one Retail scorecard definition set.
- 6.Put opening-to-activation ownership on the next live Retail Council agenda.