问题 › 我们不知道哪些产品能赚钱 › 专业服务
每家专业服务公司都有合伙人认为盈利的服务线,而通常正是这条线在通过合伙人薪酬被补贴。 对专业服务公司来说,这体现在特定地方。承载答案的数字是可计费利用率和实现率,而该行业的特定复杂性在于,合伙人薪酬理性地支付人们<em>不</em>去销售公司中最高利润率的产品。这个问题的通用版本和你实际所处的版本,第一步行动不同。
每家专业服务公司都有合伙人认为盈利的服务线,而通常正是这条线在通过合伙人薪酬被补贴。 对专业服务公司来说,这体现在特定地方。承载答案的数字是可计费利用率和实现率,而该行业的特定复杂性在于,合伙人薪酬理性地支付人们不去销售公司中最高利润率的产品。这个问题的通用版本和你实际所处的版本,第一步行动不同。
项目级利润率确实难算,因为多数成本如非计费时间和闲置人力是共用的,按每合伙人收入比例分摊通常会直接把答案定死。这种分摊让高收入项目显得成本高、低收入项目显得高效,而实际情况往往相反——低收入工作消耗了不成比例的合伙人杠杆和实现努力。
可行的做法只追踪能直接归属到项目的成本,如直接人力成本,其余不做分摊。这样就能得出服务线的贡献额,以及一个诚实的共享成本池(含利用率拖累),比没人相信的全成本吸收数字有用得多。
结果通常不舒服。大多数组合里,少数服务线撑起整个公司,至少有一条长期存在的线已亏损多年,而合伙人仍以为它在赚钱,因为薪酬奖励的是利用率而非项目利润率。
这三者同时出现才是标志。单独一个通常指向其他问题。
✓ 利用率只报公司整体目标,没有按服务线拆分
✓ 尽管部分业务存在持续闲置,仍未终止任何服务线
✓ 两位合伙人对同一类项目的实现率说法不一致
通常会让情况更糟的做法。 用任意的合伙人杠杆比率把所有间接成本全部分摊到每个项目,得出一个建立在任意规则上的精确利润率,还因为它与薪酬模型吻合而被捍卫。
It is for you if you run or finance a professional services firm and product profitability is quoted as a company-wide gross margin. 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 Aldergate Partners, a sample company profile used for testing rather than a customer — $88M revenue, 310 people.
Excerpt from a real Percision run · Competitive Positioning · sample company profile
The move. Re-align partner economics so the $85K diagnostic becomes the highest-compensated path to the $410K implementation.
The leak it closes. Partner-level incentive leakage that currently diverts 25% of diagnostic-eligible opportunities back to T&M work
The assumption it rests on. 15-of-22 partners approve compensation redesign within 60 days — the engine put the probability at 0.7.
| Investment required | $700K total over 36 months — $200K annual incentive pool × 3 years + $100K legal and change-management cost |
| Expected return | 3.4× cash-on-cash over 36 months (NPV $2.4M / $700K investment) on $58.0M current revenue base |
| Revenue, year 1 | +$1.2M incremental diagnostic and implementation revenue (15 additional diagnostics × $85K + 12 conversions × $410K) |
| Revenue, year 2 | +$2.4M cumulative incremental revenue |
| Revenue, year 3 | +$3.7M cumulative incremental revenue |
| Exit criteria | Terminate this move and revert to legacy compensation if (a) fewer than 12-of-22 partners approve redesign by Day 60, or (b) any top-3 account issues an RFP within 90 days of announcement, or (c) diagnostic-to-implementation conversion falls below 10-of-19 by December 31, 2026. |
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 billable utilisation, realisation, revenue per partner and engagement gross margin, 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. Partner compensation rationally pays people not to sell the highest-margin product in the firm — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are billable utilisation, realisation, revenue per partner, 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 billable utilisation and realisation. 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 · ไทย · हिन्दी · עברית