By Appbay Technologies
A strategic pivot needs its own evidence, not just its own slogan.
A bank has explicitly repositioned itself – moving “from a focus on transactions to a focus on relationships.” That’s a genuinely thoughtful strategic statement. But the strategy statement changed. The metrics measuring success mostly haven’t caught up yet.
This piece is a bit different from our usual ones – the fit here is real but partial, and we’d rather say that plainly than oversell it.
The Priority: A Genuine Pivot, Distinctly Stated
Repositioning “from a focus on transactions to a focus on relationships” is an unusually specific and quotable strategic statement – most banks don’t state this pivot this explicitly. It signals real intent to build long-term trust by blending digital innovation with human engagement, rather than optimizing purely for transaction throughput.
But a repositioning like this creates its own quiet operational question: how do you actually measure something as structurally different from transaction volume as relationship quality?
The Hidden Problem: One Thing Easy to Count, One Thing Almost Invisible
Here’s where the operational gap actually shows up, inside most banks making this exact pivot:
- Transaction metrics still default – existing systems keep counting what they were originally built to count
- Relationship touchpoints uncaptured – a proactive call, an unprompted check-in, advice given without a sale attached, none of it shows up anywhere
- RMs tracking activity manually – relationship managers often keep their own informal records, because the system doesn’t
- Strategy ahead of the system – the mission statement changed well before the underlying metrics did
Why does this exist? The bank’s own stated pivot – from transactions to relationships – means existing metrics and workflows built around transaction processing don’t automatically translate into relationship-tracking metrics. Measuring and operationalizing “relationship” quality is structurally harder than measuring transaction volume, because relationship-building activity happens across both digital and human-engagement channels that were never designed to report into one shared view.
Why This Matters Now
This specific repositioning is named as the top strategic priority, at board level. That means the pivot isn’t a background initiative – it’s the headline the board expects to see substantiated with evidence, not just repeated in the next strategy deck.
The board’s question isn’t whether the repositioning sounds right. It’s sharper than that:
“Where does relationship depth actually show up, other than in the mission statement?”
For the Chief Customer Officer or Head of Retail Banking, this plays out as a live measurement problem, tracked against metrics that mostly don’t exist yet:
- Relationship activity, tracked – is proactive engagement actually being logged anywhere?
- Engagement consistency over time – is relationship-building happening steadily, or only when someone remembers to note it down?
- Retention tied to relationship depth – can the bank actually connect relationship activity to customer outcomes?
A strategic repositioning needs its own evidence, not just its own slogan.
An Honest Look at the Fit
We’d rather be direct here than force a confident pitch. This is a genuinely harder fit than most of what we cover. “Relationship tracking” is a CRM-adjacent problem, and Appbay’s core strength sits in regulated operational workflows – AML, KYC, lending, compliance. That’s not where this problem naturally lives.
Where there is a real, honest fit: our Multi-Perspective Document Insight Copilot can genuinely help consolidate cross-channel interaction history into something a relationship manager can actually act on. Beyond that, a proper relationship-activity tracking workflow would be a new build, not a configuration of something that already exists.
Here’s what that build would actually involve, in principle:
1. Interaction Ingestion, Any Channel
Digital and human-engagement touchpoints captured in one place – not scattered across separate systems and personal notes.
2. AI-Driven Summarization Across Touchpoints
Consolidating interaction history so a proactive call or an unprompted check-in doesn’t just disappear once it’s happened.
3. Relationship Activity Log
A record that credits advisory conversations and check-ins – not just the transactions that happen to follow them.
4. RM Follow-Up Task Management
Prompting the next relationship-building step, not just the next sale opportunity.
5. Appian-Orchestrated Workflow and Reporting
One governed process tying activity to outcomes over time, so relationship depth becomes something reportable, not anecdotal.
This is worth an honest conversation about scope before committing to a fixed timeline. It’s a genuine build, not a quick proof of concept on an existing product.
Why We’re Saying This Plainly
Being upfront here matters more than a confident pitch would. Banks making this exact pivot deserve a straight answer about what “measuring relationships” actually requires – not a vendor claiming a plug-and-play tool already solves it. The operational problem is real and worth solving. The honest starting point is acknowledging what kind of build that actually is.
This Pattern Isn’t Unique to One Bank
Any institution making a genuine pivot from transaction-focused to relationship-focused banking will hit the same gap: the systems measuring success were built for the old model, and the new one needs its own evidence, not borrowed metrics. The banks getting ahead of this aren’t assuming a vendor has a plug-and-play answer. They’re having the honest conversation about what measuring relationships actually requires.
Let’s Compare Notes
We’re curious how other banks making this exact pivot – transactions to relationships – are actually measuring it. If your organization is navigating a similar repositioning, we’d welcome the conversation.
Send us a message – this one’s genuinely about comparing notes, not a pitch.
