问题 › 我们该收购竞争对手吗? › 银行与金融服务
收购失败多因整合而非价格,影响效率比率和资金成本的整合成本往往最难估算。 银行和金融服务机构面临的问题不同于通用版本。分支网络既是存款护城河也是成本难题,客户关系知识集中在即将退休的少数人手中,忽略效率比率的答案必然出错。分析必须从资金成本和每名银行家的获客成本出发,而非从收入开始。
收购失败多因整合而非价格,影响效率比率和资金成本的整合成本往往最难估算。 银行和金融服务机构面临的问题不同于通用版本。分支网络既是存款护城河也是成本难题,客户关系知识集中在即将退休的少数人手中,忽略效率比率的答案必然出错。分析必须从资金成本和每名银行家的获客成本出发,而非从收入开始。
收购竞争对手的理由通常建立在收入协同上,例如通过收购的存款基础扩大商业贷款,但这类收益最不可靠,也最慢实现。能改善效率比率的成本协同更可预测,实际金额通常小于模型假设。
决定结果的关键数字是整合成本——系统转换、掌握在即将退休少数人手中的客户关系知识、导致资金成本上升的客户流失,以及一年以上被分散的管理注意力。这笔成本常被省略,因为难以估算,且不在任何一方账上。
严谨版本会先问:具体得到什么,是无法用更低成本自建或外购的?例如增加商业贷款或存款基础。若收入协同全未实现,效率比率和资金成本会是什么样子。
这三者同时出现才是标志。单独一个通常指向其他问题。
✓ 理由依赖将存款交叉销售给收购的商业贷款客户
✓ 整合有描述,但未测算对效率比率的影响
✓ 收购部分动机是每名银行家获客已停滞
通常会让情况更糟的做法。 用能改善净息差的收入协同来评估交易,而这类协同通常来得晚、金额小于模型,或根本不出现。
It is for you if you run or finance a bank and the rationale leans on cross-selling to each other's customers. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.
It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Below is an excerpt from a real run of this analysis on 一家银行. It is a sample profile rather than a customer, and it is engine output translated from English — this is the format you get, on your own numbers.
The subject is Harborline Financial Group, a sample company profile used for testing rather than a customer — $3.1B commercial lending book, $410M of deposits.
Excerpt from a real Percision run · Customer Value Architecture · sample company profile
The move. Codify retiring relationship knowledge and modernize treasury services to extend the 36-48 month deposit franchise durability by 12-18 months while capturing $15M+ annual fee income.
The leak it closes. 18% profit-pool leakage to digital treasury platforms reduced to 10-12% through competitive UX; 61% digital account opening abandonment reduced to 25-30% through streamlined onboarding
The assumption it rests on. Digital treasury substitution stays ≤3% per year for next 36 months — the engine put the probability at 0.55.
| Investment required | $20-25M over three years — $2-3M codification project + $18-22M treasury platform build |
| Expected return | 208-260% over three years — $52M expected upside / $20-25M investment |
| Revenue, year 1 | $3-5M incremental fee income from treasury SaaS pilot with 50 commercial accounts |
| Revenue, year 2 | $8-12M incremental fee income from 200 commercial accounts plus commercial card float |
| Revenue, year 3 | $15-18M incremental fee income from 400 commercial accounts at 23% fee-to-revenue ratio |
| Exit criteria | Abandon if treasury SaaS pilot fails to retain 80% of 50 pilot accounts by Month 18 OR if 71% loan-to-deposit overlap falls below 60% by Month 24 |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Growth Portfolio Framework, one of 29 engagements the platform runs. For 银行和金融服务机构 it works through efficiency ratio, cost of funds, origination per banker and deposit concentration, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.
You watch the analysis get built before paying anything. 在此阅读完整报告 if you would rather see the depth first.
估值两次:一次是独立价值,一次是对你具体价值。两者差额是你能支付并仍创造价值的上限,通常比预期更窄。
成本协同更可靠得多。它们在你控制范围内,可以排期。收入协同取决于客户按模型行事,这是最常出错的假设。
整合消耗的管理注意力超出预算,导致两家企业在交易本该回本的期间都表现不佳。
Materially, yes. The branch network is simultaneously the deposit moat and the cost problem — and the relationship knowledge sits in six people close to retirement — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are efficiency ratio, cost of funds, origination per banker, and an answer built on industry-general benchmarks will usually point at the wrong one first.
Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on efficiency ratio and cost of funds. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.
Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.
English · Español · Deutsch · Português · Français · Italiano · Nederlands · 日本語 · 한국어 · 中文 · Polski · Svenska · Türkçe · العربية · Tiếng Việt · ไทย · हिन्दी · עברית