By Appbay Technologies
Funding two channels at once isn’t a problem. Not knowing which one is actually working is.
A bank is expanding its branch and ATM network while also investing in digital transformation – two separate, parallel priorities, both funded in the same budget cycle. That’s a reasonable strategy. Two channel strategies, funded in parallel, with no single view of which one is actually earning its budget.
This piece is a candid one – the fit here is genuinely weaker than most of what we cover, and we’d rather say that plainly than force a confident pitch.
The Priority: Two Channels, Funded in Parallel
Naming branch/ATM expansion and digital transformation as separate, parallel priorities – rather than a “digital-first” strategy with physical branches as an afterthought – implies deliberate parallel investment. That’s a genuinely reasonable strategic choice on its own terms.
But it also invites an obvious board question: is one channel quietly cannibalizing the other’s ROI case? Investing in physical expansion and digital transformation simultaneously means proving both investments are paying off, on different and sometimes competing logic.
The Hidden Problem: Two Reports, No Shared View
Here’s where the operational gap actually shows up, inside most banks running parallel channel investment:
- Two channels, two reports – branch and digital performance live in entirely separate reporting structures
- No unified performance view – there’s no single dashboard showing how the two channels actually compare
- Teams justifying separate budgets – each channel’s team makes its own case, with no shared evidence to compare against
- Investment overlap, unmeasured – it’s genuinely unclear whether the two investments are complementary or competing
Why does this exist? Naming branch/ATM expansion and digital transformation as separate, parallel priorities implies deliberate parallel investment – which is exactly what makes the board’s comparison question so hard to answer without a shared view. Proving both investments are paying off requires comparing them on the same terms, and most banks simply don’t have a system built to do that yet.
Why This Matters Now
Both investments are funded in the same period, and the board currently has no shared data to judge either one against the other. This isn’t a hypothetical future concern – it’s the exact position the board is in right now, budget cycle after budget cycle.
The board’s question isn’t whether investing in both channels was reasonable. It’s sharper than that:
“Which channel is actually driving growth – and should next year’s budget follow that evidence?”
For the COO or Chief Digital Officer, this plays out as a live comparison problem, measured against metrics that don’t currently share a common view:
- Channel-attributed growth – which channel is actually responsible for customer growth?
- Cost-to-income by channel – is one channel’s cost structure clearly outperforming the other’s?
- Budget reallocation confidence – can next year’s budget decision actually be backed by evidence?
Funding two channels at once isn’t a problem. Not knowing which one is actually working is.
An Honest Look at the Fit
We want to say this plainly: this is the weakest product-fit case we’ve covered in this series. This sits closer to a business intelligence and reporting problem than a workflow automation one – and Appbay’s core strength is in regulated operational workflows like AML, KYC, and lending, not cross-channel performance analytics.
Where there’s a genuine, if partial, fit: our Multi-Perspective Document Insight Copilot can help produce audience-specific reporting once the underlying data exists in one place. But building an actual unified cross-channel performance view would mean a new reporting and analytics accelerator – something outside Appbay’s core case-management and compliance strength, not a configuration of an existing product.
Here’s what that would actually involve, in principle:
1. Cross-Channel Data Ingestion
Branch and digital performance data brought into one place, rather than living in two separate systems that never talk to each other.
2. AI-Assisted Performance Normalization
Making the two channels genuinely comparable on the same terms, not just co-located in the same report.
3. Cross-Channel Comparison
A real side-by-side view of growth, cost, and customer movement between the two channels.
4. Ops/Finance Review
People interpreting what the comparison actually means for next year’s budget decisions.
5. Appian-Orchestrated Reporting Workflow
One governed process producing the unified view on a repeatable basis, not a one-time analysis that goes stale immediately.
This is honestly a build, and a fairly involved one – worth a candid conversation about scope, not a quick proof-of-concept promise dressed up as a sure thing.
Why We’re Saying This Plainly
Being upfront matters more here than a confident pitch would. This particular measurement gap is real and worth solving, but it sits further from Appbay’s core operational-workflow strength than most of what we write about. The honest starting point is naming that clearly, rather than stretching an existing product to fit a problem it wasn’t built for.
This Pattern Isn’t Unique to One Bank
Any institution funding branch expansion and digital transformation as parallel, separately-justified priorities will eventually face the same board question: which one is actually earning its budget? The banks getting ahead of this aren’t assuming an existing tool already answers it. They’re being honest about what building a real answer would take.
Let’s Compare Notes
We’re working with banks across the GCC running parallel branch and digital investment – same question, which channel is actually earning its budget. If your organization is facing a similar measurement gap, we’d welcome the conversation.
Send us a message – this one’s genuinely about comparing notes, not a pitch.
