Plainly Discovery Phase 1 — Meeting-Assistant Complaint Mining (Privacy Wedge)

Product Strategy May 17, 2026 by research-lead

#plainly #complaint-mining #fake-door #problem-gate #privacy #meeting-assistant #local-first

Plainly Discovery Phase 1 — Meeting-Assistant Complaint Mining

Paperclip issue: MOKA-2798 (status: done) Follow-up issue: [MOKA-2805] Plainly Phase 2: Concierge sprint Methodology: docs/guidelines/product-discovery.md — Problem Gate Verdict: REVIVE with Concierge Validation (conditional green light)

This report reconstructs the Research Lead’s deliverable that was originally emitted to a sandbox path (/tmp/paperclip-skills-03e1fz/) and lost when the sandbox was cleaned up. Source of truth: the Paperclip comment on MOKA-2798 from 2026-05-17T20:12 by agent d5fcce9a. The 12-row raw JSON dataset is no longer recoverable; Problem Opportunity Cards below are reconstructed from the comment summary, not the JSON.

Status

Status: COMPLAINT MINING DELIVERED
Recommendation: REVIVE Plainly with Concierge Validation (conditional green light)
Provides external evidence that contradicts the kill in MOKA-2779 (2026-05-14, reverted by founder 2026-05-15)

Mining Scope

Competitors covered (10): Otter, Fathom, Granola, Fireflies, Read AI, Limitless, tl;dv, Krisp, Cogito, Avoma (per the issue brief; specific per-competitor counts in the lost JSON)
Sources: G2/Capterra reviews, Reddit (r/productivity, r/notetaking, r/Privacy, r/macapps), Hacker News threads, Product Hunt launch comments, App Store reviews, YouTube/Twitter signals, 2025 federal lawsuit filings
Complaints extracted: 12 (across 10 competitors)
Clusters identified: 6, ranked by severity
Privacy-vs-general split: 92% privacy-related vs 8% general meeting-tool pain

Key Findings

Finding	Evidence	Implication
Privacy wedge is REAL	Federal lawsuits on Otter/Fireflies	Not a niche concern — legal liability is the wedge
92% of complaints are privacy-related	Cluster analysis across 10 competitors	Strong signal for local-first positioning
Competitors are structurally exposed	Cloud-dependent architecture	Cannot retroactively go local-first
Plainly occupies empty cell	No 100% on-device + PM + macOS competitor	Defensible position if validated

Recommendation: REVIVE with Concierge Validation (Option B)

Sprint window: 2026-05-20 → 2026-06-19 (30 days)
Owner: Founder (delivery), CPO (brief design), Research Lead (measurement)
Engineering commitment: ZERO until concierge validates
Green-light criteria: 8/10 adoption rate, 5/10 retention rate, 0 trust/confidentiality concerns raised by participants

Why the prior kill (MOKA-2779) was correct at the time

14 days of internal validation produced zero external evidence.
Without a concrete pain cluster, “privacy-first meeting tool” was a thesis, not a wedge.

Why revive now

Legal signals are external validation that privacy pain is escalating, not static.
Federal litigation against Otter and Fireflies makes the wedge legally and reputationally tangible.
Cloud competitors cannot easily fix this — their entire architecture assumes data leaves the device.

Methodology Compliance

Gate Step	Status
Problem Gate (Complaint Mining)	✅ Complete
LLM extraction with strict JSON schema	✅ Complete
Complaint-RICE prioritization	✅ Complete
Prototype-First delivery (3 artifacts)	✅ Complete
Decision memo with go/no-go criteria	✅ Complete

Next Actions

CPO reviews recommendation by 2026-05-19 — drafts Concierge Brief in MOKA-2805 (in flight as of 2026-05-17 21:55; status blocked after Paperclip restart, needs re-dispatch).
If approved → founder owns outreach + concierge delivery for 30 days, CPO measures, Research Lead tracks signal.
If rejected → close MOKA-2805, archive Plainly. Document the rejection rationale.

What Was Lost (For Audit)

The original delivery referenced three sandbox artifacts:

/tmp/paperclip-skills-03e1fz/plainly-privacy-complaints.json — 12-row complaint dataset
/tmp/paperclip-skills-03e1fz/plainly-problem-cards.md — full Problem Opportunity Cards (with evidence quotes, persona, hypothesis sections per template)
/tmp/paperclip-skills-03e1fz/plainly-kill-or-revive-recommendation.md — full decision memo

The sandbox directory was deleted before commit-to-repo. This report preserves the executive summary; the underlying complaint dataset and full per-card details are not recoverable from the Paperclip comment alone. Re-run Phase 1 if granular review of the 12 complaints becomes necessary for Concierge design.

Quality Scorecard

Dimension	Score	Notes
Sources (20%)	14/20	10 competitors covered, 2025 federal litigation cited — but specific source URLs lost with the sandbox
Quantified claims (20%)	14/20	RICE scores, 92/8% split, n=12 complaints — quantified, but raw dataset not recoverable for audit
Competitive depth (15%)	12/15	10 named competitors with positioning analysis
Actionability (20%)	18/20	Direct go/no-go criteria, sprint window, owner assignments
Recency (10%)	9/10	2025 lawsuits cited (very recent)
Counter-arguments (15%)	11/15	Acknowledges the prior kill (MOKA-2779) was correct at the time; lists what would re-kill (rejection path)
Total	78/100	Above 70 floor. Lost-sandbox issue caps it from being higher.

References

Source Paperclip comment: MOKA-2798 (issue id 8c5bfcfd-5e70-412c-bfc8-d36090c066b8), author d5fcce9a (Research Lead), 2026-05-17T20:12 UTC
Prior kill: MOKA-2779 (2026-05-14, reverted by founder 2026-05-15)
Methodology: moklabs/docs/guidelines/product-discovery.md
Problem Opportunity Card template: moklabs/docs/templates/problem-opportunity-card.md
Concierge brief follow-up: MOKA-2805 (status: blocked, needs re-dispatch after Paperclip restart 2026-05-17 22:43)