# Decision Memo: Postpartum recovery guide matched to delivery type Full report: https://ideanavigatorai.com/ideas/postpartum-guide-by-delivery-type/ Recorded: Not recorded ## Decision - Team verdict: Park - Validation verdict: Research (55/100) - Confidence: 44% - Recommendation: Keep this parked until the team has evidence for the next validation step: Pilot with two hundred new mothers segmented by delivery type and measure engagement through week six plus escalation-checklist usage. ## Team rationale No team rationale recorded yet. ## Reviewers - No named reviewers recorded. ## Source anchors - Buyer: New mother whose recovery doesn't match the generic pamphlet - Market: Maternal health apps - Problem: Recovery from an unplanned C-section, a fourth-degree tear, or a hemorrhage differs radically, yet discharge guidance is one-size-fits-all - leaving mothers googling symptoms at 3am to learn what's normal for their delivery. - Thesis: Postpartum recovery guide matched to delivery type should be tested as a narrow first-win workflow for one buyer: New mother whose recovery doesn't match the generic pamphlet. - Source: https://www.acog.org/ - Source: https://en.wikipedia.org/wiki/Caesarean_section ## Validation rubric Rubric version: INAV-VALIDATION-2026-06-04 ### Demand signal - 4.7/10 (24% weight) Demand looks weak because the report has 2 source-backed signal(s), an editorial confidence of 44/100, and a defined buyer in Maternal health apps. - Recovery timelines and complication risks differ substantially by delivery mode and intervention, documented across obstetric literature. - Target buyer: New mother whose recovery doesn't match the generic pamphlet ### Problem severity - 5/10 (22% weight) Problem severity is weak when the buyer pain, customer value, and dream-outcome scores are combined. - Recovery from an unplanned C-section, a fourth-degree tear, or a hemorrhage differs radically, yet discharge guidance is one-size-fits-all - leaving mothers googling symptoms at 3am to learn what's normal for their delivery. - Recovery timelines and complication risks differ substantially by delivery mode and intervention, documented across obstetric literature. ### Willingness to pay - 5.5/10 (20% weight) Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections. - Consumer subscription plus hospital-discharge licensing as a patient-education tool. - Pilot with two hundred new mothers segmented by delivery type and measure engagement through week six plus escalation-checklist usage. ### Competitive saturation - 5.3/10 (18% weight) No source-backed direct match is recorded yet, so saturation risk is treated as unknown rather than proof of novelty. - Existing-product check has no named direct match. - Competitive score rewards a narrow wedge, not absence of research. ### Feasibility - 7.8/10 (16% weight) Feasibility is strong for a low build if the MVP is limited to the first measurable workflow. - Pilot with two hundred new mothers segmented by delivery type and measure engagement through week six plus escalation-checklist usage. - Overlaps the already-published Firstweeks idea; differentiation must stay on delivery-type specificity. ## Market gap Underserved segments: - New mother whose recovery doesn't match the generic pamphlet who still run the workflow in spreadsheets, generic docs, email, or chat threads. - Small teams in Maternal health apps that feel the pain weekly but are too narrow for broad incumbents. - New adopters who need guided proof before committing to a larger platform. Feature gaps: - A narrow workflow that reaches value without configuration-heavy onboarding. - A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved. - A handoff path from manual concierge service to repeatable software. Differentiation levers: - Use specificity as the wedge: one buyer, one workflow, one measurable result. - Show proof earlier than broad competitors with before-and-after examples and small pilot data. - Keep implementation lighter than incumbent suites or generic AI assistants. ## Roast and risks Interesting hypothesis, but it needs sharper demand evidence before build time. Blind spots: - Overlaps the already-published Firstweeks idea; differentiation must stay on delivery-type specificity. - A broad AI assistant can flatten differentiation unless the wedge is painfully specific. - The first release can become a generic dashboard if the job is not named tightly. Hard questions: - Who wakes up already trying to solve this? - What do they stop paying for or stop doing when this works? - What proof would make a skeptical buyer trust it in one screen? - What is the smallest paid version of this idea? ## Kill criteria - Fewer than five qualified buyers agree to discuss the workflow after targeted outreach. - No buyer can name a current cost in time, money, risk, or reputation. - The first demo does not produce a clear next step, paid pilot, or specific objection. ## Offer ladder - **Lead magnet (Free)**: Postpartum Recovery Guide Matched To Delivery Type checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps New mother whose recovery doesn't match the generic pamphlet audit the painful workflow before buying software. - **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted. - **Core offer ($49-$499/month)**: Postpartum recovery guide matched to delivery type focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop. - **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk. - **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.