Lending Council
Lending platform strategy and transformation
- 1.
The key decision still is not "nCino or Newgen." It is whether the bank will anchor lending on a banker-first operating model, then force the platform choice to prove it can support that model.
- 2.
The June 26 KPMG close is now the main forcing function. If that deliverable does not produce a usable target operating model and process map, the bank will drift into August with no real basis for LTI scope.
- 3.
This week's strongest new signals are governance and timing signals, not new vendor proof: Ryan weekly and the LoanStart 1.5 / 2.0 roadmap discussion on Monday, June 22 create the right lane to align banker experience, fast-lane workflow, and interim architecture.
- 4.
The two hard-clock items are still unresolved: Precision Lender expires on July 15, 2026, and Case360 / LoanStart legacy urgency continues to narrow the room for indecision.
- 5.
Ryan's lens should remain the winning lens in the room: does the next step make bankers faster with customers? Drew's lens should translate that into specifics: what changes in workflow, document handling, handoffs, and booking.
- ›Lead with the operating model, not the vendor. The council should keep asking: what workflow makes a community banker faster in one customer sitting?
- ›nCino's recurring problem signal has not changed. The local evidence still describes a form-first flow that fits specialized lending teams better than FUB's universal-banker reality.
- ›LoanStart should not be romanticized just because nCino is weak. LoanStart still carries volume because it is faster for routine deals, but the long-term answer cannot be "keep the old path and patch around it.
- ›The best near-term posture is still to force the decision path, not the final decision:
- ›KPMG closes June 26
- ›executive review immediately after
- ›decision basis locked before August R2 scope pretends to be meaningful
- ›This remains the cleanest evidence stack in the file set. The strongest practical case is still banker-visible friction:
- ›customer-facing wait time
- ›relay-style handoffs
- ›duplicate entry
- ›document drag
- ›The design center remains Tom White's field reality: a straightforward deal should not trap a banker in thirty-plus minutes of visible system work while the customer waits.
- ›Ryan's likely question should be explicit: does the next move materially improve banker speed and confidence in front of the customer, or does it just move the same friction behind a different screen?
- ›The sunk-cost argument should lose. The right cost frame is forward cost to usable capability, not defense of prior spend.
- ›Three specific risk clusters matter most right now:
- ›decision-latency risk after KPMG closes
- ›coexistence / migration risk if the bank chooses a new platform path
- ›adoption risk if the future state still feels heavier than the informal workaround it replaces
- ›Precision Lender expiring on July 15 is now a near-term operational risk, not a background note.
- ›Case360 / legacy platform timing still narrows the path. The bank does not have unlimited time to keep architecture and operating-model questions separate.
- ›Lending is still the best test of whether transformation can translate field pain into a durable operating model instead of just another technology debate.
- ›The June 22 LoanStart architecture conversation is useful only if it clarifies the enterprise path. If it becomes a local optimization rabbit trail, it will consume attention without improving the council decision.
- ›The council should keep the sequence clean:
- ›business problem
- ›banker workflow
- ›decision / document / booking architecture
- ›platform choice
- 1.Confirm that the post-KPMG decision is about operating-model pattern first and vendor selection second.
- 2.Decide the exact review sequence after June 26: who reviews the KPMG output, on what date, and what recommendation is expected by mid-July.
- 3.Confirm whether the June 22 LoanStart 1.5 / 2.0 conversation is meant to inform the platform path or act as an interim workaround track.
- 4.Decide who owns the Precision Lender transition plan ahead of July 15.
- 5.Decide what evidence threshold is required to move from "Newgen is leading" to "this is the recommended path."
- ›No direct Ryan Suchala or Drew Stafford meeting-note artifact from the June 8-21 window was accessible locally in this run.
- ›No fresh local side-by-side TCO file was recovered for nCino vs. Newgen vs. OpenText / hybrid.
- ›The `ncino-migration` project note remains stale and unusable as a current status source.
- ›The strongest June 11-12 lending signals remain available through downstream synthesis, not direct transcript review in this run.
- ›This appears to be an off-week for the council cadence, but the June 26 KPMG close and July 15 Precision Lender expiry make this a useful forcing packet anyway.
- 1.Set the post-KPMG review now, with named attendees and a target recommendation date.
- 2.Use Monday's Ryan weekly plus LoanStart discussion to test one thing: what does the banker-first fast lane require regardless of vendor?
- 3.Pull direct Ryan and Drew notes or transcripts into the next packet so field and ops lenses are explicit, not inferred.
- 4.Replace the stale `ncino-migration` note with a current source-backed status page.
- 5.Keep every future council packet anchored to the same proof chain: banker workflow evidence, operating-model implications, and hard timing constraints.