# Execution Scorecard: Vertigo relief app Score: 65/100 Tier: Needs focused validation Vertigo relief app scores 65/100 for execution readiness. The recommended next step is Build a lightweight landing page plus a no-code guided-Epley walkthrough and run targeted ads to vertigo/BPPV search terms; measure email signups and the share who complete the maneuver flow. Validate B2B demand by pitching 10-15 ENT/audiology/physio clinics on recommending it for between-visit home care and counting how many agree to trial it with patients. ## Bottlenecks - Regulatory and medical-claims risk: positioning the app as treating or curing BPPV can trigger FDA software-as-a-medical-device scrutiny and liability; marketing must stay within wellness/educational claims and carry medical disclaimers. - Clinical safety risk: the Epley maneuver is unsafe for some users (neck/back disease, vascular conditions, retinal detachment) and self-diagnosis may miss serious causes of vertigo such as stroke, so robust screening and escalation prompts are essential. - Crowded niche with several established free and low-cost competitors and inherently low willingness-to-pay for an episodic, often self-resolving condition, making retention and recurring revenue difficult. - A broad AI assistant can flatten differentiation unless the wedge is painfully specific. - The first release can become a generic dashboard if the job is not named tightly. - Needs real buyer access, not only desk research. - Needs proof of budget or repeated urgency. ## Accelerators - Can talk to the buyer before writing much code. - Can ship a narrow first-win demo quickly. - Can use local-first research artifacts to keep validation moving without a large team. - Use specificity as the wedge: one buyer, one workflow, one measurable result. - Show proof earlier than broad competitors with before-and-after examples and small pilot data. - Keep implementation lighter than incumbent suites or generic AI assistants. - Concierge review or paid template ## Dated Launch Plan - **2026-08-13 / Frame the wedge**: Write the one-sentence promise and test it in the strongest channel. Proof: Build a lightweight landing page plus a no-code guided-Epley walkthrough and run targeted ads to vertigo/BPPV search terms; measure email signups and the share who complete the maneuver flow. Validate B2B demand by pitching 10-15 ENT/audiology/physio clinics on recommending it for between-visit home care and counting how many agree to trial it with patients. - **2026-08-16 / Interview 10 people who match the buyer persona.**: Create the lead magnet and use it to recruit interviews. Proof: Problem resonance: 5+ calls or 10+ detailed replies. - **2026-08-20 / Ship a clickable demo or concierge workflow that produces the first useful artifact.**: Build the smallest demo that proves the first win. Proof: Activation: 25% of demo visitors complete the first-win path. - **2026-08-27 / Run one paid pilot or collect explicit pricing objections before automating the rest.**: Delete any report section that feels generic before building. Proof: Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps. - **2026-09-03 / Promote to a deeper build plan only after the wedge survives validation.**: Run the lead magnet and first-win demo tests. Proof: Fewer than five qualified buyers agree to discuss the workflow after targeted outreach. - **2026-09-12 / Execution checkpoint 6**: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach. Proof: Promote to a deeper build plan only after the wedge survives validation. ## Builder Prompt Create a dated execution plan for "Vertigo relief app". Keep the first milestone tied to Build a lightweight landing page plus a no-code guided-Epley walkthrough and run targeted ads to vertigo/BPPV search terms; measure email signups and the share who complete the maneuver flow. Validate B2B demand by pitching 10-15 ENT/audiology/physio clinics on recommending it for between-visit home care and counting how many agree to trial it with patients.. Use these bottlenecks: Regulatory and medical-claims risk: positioning the app as treating or curing BPPV can trigger FDA software-as-a-medical-device scrutiny and liability; marketing must stay within wellness/educational claims and carry medical disclaimers.; Clinical safety risk: the Epley maneuver is unsafe for some users (neck/back disease, vascular conditions, retinal detachment) and self-diagnosis may miss serious causes of vertigo such as stroke, so robust screening and escalation prompts are essential.; Crowded niche with several established free and low-cost competitors and inherently low willingness-to-pay for an episodic, often self-resolving condition, making retention and recurring revenue difficult.; A broad AI assistant can flatten differentiation unless the wedge is painfully specific.; The first release can become a generic dashboard if the job is not named tightly.; Needs real buyer access, not only desk research.; Needs proof of budget or repeated urgency.. Use these accelerators: Can talk to the buyer before writing much code.; Can ship a narrow first-win demo quickly.; Can use local-first research artifacts to keep validation moving without a large team.; Use specificity as the wedge: one buyer, one workflow, one measurable result.; Show proof earlier than broad competitors with before-and-after examples and small pilot data.; Keep implementation lighter than incumbent suites or generic AI assistants.; Concierge review or paid template. Link the output to the Idea Builder prompt and do not expand beyond the first validated workflow.