# Audience Intelligence: Postpartum recovery guide matched to delivery type

New mother whose recovery doesn't match the generic pamphlet is the first audience because the report already names a repeated pain, reachable channels, and a validation test that can be run before software is complete.

## Segments
- **New mother whose recovery doesn't match the generic pamphlet**: 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. Trigger: Recovery timelines and complication risks differ substantially by delivery mode and intervention, documented across obstetric literature. Budget signal: Consumer subscription plus hospital-discharge licensing as a patient-education tool.
- **Budget owner who feels the operational cost of the broken workflow.**: Overlaps the already-published Firstweeks idea; differentiation must stay on delivery-type specificity. Trigger: AI-assisted product work and managed infrastructure reduce the first-version cost. Budget signal: $49-$499/month
- **Hands-on operator willing to pilot a narrow tool before a full rollout.**: Clinical content maintenance requires OB review cadence. Trigger: Consumer subscription plus hospital-discharge licensing as a patient-education tool. Budget signal: $99-$1,000/year add-on
- **New mother whose recovery doesn't match the generic pamphlet who still run the workflow in spreadsheets, generic docs, email, or chat threads.**: 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. Trigger: The wedge is specific enough to test without claiming the whole market. Budget signal: Custom

## Channels
- **Reddit / forums**: Look for complaints, workarounds, and repeated questions. First move: Post a problem teardown for Maternal health apps and ask how people solve it today.
- **Launch communities**: Launch traction shows whether the promise is legible. First move: Ship a narrow demo and watch which promise gets clicks.
- **Review and alternative pages**: Pricing and alternatives expose buyer objections. First move: Write an alternatives page that owns one narrow use case.
- **Community pain posts**: Use communities and forums where New mother whose recovery doesn't match the generic pamphlet already describe the painful workflow. First move: Problem teardown, interview ask, and short demo clip
- **Direct outreach**: Direct conversations are the fastest way to verify budget ownership and switching cost. First move: Concierge pilot offer with a manually prepared sample

## Intent Keywords
`postpartum workflow`, `recovery validation`, `postpartum ai`, `recovery automation`, `postpartum`, `maternal`, `Maternal health apps`

## Messaging Angles
- 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.
- Replace a narrow workflow that reaches value without configuration-heavy onboarding. with a focused first-win workflow.
- Promise proof around problem resonance: 5+ calls or 10+ detailed replies..
- De-risk adoption with concierge review or paid template.

## Objections
- Overlaps the already-published Firstweeks idea; differentiation must stay on delivery-type specificity.
- Clinical content maintenance requires OB review cadence.
- Needs real buyer access, not only desk research.
- Needs proof of budget or repeated urgency.
- Needs a crisp wedge before broad product work starts.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.