问题我们应该提高价格吗? › 金融科技

我们应该提高价格吗?
in 金融科技

问题从来不是是否普遍提高抽成比例。而是针对哪些商户细分、哪些交易流、提高多少,以及预计会损失多少交易量和坏账率。 这对金融科技公司来说更难,因为结构性原因:借贷固定了损益表,将原本7倍市盈率的收入转化成了2倍市盈率的收入。因此任何可信的答案都必须同时考虑综合抽成率和坏账率,而这正是大多数内部分析停止的地方,因为这两者存在于不同系统中。

简短回答

问题从来不是是否普遍提高抽成比例。而是针对哪些商户细分、哪些交易流、提高多少,以及预计会损失多少交易量和坏账率。 这对金融科技公司来说更难,因为结构性原因:借贷固定了损益表,将原本7倍市盈率的收入转化成了2倍市盈率的收入。因此任何可信的答案都必须同时考虑综合抽成率和坏账率,而这正是大多数内部分析停止的地方,因为这两者存在于不同系统中。

抽成率是金融科技业务中对贡献毛利率最快的杠杆。它不需要新的TPV、不需要额外商户,也不需要改变仓储设施,效果在下一个账单周期就会显现。运营者仍避免触碰它,这就是为什么综合抽成率低于扣除坏账后的贡献毛利率所能支持的水平。

有用的抽成率审查不会只产出一个数字。它会按商户生成细分:哪些群体产生的TPV,其贡献毛利率超过按渠道计算的CAC成本;哪些群体已处于进一步提高费率就会引发替代或更高坏账率的位置;以及人工豁免显示定价是按交易逐笔设定而非按政策执行的地方。

任何有效的抽成率变动都会导致部分商户流失或减少TPV。如果一次费率调整没有带来交易量损失或坏账率变化,说明调整幅度相对于可用的贡献毛利率来说太小了。

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

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

✓ 几乎所有商户在首次报价的综合抽成率上签单,没有对条款进行谈判。
✓ 抽成率例外情况频繁出现,且因销售代表不同而变化,而非取决于商户经济情况或坏账历史。
✓ 公布的抽成率表保持不变,而按渠道的CAC和坏账率已经发生变化。

通常会让情况更糟的做法。 对所有商户和所有交易流应用相同的抽成率上调,这会减少原本在贡献毛利率上已处于边缘的商户的交易量,同时让更高毛利的商户保持低价。

Who this is for — and who it is not

It is for you if you run or finance a fintech and almost every deal closes, and closes quickly. 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 · Pricing Strategy · sample company profile

The move. Scale lending book from $110M to $260M advances using existing distribution and data assets while maintaining charge-off rate below 9.0% covenant.

The leak it closes. Reduces 26% partner rev-share leakage by increasing merchant stickiness through lending relationship

The assumption it rests on. Platform partners maintain 180-day termination clauses without exercising exit — the engine put the probability at 0.7.

What the run committed to
Investment required$0 incremental equity
Expected return4.5x
Revenue, year 1$24.1M lending revenue (30% growth)
Revenue, year 2$31.3M lending revenue (30% growth)
Revenue, year 3$40.7M lending revenue (30% growth)
Exit criteriaTerminate if charge-off rate exceeds 8.7% for two consecutive quarters OR if any platform partner terminates contract

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

引擎如何处理这个问题

This question routes to 定价与收入优化, 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 · ไทย · हिन्दी · עברית