问题忙碌却不盈利 › 金融科技

忙碌却不盈利
in 金融科技

高TPV和薄贡献利润率是产品组合问题,借贷已将7倍倍数的收入转为2倍倍数的收入。 金融科技公司更难处理,因为结构原因:借贷固定了损益表,将7倍倍数的收入转为2倍倍数的收入。任何可信方案都必须同时考虑混合费率和核销率,而这正是多数内部分析停滞之处,因为两者分属不同系统。

简短回答

高TPV和薄贡献利润率是产品组合问题,借贷已将7倍倍数的收入转为2倍倍数的收入。 金融科技公司更难处理,因为结构原因:借贷固定了损益表,将7倍倍数的收入转为2倍倍数的收入。任何可信方案都必须同时考虑混合费率和核销率,而这正是多数内部分析停滞之处,因为两者分属不同系统。

当TPV很大而贡献利润率仍低时,本能反应是审查运营成本。部分成本可以削减,但这改变不了结果,因为原因在上游:被接受的支付量和商户账户需要借贷,这把混合费率向下重置。

这一模式在各渠道重复出现。小部分商户细分或获客来源在核销后产生正贡献利润率。长尾量占用了仓库融资额度和运营资源,却几乎不贡献利润。由于低利润流量占据产能,高利润业务无法扩大——限制不是需求,而是额度已分配给错误组合。

纠正方法是基于渠道和商户类型的贡献利润率制定筛选规则,而非效率提升。一旦能按核销和获客成本后的净利润影响对每个TPV来源排序,接受或拒绝哪些量就成了机械决定。

金融科技运营商在TPV和商户数量上升而净收入与贡献利润率未上升时到达此点:更大比例的流量应用了借贷,混合费率下降,仓库融资增加却未对应提升利润。在改变接受量的组合前,任何新产品或市场扩张都解决不了。

如何判断这确实是你的问题

这三者同时出现才是标志。单独一个通常指向其他问题。

✓ TPV和商户数量增加,而贡献利润率持平或下降,仓库融资额度仍满额使用
✓ 识别哪些渠道或商户群组在上期产生正贡献利润率需要一次性分析,而非常规报告
✓ 拒绝任何类别量或商户感觉不可能,因为这会降低报告TPV,即便该量的贡献利润率为负

通常会让情况更糟的做法。 增加仓库融资额度或资本以容纳更多量,这只会扩大分配给低利润组合的额度,并在更大规模上重复相同的损益压缩。

Who this is for — and who it is not

It is for you if you run or finance a fintech and everyone is fully occupied and cash is tight. 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 Verrano Pay, a sample company profile used for testing rather than a customer — $84M net revenue, 28,000 merchants, $9.4B of payment volume.

Excerpt from a real Percision run · Customer Value Architecture · sample company profile

The move. Lift lending take-up from 14% to 22% while keeping charge-offs below 9.0% by leveraging the existing vertical integrations and $9.4B TPV dataset.

What the run committed to
Investment required$2.8-3.4M total (no new equity)
Expected returnIncremental lending revenue of $8.4-11.2M annually at 70% contribution margin yields 2.1-2.8× cash-on-cash return within 24 months on the $3.4M investment
Revenue, year 1$92-96M FY2026
Revenue, year 2$101-110M FY2027
Revenue, year 3$118-130M FY2028
Exit criteriaStrategy must be abandoned or pivoted if, within 12 months, (a) take-up has not reached 16% OR (b) charge-off has exceeded 8.7% for two consecutive quarters, OR (c) any one of the three platform partners terminates its integration agreement.

This is one move out of a full analysis. Read a complete report — every page, no email required.

引擎如何处理这个问题

This question routes to Proprietary EFF Methodology, one of 29 engagements the platform runs. For 金融科技公司 it works through blended take rate, charge-off rate, contribution margin and CAC by channel, 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.

人们关于此问题的常见提问

如何知道该停止承接哪些业务?

按真实约束单位的贡献排序——机时、计费小时、配送时段、平方英尺。不要按收入,也不要按毛利率百分比,这两者在产能受限时总会偏向错误业务。

拒绝业务会损害关系吗?

有时会,但通常比替代方案更便宜。实践中反映真实消耗的价格要么让账户盈利,要么让其转向竞争对手,这两种结果都优于现状。

这是定价问题还是效率问题?

测试一下:如果每笔业务零浪费完美执行,薄利的那部分会赚钱吗?答案是否,则是定价和筛选问题,任何效率计划都触及不到。

Is this different in fintech than in other industries?

Materially, yes. Lending fixed the P&L and converts revenue worth a 7x multiple into revenue worth a 2x multiple — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are blended take rate, charge-off rate, contribution margin, and an answer built on industry-general benchmarks will usually point at the wrong one first.

What data do I need before this analysis is worth running for a fintech?

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 blended take rate and charge-off rate. 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.

When is Percision the wrong tool?

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.

Does Percision replace a lawyer, tax advisor, auditor, or AI implementation team?

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 · ไทย · हिन्दी · עברית