Execution Scorecard

Recovery-percentile tracker for orthopedic surgery patients

Recovery-percentile tracker for orthopedic surgery patients scores 44/100 for execution readiness. The recommended next step is 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.

Back to report Markdown version Open accelerator

Bottlenecks

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.
Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.
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.
Needs real buyer access, not only desk research.
Needs proof of budget or repeated urgency.
Needs a crisp wedge before broad product work starts.

Accelerators

Can talk to the buyer before writing much code.
Can ship a narrow first-win demo quickly.
Can use local-first research artifacts to keep validation moving without a large team.
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.
Concierge review or paid template

Dated Plan

First 30 days to evidence.

The plan starts from build time and should be re-exported when the founder chooses a real start date.

2026-06-09

1. Frame the wedge

Write the one-sentence promise and test it in the strongest channel.

Proof: 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.

2026-06-12

2. Interview 10 people who match the buyer persona.

Create the lead magnet and use it to recruit interviews.

Proof: Problem resonance: 5+ calls or 10+ detailed replies.

2026-06-16

3. Ship a clickable demo or concierge workflow that produces the first useful artifact.

Build the smallest demo that proves the first win.

Proof: Activation: 25% of demo visitors complete the first-win path.

2026-06-23

4. Run one paid pilot or collect explicit pricing objections before automating the rest.

Delete any report section that feels generic before building.

Proof: Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.

2026-06-30

5. Promote to a deeper build plan only after the wedge survives validation.

Run the lead magnet and first-win demo tests.

Proof: Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.

2026-07-09

6. Execution checkpoint 6

Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.

Proof: Promote to a deeper build plan only after the wedge survives validation.

First actions

Write the one-sentence promise and test it in the strongest channel.
Create the lead magnet and use it to recruit interviews.
Build the smallest demo that proves the first win.
Delete any report section that feels generic before building.
Run the lead magnet and first-win demo tests.
Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.

Builder prompt

Create a dated execution plan for "Recovery-percentile tracker for orthopedic surgery patients". Keep the first milestone tied to 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.. Use these bottlenecks: 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.; Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.; 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.; Needs real buyer access, not only desk research.; Needs proof of budget or repeated urgency.; Needs a crisp wedge before broad product work starts.. Use these accelerators: Can talk to the buyer before writing much code.; Can ship a narrow first-win demo quickly.; Can use local-first research artifacts to keep validation moving without a large team.; 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.; Concierge review or paid template. Link the output to the Idea Builder prompt and do not expand beyond the first validated workflow.