On a Thursday in late April a corporate banker at a Johannesburg lender sat down to her Monday-morning weekly client review and noticed, two slides in, that one of her largest accounts had moved nine hundred million rand of operational cash offshore three days earlier. She had not known. The treasurer of the client, who is paid to move cash, had not told her. The bank's correspondent system had registered the wire on the day. The CRM had not surfaced it, because the CRM had been built to remind her about her weekly review, not to interrupt her week.
She missed a meaningful conversation. The next quarter, her client moved the corresponding lending mandate to a competitor that had — pointedly — called the same day.
The CRM was built for periodic. CIB is continuous.
The CRM is a triumph of 1990s software engineering. Tom Siebel built the original Siebel Systems to give salespeople a place to record their calls, their next steps, and their pipeline status. That mental model — sales as a sequence of recorded interactions, reviewed weekly, summarised quarterly — was correct for the kind of selling Siebel was watching: enterprise software to enterprise IT departments, long cycles, predictable cadences, planned activity.
It is wrong for the kind of selling Corporate and Investment Banking now is. CIB is not a sequence of recorded interactions. CIB is a continuous flow of signals that, taken together, describe a relationship the banker is responsible for stewarding. The signals are interruptions, not entries. The relevant cadence is the cadence of the client's economic life, not the calendar of the banker's review meetings.
“In CIB, the second product wins the third. The signal that something is the right conversation does not arrive on Monday morning.”
What a Coverage Console actually is
What CIB needs is not a better CRM. It needs a Coverage Console. A Coverage Console is a single screen, per client, that brings together every signal the bank already has access to — wires, drawdowns, market trades, rating actions, news, network moves — and ranks them by what the banker needs to do about them, today.
- One screen per client, refreshed in real time
- Signals across Markets, Lending, Advisory and Transactional, ranked by materiality
- Recommended next-best-action, scored and explained, with talking points and a playbook attached
- Audit trail of every outreach, every approval, every decision
- Cross-coverage visibility for credit, risk and product teams so nothing is news to the people downstream
The Coverage Console does not replace the CRM. The CRM remains the system of record for accounts, contacts, opportunities. The Coverage Console replaces the CRM as the daily workflow surface for the coverage banker. The relationship moves from a folder you open on Monday to a live screen that interrupts you when something matters.
The four signals every relationship business needs to ingest
A bank cannot run a Coverage Console design that ignores the structural difference between a B2C relationship and a B2B relationship. A B2C relationship is high-volume, low-decision-count: most customers do not need a banker to be paying attention this week. A B2B relationship is low-volume, high-decision-count: every CIB client is producing material events most weeks of the year.
- Financial signals — drawdowns, repayments, hedging activity, FX flow, cash position movements, salary runs, large payments, treasury anomalies
- Relationship signals — board changes, named officer changes, deal activity, M&A pipeline, advisory engagements, new mandates lost or won at the periphery
- Market signals — credit-rating actions, peer-set moves, sector announcements, regulatory actions, sanctioned-party adjacency
- External signals — adverse media, named-officer adverse media, regulator filings, supplier and customer concentration changes, geopolitical exposure
A Coverage Console worth the name ingests all four. A CRM, in the conventional sense, ingests none of them — or ingests them as line items in a feed nobody reads.
What banks already have but cannot use
The frustrating truth of CIB is that the signals are already in the bank. The wire system knows about the wire. The credit risk system knows about the drawdown. The market data feed knows about the rating action. The compliance system knows about the adverse-media match. What is missing is the layer that fuses these into one client view and routes the relevant interruption to the right named owner with a recommended action and an SLA.
Banks have for two decades treated this as a data-warehouse problem. Build a data lake, run analytics, render a dashboard. The dashboard tells the banker what happened last week. It does not interrupt her with what happened this morning. The relevant time horizon for a Coverage Console is the time horizon of an event — minutes, sometimes hours. The relevant time horizon for a data-warehouse refresh is overnight.
The audit trail problem
There is a regulatory reason the conventional CRM is unsuitable. Banks operate inside a compliance perimeter that makes the line "the banker called the client" an event that must be logged, the call sometimes recorded, the substance summarised in writing, and the entire trail produced on demand for the regulator, internal audit, or — in the worst case — a subject-access request. A Coverage Console worth its keep must log every signal it raised, every recommendation it made, every action the banker took or did not take, and every outreach that flowed downstream. Without that audit trail the Coverage Console is a productivity tool that the compliance officer will, properly, refuse to certify.
This is non-trivial. The audit trail must be immutable, attributable and explainable. The model that scored "this client is at risk of moving its treasury mandate" must be willing to produce, at any moment, the signals and weights behind the score. Black boxes do not survive a compliance review.
Build, buy, or fold
The build-or-buy decision is genuinely hard. Building takes 18 months, a credit committee that understands what a coverage system is, and the political capital to deprecate the CRM as the daily workflow surface. Buying — even from one of the small number of vendors that have purpose-built coverage consoles for the CIB segment — exposes the bank to vendor lock-in on a workflow that touches every banker, every client and every regulatory disclosure.
The third option, folding, is the option most banks are exercising by default. They are not building a Coverage Console. They are not buying one. They are continuing to operate the CRM the way they always have, while quietly losing relationship economics to competitors that are running an early version of the right workflow.
“Every relationship business has the data. The question is whether it interrupts the banker when it matters, or files itself on the dashboard nobody opens.”
In ten years' time the conventional CRM will be remembered the way we now remember the contact-book on the receptionist's desk. The relationship-management profession will be operating on a console, not a calendar. The banks that built the console first will own the deepest client relationships of the next decade. The banks that watched will be the banks the agentic-commerce era will, with a certain symmetry, leave behind.