The Cost of Onboarding Drop-Off Is Four Different Bills

The number in the business case

Most banks that ask about the financial impact of onboarding drop-off already have a figure. It is built the same way almost everywhere. Take the applications that started and did not become funded accounts, multiply them by the average annual revenue of a funded customer, and present the product as revenue the bank is leaving on the table. The figure is usually large, it is easy to explain, and it is the opening slide of most onboarding redesign proposals.

The figure is large enough to fund a project and too blunt to tell the project where to aim. It answers whether drop-off matters. It says nothing about which drop-off matters, and that is the question the money is about to be spent on.

Why one multiplier misleads

The single multiplier rests on four assumptions, and none of them survives contact with a traced month of applications. It assumes every lost applicant would have been an average customer. It assumes every lost applicant was lost for good. It ignores what the bank had already spent on each of them before they left. And it treats every applicant the bank turned away as a loss, including the ones it was right to turn away. The first two inflate the figure. The last two distort it in ways that can make it too small exactly where it matters most.

Four groups, four bills

Applicants leave digital account opening in four broad ways, which we set out in why banks lose applicants where the funnel stops looking. Each one costs the bank something different:

• applicants who decided to leave mid-flow cost the acquisition spend that brought them in, but only those who matched the customer the bank was trying to win represent lost revenue
• applicants who were interrupted and found an expired session are largely recoverable, and many reappear as new applicants, so the bank pays to acquire them twice and counts them twice in its own denominator
• applicants who submitted and then waited on the bank cost acquisition, verification fees and review time, and they were the most committed people in the whole flow
• applicants the bank declined split in two: correct declines are a saving the bank should be glad of, and wrong declines cost the full value of a customer who qualified

Read together, the list reverses the intuition behind most redesigns. The loss a redesign targets, the applicant who gives up on a screen, is the cheapest one per head. The costliest applicant to lose is the one who has already passed through every step the bank pays for. A referred applicant who gives up waiting for a document request has consumed marketing budget, a vendor check and an analyst's time, and leaves with nothing to show for any of it.

Four inputs per group

We start from the same traced month used to place each lost applicant in a group, and for each group we assemble four inputs:

• how many applicants it holds, from the trace itself
• what the bank had already spent on each of them, from media cost per application started, vendor fees per verification and minutes of manual review
• how likely each is to be recovered, from what happened to similar applicants who were contacted, or who returned on their own
• what each would have been worth if retained, taken from funded customers who resemble that group rather than from the book average

The last input carries most of the judgement. A bank's average customer is a blend of salaried current accounts, dormant savings and a small number of valuable relationships. The applicants who leave mid-flow after seeing a rate often resemble the dormant end of that blend. The applicants stuck in a referral queue often resemble the other end, because complex income and recent address changes are what trigger referral in the first place.

An average customer value applied to an unusual applicant is a guess with a decimal point.

Where the numbers live

None of these inputs sits in the digital team's analytics. Acquisition cost lives in marketing. Vendor fees live in procurement invoices. Review time lives in operations workforce data. Customer value by segment lives in finance. Assembling the four inputs means asking four functions for figures they have never been asked to join, and that request is itself half the diagnosis. It is the same cross-functional gap the cohort trace exposes, now expressed in money.

What the repricing showed

At the digital bank described in the earlier note, the original redesign case had priced every abandoned application at the full average value. Repriced by group, the mid-flow leavers shrank considerably: many had been comparing a savings rate and resembled the low-balance customers the bank already struggled to make profitable. The referral queue grew. Its applicants had been verified, paid for and were disproportionately the higher-income customers the bank wanted. The wrong declines were few, but each represented a qualified customer turned away by a rule written for a fraud pattern that had since faded.

The repair that followed cost far less than the redesign it replaced. A contact standard for referred applicants, a saved application that survived a closed browser, and a review of the address rule were each owned by a function that had not previously been in the onboarding meeting. The cheapest repairs addressed the most expensive losses, and the screen work moved to the back of the queue. The same instinct to fix the visible step rather than the upstream cause is traced in when to add headcount and when to fix the process.

The figure the board sees

A single headline figure invites a single fix. We report the financial impact as four lines, each with its own owner and its own recovery estimate, so the executive team can see which function holds which share of the loss. The total is usually smaller than the original business case claimed. The part of it that can actually be recovered is usually larger than anyone expected.

Where the method is weak

Recovery probabilities are estimates, and in a bank that has never contacted a stalled applicant there is little history to estimate from. We use first-year value rather than lifetime value, because lifetime figures carry assumptions about retention and pricing that no function has signed. Both choices make the result conservative. That is deliberate, because a figure the finance director will defend does more work than a larger one the finance director will not.

Our work on onboarding economics begins with the cohort trace and ends with a priced view of the loss, built from figures the bank already holds in four separate places. It usually changes which repair is funded first.

Our consulting engagements inside the diagnosis before solution pillar assemble those figures, assign each group of lost applicants an owner and sequence the recovery, and our training programmes teach product, operations, risk and finance teams to price a loss before they argue about how to fix it. The financial impact of onboarding drop-off is worth knowing only once it is split into the losses each function can act on.