{
  "schemaVersion": "INAV-BUNDLE-1",
  "slug": "post-surgery-progress-app",
  "title": "Recovery-percentile tracker for orthopedic surgery patients",
  "url": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/",
  "report": {
    "title": "Recovery-percentile tracker for orthopedic surgery patients",
    "date": "2026-06-09T00:00:00.000Z",
    "slug": "post-surgery-progress-app",
    "market": "Orthopedic post-operative recovery tracking",
    "buyer": "Orthopedic surgeon office staff fielding daily post-op patient calls",
    "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.",
    "whyNow": "Outpatient orthopedic procedures keep rising and offices are understaffed, so phones overflow with anxious recovery questions that have no data-backed answer at the point of contact.",
    "evidence": [
      "Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.",
      "Post-op patients repeatedly call offices asking whether their pain and swelling levels are expected for their stage of healing."
    ],
    "mvp": "A daily check-in for one procedure (e.g. knee replacement) where the patient logs pain, range-of-motion, and a walking milestone, then sees their numbers plotted as a percentile against anonymized recovery curves for the same surgery.",
    "difficulty": "high",
    "confidence": 54,
    "monetization": "Per-seat subscription billed to surgeon offices to cut call volume.",
    "risks": [
      "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."
    ],
    "validationTest": "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.",
    "validation": {
      "rubricVersion": "INAV-VALIDATION-2026-06-04",
      "overallScore": 55,
      "verdict": "Research",
      "summary": "Research is the current validation verdict: problem severity is the strongest signal, while feasibility is the main evidence gap to close before scaling the build.",
      "criteria": [
        {
          "id": "demand-signal",
          "label": "Demand signal",
          "weight": 0.24,
          "score": 5.5,
          "reasoning": "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.",
          "evidence": [
            "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"
          ]
        },
        {
          "id": "problem-severity",
          "label": "Problem severity",
          "weight": 0.22,
          "score": 6.3,
          "reasoning": "Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.",
          "evidence": [
            "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."
          ]
        },
        {
          "id": "willingness-to-pay",
          "label": "Willingness to pay",
          "weight": 0.2,
          "score": 5,
          "reasoning": "Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.",
          "evidence": [
            "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."
          ]
        },
        {
          "id": "competitive-saturation",
          "label": "Competitive saturation",
          "weight": 0.18,
          "score": 6.3,
          "reasoning": "No source-backed direct match is recorded yet, so saturation risk is treated as unknown rather than proof of novelty.",
          "evidence": [
            "Existing-product check has no named direct match.",
            "Competitive score rewards a narrow wedge, not absence of research."
          ]
        },
        {
          "id": "feasibility",
          "label": "Feasibility",
          "weight": 0.16,
          "score": 4,
          "reasoning": "Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.",
          "evidence": [
            "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."
          ]
        }
      ],
      "nextValidationStep": "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.",
      "generatedAt": "Tue Jun 09 2026 10:00:00 GMT+0200 (Central European Summer Time)"
    },
    "tags": [
      "orthopedics",
      "recovery",
      "tracking"
    ],
    "sources": [
      "https://www.aaos.org/",
      "https://en.wikipedia.org/wiki/Range_of_motion"
    ],
    "affiliate": false,
    "affiliateProducts": [],
    "reportGeneratedAt": "Tue Jun 09 2026 10:00:00 GMT+0200 (Central European Summer Time)",
    "oneLine": "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.",
    "complaintSeeds": [],
    "scorecard": [
      {
        "label": "Opportunity",
        "score": 5,
        "rating": "Promising",
        "detail": "Recovery-percentile tracker for orthopedic surgery patients has an editorial confidence score of 54/100 before live buyer validation."
      },
      {
        "label": "Problem",
        "score": 5,
        "rating": "Promising",
        "detail": "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."
      },
      {
        "label": "Feasibility",
        "score": 4,
        "rating": "Needs proof",
        "detail": "A high build can work if the MVP stays limited to the first repeated workflow."
      },
      {
        "label": "Why now",
        "score": 9,
        "rating": "Exceptional",
        "detail": "Outpatient orthopedic procedures keep rising and offices are understaffed, so phones overflow with anxious recovery questions that have no data-backed answer at the point of contact."
      }
    ],
    "businessFit": {
      "revenuePotential": "$250K-$2M ARR potential if the wedge proves budget urgency and becomes a recurring workflow.",
      "executionDifficulty": "Execution is high; the main constraint is staying narrow enough for a first proof loop.",
      "goToMarket": "Start with manual concierge output, direct outreach, and community proof before paid acquisition.",
      "founderFit": "Best for an AI-assisted solo founder who can interview the buyer and ship a focused first version quickly."
    },
    "offerLadder": [
      {
        "stage": "lead-magnet",
        "label": "Lead magnet",
        "offer": "Recovery-percentile Tracker For Orthopedic Surgery Patients checklist",
        "price": "Free",
        "valueProvided": "Helps Orthopedic surgeon office staff fielding daily post-op patient calls audit the painful workflow before buying software.",
        "goal": "Capture qualified leads and learn the buyer's exact language."
      },
      {
        "stage": "frontend",
        "label": "Frontend offer",
        "offer": "Concierge review or paid template",
        "price": "$19-$99",
        "valueProvided": "Delivers the first useful output manually before automation is trusted.",
        "goal": "Validate urgency, workflow fit, and willingness to pay."
      },
      {
        "stage": "core",
        "label": "Core offer",
        "offer": "Recovery-percentile tracker for orthopedic surgery patients focused SaaS",
        "price": "$49-$499/month",
        "valueProvided": "Turns the recurring manual workflow into a repeatable product loop.",
        "goal": "Create the recurring revenue product after the narrow wedge survives tests."
      },
      {
        "stage": "continuity",
        "label": "Continuity",
        "offer": "Monitoring, benchmarks, and monthly reporting",
        "price": "$99-$1,000/year add-on",
        "valueProvided": "Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.",
        "goal": "Increase retention and make the product part of a routine."
      },
      {
        "stage": "backend",
        "label": "Backend offer",
        "offer": "Done-with-you setup, agency, or team rollout",
        "price": "Custom",
        "valueProvided": "Adds implementation help, integrations, and workflow migration.",
        "goal": "Capture higher-value accounts once the productized wedge is proven."
      }
    ],
    "whyNowFactors": [
      {
        "label": "Demand visibility",
        "score": 5,
        "signal": "Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.",
        "detail": "Build only if the complaint repeats across interviews, posts, or existing workflow artifacts.",
        "evidenceUrl": "https://www.aaos.org/"
      },
      {
        "label": "Tooling readiness",
        "score": 4,
        "signal": "AI-assisted product work and managed infrastructure reduce the first-version cost.",
        "detail": "The first release should automate one high-friction step rather than become a broad platform.",
        "evidenceUrl": "https://en.wikipedia.org/wiki/Range_of_motion"
      },
      {
        "label": "Budget clarity",
        "score": 4,
        "signal": "Per-seat subscription billed to surgeon offices to cut call volume.",
        "detail": "Ask for money during validation before building the full workflow.",
        "evidenceUrl": "https://www.aaos.org/"
      },
      {
        "label": "Competitive window",
        "score": 7,
        "signal": "The wedge is specific enough to test without claiming the whole market.",
        "detail": "Position around one buyer and one measurable first-win outcome.",
        "evidenceUrl": "https://www.aaos.org/"
      }
    ],
    "proofSignals": [
      {
        "category": "Pain",
        "score": 5,
        "title": "Repeated workflow friction",
        "detail": "Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.",
        "evidenceUrl": "https://www.aaos.org/"
      },
      {
        "category": "Money",
        "score": 4,
        "title": "Budget hypothesis",
        "detail": "Orthopedic surgeon office staff fielding daily post-op patient calls is the first group to test because the monetization path is: Per-seat subscription billed to surgeon offices to cut call volume.",
        "evidenceUrl": "https://www.aaos.org/"
      },
      {
        "category": "Urgency",
        "score": 6,
        "title": "Switching pressure",
        "detail": "Urgency becomes real only if the current workaround costs time, risk, money, or reputation every week.",
        "evidenceUrl": "https://en.wikipedia.org/wiki/Range_of_motion"
      },
      {
        "category": "Distribution",
        "score": 8,
        "title": "Reachable buyer language",
        "detail": "The first channel should be whichever source lane already contains the buyer's vocabulary.",
        "evidenceUrl": "https://www.aaos.org/"
      }
    ],
    "existingProducts": [],
    "marketGap": {
      "underservedSegments": [
        "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."
      ],
      "featureGaps": [
        "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."
      ],
      "differentiationLevers": [
        "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."
      ]
    },
    "executionPlan": {
      "businessType": "Focused SaaS validation",
      "timeline": "8-12 weeks",
      "budget": "Local-first MVP budget: $0-$10K before paid acquisition.",
      "buyerPersonas": [
        "Orthopedic surgeon office staff fielding daily post-op patient calls",
        "Budget owner who feels the operational cost of the broken workflow.",
        "Hands-on operator willing to pilot a narrow tool before a full rollout."
      ],
      "painPoints": [
        "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.",
        "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."
      ],
      "mvpApproach": "Build only the first-win workflow for \"Recovery-percentile tracker for orthopedic surgery patients\" and keep research, setup, and exceptions manual until the wedge is proven.",
      "initialOffer": "Concierge review or paid template",
      "acquisitionChannels": [
        {
          "channel": "Community pain posts",
          "cadence": "Weekly",
          "why": "Use communities and forums where Orthopedic surgeon office staff fielding daily post-op patient calls already describe the painful workflow.",
          "format": "Problem teardown, interview ask, and short demo clip",
          "targetMetric": "5 qualified calls or 10 detailed replies in 7 days"
        },
        {
          "channel": "Direct outreach",
          "cadence": "Daily during validation",
          "why": "Direct conversations are the fastest way to verify budget ownership and switching cost.",
          "format": "Concierge pilot offer with a manually prepared sample",
          "targetMetric": "3 paid pilots, LOIs, or budget-owner follow-ups"
        },
        {
          "channel": "Searchable comparison content",
          "cadence": "Bi-weekly",
          "why": "Alternative and comparison pages reveal objections, pricing language, and buying intent.",
          "format": "Before-and-after page or alternatives memo for the exact workflow",
          "targetMetric": "Organic clicks, booked demos, or waitlist joins from comparison intent"
        },
        {
          "channel": "Launch directory",
          "cadence": "Once MVP is clickable",
          "why": "Launches test whether the promise is legible to people outside the first interview set.",
          "format": "Single-purpose demo and first-win story",
          "targetMetric": "25% demo completion or 10 waitlist joins"
        }
      ],
      "milestones": [
        "Interview 10 people who match the buyer persona.",
        "Ship a clickable demo or concierge workflow that produces the first useful artifact.",
        "Run one paid pilot or collect explicit pricing objections before automating the rest.",
        "Promote to a deeper build plan only after the wedge survives validation."
      ],
      "successMetrics": [
        "Problem resonance: 5+ calls or 10+ detailed replies.",
        "Activation: 25% of demo visitors complete the first-win path.",
        "Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps."
      ],
      "risks": [
        "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.",
        "Trying to build a broad platform before the narrow workflow has proof."
      ],
      "nextActions": [
        "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."
      ]
    },
    "frameworks": {
      "valueEquation": {
        "dreamOutcome": {
          "label": "Dream outcome",
          "score": 8,
          "rating": "Strong",
          "detail": "The buyer gets a visible first win around Recovery-percentile tracker for orthopedic surgery patients."
        },
        "perceivedLikelihood": {
          "label": "Perceived likelihood",
          "score": 6,
          "rating": "Promising",
          "detail": "Trust depends on proof, demos, and credible source links."
        },
        "timeDelay": {
          "label": "Time delay",
          "score": 4,
          "rating": "Needs proof",
          "detail": "Short setup and concierge onboarding make the promise easier to believe."
        },
        "effortAndSacrifice": {
          "label": "Effort and sacrifice",
          "score": 4,
          "rating": "Needs proof",
          "detail": "Reduce switching cost with imports, templates, and a manual migration path."
        },
        "improvements": [
          "Increase proof with a specific before-and-after demo.",
          "Reduce time to value with concierge onboarding.",
          "Remove effort by deferring integrations until one workflow is proven."
        ]
      },
      "marketMatrix": {
        "uniqueness": 7,
        "customerValue": 7,
        "quadrant": "Category king candidate",
        "detail": "High value plus high uniqueness deserves deeper research; lower uniqueness requires a clear distribution advantage."
      },
      "acp": {
        "audience": {
          "label": "Audience",
          "score": 5,
          "rating": "Promising",
          "detail": "Orthopedic surgeon office staff fielding daily post-op patient calls"
        },
        "community": {
          "label": "Community",
          "score": 7,
          "rating": "Strong",
          "detail": "Use the strongest source lane as the first reachable community."
        },
        "product": {
          "label": "Product",
          "score": 4,
          "rating": "Needs proof",
          "detail": "Keep the first product narrower than the market category."
        }
      },
      "categorization": {
        "type": "SaaS validation",
        "market": "Orthopedic post-operative recovery tracking",
        "target": "Orthopedic surgeon office staff fielding daily post-op patient calls",
        "mainCompetitor": "Manual status quo and broad generic AI tools",
        "trendAnalysis": "Trend and keyword signals are directional until verified with live customers and source citations."
      }
    },
    "communitySignals": [
      {
        "channel": "Reddit / forums",
        "count": "Research lane",
        "signal": "Look for complaints, workarounds, and repeated questions.",
        "firstMove": "Post a problem teardown for Orthopedic post-operative recovery tracking and ask how people solve it today."
      },
      {
        "channel": "Launch communities",
        "count": "Validation lane",
        "signal": "Launch traction shows whether the promise is legible.",
        "firstMove": "Ship a narrow demo and watch which promise gets clicks."
      },
      {
        "channel": "Review and alternative pages",
        "count": "Objection lane",
        "signal": "Pricing and alternatives expose buyer objections.",
        "firstMove": "Write an alternatives page that owns one narrow use case."
      }
    ],
    "keywordAnalysis": {
      "summary": "Keyword signals should be treated as directional. The strongest terms combine Orthopedic post-operative recovery tracking, the buyer workflow, and the first output the product creates.",
      "fastestGrowing": [
        {
          "keyword": "recovery ai",
          "volume": "directional medium",
          "growth": "rising with AI adoption",
          "competition": "medium"
        },
        {
          "keyword": "percentile automation",
          "volume": "directional low",
          "growth": "steady niche demand",
          "competition": "medium"
        }
      ],
      "highestVolume": [
        {
          "keyword": "tracker software",
          "volume": "directional medium",
          "growth": "rising with AI adoption",
          "competition": "high"
        },
        {
          "keyword": "orthopedic template",
          "volume": "directional low",
          "growth": "steady niche demand",
          "competition": "medium"
        }
      ],
      "mostRelevant": [
        {
          "keyword": "recovery workflow",
          "volume": "directional medium",
          "growth": "rising with AI adoption",
          "competition": "medium"
        },
        {
          "keyword": "percentile validation",
          "volume": "directional low",
          "growth": "steady niche demand",
          "competition": "low"
        }
      ],
      "source": "IdeaNavigator AI editorial keyword heuristic",
      "freshness": "generated with the daily report"
    },
    "founderFit": {
      "score": 6,
      "idealFor": "A solo or AI-assisted founder with direct access to Orthopedic surgeon office staff fielding daily post-op patient calls.",
      "advantages": [
        "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."
      ],
      "gaps": [
        "Needs real buyer access, not only desk research.",
        "Needs proof of budget or repeated urgency.",
        "Needs a crisp wedge before broad product work starts."
      ],
      "avoidIf": [
        "You cannot reach the buyer directly.",
        "The idea only sounds interesting but does not save time, money, risk, or reputation.",
        "You want to build the full platform before validating the first workflow."
      ],
      "nextMove": "Run the lead magnet and first-win demo tests before promoting the broad version."
    },
    "roast": {
      "verdict": "Interesting hypothesis, but it needs sharper demand evidence before build time.",
      "blindSpots": [
        "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."
      ],
      "hardQuestions": [
        "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?"
      ],
      "deRiskingMoves": [
        "Sell a manual pilot before building automation.",
        "Record five exact phrases buyers use to describe the pain.",
        "Cut any feature that does not support the first measurable win."
      ]
    },
    "buildActions": [
      "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."
    ],
    "handoffPrompts": {
      "buildPrompt": "Build a narrow MVP for \"Recovery-percentile tracker for orthopedic surgery patients\" for Orthopedic surgeon office staff fielding daily post-op patient calls. Preserve the evidence, build only the first-win workflow, include source links, and treat 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. as the first acceptance gate.",
      "reviewPrompt": "Review the \"Recovery-percentile tracker for orthopedic surgery patients\" MVP for over-breadth, unsupported claims, weak buyer proof, privacy risk, and missing validation instrumentation. Do not approve expansion until the kill criteria and success metrics are measurable."
    },
    "killCriteria": [
      "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."
    ],
    "sourceDetails": [
      {
        "title": "American Academy of Orthopaedic Surgeons",
        "url": "https://www.aaos.org/",
        "sourceType": "medical-association",
        "summary": "AAOS is the professional body for orthopedic surgeons and publishes recovery and rehabilitation guidance, establishing that structured post-op milestone tracking is clinically grounded."
      },
      {
        "title": "Range of Motion",
        "url": "https://en.wikipedia.org/wiki/Range_of_motion",
        "sourceType": "reference",
        "summary": "Documents how joint range of motion is measured in degrees and varies by joint and individual, confirming that ROM is a trackable recovery metric patients can log daily."
      }
    ]
  },
  "verdict": {
    "verdict": "Research",
    "overallScore": 55,
    "summary": "Research is the current validation verdict: problem severity is the strongest signal, while feasibility is the main evidence gap to close before scaling the build.",
    "confidence": 54,
    "difficulty": "high"
  },
  "provenance": {
    "sourceCount": 2,
    "sources": [
      "https://www.aaos.org/",
      "https://en.wikipedia.org/wiki/Range_of_motion"
    ],
    "sourceDetails": [
      {
        "title": "American Academy of Orthopaedic Surgeons",
        "url": "https://www.aaos.org/",
        "sourceType": "medical-association",
        "summary": "AAOS is the professional body for orthopedic surgeons and publishes recovery and rehabilitation guidance, establishing that structured post-op milestone tracking is clinically grounded."
      },
      {
        "title": "Range of Motion",
        "url": "https://en.wikipedia.org/wiki/Range_of_motion",
        "sourceType": "reference",
        "summary": "Documents how joint range of motion is measured in degrees and varies by joint and individual, confirming that ROM is a trackable recovery metric patients can log daily."
      }
    ],
    "evidence": [
      "Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.",
      "Post-op patients repeatedly call offices asking whether their pain and swelling levels are expected for their stage of healing.",
      "Target buyer: Orthopedic surgeon office staff fielding daily post-op patient calls",
      "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.",
      "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.",
      "Existing-product check has no named direct match.",
      "Competitive score rewards a narrow wedge, not absence of research.",
      "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."
    ],
    "rubricVersion": "INAV-VALIDATION-2026-06-04"
  },
  "backlog": {
    "schemaVersion": "INAV-BACKLOG-1",
    "slug": "post-surgery-progress-app",
    "title": "Recovery-percentile tracker for orthopedic surgery patients",
    "generatedFrom": "frontmatter+execution-readiness",
    "vertical": {
      "name": "Healthcare & Life Sciences",
      "slug": "healthcare"
    },
    "issueCount": 6,
    "issues": [
      {
        "id": "post-surgery-progress-app-01-frame-the-wedge",
        "title": "[1] Frame the wedge",
        "body": "## Outcome\nWrite the one-sentence promise and test it in the strongest channel.\n## Proof to collect\nRecruit 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.\n## Kill criterion\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Success metric\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Write the one-sentence promise and test it in the strongest channel.\n- Build action: Delete any report section that feels generic before building.\n- Risk to watch: 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.\n## Agent build prompt\nBuild a narrow MVP for \"Recovery-percentile tracker for orthopedic surgery patients\" for Orthopedic surgeon office staff fielding daily post-op patient calls. Preserve the evidence, build only the first-win workflow, include source links, and treat 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. as the first acceptance gate.\n\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).",
        "labels": [
          "ideanavigator",
          "vertical:healthcare",
          "difficulty:high",
          "stage:validation",
          "verdict:research"
        ],
        "milestone": "01 Frame the wedge",
        "stage": "validation",
        "source": {
          "reportUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/",
          "backlogUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json",
          "calendarUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics"
        }
      },
      {
        "id": "post-surgery-progress-app-02-interview-10-people-who-match-the-buyer-persona",
        "title": "[2] Interview 10 people who match the buyer persona.",
        "body": "## Outcome\nCreate the lead magnet and use it to recruit interviews.\n## Proof to collect\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Kill criterion\nNo buyer can name a current cost in time, money, risk, or reputation.\n## Success metric\nActivation: 25% of demo visitors complete the first-win path.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Create the lead magnet and use it to recruit interviews.\n- Build action: Run the lead magnet and first-win demo tests.\n- Risk to watch: Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).",
        "labels": [
          "ideanavigator",
          "vertical:healthcare",
          "difficulty:high",
          "stage:discovery",
          "verdict:research"
        ],
        "milestone": "02 Interview 10 people who match the buyer persona.",
        "stage": "discovery",
        "source": {
          "reportUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/",
          "backlogUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json",
          "calendarUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics"
        }
      },
      {
        "id": "post-surgery-progress-app-03-ship-a-clickable-demo-or-concierge-workflow-that-produces-the-first-useful-artifact",
        "title": "[3] Ship a clickable demo or concierge workflow that produces the first useful artifact.",
        "body": "## Outcome\nBuild the smallest demo that proves the first win.\n## Proof to collect\nActivation: 25% of demo visitors complete the first-win path.\n## Kill criterion\nThe first demo does not produce a clear next step, paid pilot, or specific objection.\n## Success metric\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Build the smallest demo that proves the first win.\n- Build action: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n- Risk to watch: Trying to build a broad platform before the narrow workflow has proof.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).",
        "labels": [
          "ideanavigator",
          "vertical:healthcare",
          "difficulty:high",
          "stage:prototype",
          "verdict:research"
        ],
        "milestone": "03 Ship a clickable demo or concierge workflow that produces the first useful artifact.",
        "stage": "prototype",
        "source": {
          "reportUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/",
          "backlogUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json",
          "calendarUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics"
        }
      },
      {
        "id": "post-surgery-progress-app-04-run-one-paid-pilot-or-collect-explicit-pricing-objections-before-automating-the-rest",
        "title": "[4] Run one paid pilot or collect explicit pricing objections before automating the rest.",
        "body": "## Outcome\nDelete any report section that feels generic before building.\n## Proof to collect\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Kill criterion\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Success metric\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Write the one-sentence promise and test it in the strongest channel.\n- Build action: Delete any report section that feels generic before building.\n- Risk to watch: 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.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).",
        "labels": [
          "ideanavigator",
          "vertical:healthcare",
          "difficulty:high",
          "stage:pilot",
          "verdict:research"
        ],
        "milestone": "04 Run one paid pilot or collect explicit pricing objections before automating the rest.",
        "stage": "pilot",
        "source": {
          "reportUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/",
          "backlogUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json",
          "calendarUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics"
        }
      },
      {
        "id": "post-surgery-progress-app-05-promote-to-a-deeper-build-plan-only-after-the-wedge-survives-validation",
        "title": "[5] Promote to a deeper build plan only after the wedge survives validation.",
        "body": "## Outcome\nRun the lead magnet and first-win demo tests.\n## Proof to collect\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Kill criterion\nNo buyer can name a current cost in time, money, risk, or reputation.\n## Success metric\nActivation: 25% of demo visitors complete the first-win path.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Create the lead magnet and use it to recruit interviews.\n- Build action: Run the lead magnet and first-win demo tests.\n- Risk to watch: Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).",
        "labels": [
          "ideanavigator",
          "vertical:healthcare",
          "difficulty:high",
          "stage:measurement",
          "verdict:research"
        ],
        "milestone": "05 Promote to a deeper build plan only after the wedge survives validation.",
        "stage": "measurement",
        "source": {
          "reportUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/",
          "backlogUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json",
          "calendarUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics"
        }
      },
      {
        "id": "post-surgery-progress-app-06-execution-checkpoint-6",
        "title": "[6] Execution checkpoint 6",
        "body": "## Outcome\nPromote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n## Proof to collect\nPromote to a deeper build plan only after the wedge survives validation.\n## Kill criterion\nThe first demo does not produce a clear next step, paid pilot, or specific objection.\n## Success metric\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Build the smallest demo that proves the first win.\n- Build action: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n- Risk to watch: Trying to build a broad platform before the narrow workflow has proof.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).",
        "labels": [
          "ideanavigator",
          "vertical:healthcare",
          "difficulty:high",
          "stage:decision",
          "verdict:research"
        ],
        "milestone": "06 Execution checkpoint 6",
        "stage": "decision",
        "source": {
          "reportUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/",
          "backlogUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json",
          "calendarUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics"
        }
      }
    ],
    "exports": {
      "githubCliScript": "#!/bin/sh\nset -eu\n# IdeaNavigator backlog: Recovery-percentile tracker for orthopedic surgery patients\ngh issue create \\\n  --title '[1] Frame the wedge' \\\n  --body '## Outcome\nWrite the one-sentence promise and test it in the strongest channel.\n## Proof to collect\nRecruit 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.\n## Kill criterion\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Success metric\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Write the one-sentence promise and test it in the strongest channel.\n- Build action: Delete any report section that feels generic before building.\n- Risk to watch: 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.\n## Agent build prompt\nBuild a narrow MVP for \"Recovery-percentile tracker for orthopedic surgery patients\" for Orthopedic surgeon office staff fielding daily post-op patient calls. Preserve the evidence, build only the first-win workflow, include source links, and treat 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. as the first acceptance gate.\n\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator,vertical:healthcare,difficulty:high,stage:validation,verdict:research' \\\n  --milestone '01 Frame the wedge'\ngh issue create \\\n  --title '[2] Interview 10 people who match the buyer persona.' \\\n  --body '## Outcome\nCreate the lead magnet and use it to recruit interviews.\n## Proof to collect\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Kill criterion\nNo buyer can name a current cost in time, money, risk, or reputation.\n## Success metric\nActivation: 25% of demo visitors complete the first-win path.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Create the lead magnet and use it to recruit interviews.\n- Build action: Run the lead magnet and first-win demo tests.\n- Risk to watch: Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator,vertical:healthcare,difficulty:high,stage:discovery,verdict:research' \\\n  --milestone '02 Interview 10 people who match the buyer persona.'\ngh issue create \\\n  --title '[3] Ship a clickable demo or concierge workflow that produces the first useful artifact.' \\\n  --body '## Outcome\nBuild the smallest demo that proves the first win.\n## Proof to collect\nActivation: 25% of demo visitors complete the first-win path.\n## Kill criterion\nThe first demo does not produce a clear next step, paid pilot, or specific objection.\n## Success metric\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Build the smallest demo that proves the first win.\n- Build action: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n- Risk to watch: Trying to build a broad platform before the narrow workflow has proof.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator,vertical:healthcare,difficulty:high,stage:prototype,verdict:research' \\\n  --milestone '03 Ship a clickable demo or concierge workflow that produces the first useful artifact.'\ngh issue create \\\n  --title '[4] Run one paid pilot or collect explicit pricing objections before automating the rest.' \\\n  --body '## Outcome\nDelete any report section that feels generic before building.\n## Proof to collect\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Kill criterion\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Success metric\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Write the one-sentence promise and test it in the strongest channel.\n- Build action: Delete any report section that feels generic before building.\n- Risk to watch: 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.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator,vertical:healthcare,difficulty:high,stage:pilot,verdict:research' \\\n  --milestone '04 Run one paid pilot or collect explicit pricing objections before automating the rest.'\ngh issue create \\\n  --title '[5] Promote to a deeper build plan only after the wedge survives validation.' \\\n  --body '## Outcome\nRun the lead magnet and first-win demo tests.\n## Proof to collect\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Kill criterion\nNo buyer can name a current cost in time, money, risk, or reputation.\n## Success metric\nActivation: 25% of demo visitors complete the first-win path.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Create the lead magnet and use it to recruit interviews.\n- Build action: Run the lead magnet and first-win demo tests.\n- Risk to watch: Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator,vertical:healthcare,difficulty:high,stage:measurement,verdict:research' \\\n  --milestone '05 Promote to a deeper build plan only after the wedge survives validation.'\ngh issue create \\\n  --title '[6] Execution checkpoint 6' \\\n  --body '## Outcome\nPromote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n## Proof to collect\nPromote to a deeper build plan only after the wedge survives validation.\n## Kill criterion\nThe first demo does not produce a clear next step, paid pilot, or specific objection.\n## Success metric\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Build the smallest demo that proves the first win.\n- Build action: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n- Risk to watch: Trying to build a broad platform before the narrow workflow has proof.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator,vertical:healthcare,difficulty:high,stage:decision,verdict:research' \\\n  --milestone '06 Execution checkpoint 6'\n",
      "linearCliScript": "#!/bin/sh\nset -eu\n# IdeaNavigator backlog: Recovery-percentile tracker for orthopedic surgery patients\nlinear issue create \\\n  --title '[1] Frame the wedge' \\\n  --description '## Outcome\nWrite the one-sentence promise and test it in the strongest channel.\n## Proof to collect\nRecruit 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.\n## Kill criterion\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Success metric\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Write the one-sentence promise and test it in the strongest channel.\n- Build action: Delete any report section that feels generic before building.\n- Risk to watch: 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.\n## Agent build prompt\nBuild a narrow MVP for \"Recovery-percentile tracker for orthopedic surgery patients\" for Orthopedic surgeon office staff fielding daily post-op patient calls. Preserve the evidence, build only the first-win workflow, include source links, and treat 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. as the first acceptance gate.\n\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator' \\\n  --label 'vertical:healthcare' \\\n  --label 'difficulty:high' \\\n  --label 'stage:validation' \\\n  --label 'verdict:research'\nlinear issue create \\\n  --title '[2] Interview 10 people who match the buyer persona.' \\\n  --description '## Outcome\nCreate the lead magnet and use it to recruit interviews.\n## Proof to collect\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Kill criterion\nNo buyer can name a current cost in time, money, risk, or reputation.\n## Success metric\nActivation: 25% of demo visitors complete the first-win path.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Create the lead magnet and use it to recruit interviews.\n- Build action: Run the lead magnet and first-win demo tests.\n- Risk to watch: Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator' \\\n  --label 'vertical:healthcare' \\\n  --label 'difficulty:high' \\\n  --label 'stage:discovery' \\\n  --label 'verdict:research'\nlinear issue create \\\n  --title '[3] Ship a clickable demo or concierge workflow that produces the first useful artifact.' \\\n  --description '## Outcome\nBuild the smallest demo that proves the first win.\n## Proof to collect\nActivation: 25% of demo visitors complete the first-win path.\n## Kill criterion\nThe first demo does not produce a clear next step, paid pilot, or specific objection.\n## Success metric\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Build the smallest demo that proves the first win.\n- Build action: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n- Risk to watch: Trying to build a broad platform before the narrow workflow has proof.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator' \\\n  --label 'vertical:healthcare' \\\n  --label 'difficulty:high' \\\n  --label 'stage:prototype' \\\n  --label 'verdict:research'\nlinear issue create \\\n  --title '[4] Run one paid pilot or collect explicit pricing objections before automating the rest.' \\\n  --description '## Outcome\nDelete any report section that feels generic before building.\n## Proof to collect\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Kill criterion\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Success metric\nProblem resonance: 5+ calls or 10+ detailed replies.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Write the one-sentence promise and test it in the strongest channel.\n- Build action: Delete any report section that feels generic before building.\n- Risk to watch: 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.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator' \\\n  --label 'vertical:healthcare' \\\n  --label 'difficulty:high' \\\n  --label 'stage:pilot' \\\n  --label 'verdict:research'\nlinear issue create \\\n  --title '[5] Promote to a deeper build plan only after the wedge survives validation.' \\\n  --description '## Outcome\nRun the lead magnet and first-win demo tests.\n## Proof to collect\nFewer than five qualified buyers agree to discuss the workflow after targeted outreach.\n## Kill criterion\nNo buyer can name a current cost in time, money, risk, or reputation.\n## Success metric\nActivation: 25% of demo visitors complete the first-win path.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Create the lead magnet and use it to recruit interviews.\n- Build action: Run the lead magnet and first-win demo tests.\n- Risk to watch: Building credible anonymized benchmark curves requires volume of comparable cases before the percentile is meaningful.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator' \\\n  --label 'vertical:healthcare' \\\n  --label 'difficulty:high' \\\n  --label 'stage:measurement' \\\n  --label 'verdict:research'\nlinear issue create \\\n  --title '[6] Execution checkpoint 6' \\\n  --description '## Outcome\nPromote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n## Proof to collect\nPromote to a deeper build plan only after the wedge survives validation.\n## Kill criterion\nThe first demo does not produce a clear next step, paid pilot, or specific objection.\n## Success metric\nCommercial pull: 3 paid pilots, LOIs, or concrete procurement next steps.\n## Implementation notes\n- Buyer: Orthopedic surgeon office staff fielding daily post-op patient calls\n- Validation test: 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.\n- Next action: Build the smallest demo that proves the first win.\n- Build action: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach.\n- Risk to watch: Trying to build a broad platform before the narrow workflow has proof.\n## Source links\n- [Full report](https://ideanavigatorai.com/ideas/post-surgery-progress-app/)\n- [Backlog JSON](https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json)\n- [Calendar handoff](https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics)\nValidation verdict: Research (55/100).' \\\n  --label 'ideanavigator' \\\n  --label 'vertical:healthcare' \\\n  --label 'difficulty:high' \\\n  --label 'stage:decision' \\\n  --label 'verdict:research'\n"
    }
  },
  "decisionMemo": {
    "slug": "post-surgery-progress-app",
    "title": "Recovery-percentile tracker for orthopedic surgery patients",
    "teamVerdict": "Park",
    "rationale": "No team rationale recorded yet.",
    "reviewers": [],
    "recordedAt": "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.",
    "idea": {
      "title": "Recovery-percentile tracker for orthopedic surgery patients",
      "date": "2026-06-09T00:00:00.000Z",
      "slug": "post-surgery-progress-app",
      "market": "Orthopedic post-operative recovery tracking",
      "buyer": "Orthopedic surgeon office staff fielding daily post-op patient calls",
      "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.",
      "whyNow": "Outpatient orthopedic procedures keep rising and offices are understaffed, so phones overflow with anxious recovery questions that have no data-backed answer at the point of contact.",
      "evidence": [
        "Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.",
        "Post-op patients repeatedly call offices asking whether their pain and swelling levels are expected for their stage of healing."
      ],
      "mvp": "A daily check-in for one procedure (e.g. knee replacement) where the patient logs pain, range-of-motion, and a walking milestone, then sees their numbers plotted as a percentile against anonymized recovery curves for the same surgery.",
      "difficulty": "high",
      "confidence": 54,
      "monetization": "Per-seat subscription billed to surgeon offices to cut call volume.",
      "risks": [
        "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."
      ],
      "validationTest": "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.",
      "validation": {
        "rubricVersion": "INAV-VALIDATION-2026-06-04",
        "overallScore": 55,
        "verdict": "Research",
        "summary": "Research is the current validation verdict: problem severity is the strongest signal, while feasibility is the main evidence gap to close before scaling the build.",
        "criteria": [
          {
            "id": "demand-signal",
            "label": "Demand signal",
            "weight": 0.24,
            "score": 5.5,
            "reasoning": "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.",
            "evidence": [
              "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"
            ]
          },
          {
            "id": "problem-severity",
            "label": "Problem severity",
            "weight": 0.22,
            "score": 6.3,
            "reasoning": "Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.",
            "evidence": [
              "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."
            ]
          },
          {
            "id": "willingness-to-pay",
            "label": "Willingness to pay",
            "weight": 0.2,
            "score": 5,
            "reasoning": "Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.",
            "evidence": [
              "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."
            ]
          },
          {
            "id": "competitive-saturation",
            "label": "Competitive saturation",
            "weight": 0.18,
            "score": 6.3,
            "reasoning": "No source-backed direct match is recorded yet, so saturation risk is treated as unknown rather than proof of novelty.",
            "evidence": [
              "Existing-product check has no named direct match.",
              "Competitive score rewards a narrow wedge, not absence of research."
            ]
          },
          {
            "id": "feasibility",
            "label": "Feasibility",
            "weight": 0.16,
            "score": 4,
            "reasoning": "Feasibility is weak for a high build if the MVP is limited to the first measurable workflow.",
            "evidence": [
              "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."
            ]
          }
        ],
        "nextValidationStep": "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.",
        "generatedAt": "Tue Jun 09 2026 10:00:00 GMT+0200 (Central European Summer Time)"
      },
      "tags": [
        "orthopedics",
        "recovery",
        "tracking"
      ],
      "sources": [
        "https://www.aaos.org/",
        "https://en.wikipedia.org/wiki/Range_of_motion"
      ],
      "affiliate": false,
      "affiliateProducts": [],
      "reportGeneratedAt": "Tue Jun 09 2026 10:00:00 GMT+0200 (Central European Summer Time)",
      "oneLine": "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.",
      "complaintSeeds": [],
      "scorecard": [
        {
          "label": "Opportunity",
          "score": 5,
          "rating": "Promising",
          "detail": "Recovery-percentile tracker for orthopedic surgery patients has an editorial confidence score of 54/100 before live buyer validation."
        },
        {
          "label": "Problem",
          "score": 5,
          "rating": "Promising",
          "detail": "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."
        },
        {
          "label": "Feasibility",
          "score": 4,
          "rating": "Needs proof",
          "detail": "A high build can work if the MVP stays limited to the first repeated workflow."
        },
        {
          "label": "Why now",
          "score": 9,
          "rating": "Exceptional",
          "detail": "Outpatient orthopedic procedures keep rising and offices are understaffed, so phones overflow with anxious recovery questions that have no data-backed answer at the point of contact."
        }
      ],
      "businessFit": {
        "revenuePotential": "$250K-$2M ARR potential if the wedge proves budget urgency and becomes a recurring workflow.",
        "executionDifficulty": "Execution is high; the main constraint is staying narrow enough for a first proof loop.",
        "goToMarket": "Start with manual concierge output, direct outreach, and community proof before paid acquisition.",
        "founderFit": "Best for an AI-assisted solo founder who can interview the buyer and ship a focused first version quickly."
      },
      "offerLadder": [
        {
          "stage": "lead-magnet",
          "label": "Lead magnet",
          "offer": "Recovery-percentile Tracker For Orthopedic Surgery Patients checklist",
          "price": "Free",
          "valueProvided": "Helps Orthopedic surgeon office staff fielding daily post-op patient calls audit the painful workflow before buying software.",
          "goal": "Capture qualified leads and learn the buyer's exact language."
        },
        {
          "stage": "frontend",
          "label": "Frontend offer",
          "offer": "Concierge review or paid template",
          "price": "$19-$99",
          "valueProvided": "Delivers the first useful output manually before automation is trusted.",
          "goal": "Validate urgency, workflow fit, and willingness to pay."
        },
        {
          "stage": "core",
          "label": "Core offer",
          "offer": "Recovery-percentile tracker for orthopedic surgery patients focused SaaS",
          "price": "$49-$499/month",
          "valueProvided": "Turns the recurring manual workflow into a repeatable product loop.",
          "goal": "Create the recurring revenue product after the narrow wedge survives tests."
        },
        {
          "stage": "continuity",
          "label": "Continuity",
          "offer": "Monitoring, benchmarks, and monthly reporting",
          "price": "$99-$1,000/year add-on",
          "valueProvided": "Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.",
          "goal": "Increase retention and make the product part of a routine."
        },
        {
          "stage": "backend",
          "label": "Backend offer",
          "offer": "Done-with-you setup, agency, or team rollout",
          "price": "Custom",
          "valueProvided": "Adds implementation help, integrations, and workflow migration.",
          "goal": "Capture higher-value accounts once the productized wedge is proven."
        }
      ],
      "whyNowFactors": [
        {
          "label": "Demand visibility",
          "score": 5,
          "signal": "Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.",
          "detail": "Build only if the complaint repeats across interviews, posts, or existing workflow artifacts.",
          "evidenceUrl": "https://www.aaos.org/"
        },
        {
          "label": "Tooling readiness",
          "score": 4,
          "signal": "AI-assisted product work and managed infrastructure reduce the first-version cost.",
          "detail": "The first release should automate one high-friction step rather than become a broad platform.",
          "evidenceUrl": "https://en.wikipedia.org/wiki/Range_of_motion"
        },
        {
          "label": "Budget clarity",
          "score": 4,
          "signal": "Per-seat subscription billed to surgeon offices to cut call volume.",
          "detail": "Ask for money during validation before building the full workflow.",
          "evidenceUrl": "https://www.aaos.org/"
        },
        {
          "label": "Competitive window",
          "score": 7,
          "signal": "The wedge is specific enough to test without claiming the whole market.",
          "detail": "Position around one buyer and one measurable first-win outcome.",
          "evidenceUrl": "https://www.aaos.org/"
        }
      ],
      "proofSignals": [
        {
          "category": "Pain",
          "score": 5,
          "title": "Repeated workflow friction",
          "detail": "Range of motion and joint mobility are routinely measured during orthopedic recovery and vary by joint, age, and procedure.",
          "evidenceUrl": "https://www.aaos.org/"
        },
        {
          "category": "Money",
          "score": 4,
          "title": "Budget hypothesis",
          "detail": "Orthopedic surgeon office staff fielding daily post-op patient calls is the first group to test because the monetization path is: Per-seat subscription billed to surgeon offices to cut call volume.",
          "evidenceUrl": "https://www.aaos.org/"
        },
        {
          "category": "Urgency",
          "score": 6,
          "title": "Switching pressure",
          "detail": "Urgency becomes real only if the current workaround costs time, risk, money, or reputation every week.",
          "evidenceUrl": "https://en.wikipedia.org/wiki/Range_of_motion"
        },
        {
          "category": "Distribution",
          "score": 8,
          "title": "Reachable buyer language",
          "detail": "The first channel should be whichever source lane already contains the buyer's vocabulary.",
          "evidenceUrl": "https://www.aaos.org/"
        }
      ],
      "existingProducts": [],
      "marketGap": {
        "underservedSegments": [
          "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."
        ],
        "featureGaps": [
          "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."
        ],
        "differentiationLevers": [
          "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."
        ]
      },
      "executionPlan": {
        "businessType": "Focused SaaS validation",
        "timeline": "8-12 weeks",
        "budget": "Local-first MVP budget: $0-$10K before paid acquisition.",
        "buyerPersonas": [
          "Orthopedic surgeon office staff fielding daily post-op patient calls",
          "Budget owner who feels the operational cost of the broken workflow.",
          "Hands-on operator willing to pilot a narrow tool before a full rollout."
        ],
        "painPoints": [
          "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.",
          "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."
        ],
        "mvpApproach": "Build only the first-win workflow for \"Recovery-percentile tracker for orthopedic surgery patients\" and keep research, setup, and exceptions manual until the wedge is proven.",
        "initialOffer": "Concierge review or paid template",
        "acquisitionChannels": [
          {
            "channel": "Community pain posts",
            "cadence": "Weekly",
            "why": "Use communities and forums where Orthopedic surgeon office staff fielding daily post-op patient calls already describe the painful workflow.",
            "format": "Problem teardown, interview ask, and short demo clip",
            "targetMetric": "5 qualified calls or 10 detailed replies in 7 days"
          },
          {
            "channel": "Direct outreach",
            "cadence": "Daily during validation",
            "why": "Direct conversations are the fastest way to verify budget ownership and switching cost.",
            "format": "Concierge pilot offer with a manually prepared sample",
            "targetMetric": "3 paid pilots, LOIs, or budget-owner follow-ups"
          },
          {
            "channel": "Searchable comparison content",
            "cadence": "Bi-weekly",
            "why": "Alternative and comparison pages reveal objections, pricing language, and buying intent.",
            "format": "Before-and-after page or alternatives memo for the exact workflow",
            "targetMetric": "Organic clicks, booked demos, or waitlist joins from comparison intent"
          },
          {
            "channel": "Launch directory",
            "cadence": "Once MVP is clickable",
            "why": "Launches test whether the promise is legible to people outside the first interview set.",
            "format": "Single-purpose demo and first-win story",
            "targetMetric": "25% demo completion or 10 waitlist joins"
          }
        ],
        "milestones": [
          "Interview 10 people who match the buyer persona.",
          "Ship a clickable demo or concierge workflow that produces the first useful artifact.",
          "Run one paid pilot or collect explicit pricing objections before automating the rest.",
          "Promote to a deeper build plan only after the wedge survives validation."
        ],
        "successMetrics": [
          "Problem resonance: 5+ calls or 10+ detailed replies.",
          "Activation: 25% of demo visitors complete the first-win path.",
          "Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps."
        ],
        "risks": [
          "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.",
          "Trying to build a broad platform before the narrow workflow has proof."
        ],
        "nextActions": [
          "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."
        ]
      },
      "frameworks": {
        "valueEquation": {
          "dreamOutcome": {
            "label": "Dream outcome",
            "score": 8,
            "rating": "Strong",
            "detail": "The buyer gets a visible first win around Recovery-percentile tracker for orthopedic surgery patients."
          },
          "perceivedLikelihood": {
            "label": "Perceived likelihood",
            "score": 6,
            "rating": "Promising",
            "detail": "Trust depends on proof, demos, and credible source links."
          },
          "timeDelay": {
            "label": "Time delay",
            "score": 4,
            "rating": "Needs proof",
            "detail": "Short setup and concierge onboarding make the promise easier to believe."
          },
          "effortAndSacrifice": {
            "label": "Effort and sacrifice",
            "score": 4,
            "rating": "Needs proof",
            "detail": "Reduce switching cost with imports, templates, and a manual migration path."
          },
          "improvements": [
            "Increase proof with a specific before-and-after demo.",
            "Reduce time to value with concierge onboarding.",
            "Remove effort by deferring integrations until one workflow is proven."
          ]
        },
        "marketMatrix": {
          "uniqueness": 7,
          "customerValue": 7,
          "quadrant": "Category king candidate",
          "detail": "High value plus high uniqueness deserves deeper research; lower uniqueness requires a clear distribution advantage."
        },
        "acp": {
          "audience": {
            "label": "Audience",
            "score": 5,
            "rating": "Promising",
            "detail": "Orthopedic surgeon office staff fielding daily post-op patient calls"
          },
          "community": {
            "label": "Community",
            "score": 7,
            "rating": "Strong",
            "detail": "Use the strongest source lane as the first reachable community."
          },
          "product": {
            "label": "Product",
            "score": 4,
            "rating": "Needs proof",
            "detail": "Keep the first product narrower than the market category."
          }
        },
        "categorization": {
          "type": "SaaS validation",
          "market": "Orthopedic post-operative recovery tracking",
          "target": "Orthopedic surgeon office staff fielding daily post-op patient calls",
          "mainCompetitor": "Manual status quo and broad generic AI tools",
          "trendAnalysis": "Trend and keyword signals are directional until verified with live customers and source citations."
        }
      },
      "communitySignals": [
        {
          "channel": "Reddit / forums",
          "count": "Research lane",
          "signal": "Look for complaints, workarounds, and repeated questions.",
          "firstMove": "Post a problem teardown for Orthopedic post-operative recovery tracking and ask how people solve it today."
        },
        {
          "channel": "Launch communities",
          "count": "Validation lane",
          "signal": "Launch traction shows whether the promise is legible.",
          "firstMove": "Ship a narrow demo and watch which promise gets clicks."
        },
        {
          "channel": "Review and alternative pages",
          "count": "Objection lane",
          "signal": "Pricing and alternatives expose buyer objections.",
          "firstMove": "Write an alternatives page that owns one narrow use case."
        }
      ],
      "keywordAnalysis": {
        "summary": "Keyword signals should be treated as directional. The strongest terms combine Orthopedic post-operative recovery tracking, the buyer workflow, and the first output the product creates.",
        "fastestGrowing": [
          {
            "keyword": "recovery ai",
            "volume": "directional medium",
            "growth": "rising with AI adoption",
            "competition": "medium"
          },
          {
            "keyword": "percentile automation",
            "volume": "directional low",
            "growth": "steady niche demand",
            "competition": "medium"
          }
        ],
        "highestVolume": [
          {
            "keyword": "tracker software",
            "volume": "directional medium",
            "growth": "rising with AI adoption",
            "competition": "high"
          },
          {
            "keyword": "orthopedic template",
            "volume": "directional low",
            "growth": "steady niche demand",
            "competition": "medium"
          }
        ],
        "mostRelevant": [
          {
            "keyword": "recovery workflow",
            "volume": "directional medium",
            "growth": "rising with AI adoption",
            "competition": "medium"
          },
          {
            "keyword": "percentile validation",
            "volume": "directional low",
            "growth": "steady niche demand",
            "competition": "low"
          }
        ],
        "source": "IdeaNavigator AI editorial keyword heuristic",
        "freshness": "generated with the daily report"
      },
      "founderFit": {
        "score": 6,
        "idealFor": "A solo or AI-assisted founder with direct access to Orthopedic surgeon office staff fielding daily post-op patient calls.",
        "advantages": [
          "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."
        ],
        "gaps": [
          "Needs real buyer access, not only desk research.",
          "Needs proof of budget or repeated urgency.",
          "Needs a crisp wedge before broad product work starts."
        ],
        "avoidIf": [
          "You cannot reach the buyer directly.",
          "The idea only sounds interesting but does not save time, money, risk, or reputation.",
          "You want to build the full platform before validating the first workflow."
        ],
        "nextMove": "Run the lead magnet and first-win demo tests before promoting the broad version."
      },
      "roast": {
        "verdict": "Interesting hypothesis, but it needs sharper demand evidence before build time.",
        "blindSpots": [
          "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."
        ],
        "hardQuestions": [
          "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?"
        ],
        "deRiskingMoves": [
          "Sell a manual pilot before building automation.",
          "Record five exact phrases buyers use to describe the pain.",
          "Cut any feature that does not support the first measurable win."
        ]
      },
      "buildActions": [
        "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."
      ],
      "handoffPrompts": {
        "buildPrompt": "Build a narrow MVP for \"Recovery-percentile tracker for orthopedic surgery patients\" for Orthopedic surgeon office staff fielding daily post-op patient calls. Preserve the evidence, build only the first-win workflow, include source links, and treat 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. as the first acceptance gate.",
        "reviewPrompt": "Review the \"Recovery-percentile tracker for orthopedic surgery patients\" MVP for over-breadth, unsupported claims, weak buyer proof, privacy risk, and missing validation instrumentation. Do not approve expansion until the kill criteria and success metrics are measurable."
      },
      "killCriteria": [
        "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."
      ],
      "sourceDetails": [
        {
          "title": "American Academy of Orthopaedic Surgeons",
          "url": "https://www.aaos.org/",
          "sourceType": "medical-association",
          "summary": "AAOS is the professional body for orthopedic surgeons and publishes recovery and rehabilitation guidance, establishing that structured post-op milestone tracking is clinically grounded."
        },
        {
          "title": "Range of Motion",
          "url": "https://en.wikipedia.org/wiki/Range_of_motion",
          "sourceType": "reference",
          "summary": "Documents how joint range of motion is measured in degrees and varies by joint and individual, confirming that ROM is a trackable recovery metric patients can log daily."
        }
      ]
    }
  },
  "calendarIcs": "BEGIN:VCALENDAR\r\nVERSION:2.0\r\nPRODID:-//IdeaNavigator AI//Execution Plan//EN\r\nCALSCALE:GREGORIAN\r\nMETHOD:PUBLISH\r\nX-WR-CALNAME:IdeaNavigator: Recovery-percentile tracker for orthopedic surg\r\n ery patients\r\nBEGIN:VEVENT\r\nUID:post-surgery-progress-app-1@ideanavigatorai.com\r\nDTSTAMP:20260609T080000Z\r\nDTSTART;VALUE=DATE:20260609\r\nDTEND;VALUE=DATE:20260610\r\nSUMMARY:Frame the wedge\r\nDESCRIPTION:Write the one-sentence promise and test it in the strongest cha\r\n nnel.\\n\\nProof: Recruit one orthopedic practice\\, have 15 knee-replacement\r\n  patients log daily for two weeks\\, and measure whether tracked patients p\r\n lace fewer 'is this normal' calls than a comparison group.\\nOpen builder: \r\n https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-app\\n\r\n Report: https://ideanavigatorai.com/ideas/post-surgery-progress-app/\\nNote\r\n : Plan dates are anchored to the report publish date (2026-06-09)\\; shift \r\n them to your real start date when importing.\r\nURL:https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-ap\r\n p\r\nBEGIN:VALARM\r\nACTION:DISPLAY\r\nDESCRIPTION:Validation test due soon: Recruit one orthopedic practice\\, hav\r\n e 15 knee-replacement patients log daily for two weeks\\, and measure wheth\r\n er tracked patients place fewer 'is this normal' calls than a comparison g\r\n roup.\r\nTRIGGER:-P7D\r\nEND:VALARM\r\nEND:VEVENT\r\nBEGIN:VEVENT\r\nUID:post-surgery-progress-app-2@ideanavigatorai.com\r\nDTSTAMP:20260609T080000Z\r\nDTSTART;VALUE=DATE:20260612\r\nDTEND;VALUE=DATE:20260613\r\nSUMMARY:Interview 10 people who match the buyer persona.\r\nDESCRIPTION:Create the lead magnet and use it to recruit interviews.\\n\\nPro\r\n of: Problem resonance: 5+ calls or 10+ detailed replies.\\nOpen builder: ht\r\n tps://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-app\\nRe\r\n port: https://ideanavigatorai.com/ideas/post-surgery-progress-app/\\nNote: \r\n Plan dates are anchored to the report publish date (2026-06-09)\\; shift th\r\n em to your real start date when importing.\r\nURL:https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-ap\r\n p\r\nEND:VEVENT\r\nBEGIN:VEVENT\r\nUID:post-surgery-progress-app-3@ideanavigatorai.com\r\nDTSTAMP:20260609T080000Z\r\nDTSTART;VALUE=DATE:20260616\r\nDTEND;VALUE=DATE:20260617\r\nSUMMARY:Ship a clickable demo or concierge workflow that produces the first\r\n  useful artifact.\r\nDESCRIPTION:Build the smallest demo that proves the first win.\\n\\nProof: Ac\r\n tivation: 25% of demo visitors complete the first-win path.\\nOpen builder:\r\n  https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-app\\\r\n nReport: https://ideanavigatorai.com/ideas/post-surgery-progress-app/\\nNot\r\n e: Plan dates are anchored to the report publish date (2026-06-09)\\; shift\r\n  them to your real start date when importing.\r\nURL:https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-ap\r\n p\r\nEND:VEVENT\r\nBEGIN:VEVENT\r\nUID:post-surgery-progress-app-4@ideanavigatorai.com\r\nDTSTAMP:20260609T080000Z\r\nDTSTART;VALUE=DATE:20260623\r\nDTEND;VALUE=DATE:20260624\r\nSUMMARY:Run one paid pilot or collect explicit pricing objections before au\r\n tomating the rest.\r\nDESCRIPTION:Delete any report section that feels generic before building.\\n\r\n \\nProof: Commercial pull: 3 paid pilots\\, LOIs\\, or concrete procurement n\r\n ext steps.\\nOpen builder: https://ideanavigatorai.com/idea-builder/?idea=p\r\n ost-surgery-progress-app\\nReport: https://ideanavigatorai.com/ideas/post-s\r\n urgery-progress-app/\\nNote: Plan dates are anchored to the report publish \r\n date (2026-06-09)\\; shift them to your real start date when importing.\r\nURL:https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-ap\r\n p\r\nEND:VEVENT\r\nBEGIN:VEVENT\r\nUID:post-surgery-progress-app-5@ideanavigatorai.com\r\nDTSTAMP:20260609T080000Z\r\nDTSTART;VALUE=DATE:20260630\r\nDTEND;VALUE=DATE:20260701\r\nSUMMARY:Promote to a deeper build plan only after the wedge survives valida\r\n tion.\r\nDESCRIPTION:Run the lead magnet and first-win demo tests.\\n\\nProof: Fewer t\r\n han five qualified buyers agree to discuss the workflow after targeted out\r\n reach.\\nOpen builder: https://ideanavigatorai.com/idea-builder/?idea=post-\r\n surgery-progress-app\\nReport: https://ideanavigatorai.com/ideas/post-surge\r\n ry-progress-app/\\nNote: Plan dates are anchored to the report publish date\r\n  (2026-06-09)\\; shift them to your real start date when importing.\r\nURL:https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-ap\r\n p\r\nEND:VEVENT\r\nBEGIN:VEVENT\r\nUID:post-surgery-progress-app-6@ideanavigatorai.com\r\nDTSTAMP:20260609T080000Z\r\nDTSTART;VALUE=DATE:20260709\r\nDTEND;VALUE=DATE:20260710\r\nSUMMARY:Execution checkpoint 6\r\nDESCRIPTION:Promote to deeper implementation only once the wedge survives i\r\n nterviews or paid-pilot outreach.\\n\\nProof: Promote to a deeper build plan\r\n  only after the wedge survives validation.\\nOpen builder: https://ideanavi\r\n gatorai.com/idea-builder/?idea=post-surgery-progress-app\\nReport: https://\r\n ideanavigatorai.com/ideas/post-surgery-progress-app/\\nNote: Plan dates are\r\n  anchored to the report publish date (2026-06-09)\\; shift them to your rea\r\n l start date when importing.\r\nURL:https://ideanavigatorai.com/idea-builder/?idea=post-surgery-progress-ap\r\n p\r\nEND:VEVENT\r\nEND:VCALENDAR\r\n",
  "exports": {
    "bundleUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.bundle.json",
    "jsonUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.json",
    "markdownUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.md",
    "calendarUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app.ics",
    "backlogUrl": "https://ideanavigatorai.com/ideas/post-surgery-progress-app/backlog.json"
  }
}