满员 enrollment 但利润微薄，这其实是合同选择问题，只是披着运营的外衣。 数字健康公司面临的问题版本并不通用。成果风险被签署的速度快于公司能否判断自身能否承担——12个月测量窗口对上11个月销售周期，因此忽略风险收入分成的答案必然出错。分析必须从参与率和毛利率而非收入开始。
满员 enrollment 但利润微薄，这其实是合同选择问题，只是披着运营的外衣。 数字健康公司面临的问题版本并不通用。成果风险被签署的速度快于公司能否判断自身能否承担——12个月测量窗口对上11个月销售周期，因此忽略风险收入分成的答案必然出错。分析必须从参与率和毛利率而非收入开始。
当一家数字健康公司承载大量 enrolled 人群却仍显示微薄利润时，本能反应是检查交付运营。可能存在低效，但消除它无法解决问题，因为根源在上游：合同被接受时附带的风险收入分成，参与率和毛利率无法支撑。
这一模式在投资组合中反复出现。少数项目在成果测量后产生正贡献。更多合同消耗人力和平台容量，却产生低参与率和反复的客户流失，因此组织显得活跃而现金状况未改善。由于这些合同已占用测量和支持容量，更优质的风险共享安排无法加入。
因此纠正步骤是合同选择规则，而非生产力举措。一旦每项安排能按测量窗口后的预期贡献排序，大部分后续决策便直接得出。
数字健康运营商陷入此状态，是因为新风险协议在先前队列完成12个月成果周期前就被签署：销售势头填满日历，而公司仍缺乏数据判断哪种PMPM或成果条款能达到毛利率目标。
这三者同时出现才是标志。单独一个通常指向其他问题。
✓ 团队报告现有项目已满负荷，而月度现金提取仍必要，尽管报告的ARR存在。
✓ 财务无法在不委托一次性分析的情况下，识别哪些合同或成员队列产生正贡献。
✓ 领导层继续接受新风险条款，即便内部审查已标记低预期参与率或高流失风险。
通常会让情况更糟的做法。 扩大人员或平台容量以处理当前业务量，这只会放大低贡献合同的数量并扩大同样的错配。
It is for you if you run or finance a digital health company 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 Vantabridge Health, a sample company profile used for testing rather than a customer — $62M ARR, 340,000 enrolled members.
Excerpt from a real Percision run · Cost Reduction & Efficiency · sample company profile
The move. Convert 180 existing employer relationships into $11.7M incremental outcomes-contingent revenue by Month 24 without new-plan procurement.
The leak it closes. $6.5M device leakage reduced by shifting kit cost to employer opt-in, improving gross margin 7 points on employer cohort
The assumption it rests on. 180 employers accept outcomes-contingent terms at 45% at-risk share — the engine put the probability at 0.7.
| Investment required | $0.6–0.9M total (2 FTE employer specialists @ $180K fully loaded each × 18 months + $120K enablement tools) |
| Expected return | 13.0× on $0.9M investment ($11.7M incremental revenue by Month 24) |
| Revenue, year 1 | $3.9M incremental employer outcomes revenue |
| Revenue, year 2 | $11.7M cumulative incremental employer outcomes revenue |
| Revenue, year 3 | $18.5M cumulative if employer cohort grows 15% YoY |
| Exit criteria | Terminate move if employer conversion rate <25% by Month 12 OR if employer at-risk share demanded exceeds 50% OR if device-kit leakage reduction <10 points by Month 18. |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to 专有EFF方法论, one of 29 engagements the platform runs. For 数字健康公司 it works through at-risk revenue share, engagement rate, gross margin and logo churn, 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. Outcomes risk is being signed faster than the company can learn whether it can carry it — a 12-month measurement window against an 11-month sales cycle — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are at-risk revenue share, engagement rate, gross margin, 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 at-risk revenue share and engagement 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.
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 · ไทย · हिन्दी · עברית