# Audience Intelligence: Evidence packager for disputing fake reviews

Local business owner hit by fake or malicious reviews 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
- **Local business owner hit by fake or malicious reviews**: Platforms remove fake reviews only with documented evidence, and owners don't know what evidence works - so defamatory reviews from non-customers sit on the profile bleeding bookings while removal requests get denied. Trigger: The FTC's 2024 fake-review rule and platform policy tightening created explicit standards for what constitutes a removable review. Budget signal: Per-dispute pricing plus a monitoring subscription for multi-location businesses.
- **Budget owner who feels the operational cost of the broken workflow.**: Platform dispute-process changes can invalidate the playbook overnight. 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.**: Reputation-management incumbents could add structured disputes as a feature. Trigger: Per-dispute pricing plus a monitoring subscription for multi-location businesses. Budget signal: $99-$1,000/year add-on
- **Local business owner hit by fake or malicious reviews who still run the workflow in spreadsheets, generic docs, email, or chat threads.**: Platforms remove fake reviews only with documented evidence, and owners don't know what evidence works - so defamatory reviews from non-customers sit on the profile bleeding bookings while removal requests get denied. 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 Local business reputation tools 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 Local business owner hit by fake or malicious reviews 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
`evidence workflow`, `packager validation`, `evidence ai`, `packager automation`, `smb`, `reputation`, `Local business reputation tools`

## Messaging Angles
- Evidence packager for disputing fake reviews should be tested as a narrow first-win workflow for one buyer: Local business owner hit by fake or malicious reviews.
- 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
- Platform dispute-process changes can invalidate the playbook overnight.
- Reputation-management incumbents could add structured disputes as a feature.
- 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.