# Decision Memo: Evidence packager for disputing fake reviews

Full report: https://ideanavigatorai.com/ideas/fake-review-dispute-packager/
Recorded: Not recorded

## Decision
- Team verdict: Park
- Validation verdict: Research (58/100)
- Confidence: 46%
- Recommendation: Keep this parked until the team has evidence for the next validation step: File fifty disputes across Google and Yelp with packaged evidence and measure removal rate versus owners' self-filed baseline.

## Team rationale
No team rationale recorded yet.

## Reviewers
- No named reviewers recorded.

## Source anchors
- Buyer: Local business owner hit by fake or malicious reviews
- Market: Local business reputation tools
- Problem: 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.
- Thesis: 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.
- Source: https://www.ftc.gov/
- Source: https://en.wikipedia.org/wiki/Customer_review

## Validation rubric
Rubric version: INAV-VALIDATION-2026-06-04

### Demand signal - 4.7/10 (24% weight)
Demand looks weak because the report has 2 source-backed signal(s), an editorial confidence of 46/100, and a defined buyer in Local business reputation tools.

- The FTC's 2024 fake-review rule and platform policy tightening created explicit standards for what constitutes a removable review.
- Target buyer: Local business owner hit by fake or malicious reviews

### Problem severity - 5.3/10 (22% weight)
Problem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.

- 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.
- The FTC's 2024 fake-review rule and platform policy tightening created explicit standards for what constitutes a removable review.

### Willingness to pay - 6/10 (20% weight)
Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.

- Per-dispute pricing plus a monitoring subscription for multi-location businesses.
- File fifty disputes across Google and Yelp with packaged evidence and measure removal rate versus owners' self-filed baseline.

### Competitive saturation - 5.7/10 (18% weight)
No source-backed direct match is recorded yet, so saturation risk is treated as unknown rather than proof of novelty.

- Existing-product check has no named direct match.
- Competitive score rewards a narrow wedge, not absence of research.

### Feasibility - 7.8/10 (16% weight)
Feasibility is strong for a low build if the MVP is limited to the first measurable workflow.

- File fifty disputes across Google and Yelp with packaged evidence and measure removal rate versus owners' self-filed baseline.
- Platform dispute-process changes can invalidate the playbook overnight.

## Market gap
Underserved segments:
- Local business owner hit by fake or malicious reviews who still run the workflow in spreadsheets, generic docs, email, or chat threads.
- Small teams in Local business reputation tools that feel the pain weekly but are too narrow for broad incumbents.
- New adopters who need guided proof before committing to a larger platform.

Feature gaps:
- A narrow workflow that reaches value without configuration-heavy onboarding.
- A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved.
- A handoff path from manual concierge service to repeatable software.

Differentiation levers:
- Use specificity as the wedge: one buyer, one workflow, one measurable result.
- Show proof earlier than broad competitors with before-and-after examples and small pilot data.
- Keep implementation lighter than incumbent suites or generic AI assistants.

## Roast and risks
Interesting hypothesis, but it needs sharper demand evidence before build time.

Blind spots:
- Platform dispute-process changes can invalidate the playbook overnight.
- A broad AI assistant can flatten differentiation unless the wedge is painfully specific.
- The first release can become a generic dashboard if the job is not named tightly.

Hard questions:
- Who wakes up already trying to solve this?
- What do they stop paying for or stop doing when this works?
- What proof would make a skeptical buyer trust it in one screen?
- What is the smallest paid version of this idea?

## Kill criteria
- Fewer than five qualified buyers agree to discuss the workflow after targeted outreach.
- No buyer can name a current cost in time, money, risk, or reputation.
- The first demo does not produce a clear next step, paid pilot, or specific objection.

## Offer ladder
- **Lead magnet (Free)**: Evidence Packager For Disputing Fake Reviews checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps Local business owner hit by fake or malicious reviews audit the painful workflow before buying software.
- **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted.
- **Core offer ($49-$499/month)**: Evidence packager for disputing fake reviews focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop.
- **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk.
- **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.