# Audience Intelligence: Right-sized planning checklist for 30-guest weddings

Couple planning a micro-wedding of around 30 guests 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
- **Couple planning a micro-wedding of around 30 guests**: Mainstream wedding planners assume 150-plus guests with vendors, seating charts, and budgets that overwhelm a couple hosting an intimate 30-person ceremony who just need a simple, scaled-down checklist. Trigger: Micro-weddings of around 30 guests have grown as a deliberate choice for cost and intimacy. Budget signal: One-time fee for the full planning checklist and timeline.
- **Budget owner who feels the operational cost of the broken workflow.**: The micro-wedding niche may be too small or too one-time to sustain recurring revenue. 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.**: Large incumbents could add a small-wedding template and remove the differentiation. Trigger: One-time fee for the full planning checklist and timeline. Budget signal: $99-$1,000/year add-on
- **Couple planning a micro-wedding of around 30 guests who still run the workflow in spreadsheets, generic docs, email, or chat threads.**: Mainstream wedding planners assume 150-plus guests with vendors, seating charts, and budgets that overwhelm a couple hosting an intimate 30-person ceremony who just need a simple, scaled-down checklist. 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 Wedding planning software 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 Couple planning a micro-wedding of around 30 guests 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
`right workflow`, `sized validation`, `right ai`, `sized automation`, `wedding`, `micro-wedding`, `planning`, `Wedding planning software`

## Messaging Angles
- Right-sized planning checklist for 30-guest weddings should be tested as a narrow first-win workflow for Couple planning a micro-wedding of around 30 guests.
- 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
- The micro-wedding niche may be too small or too one-time to sustain recurring revenue.
- Large incumbents could add a small-wedding template and remove the differentiation.
- 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.