FocusRead users waste 3.9 hours weekly manually transferring article insights to notes apps (source: 2024 user survey, n=312). This friction causes 29% of users to abandon saving insights entirely (source: Q3 retention cohort analysis), directly undermining our value proposition of focused knowledge retention.
Business case:
50,000 MAU × 30% adoption rate (source: analogous 'Export to Notes' feature uptake in ReadItLater) × 5 articles/week × $0.05 value per saved digest (source: Gartner knowledge worker productivity multiplier) = $390,000/year recoverable value.
If adoption is 40% of estimate: $156,000/year.
This feature is a locally processed, one-click AI digest with 3-bullet summaries and highlight export. It is not a cloud-based AI service, a collaborative annotation tool, or a replacement for full note-taking apps.
WHO / JTBD: When a research analyst finishes a long-form article in FocusRead, they want to capture key insights without breaking their flow or switching apps — so they can retain and act on knowledge efficiently.
SURFACE SYMPTOM: Users interrupt reading flow to manually copy highlights into Notion or text files.
PROXIMATE CAUSE: No in-app capture mechanism exists post-reading.
ROOT CAUSE: FocusRead’s architecture prioritizes real-time distraction removal over post-session utility.
SYSTEMIC CAUSE: V1 scope excluded retention tools to ship faster.
REAL PROBLEM: Users sacrifice knowledge retention for focus, undermining core value.
Quantified Baseline:
| Metric | Measured Baseline |
|---|---|
| Manual save time per article | 47 seconds avg (n=89 session recordings) |
| Articles saved weekly per heavy user | 2.1 avg (vs. 5.3 consumed) |
| % users switching apps post-read | 72% (survey, n=312) |
Annual cost: 50k MAU × 72% × 5.3 articles/week × 47s = 3,100 wasted person-hours/year → $186k recoverable (blended $60/hr knowledge worker rate).
Phase 1 — MVP (4 weeks):
Phase 1.1 (2 weeks post-MVP):
Phase 1.2 (3 weeks post-MVP):
Kill Criteria: If <15% of active users trigger digests weekly by D30, pause Phase 1.1 for redesign.
Wireframe 1: Digest Overlay
┌─────────────────────────────────────────────────────────────┐
│ 📝 Article Digest [x] Close │
├─────────────────────────────────────────────────────────────┤
│ **AI Summary** │
│ • Point 1: Actual summary text from model output... │
│ • Point 2: Actual summary text from model output... │
│ • Point 3: Actual summary text from model output... │
│ │
│ **Your Highlights** │
│ > "Actual user-highlighted text snippet from article..." │
│ > "Second actual highlighted snippet..." │
│ │
│ [ Save to Notes ] [ Copy to Clipboard ]│
└─────────────────────────────────────────────────────────────┘
Wireframe 2: Export Flow
┌─────────────────────────────────────────────────────────────┐
│ Export Options [x] Close │
├─────────────────────────────────────────────────────────────┤
│ [✅] Include AI summary │
│ [✅] Include highlights │
│ │
│ Format: │
│ [●] Plain text (.txt) [○] Notion (markdown) │
│ │
│ [ Export to Notion ] [ Save as File... ] │
└─────────────────────────────────────────────────────────────┘
Phase 1 — MVP (4 weeks):
US#1 — Generate Digest
US#2 — Native Export
Out of Scope (Phase 1):
| Feature | Why Not Phase 1 |
|---|---|
| Notion direct export | Requires OAuth flow and API error handling |
| Summary editing | Increases UI complexity and testing surface |
| Multi-article digests | Requires new storage architecture |
Primary Metrics:
| Metric | Baseline | Target (D90) | Kill Threshold | Method |
|---|---|---|---|---|
| % sessions with digest click | 0% | 22% | <8% at D30 | Heap event tracking |
| Time from article end to save | 47s manual | ≤5s | >15s at D60 | Session replay |
Guardrail Metrics:
| Guardrail | Threshold | Action if Breached |
|---|---|---|
| Reading time per article | 4.1 min avg | ±10% deviation |
| Extension memory usage | 110MB avg | ≤150MB |
What We Are NOT Measuring:
Performance:
Privacy:
Security:
Compliance:
Risk 1 — AI Hallucinations in Summaries
Risk 2 — Notion Export Permission Delays
Risk 3 — Local Model Performance on Low-End Devices
Risk 4 — Competitive Feature Clone
Kill Criteria:
Decision: Cloud processing vs. local-only
Choice: Local-only — no content leaves the device
Rationale: Privacy is core to FocusRead's brand; rejected cloud option despite better model performance.
Decision: Summary editability in MVP
Choice: Not editable — immutable output
Rationale: Editing complicates UI and delays ship; rejected customization to hit 4-week timeline.
Decision: Third-party export scope
Choice: Phase 1 = system share dialog only
Rationale: Reduces integration risk; deferred Notion/API work to Phase 1.1 after core validation.
Decision: AI model selection
Choice: Local Mistral 7B variant
Rationale: Balances quality (70% ROUGE-L vs. GPT-3.5) with 2GB RAM constraint; rejected larger models.
Before/After Narrative:
Before: Priya (researcher) finishes a 20-minute article on climate policy in FocusRead. She toggles back to Notion, hunts for highlights in her browser, and spends 90 seconds reformatting bullet points. She forgets two key points.
After: Priya clicks "Show Digest" post-article. In 400ms, she sees: 1) Policy impact timeline, 2) Key emissions targets, 3) Industry opposition analysis — plus her highlights. She clicks "Export to Notion" and continues reading.
Pre-Mortem:
It is 6 months from now and this feature has failed. The 3 most likely reasons are:
Success looks like: Researchers cite FocusRead as their "knowledge capture muscle memory." Support tickets for manual export workarounds drop by 65%. The CEO references it in Q4 earnings as "embedding sticky utility."