Problems › Our Sales Cycle Is Too Long › HealthTech & Digital Health
Long cycles are usually the operator failing to show the CFO that at-risk share will hold after the measurement window, not the seller failing to explain the product. What makes this harder for digital health companies is structural: 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. Any credible answer therefore has to hold at-risk revenue share and engagement rate in the same view, which is exactly where most internal analysis stops because the two live in different systems.
Long cycles are usually the operator failing to show the CFO that at-risk share will hold after the measurement window, not the seller failing to explain the product. What makes this harder for digital health companies is structural: 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. Any credible answer therefore has to hold at-risk revenue share and engagement rate in the same view, which is exactly where most internal analysis stops because the two live in different systems.
A cycle that runs long is rarely stalled on interest in the platform. It is stalled at the stage where the operator must justify the at-risk revenue share to the CFO or CEO who was never in the room, using only the engagement rate and attributed outcomes data collected so far.
Which reframes the fix. Shortening the cycle is mostly a matter of giving the champion the material to win the internal argument on PMPM, the risk that gross margin will compress if engagement rate falls, and the comparison of attributed outcomes against continued logo churn.
The other frequent cause is selling to a clinical or operations lead who cannot authorise the at-risk share. That does not lengthen the visible cycle so much as add a hidden one at the end while the deal waits for CFO review.
These three together are the signature. One on its own usually points somewhere else.
✓ Deals consistently stall after the pilot once engagement rate data must be turned into an at-risk share model
✓ Forecast dates slip repeatedly on the same opportunities while the CFO reviews PMPM and gross margin projections
✓ The main competitor in lost deals is no decision, visible as continued logo churn on the enrolled member base
The move that usually makes it worse. Adding follow-up activity, which increases pressure on the champion without giving them new material on attributed outcomes or PMPM to take to the CFO.
It is for you if you run or finance a digital health company and deals consistently stall at the same stage. 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 a digital health company. It is a sample profile rather than a customer, and it is unedited engine output — 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 · Competitive Positioning · sample company profile
The move. Monetize the largest three-condition outcomes dataset to subsidize outcomes risk and generate 13% growth without increasing at-risk share.
The leak it closes. Reduces dependence on 38% at-risk PMPM revenue by adding non-at-risk, high-margin revenue stream
The assumption it rests on. State privacy laws do not mandate patient-level consent for de-identified data before 2029 — the engine put the probability at 0.7.
| Investment required | $1.8–2.4M over 18 months |
| Expected return | 2.3–3.8× on $2.1M midpoint investment within 36 months |
| Revenue, year 1 | $0.8–1.2M ARR (3–4 deals) |
| Revenue, year 2 | $2.4–3.6M ARR (9–12 deals) |
| Revenue, year 3 | $4.2–6.8M ARR (15–20 deals) |
| Exit criteria | Kill move if fewer than 2 deals ≥$150k ACV close by Month 12 OR if any state privacy statute requiring patient-level consent for de-identified data is enacted before Month 18; reallocate remaining budget to Clinical Coaching Capacity Marketplace node |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Go-to-Market & Commercial Strategy, one of 29 engagements the platform runs. For digital health companies 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. Read a complete report here if you would rather see the depth first.
Find the stage where deals sit longest and work out what the buyer has to do there. It is almost always an internal approval, and the fix is material rather than persuasion.
It compresses the last step and does nothing to the stalls earlier in the cycle, which is where the time actually goes. It also teaches buyers that waiting is rewarded.
No, if the deal size and win rate justify it. It becomes a problem when the cycle is longer than your cash conversion allows, which is a financing constraint rather than a sales one.
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 · ไทย · हिन्दी · עברית