# Audience Intelligence: Guest app with day-of seating lookup and schedule

Engaged couple planning their own wedding 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
- **Engaged couple planning their own wedding**: Guests constantly text the couple asking where they sit, when the ceremony starts, and what to wear, flooding the couple with logistics questions during the most stressful week. Trigger: Wedding websites have become standard, with most couples building one before the event. Budget signal: One-time per-wedding fee paid by the couple.
- **Budget owner who feels the operational cost of the broken workflow.**: Wedding website platforms could add seating and schedule features and absorb the wedge. 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.**: Single-event purchases mean no recurring revenue and high reacquisition cost. Trigger: One-time per-wedding fee paid by the couple. Budget signal: $99-$1,000/year add-on
- **Engaged couple planning their own wedding who still run the workflow in spreadsheets, generic docs, email, or chat threads.**: Guests constantly text the couple asking where they sit, when the ceremony starts, and what to wear, flooding the couple with logistics questions during the most stressful week. 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 technology and guest experience 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 Engaged couple planning their own wedding 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
`guest workflow`, `seating validation`, `guest ai`, `seating automation`, `wedding`, `events`, `guest-experience`, `Wedding technology and guest experience`

## Messaging Angles
- Guest app with day-of seating lookup and schedule should be tested as a narrow first-win workflow for Engaged couple planning their own wedding.
- 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
- Wedding website platforms could add seating and schedule features and absorb the wedge.
- Single-event purchases mean no recurring revenue and high reacquisition cost.
- 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.