# Audience Intelligence: RSVP-and-payment co-host tool for supper club hosts

Independent supper-club or salon host running recurring paid dinners 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
- **Independent supper-club or salon host running recurring paid dinners**: Hosts of private salons and supper clubs juggle RSVPs, dietary restrictions, payments, and waitlists across DMs and spreadsheets, with no tool built for invite-only recurring gatherings. Trigger: Invite-only supper clubs and salons increasingly charge guests and run recurring seatings. Budget signal: Per-seat service fee or flat monthly host subscription.
- **Budget owner who feels the operational cost of the broken workflow.**: Hosts may prefer free general tools like Partiful or Eventbrite and resist paying. 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.**: Collecting payments introduces refund, chargeback, and tax handling complexity early. Trigger: Per-seat service fee or flat monthly host subscription. Budget signal: $99-$1,000/year add-on
- **Independent supper-club or salon host running recurring paid dinners who still run the workflow in spreadsheets, generic docs, email, or chat threads.**: Hosts of private salons and supper clubs juggle RSVPs, dietary restrictions, payments, and waitlists across DMs and spreadsheets, with no tool built for invite-only recurring gatherings. 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 Private events and community hosting 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 Independent supper-club or salon host running recurring paid dinners 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
`rsvp workflow`, `payment validation`, `rsvp ai`, `payment automation`, `events`, `hosting`, `community`, `Private events and community hosting`

## Messaging Angles
- RSVP-and-payment co-host tool for supper club hosts should be tested as a narrow first-win workflow for Independent supper-club or salon host running recurring paid dinners.
- 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
- Hosts may prefer free general tools like Partiful or Eventbrite and resist paying.
- Collecting payments introduces refund, chargeback, and tax handling complexity early.
- 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.