Decision Memo

Recovery-percentile tracker for orthopedic surgery patients

Record the team verdict, rationale, and reviewer leans locally, then print or share a source-anchored memo.

Markdown export

Agent and email version.

# Decision Memo: Recovery-percentile tracker for orthopedic surgery patients

Full report: https://ideanavigatorai.com/ideas/post-surgery-progress-app/
Recorded: Not recorded

## Decision
- Team verdict: Park
- Validation verdict: Research (55/100)
- Confidence: 54%
- Recommendation: Keep this parked until the team has evidence for the next validation step: Recruit one orthopedic practice, have 15 knee-replacement patients log daily for two weeks, and measure whether tracked patients place fewer 'is this normal' calls than a comparison group.

## Team rationale
No team rationale recorded yet.

## Reviewers
- No named reviewers recorded.

## Source anchors
- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls
- Market: Orthopedic post-operative recovery tracking
- Problem: After orthopedic surgery, patients cannot tell whether their pain, swelling, and stiffness are normal, so they flood surgeon offices with 'is this normal?' calls while staff have no objective benchmark to reassure or escalate.
- Thesis: Recovery-percentile tracker for orthopedic surgery patients should be tested as a narrow first-win workflow for Orthopedic surgeon office staff fielding daily post-op patient calls.
- Source: https://www.aaos.org/
- Source: https://en.wikipedia.org/wiki/Range_of_motion

## Validation rubric
Rubric version: INAV-VALIDATION-2026-06-04

### Demand signal - 5.5/10 (24% weight)
Demand looks thin because the report has 2 source-backed signal(s), an editorial confidence of 54/100, and a defined buyer in Orthopedic post-operative recovery tracking.

- Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.
- Target buyer: Orthopedic surgeon office staff fielding daily post-op patient calls

### Problem severity - 6.3/10 (22% weight)
Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.

- After orthopedic surgery, patients cannot tell whether their pain, swelling, and stiffness are normal, so they flood surgeon offices with 'is this normal?' calls while staff have no objective benchmark to reassure or escalate.
- Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.

### Willingness to pay - 5/10 (20% weight)
Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

- Per-seat subscription billed to surgeon offices to cut call volume.
- Recruit one orthopedic practice, have 15 knee-replacement patients log daily for two weeks, and measure whether tracked patients place fewer 'is this normal' calls than a comparison group.

### Competitive saturation - 6.3/10 (18% weight)
No source-backed direct match is recorded yet, so saturation risk is treated as unknown rather than proof of novelty.

- Existing-product check has no named direct match.
- Competitive score rewards a narrow wedge, not absence of research.

### Feasibility - 4/10 (16% weight)
Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.

- Recruit one orthopedic practice, have 15 knee-replacement patients log daily for two weeks, and measure whether tracked patients place fewer 'is this normal' calls than a comparison group.
- Recovery-curve percentiles could be read as clinical advice, so the app must stay a tracking and journaling aid that supports rather than replaces the surgeon's care.

## Market gap
Underserved segments:
- Orthopedic surgeon office staff fielding daily post-op patient calls who still run the workflow in spreadsheets, generic docs, email, or chat threads.
- Small teams in Orthopedic post-operative recovery tracking that feel the pain weekly but are too narrow for broad incumbents.
- New adopters who need guided proof before committing to a larger platform.

Feature gaps:
- A narrow workflow that reaches value without configuration-heavy onboarding.
- A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
- A handoff path from manual concierge service to repeatable software.

Differentiation levers:
- Use specificity as the wedge: one buyer, one workflow, one measurable result.
- Show proof earlier than broad competitors with before-and-after examples and small pilot data.
- Keep implementation lighter than incumbent suites or generic AI assistants.

## Roast and risks
Interesting hypothesis, but it needs sharper demand evidence before build time.

Blind spots:
- Recovery-curve percentiles could be read as clinical advice, so the app must stay a tracking and journaling aid that supports rather than replaces the surgeon's care.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
- The first release can become a generic dashboard if the job is not named tightly.

Hard questions:
- Who wakes up already trying to solve this?
- What do they stop paying for or stop doing when this works?
- What proof would make a skeptical buyer trust it in one screen?
- What is the smallest paid version of this idea?

## Kill criteria
- Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
- No buyer can name a current cost in time, money, risk, or reputation.
- The first demo does not produce a clear next step, paid pilot, or specific objection.

## Offer ladder
- **Lead magnet (Free)**: Recovery-percentile Tracker For Orthopedic Surgery Patients checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps Orthopedic surgeon office staff fielding daily post-op patient calls audit the painful workflow before buying software.
- **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted.
- **Core offer ($49-$499/month)**: Recovery-percentile tracker for orthopedic surgery patients focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop.
- **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.
- **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.

Print-ready memo

Decision Memo: Recovery-percentile tracker for orthopedic surgery patients

Team verdict: Park
Validation verdict: Research / 55/100
Confidence: 54%
Recorded: Not recorded

Recommendation

Keep this parked until the team has evidence for the next validation step: Recruit one orthopedic practice, have 15 knee-replacement patients log daily for two weeks, and measure whether tracked patients place fewer 'is this normal' calls than a comparison group.

Team rationale

No team rationale recorded yet.

Reviewers

No named reviewers recorded.

Source anchors

Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls
Market: Orthopedic post-operative recovery tracking
Problem: After orthopedic surgery, patients cannot tell whether their pain, swelling, and stiffness are normal, so they flood surgeon offices with 'is this normal?' calls while staff have no objective benchmark to reassure or escalate.
Thesis: Recovery-percentile tracker for orthopedic surgery patients should be tested as a narrow first-win workflow for Orthopedic surgeon office staff fielding daily post-op patient calls.

Validation rubric

Demand signal

24% weight

5.5/10

Demand looks thin because the report has 2 source-backed signal(s), an editorial confidence of 54/100, and a defined buyer in Orthopedic post-operative recovery tracking.

Problem severity

22% weight

6.3/10

Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.

Willingness to pay

20% weight

5/10

Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

Competitive saturation

18% weight

6.3/10

No source-backed direct match is recorded yet, so saturation risk is treated as unknown rather than proof of novelty.

Feasibility

16% weight

4/10

Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.

Market gap

Underserved segments

Orthopedic surgeon office staff fielding daily post-op patient calls who still run the workflow in spreadsheets, generic docs, email, or chat threads.
Small teams in Orthopedic post-operative recovery tracking that feel the pain weekly but are too narrow for broad incumbents.
New adopters who need guided proof before committing to a larger platform.

Feature gaps

A narrow workflow that reaches value without configuration-heavy onboarding.
A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
A handoff path from manual concierge service to repeatable software.

Differentiation levers

Use specificity as the wedge: one buyer, one workflow, one measurable result.
Show proof earlier than broad competitors with before-and-after examples and small pilot data.
Keep implementation lighter than incumbent suites or generic AI assistants.

Roast and risks

Interesting hypothesis, but it needs sharper demand evidence before build time.

Blind spots

Recovery-curve percentiles could be read as clinical advice, so the app must stay a tracking and journaling aid that supports rather than replaces the surgeon's care.
A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
The first release can become a generic dashboard if the job is not named tightly.

Hard questions

Who wakes up already trying to solve this?
What do they stop paying for or stop doing when this works?
What proof would make a skeptical buyer trust it in one screen?
What is the smallest paid version of this idea?

Kill criteria

Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
No buyer can name a current cost in time, money, risk, or reputation.
The first demo does not produce a clear next step, paid pilot, or specific objection.

Offer ladder

Lead magnet