gitea

2026-01-19 08:32:44 +01:00
parent b4f6a83da0
commit 818779ab07
125 changed files with 32456 additions and 21017 deletions
--- a/findings_market.md
+++ b/findings_market.md
@@ -0,0 +1,441 @@
+# Competitive Intelligence - Website Change Detection Market Analysis
+
+**Analysis Date:** 2026-01-18
+**Source:** ChatGPT Market Crawl (7 competitors: Visualping, Distill, Hexowatch, Wachete, Sken.io, ChangeDetection.io, Fluxguard)
+
+---
+
+## Executive Summary
+
+Der Website Change Detection Markt ist **mature und competitive**. Erfolg hängt ab von:
+1. **Noise Control Quality** (wichtigster Differentiator)
+2. **Workflow Integrations** (Slack/Teams/Webhooks sind Pflicht, nicht optional)
+3. **Proof/History Features** ("Beweise Änderungen" > "Sieh Änderungen")
+4. **Use-Case-spezifisches Marketing** (SEO, Competitor, Policy als Segmente)
+
+**Kritische Erkenntnis:** "Change Detection" allein ist kein USP mehr. Gewinner differenzieren sich durch **weniger False Positives**, **bessere Integrationen** und **AI-gestützte Features**.
+
+---
+
+## 1. Competitive Landscape
+
+| Competitor | Trust Signal | Key Differentiator | Pricing Entry |
+|------------|--------------|-------------------|---------------|
+| **Visualping** | "2M users, 85% Fortune 500" | Enterprise trust, breite Use Cases | Free tier |
+| **Distill.io** | "Millions of monitors tracked" | Conditions/Filters für Noise Control | Free plan |
+| **Hexowatch** | 13+ Monitoring-Typen | Archiving, Multi-Type Monitoring | Trial |
+| **Wachete** | Dynamic Page Focus | JS Rendering, Form Monitoring | Free tier |
+| **Sken.io** | €3/mo Entry | Einfach & günstig, 14-day trial | €3/mo |
+| **ChangeDetection.io** | Restock Alerts Focus | Consumer/Smart Shoppers | $8.99/mo |
+| **Fluxguard** | Enterprise/AI Focus | AI Filtering & Summaries, Sales-led | 7-day trial |
+
+---
+
+## 2. Core Value Propositions (Ranked)
+
+### Was der Markt verspricht (in Reihenfolge der Prominenz):
+
+1. **"Sofort wissen, wenn etwas Wichtiges passiert"**
+   → Alerts/Integrations (Slack/Teams/Webhooks) sind **prominentes Feature**, nicht Afterthought
+
+2. **"Weniger Lärm/False Alerts"**
+   → Conditions/Filter/AI Filtering als Kern-Differentiator
+
+3. **"Änderungen verstehen & belegen"**
+   → Compare/History/Snapshots/Versions (Audit-Trail, Compliance)
+
+4. **"Wettbewerb & Märkte schneller beobachten"**
+   → Competitive Intelligence / Pricing/Product Launches
+
+5. **"Risiko/Compliance/Security absichern"**
+   → Policy/Legal/Defacement/Compliance Monitoring
+
+---
+
+## 3. Top Use Cases (Jobs-to-be-Done)
+
+### Primary Use Cases (direkt von Competitor-Homepages):
+
+1. **Competitor Monitoring** 🔥
+   "Sag mir, wenn Wettbewerber Preise/Angebote/Produkte ändern"
+
+2. **SEO Monitoring** 🔥
+   "Sag mir, wenn Content/SERPs sich ändern, bevor Rankings leiden"
+
+3. **Policy/Legal Tracking** 🔥
+   "Sag mir, wenn Policy/Regulatory Content updated wird"
+
+4. **Stock/Availability Monitoring** 🔥
+   "Sag mir, wenn Restock/Availability sich ändert"
+
+5. **Job Postings Monitoring**
+   "Sag mir, wenn neue Job Postings erscheinen"
+
+### Segmente nach Buyer Persona:
+
+- **SEO/Growth Teams** (SMB → Mid-Market): Competitor + SERP Changes
+- **E-Commerce Ops**: Pricing, Stock von Wettbewerbern
+- **Compliance/Legal**: Policy-Änderungen dokumentieren
+- **Job Seekers** (Consumer): Career Pages tracken
+
+---
+
+## 4. KRITISCHE Gaps in unserem Plan
+
+### ❌ Gap #1: Integrations zu spät (MOST CRITICAL)
+
+**Markt-Evidence:**
+- Visualping, Wachete, ChangeDetection zeigen **Slack/Teams/Webhooks** prominent auf Homepage
+- Integrations sind **Core Feature**, nicht "Nice to have"
+
+**Unser Plan:**
+- Integrations für **V2 (Week 13-15)** geplant ❌
+
+**Recommendation:**
+- **Webhooks** → MVP (Week 3) ✅
+- **Slack** → V1 (Week 7-8) ✅
+- **Teams/Discord** → V2 (wie geplant)
+
+**Reasoning:** Users wollen Alerts in ihren Workflow-Tools, nicht nur Email. Ohne Integrations verlieren wir Pro-Tier-Conversions.
+
+---
+
+### ⚠️ Gap #2: Dynamic Pages/JS-Rendering unterschätzt
+
+**Markt-Evidence:**
+- Wachete: "Monitor dynamic JavaScript pages" als Core Feature
+- Fluxguard: "Form tracking behind logins" als Differentiator
+
+**Unser Plan:**
+- "Complex Page Support" für **V2 (Week 12-13)**
+
+**Recommendation:**
+- **Basic JS-Rendering Toggle** → V1 (Week 7) als optionales Feature
+- Full "Behind Login" Support → V2 (wie geplant)
+
+**Reasoning:** Moderne Sites sind JS-heavy. Ohne JS-Rendering können wir viele relevante Sites nicht monitoren.
+
+---
+
+### ⚠️ Gap #3: History/Snapshots als "Proof" Feature
+
+**Markt-Evidence:**
+- Sken: "Compare versions" prominent featured
+- Fluxguard: "Versions kept" als Selling Point
+- Messaging: **"Beweise was sich geändert hat"** > "Sieh Änderungen"
+
+**Unser Plan:**
+- Diff Viewer im MVP ✅
+- Aber Messaging betont nicht **"Audit-proof history"**
+
+**Recommendation:**
+- Messaging-Update: Fokus auf **"Prove changes"** statt nur "See changes"
+- Snapshot Retention prominent in Pricing-Tiers zeigen
+
+---
+
+### ⚠️ Gap #4: Pricing Model - Checks/Month vs. Monitors
+
+**Markt-Evidence:**
+- **Sken:** Checks/month model (z.B. "10,000 checks/mo")
+- **Fluxguard:** Hybrid (Sites + Checks/month)
+- **Unser Plan:** Monitors + Frequency
+
+**Problem:**
+- 50 Monitors à 5min = **14,400 checks/day** = sehr teuer
+- 50 Monitors à 1hr = **1,200 checks/day** = viel günstiger
+- **Gleicher Preis für völlig unterschiedliche Kosten** → nicht nachhaltig
+
+**Options:**
+
+#### Option A: Checks/Month (Fairest)
+```
+Free:     1,000 checks/mo   (~3 monitors à 1hr)
+Pro:      10,000 checks/mo  (~50 monitors à 1hr OR 10 à 5min)
+Business: 50,000 checks/mo  (~200 monitors à 1hr OR 40 à 5min)
+```
+**Pros:** Fair, scales with costs, clear value
+**Cons:** Schwerer zu erklären für User
+
+#### Option B: Hybrid (Monitors + Check Cap)
+```
+Pro: 50 monitors, max 15k checks/mo
+```
+**Pros:** Einfach zu verstehen, verhindert Abuse
+**Cons:** User hit Caps unpredictably
+
+#### Option C: Current Plan (Monitors + Frequency)
+```
+Pro: 50 monitors at 5min frequency
+```
+**Pros:** Easy to understand
+**Cons:** **Unsustainable** cost structure
+
+**Recommendation:** Test **Option A (Checks/Month)** mit ersten Beta-Usern via Survey.
+
+---
+
+## 5. Ideal Customer Profile (ICP) - Validated
+
+### Primary ICP
+
+**SEO & Growth Teams (SMB → Mid-Market)**
+- **Company Size:** 10-200 employees
+- **Role:** SEO Manager, Growth Lead, Content Ops, Product Marketing
+- **Pain:** Konkurrenten ändern Preise/Landingpages ohne dass sie es merken; Rankings droppen durch unbemerkte Site-Änderungen
+- **Trigger:** Ranking Drop, Competitor launcht Feature, SERP Snippet ändert sich
+- **Desired Outcome:** Fast Alerts mit low noise, Proof für Reporting
+- **Budget:** $19-99/mo (Pro/Business tier)
+
+### Secondary ICPs
+
+**E-Commerce Operators**
+- Monitor competitor pricing, stock availability
+- High urgency, brauchen fast frequency (5min)
+
+**Compliance/Legal Teams**
+- Monitor policy changes, regulatory updates
+- Brauchen Audit Trail, History, Snapshots für Proof
+
+**Job Seekers (Consumer)**
+- Monitor Career Pages für neue Postings
+- High Conversion free → paid wenn Feature funktioniert
+
+---
+
+## 6. Messaging & Positioning Updates
+
+### ❌ Current Messaging (zu generisch)
+> "I watch pages so you don't have to"
+
+**Problem:** Zu vage, kommuniziert weder Value noch Use Cases
+
+### ✅ Recommended Messaging
+
+**Option 1: Signal/Noise Focus**
+> "Website change detection that actually works – less noise, more signal, with proof"
+
+**Option 2: Use Case Focus** (Recommended)
+> "Track competitor changes, SEO updates & policy shifts – automatically filtered, instantly alerted"
+
+**Option 3: Workflow Focus**
+> "Monitor website changes in Slack/Teams – only get alerts that matter, with full history"
+
+### Updated Tagline
+**Before:** "I watch pages so you don't have to"
+**After:** **"Less noise. More signal. Proof included."**
+
+---
+
+## 7. Competitive Positioning
+
+### vs. Visualping
+- **Their Strength:** Enterprise trust (85% Fortune 500), established brand
+- **Our Angle:** "Better noise control + fairer pricing – without the enterprise bloat"
+- **Messaging:** "Built for teams who need results, not demos"
+
+### vs. Distill.io
+- **Their Strength:** Conditions/Filters, established user base
+- **Our Angle:** "Team features built-in + modern UX – not stuck in 2015"
+- **Messaging:** "Collaboration-first, not an afterthought"
+
+### vs. Fluxguard
+- **Their Strength:** AI summaries, enterprise focus, sales-led
+- **Our Angle:** "Self-serve pricing + instant setup – no demo calls required"
+- **Messaging:** "AI-powered intelligence without the enterprise tax"
+
+### vs. ChangeDetection.io / Sken.io
+- **Their Strength:** Low price ($3-9/mo), simple
+- **Our Angle:** "Advanced features (keywords, integrations, teams) without complexity"
+- **Messaging:** "Powerful, but still simple"
+
+---
+
+## 8. Feature Prioritization Updates
+
+### 🔼 MOVE UP in Priority
+
+| Feature | Old Plan | **New Plan** | Reason |
+|---------|----------|-------------|--------|
+| **Webhooks** | V2 (Week 13) | **MVP (Week 3)** | Core workflow integration |
+| **Slack Integration** | V2 (Week 13) | **V1 (Week 8)** | Strongly demanded by market |
+| **Basic JS-Rendering** | V2 (Week 12) | **V1 (Week 7)** | Modern sites need this |
+
+### ✅ Keep as Planned
+- Noise Reduction (V1) ✅
+- Keyword Alerts (V1) ✅
+- AI Summaries (V2) ✅
+
+---
+
+## 9. Go-to-Market Strategy (Evidence-Based)
+
+### Acquisition Channels (basierend auf Markt-Evidence)
+
+1. **SEO (Long-tail Keywords)** 🔥 PRIMARY
+   - "monitor competitor pricing"
+   - "SEO change detection tool"
+   - "track policy changes automatically"
+   - "website availability monitoring"
+   - **Evidence:** Alle Competitors haben starken SEO-Footprint
+
+2. **Free Tier → Viral Loop** 🔥
+   - Visualping: "Get started it's free"
+   - Distill: Free plan with generous limits
+   - **Strategy:** Hook users mit Free Tier, convert on limits/features
+
+3. **Integration Directories**
+   - Zapier Marketplace
+   - Slack App Directory
+   - Chrome Extension Store (V2)
+
+4. **Content Marketing**
+   - "How to monitor job postings" (Tutorial)
+   - "Competitor price tracking guide" (Playbook)
+   - "SEO monitoring checklist" (Template)
+
+---
+
+## 10. Social Proof Strategy
+
+### Was im Markt funktioniert
+
+- **Visualping:** "Trusted by 2 million users" + "85% of Fortune 500"
+- **Distill:** Usage numbers ("X monitors tracked", "Y happy users")
+- **Fluxguard:** Enterprise logos, Case Studies
+
+### Unsere Strategie (Launch → Growth)
+
+**Launch (Month 1-3):**
+- "Join 500+ users monitoring X pages"
+- Testimonials von Beta Usern
+- Use Case Examples (anonymized)
+
+**Growth (Month 4-12):**
+- "X million checks performed"
+- Customer Logos (mit Permission)
+- Case Studies für jeden Use Case (SEO, Competitor, Policy)
+
+**Scale (Year 2+):**
+- Industry Benchmarks
+- "Most trusted by [segment]"
+- Awards/Certifications
+
+---
+
+## 11. Open Questions & Assumptions
+
+### Assumptions to Validate
+
+1. **Use Case Priority**
+   - **Assumption:** SEO monitoring ist #1 use case
+   - **Validate:** Landing Page A/B test (SEO vs Competitor vs Policy Hero)
+
+2. **Noise Reduction Messaging**
+   - **Assumption:** "Less noise" resonates als top pain
+   - **Validate:** Survey Beta Users: "Was frustriert dich am meisten bei Competitors?"
+
+3. **Pricing Model**
+   - **Assumption:** Checks/month ist klarer als monitors
+   - **Validate:** Pricing Page Tests mit verschiedenen Modellen
+
+4. **Integration Priority**
+   - **Assumption:** Slack > Teams > Discord
+   - **Validate:** Survey "Welches Tool nutzt du für Alerts?"
+
+5. **JS-Rendering Demand**
+   - **Assumption:** 40%+ der Use Cases brauchen JS rendering
+   - **Validate:** Track "Page failed to load" Errors in Beta
+
+---
+
+## 12. Action Items
+
+### 🚨 Immediate (Before Further Development)
+
+- [ ] **Update Messaging** in Landing Page Copy
+  - Hero: "Less noise. More signal. Proof included."
+  - Use Cases: SEO, Competitor, Policy prominent
+
+- [ ] **Update Roadmap** (task.md)
+  - Move Webhooks to MVP
+  - Move Slack to V1
+  - Add JS-Rendering option to V1
+
+- [ ] **Decide on Pricing Model**
+  - Create mockups: Checks/month vs Monitors
+  - Survey target users (LinkedIn outreach)
+
+- [ ] **Update Competitive Positioning** (CLAUDE.md)
+  - Add vs. Visualping, Distill, Fluxguard sections
+
+### 📅 Short-term (Next 2 Weeks)
+
+- [ ] Create **Use-Case Landing Pages**
+  - /use-cases/seo-monitoring
+  - /use-cases/competitor-tracking
+  - /use-cases/policy-compliance
+
+- [ ] Build **Comparison Pages**
+  - /vs/visualping
+  - /vs/distill
+  - /vs/fluxguard
+
+- [ ] Set up **Beta User Survey**
+  - Top frustration with current tools
+  - Pricing model preference
+  - Alert channel preference
+
+---
+
+## 13. Confidence & Limitations
+
+### Confidence Level: **Medium-High (75%)**
+
+**Why Medium-High:**
+- Data ist von **Proxy Competitors** (nicht direct user research) ⚠️
+- Use Cases validated across 7 competitors ✅
+- Pricing models vary (kein clear winner) ⚠️
+- Free tier + self-serve is universal ✅
+
+**Was würde Confidence erhöhen:**
+- User Interviews mit target ICP (SEO/Growth Teams)
+- Competitor User Reviews (G2, Capterra scrape)
+- Pricing Tests mit real landing page traffic
+
+### Limitations
+
+1. **No Direct User Research** – Alle Insights inferred von competitor sites
+2. **No Revenue Data** – Können nicht validieren welches Pricing Model am besten funktioniert
+3. **No Churn Data** – Don't know what causes users to leave competitors
+4. **Limited Feature Usage Data** – Don't know which features drive retention
+
+---
+
+## 14. Summary & Next Steps
+
+### ✅ Was die Analyse bestätigt (gut aligned)
+
+1. **Noise Reduction als Differentiator** ✅
+2. **Keyword-based Alerts** als High-Value Feature ✅
+3. **Use Cases klar definiert** (SEO, Competitor, Policy, Stock, Jobs) ✅
+4. **Free tier + Self-serve Funnel** ✅
+
+### ❌ Was wir ändern müssen
+
+1. **Integrations früher** (Webhooks → MVP, Slack → V1) 🔥
+2. **Pricing Model überdenken** (Checks/month fairer) 🔥
+3. **Messaging schärfen** (Use-Case-fokussiert) 🔥
+4. **JS-Rendering früher** (V1 statt V2) ⚠️
+
+### 🎯 Recommended Actions (in Order)
+
+1. **Update task.md** mit neuen Feature-Priorities
+2. **Update CLAUDE.md** mit geschärftem Messaging
+3. **Create Killer Landing Page** mit Frontend-Design Skill
+4. **Launch Beta** mit 50 Users zur Validation
+
+---
+
+**Last Updated:** 2026-01-18
+**Next Review:** After first 50 beta signups