Rebuild as InnungsApp project: replace stadtwerke analysis with full documentation
- PRD: vollständige Produktspezifikation (5 Module, Scope, Akzeptanzkriterien) - ARCHITECTURE: Tech Stack, Ordnerstruktur, Multi-Tenancy, Push, Kosten - DATABASE_SCHEMA: Vollständiges SQL-Schema mit RLS Policies und Views - USER_STORIES: 40+ Stories nach Rolle (Admin, Mitglied, Azubi, Obermeister) - PERSONAS: 5 detaillierte Nutzerprofile mit Alltag, Zitaten und Erwartungen - BUSINESS_MODEL: Preistabellen, Unit Economics, Revenue-Projektionen, Distribution - ROADMAP: 6 Phasen, Sprint-Planung, Meilensteine und KPIs - COMPETITIVE_ANALYSIS: Wettbewerbsmatrix, USPs, Preispositionierung - API_DESIGN: Supabase Query Patterns, Edge Functions, Realtime Subscriptions - ONBOARDING_FLOWS: 7 User Flows von Setup bis Fehlerfall - GTM_STRATEGY: 3-Phasen-Vertrieb, Outreach-Sequenz, Einwandbehandlung - AZUBI_MODULE: Video-Feed, 1-Click-Apply, Chat, Berichtsheft, Quiz - DSGVO_KONZEPT: Rechtsgrundlagen, TOMs, AVV, Minderjährige, Incident Response - FEATURES_BACKLOG: 72 Features nach MoSCoW + Technische Schulden Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Timo Knuth
@@ -1,560 +1,250 @@
|
||||
# VALIDATION PLAYBOOK
|
||||
# InnungsApp — Validation Playbook
|
||||
|
||||
**Ziel:** Schnell validieren, ob SmartMeter-App ein echtes Problem löst
|
||||
**Dauer:** 2-3 Wochen
|
||||
**Output:** GO/NO-GO Entscheidung mit Daten
|
||||
> **Ziel:** Hypothesen vor großen Investitionen mit echten Nutzern validieren
|
||||
|
||||
---
|
||||
|
||||
## PHASE 0: Interviews mit Entscheidungsträgern
|
||||
## 1. Kern-Hypothesen
|
||||
|
||||
### Zielgruppe
|
||||
| # | Hypothese | Validierungsmethode | Zielwert |
|
||||
|---|---|---|---|
|
||||
| H1 | Innungen zahlen 99–199 €/Monat für eine bessere App | Pilot-Conversion | ≥ 60 % Pilot → Paid |
|
||||
| H2 | Mitglieder loggen sich aktiv ein (kein "Geisterprojekt") | WAU-Rate | ≥ 40 % der eingeladenen Mitglieder |
|
||||
| H3 | Push-Notifications erhöhen Leserate vs. E-Mail | A/B-Test (Piloten) | Push-Leserate ≥ 2x E-Mail |
|
||||
| H4 | Azubis nutzen die Lehrlingsbörse ohne Login | Analytics | ≥ 50 % der Aufrufe ohne Auth |
|
||||
| H5 | Betriebe stellen Stellen selbst ein (kein Admin-Overhead) | Feature-Nutzung | ≥ 70 % Stellen vom Betrieb selbst |
|
||||
| H6 | HWK sind bereit, InnungsApp zu empfehlen | HWK-Gespräche | 1 LOI innerhalb 6 Monate |
|
||||
|
||||
```
|
||||
Pro Stadtwerk: 2-3 Personen
|
||||
1. IT-Leiter (Technical, Integration-Fragen)
|
||||
2. Kundenservice-Leiter oder Betriebsleiter (Use Case, ROI)
|
||||
3. CFO/Geschäftsführer (Budget, Priority)
|
||||
|
||||
Total Target: 10-15 Stadtwerke
|
||||
= 20-45 Interviews
|
||||
```
|
||||
|
||||
### Kontakt-Strategie
|
||||
|
||||
**Tiered Approach:**
|
||||
|
||||
```
|
||||
Tier 1 (Known): Bestehende Kontakte
|
||||
- LinkedIn Outreach zu IT Directors
|
||||
- Existierende Geschäftspartner
|
||||
- Networking Events (VKU)
|
||||
|
||||
Tier 2 (Warm): Via Referrals
|
||||
- Ask friends/advisors for intros
|
||||
- Chamber of Commerce
|
||||
- Industry associations
|
||||
|
||||
Tier 3 (Cold): Direct Outreach
|
||||
- LinkedIn Messages
|
||||
- Email to general contacts
|
||||
- VKU member database
|
||||
|
||||
Template Email:
|
||||
---
|
||||
Subject: 15-Min Interview: Smart Meter Lösung für Stadtwerke
|
||||
|
||||
Hallo [Name],
|
||||
## 2. Phase 0: Pre-Product Validation (vor der ersten Zeile Code)
|
||||
|
||||
wir entwickeln eine mobile App zur automatisierten Zählerablesung
|
||||
für Stadtwerke. [Your Company] hat Expertise in diesem Bereich und
|
||||
wir möchten von dir lernen.
|
||||
### Customer Discovery Interviews
|
||||
|
||||
Hätte du Zeit für ein 15-Min Call diese Woche? Gerne telefonisch
|
||||
oder per Zoom.
|
||||
**Ziel:** Verstehen ob das Problem real und schmerzhaft genug ist.
|
||||
|
||||
**Zielgruppe:** 10 Innungsgeschäftsführer, 5 Obermeister, 5 Mitglieder
|
||||
|
||||
**Interview-Struktur (30 Minuten):**
|
||||
|
||||
```
|
||||
Teil 1: Kontext verstehen (10 Min.)
|
||||
──────────────────────────────────
|
||||
"Beschreiben Sie mir, wie ein typischer Montag für Sie aussieht."
|
||||
"Wie verwalten Sie aktuell die Mitglieder Ihrer Innung?"
|
||||
"Wie kommunizieren Sie mit Mitgliedern — welche Tools nutzen Sie?"
|
||||
"Wie oft haben Sie Kontakt zu einzelnen Mitgliedern?"
|
||||
"Erzählen Sie mir von einem konkreten Moment, wo die Kommunikation schiefgelaufen ist."
|
||||
|
||||
Teil 2: Pain Points herausarbeiten (10 Min.)
|
||||
────────────────────────────────────────────
|
||||
"Was kostet Sie die meiste Zeit bei der Innungsarbeit?"
|
||||
"Wenn Sie eine Sache sofort verbessern könnten, was wäre das?"
|
||||
"Wie viele Stunden pro Woche verbringen Sie mit Verwaltungsaufgaben?"
|
||||
"Was passiert, wenn ein Mitglied Sie wegen etwas anruft, das es selbst nachschlagen könnte?"
|
||||
"Haben Sie schon andere Tools probiert? Was hat nicht funktioniert?"
|
||||
|
||||
Teil 3: Lösung sondieren (10 Min.)
|
||||
───────────────────────────────────
|
||||
[Figma Prototype / Mockup zeigen]
|
||||
"Wenn ich Ihnen eine App zeige, die X und Y macht — was würden Sie als erstes tippen?"
|
||||
"Was fehlt hier, was Sie erwartet hätten?"
|
||||
"Was würden Sie daran anders machen?"
|
||||
"Wenn diese App heute verfügbar wäre — würden Sie sie testen wollen?"
|
||||
"Was würden Sie für diese Lösung bezahlen?"
|
||||
```
|
||||
|
||||
**Auswertung:**
|
||||
- Probleme die 3+ Personen unaufgefordert nennen = validiert
|
||||
- Zahlungsbereitschaft > 100 €/Monat bei 3+ Personen = validiert
|
||||
|
||||
**Interview-Aufzeichnung:** Notion-Template mit Zitaten, Audio-Mitschnitt (mit Erlaubnis)
|
||||
|
||||
Danke!
|
||||
[Your Name]
|
||||
---
|
||||
|
||||
## 3. Phase 1: MVP Pilot Validation (Monat 1–3)
|
||||
|
||||
### Pilot-Setup
|
||||
|
||||
| Parameter | Wert |
|
||||
|---|---|
|
||||
| Anzahl Pilotinnungen | 5 |
|
||||
| Pilot-Dauer | 3 Monate |
|
||||
| Preis | kostenlos |
|
||||
| Erwartung an Innung | Aktive Nutzung + wöchentlicher Feedback-Call |
|
||||
| Erwartung an uns | Schnelle Bugfixes (< 24h), persönlicher Support |
|
||||
|
||||
### Aktivierungsmetriken (Woche 1 nach Go-Live)
|
||||
|
||||
| KPI | Definition | Zielwert | Alarmsignal |
|
||||
|---|---|---|---|
|
||||
| Einladungsrate | Eingeladene Mitglieder / Gesamt-Mitglieder | ≥ 80 % | < 50 % |
|
||||
| Aktivierungsrate | Eingeloggte Nutzer / Eingeladene | ≥ 60 % | < 30 % |
|
||||
| Time to First Action | Zeit bis erster Aktion nach Login | < 2 Min. | > 5 Min. |
|
||||
| Feature Discovery | Nutzer die ≥ 3 Features genutzt haben | ≥ 50 % | < 20 % |
|
||||
|
||||
### Engagement-Metriken (Monat 1–3)
|
||||
|
||||
| KPI | Definition | Zielwert |
|
||||
|---|---|---|
|
||||
| WAU Rate | Wöchentl. aktive Nutzer / Gesamt-Nutzer | ≥ 40 % |
|
||||
| News Leserate | Gelesen / Empfangen pro Beitrag | ≥ 50 % |
|
||||
| Termin-Anmeldequote | Angemeldete / Eingeladene pro Termin | ≥ 40 % |
|
||||
| Lehrlingsbörse Views | Öffentliche Aufrufe der Stellenliste | > 0 Bewerberkontakte |
|
||||
| NPS (Admin) | Net Promoter Score der Geschäftsführer | ≥ 50 |
|
||||
| NPS (Mitglied) | Net Promoter Score der Mitglieder | ≥ 40 |
|
||||
| Support-Tickets | Kritische Bugs gemeldet | < 2 pro Innung |
|
||||
|
||||
### Wöchentlicher Check-In mit Pilot-Innungen
|
||||
|
||||
**Format:** 20-Minuten-Video-Call, jede Woche
|
||||
|
||||
```
|
||||
Agenda:
|
||||
1. "Was hat gut funktioniert diese Woche?" (5 Min.)
|
||||
2. "Was hat nicht funktioniert / gefehlt?" (5 Min.)
|
||||
3. "Zeigen Sie mir, wie Sie X benutzt haben" (5 Min.)
|
||||
4. "Nächste Woche freischalten wir Feature Y — was erwarten Sie?" (5 Min.)
|
||||
```
|
||||
|
||||
**Dokumentation:** Call-Notizen in Notion → Feature-Feedback → Backlog-Update
|
||||
|
||||
### NPS-Umfrage (nach 6 Wochen)
|
||||
|
||||
**Zeitpunkt:** 6 Wochen nach Go-Live, via In-App-Banner
|
||||
|
||||
**Fragen:**
|
||||
1. "Wie wahrscheinlich ist es, dass Sie InnungsApp einer anderen Innung empfehlen?" (0–10)
|
||||
2. "Was würden Sie sofort verbessern?" (Freitext)
|
||||
3. "Welches Feature ist für Sie am wichtigsten?" (Auswahl + Ranking)
|
||||
|
||||
---
|
||||
|
||||
## 4. Phase 2: Conversion Validation (Monat 3)
|
||||
|
||||
### Pilot → Bezahlt Gespräch
|
||||
|
||||
**Zeitpunkt:** 2 Wochen vor Pilot-Ende
|
||||
|
||||
**Script:**
|
||||
```
|
||||
"Wir sind jetzt 3 Monate dabei. Ich möchte offen mit Ihnen sprechen.
|
||||
Was hat die App für Ihre Innung verändert?
|
||||
[Zuhören, konkrete Beispiele erfragen]
|
||||
|
||||
Basierend auf dem, was ich gesehen habe, glaube ich, dass
|
||||
[konkrete Zahl: z.B. "60 % Ihrer Mitglieder sind wöchentlich aktiv"].
|
||||
|
||||
Wir werden die App nach dem Piloten für 149 €/Monat anbieten.
|
||||
Was braucht es von unserer Seite, damit Sie dabei bleiben?"
|
||||
```
|
||||
|
||||
**Conversion-Trigger:**
|
||||
- Intern: WAU > 40 % UND Leserate > 50 % → hohe Conversion-Wahrscheinlichkeit
|
||||
- Zeige dem Admin seine eigenen Metriken im Gespräch
|
||||
|
||||
**Ziel:** ≥ 3 von 5 Piloten konvertieren
|
||||
|
||||
### Preis-Sensitivität testen
|
||||
|
||||
**Methode:** Van Westendorp Price Sensitivity Meter im Gespräch:
|
||||
|
||||
```
|
||||
"Zu welchem Preis würden Sie sagen, die App ist..."
|
||||
1. "...zu günstig, sodass Sie an der Qualität zweifeln würden?" [€]
|
||||
2. "...günstig — ein gutes Preis-Leistungs-Verhältnis?" [€]
|
||||
3. "...teuer, aber Sie würden es noch überlegen?" [€]
|
||||
4. "...zu teuer — Sie würden es nicht kaufen?" [€]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Interview Guide
|
||||
## 5. Phase 3: Kanal-Validation (Monat 4–6)
|
||||
|
||||
### PART A: Problem Discovery (5 Min)
|
||||
### Hypothese: "Direktakquise funktioniert"
|
||||
|
||||
**Q1: Current State**
|
||||
```
|
||||
"Wie funktioniert eure Zählerablesung heute?"
|
||||
**Test:**
|
||||
- 50 Kaltakquise-E-Mails an Innungen in BW
|
||||
- Tracking: Öffnungsrate, Antwortrate, Demo-Rate, Pilot-Rate
|
||||
|
||||
Expected Answers (flag if they say):
|
||||
- Manual reading by customer
|
||||
- Reading by technician
|
||||
- Automated meter (smart meter)
|
||||
- Mix of the above
|
||||
**Erfolgskriterium:** Pilot-Rate > 10 % (5 von 50)
|
||||
|
||||
Red Flag: If 100% automated already → No problem to solve
|
||||
Green Flag: If manual + high error rate → Good fit
|
||||
```
|
||||
### Hypothese: "LinkedIn-Outreach funktioniert besser als E-Mail"
|
||||
|
||||
**Q2: Problem Validation**
|
||||
```
|
||||
"Wie viel Zeit/Kosten investiert ihr jährlich in Zählerablesung?"
|
||||
**Test:**
|
||||
- 20 E-Mail-Kaltakquise (Kontrollgruppe)
|
||||
- 20 LinkedIn-Direktnachrichten (Testgruppe)
|
||||
- Messen: Antwortrate, Demo-Rate
|
||||
|
||||
Deep Dive:
|
||||
- "Wie viele Zählerstände werden abgelesen pro Jahr?"
|
||||
- "Wer macht das - Mitarbeiter oder Kunden?"
|
||||
- "Wie hoch ist die Fehlerquote?" (Ziel: >20% = pain point)
|
||||
- "Was kostet euch jede manuelle Ablesung?"
|
||||
**Erfolgskriterium:** Einer der Kanäle > 15 % Demo-Rate
|
||||
|
||||
Example Math:
|
||||
- 100K Kunden × 1 reading/year = 100K readings
|
||||
- 30% need manual follow-up = 30K manual readings
|
||||
- @€2 per reading = €60K/year cost
|
||||
### Hypothese: "Zielgruppe sucht aktiv nach Lösung (SEO-Potenzial)"
|
||||
|
||||
Red Flag: Low error rate (<5%) or low cost (<€20K) → not a pain point
|
||||
Green Flag: >20% error rate or >€50K/year cost → worth solving
|
||||
```
|
||||
|
||||
**Q3: Current Frustrations**
|
||||
```
|
||||
"Welche sind eure Top 3 Probleme mit dem aktuellen Process?"
|
||||
|
||||
Listen for:
|
||||
- Customer disputes over readings
|
||||
- Staff effort (time-consuming)
|
||||
- Data quality issues
|
||||
- Customer complaints (feedback)
|
||||
- Billing inaccuracies
|
||||
|
||||
Probe deeper on each:
|
||||
- "How often does this happen?"
|
||||
- "What's the impact?" (Cost? Customer satisfaction?)
|
||||
- "Who feels the pain most?" (Support team? Finance? Customers?)
|
||||
```
|
||||
**Test:**
|
||||
- Google Search Console nach 3 Monaten Blog-Content
|
||||
- Keywords: "Innungsverwaltung Software", "App für Innungen", "Mitgliederverwaltung Handwerk"
|
||||
- Ziel: > 100 organische Besucher/Monat nach 3 Monaten
|
||||
|
||||
---
|
||||
|
||||
### PART B: Solution Fit (5 Min)
|
||||
## 6. Kill Criteria
|
||||
|
||||
**Q4: Appetite for Change**
|
||||
```
|
||||
"Würdet ihr eine Mobile App für die Zählerablesung einführen?"
|
||||
**Wir stoppen das Projekt wenn:**
|
||||
|
||||
Expected Answers:
|
||||
A) "Yes, if it solves [specific problem]"
|
||||
B) "Maybe, but we need to think about it"
|
||||
C) "No, not interested"
|
||||
D) "We're already evaluating solutions"
|
||||
| Kriterium | Wert |
|
||||
|---|---|
|
||||
| Aktivierungsrate nach 3 Monaten Pilot | < 20 % |
|
||||
| Pilot → Paid Conversion | < 2 von 5 (40 %) |
|
||||
| NPS Admin | < 20 |
|
||||
| Zahlungsbereitschaft | < 99 €/Monat bei Mehrheit |
|
||||
| Support-Aufwand | > 5h/Woche pro Innung (nicht skalierbar) |
|
||||
|
||||
Green Flag: Answer A or D
|
||||
Red Flag: Answer C or B (lukewarm interest)
|
||||
|
||||
Follow-up:
|
||||
- "What would make this compelling for you?"
|
||||
- "What would be blockers?"
|
||||
- "Timeline - when would you need this?"
|
||||
```
|
||||
|
||||
**Q5: Customer Adoption Likelihood**
|
||||
```
|
||||
"Glaubst du, dass deine Kunden eine App nutzen würden
|
||||
zur Zählerablesung?"
|
||||
|
||||
Dig deeper:
|
||||
- "What % of your customers would use it?" (Target: >20% = viable)
|
||||
- "What incentives would help adoption?"
|
||||
- Free (most customers don't care)
|
||||
- Small discount (€1-2/year per reading)
|
||||
- Instant feedback (meter consumption insights)
|
||||
- "Would you push it to customers or wait for demand?"
|
||||
|
||||
Red Flag: <10% adoption estimate
|
||||
Green Flag: >20% adoption estimate
|
||||
```
|
||||
|
||||
**Q6: Integration Feasibility**
|
||||
```
|
||||
"Welche Systeme nutzt ihr für Kundenmanagement?"
|
||||
|
||||
Record:
|
||||
- Billing system (SAP, Oracle, Infor, etc.)
|
||||
- CRM (Salesforce, etc.)
|
||||
- Meter database (own, external, etc.)
|
||||
- IT infrastructure (on-prem, cloud, hybrid)
|
||||
|
||||
Follow-up:
|
||||
- "How open is your IT for external integrations?"
|
||||
- "Who would need to approve this?"
|
||||
- "Do you have an API layer?"
|
||||
|
||||
Red Flag: Very legacy, no API access, slow approval
|
||||
Green Flag: Modern stack, willing to integrate
|
||||
```
|
||||
**Pivots bei Kill-Criteria:**
|
||||
- WAU niedrig, aber Lehrlingsbörse-Traffic hoch → Pivot zu reiner Azubi-Plattform
|
||||
- Admins mögen es, Mitglieder nicht → Pivot zu reinem Admin-Tool (Web-only)
|
||||
- Innungen zahlen nicht → HWK direkt als zahlender Kunde angehen
|
||||
|
||||
---
|
||||
|
||||
### PART C: Commercial Viability (3 Min)
|
||||
## 7. Tracking Setup
|
||||
|
||||
**Q7: Budget & Pricing**
|
||||
```
|
||||
"Wie viel würdet ihr für eine Lösung budgetieren?"
|
||||
### Analytics Events (PostHog)
|
||||
|
||||
Open-ended first:
|
||||
- Listen to their thinking
|
||||
- Don't anchor them to your price
|
||||
|
||||
Then probe:
|
||||
- "Is that annual or one-time?"
|
||||
- "Would you pay monthly/yearly/license?"
|
||||
- "What's the ROI threshold?" (Typical: payback in 1-2 years)
|
||||
|
||||
Red Flag: Budget <€20K/year or willing to pay only if risk-free
|
||||
Green Flag: Budget >€50K/year, willing to invest for ROI
|
||||
```typescript
|
||||
// Alle kritischen User Actions tracken
|
||||
posthog.capture('member_invited', { org_id, member_count: 1 });
|
||||
posthog.capture('member_activated', { org_id, time_since_invite_hours: 24 });
|
||||
posthog.capture('news_opened', { org_id, news_id, kategorie });
|
||||
posthog.capture('news_attachment_downloaded', { org_id, news_id });
|
||||
posthog.capture('termin_angemeldet', { org_id, termin_id, termin_typ });
|
||||
posthog.capture('ical_exported', { org_id });
|
||||
posthog.capture('stelle_created', { org_id });
|
||||
posthog.capture('stelle_viewed', { org_id, stelle_id, sparte, is_logged_in: false });
|
||||
posthog.capture('stelle_contact_tapped', { org_id, stelle_id, contact_method: 'call' });
|
||||
```
|
||||
|
||||
**Q8: Decision Making Process**
|
||||
```
|
||||
"Wie würde so eine Entscheidung ablaufen?"
|
||||
### Funnels in PostHog
|
||||
|
||||
Map:
|
||||
- Who needs to approve? (Budget owner, IT, Board?)
|
||||
- Timeline? (Fast-track vs. normal process)
|
||||
- RFP required? (Or can you do handshake deal?)
|
||||
- Contract terms? (1-year, 3-year, multi-year discount?)
|
||||
1. **Aktivierungs-Funnel:** Eingeladen → E-Mail geöffnet → Link geklickt → Login → Erste Aktion
|
||||
2. **News-Funnel:** Push erhalten → App geöffnet → Beitrag gelesen → Anhang geöffnet
|
||||
3. **Stellen-Funnel:** Stellenliste aufgerufen → Stelle geöffnet → Kontakt aufgenommen
|
||||
4. **Admin-Funnel:** Login → Beitrag erstellt → Veröffentlicht → Push gesendet
|
||||
|
||||
Red Flag: Requires months-long RFP, many approvers, slow
|
||||
Green Flag: Can decide quickly, fewer stakeholders
|
||||
```
|
||||
|
||||
**Q9: Switching Costs**
|
||||
```
|
||||
"Wenn die App nicht funktioniert, wie schnell könnt ihr
|
||||
rückwärts gehen?"
|
||||
|
||||
This matters because:
|
||||
- High switching costs = stickier customer
|
||||
- Easy exit = customer feels safer trying
|
||||
|
||||
Answer:
|
||||
- "We'd just stop recommending it to customers"
|
||||
- "We'd need to ramp down over X months"
|
||||
- etc.
|
||||
|
||||
Green Flag: Easy to exit → customer feels safe to try
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
### PART D: Follow-Up / Qualification (2 Min)
|
||||
|
||||
**Q10: Next Steps**
|
||||
```
|
||||
"Wäre es interessant, wenn wir euch eine Demo/Beta
|
||||
im nächsten Monat zeigen?"
|
||||
|
||||
Clear YES:
|
||||
- "Yes, I want to see this"
|
||||
- "Yes, let's do a pilot"
|
||||
|
||||
Soft YES:
|
||||
- "Maybe, depends on what I see"
|
||||
- "Let me talk to my team first"
|
||||
|
||||
NO:
|
||||
- "Not right now"
|
||||
- "We're happy with our current approach"
|
||||
|
||||
Green Flag: Clear YES → Schedule demo/pilot for them
|
||||
Soft YES: Send materials, follow up in 2 weeks
|
||||
NO: Thank them, add to "maybe later" list
|
||||
```
|
||||
|
||||
**Q11: Introductions**
|
||||
```
|
||||
"Kennst du andere Stadtwerke, die ähnliche Probleme haben?"
|
||||
|
||||
Goal: Get warm referrals
|
||||
- "Can you introduce me to [competitor]?"
|
||||
- "Would you be willing to be a reference?"
|
||||
|
||||
Green Flag: YES on both → builds your network, proof
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Data Collection Template
|
||||
|
||||
Create a Spreadsheet with:
|
||||
### Dashboard für Piloten (Wöchentlicher Report per E-Mail)
|
||||
|
||||
```
|
||||
| Stadtwerk | Size | Contact | Q1 Method | Q2 Cost/Error | Q3 Pain | Q4 Appetite | Q5 Adoption | Q6 Integration | Q7 Budget | Q8 Timeline | Score | Notes |
|
||||
|-----------|------|---------|-----------|----------------|---------|-------------|------------|-----------------|-----------|-----------|-------|-------|
|
||||
| Stadt A | 100K | John D. | Manual 50%| €60K, 30% err | High | Yes | 30% | SAP, open | €80K | 2 months | 9/10 | Hot lead |
|
||||
| Stadt B | 50K | Jane S. | Manual 70%| €40K, 25% err | Medium | Maybe | 15% | Legacy, closed | €30K | 6 months | 5/10 | Cold |
|
||||
Betreff: Ihre InnungsApp Wochenbericht — KW 12
|
||||
|
||||
Aktivität diese Woche:
|
||||
✓ 45 von 78 Mitgliedern waren aktiv (58 %)
|
||||
✓ 2 Beiträge veröffentlicht → Ø Leserate: 71 %
|
||||
✓ 3 neue Terminanmeldungen
|
||||
✓ 4 Aufrufe der Lehrlingsbörse (2 Kontaktanfragen)
|
||||
|
||||
Vergleich zu letzter Woche:
|
||||
↑ +12 % mehr aktive Nutzer
|
||||
↑ +8 % höhere Leserate
|
||||
|
||||
Ausstehend:
|
||||
⚠ 14 Mitglieder haben sich noch nie eingeloggt → [Erinnerung senden]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## GO / NO-GO Decision Framework
|
||||
|
||||
### Scoring Matrix
|
||||
|
||||
Assign points (1-10) for each question:
|
||||
|
||||
```
|
||||
Q1: Current Manual Process = ___ / 10
|
||||
(1 = fully automated, 10 = fully manual)
|
||||
|
||||
Q2: Annual Cost/Pain = ___ / 10
|
||||
(1 = <€10K cost, 10 = >€100K cost)
|
||||
|
||||
Q3: Frustration Level = ___ / 10
|
||||
(1 = not a priority, 10 = huge pain)
|
||||
|
||||
Q4: Appetite for Change = ___ / 10
|
||||
(1 = no, 10 = ready to sign today)
|
||||
|
||||
Q5: Customer Adoption = ___ / 10
|
||||
(1 = <5%, 10 = >50%)
|
||||
|
||||
Q6: Integration Feasible = ___ / 10
|
||||
(1 = impossible, 10 = very easy)
|
||||
|
||||
Q7: Budget Available = ___ / 10
|
||||
(1 = <€20K, 10 = >€100K)
|
||||
|
||||
Q8: Fast Decision = ___ / 10
|
||||
(1 = >6 months, 10 = <1 month)
|
||||
|
||||
TOTAL SCORE = Sum of all 8 / 8 × 10 = ___ / 10
|
||||
```
|
||||
|
||||
### Go/No-Go Thresholds
|
||||
|
||||
```
|
||||
SCORE 8-10: HOT LEADS (Definitely pursue)
|
||||
- Validate further with second/third meetings
|
||||
- Structure a pilot/POC
|
||||
- These are your first customers
|
||||
|
||||
SCORE 6-7: WARM LEADS (Worth pursuing)
|
||||
- Keep in pipeline
|
||||
- Send materials, stay in touch
|
||||
- Re-engage in 3 months
|
||||
|
||||
SCORE 4-5: COOL LEADS (Maybe later)
|
||||
- Add to "monitor" list
|
||||
- Market conditions may change
|
||||
- Re-approach in 6 months
|
||||
|
||||
SCORE <4: COLD LEADS (Not a fit now)
|
||||
- Don't waste time
|
||||
- Maybe re-approach if product evolves
|
||||
```
|
||||
|
||||
### Portfolio Requirements for GO Decision
|
||||
|
||||
After 10-15 interviews, you need:
|
||||
|
||||
```
|
||||
✅ GO Signal if:
|
||||
- 5+ Hot Leads (score 8-10) with €50K+ budget each
|
||||
- OR 10+ Warm Leads (score 6-7) that could grow into hot
|
||||
- Average adoption estimate: >20%
|
||||
- Average budget: >€50K/year
|
||||
- Market size (sum of budgets): >€500K
|
||||
|
||||
❌ NO-GO Signal if:
|
||||
- <3 Hot Leads
|
||||
- Average score <5
|
||||
- Average adoption <10%
|
||||
- Market size <€300K
|
||||
- Pattern of "we'll wait and see"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Competitive Positioning
|
||||
|
||||
During interviews, also ask:
|
||||
|
||||
```
|
||||
"Are you evaluating any other solutions?"
|
||||
|
||||
Typical answers:
|
||||
A) "Yes, we're in RFP with SAP/Oracle"
|
||||
B) "No, but considering some options"
|
||||
C) "Not actively, but open to ideas"
|
||||
D) "We tried something similar, didn't work"
|
||||
|
||||
Analysis:
|
||||
- A: You're late, but potentially better/cheaper/faster
|
||||
- B: You're in conversation, good timing
|
||||
- C: You're educating the market, need strong proof
|
||||
- D: Understand what failed, position differently
|
||||
|
||||
Use competitive insights to position your MVP:
|
||||
- Faster to market vs. SAP
|
||||
- Cheaper than Oracle (€50K vs. €200K+)
|
||||
- Mobile-first (better UX)
|
||||
- Customizable (specific to Stadtwerke)
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Timeline & Execution
|
||||
|
||||
### Week 1: Prep & Recruiting
|
||||
```
|
||||
Mon-Tue:
|
||||
- Create interview guide (this doc)
|
||||
- Build data collection spreadsheet
|
||||
- Create email template
|
||||
|
||||
Wed-Fri:
|
||||
- Start outreach (LinkedIn, email, phone)
|
||||
- Target: 10-15 interviews scheduled
|
||||
|
||||
Tools:
|
||||
- Calendly for scheduling
|
||||
- Zoom for remote calls
|
||||
- Google Sheets for data
|
||||
```
|
||||
|
||||
### Week 2-3: Conduct Interviews
|
||||
```
|
||||
Goal: 10-15 interviews (2 per day)
|
||||
Prep for each:
|
||||
- Research company (size, industry focus)
|
||||
- Prepare notes
|
||||
- Test audio/video
|
||||
|
||||
During:
|
||||
- Record (with permission) or take notes
|
||||
- Be friendly, genuine, listening-focused
|
||||
- Don't pitch hard (listen more than talk)
|
||||
|
||||
After:
|
||||
- Score each interview
|
||||
- Add to spreadsheet
|
||||
- Send thank you note + case study PDF
|
||||
|
||||
Time per interview: 20-30 min (including travel/setup)
|
||||
Total time: ~10 hours for 15 interviews
|
||||
```
|
||||
|
||||
### Week 4: Analysis & Decision
|
||||
```
|
||||
Mon-Tue:
|
||||
- Score all interviews
|
||||
- Aggregate data in spreadsheet
|
||||
- Create summary report
|
||||
|
||||
Wed:
|
||||
- Team discussion
|
||||
- GO/NO-GO vote
|
||||
|
||||
Thu-Fri:
|
||||
- If GO: Contact top Hot Leads about pilot
|
||||
- If NO-GO: Pivot to different pain point or market
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Sample Report Template
|
||||
|
||||
After Week 3, create:
|
||||
|
||||
```
|
||||
# VALIDATION REPORT: SmartMeter-Lite App
|
||||
Date: [Date]
|
||||
Conducted by: [Name]
|
||||
|
||||
## Executive Summary
|
||||
- 12 Interviews conducted
|
||||
- 7 Hot Leads (58%), 3 Warm Leads (25%), 2 Cold (17%)
|
||||
- Average budget: €65K/year
|
||||
- Market opportunity: €780K in year 1
|
||||
- **Recommendation: GO** ✅
|
||||
|
||||
## Key Findings
|
||||
1. Manual meter reading is REAL pain
|
||||
- Avg cost: €50K/year per Stadtwerk
|
||||
- Avg error rate: 28%
|
||||
- Top frustration: Customer disputes
|
||||
|
||||
2. Market appetite is strong
|
||||
- 58% very interested (Hot)
|
||||
- 25% interested (Warm)
|
||||
- Would pay avg €65K/year
|
||||
|
||||
3. Integration is manageable
|
||||
- 75% have API-accessible systems
|
||||
- 60% can integrate within 3-6 months
|
||||
- Legacy systems are minority
|
||||
|
||||
4. Customer adoption is solid
|
||||
- Avg expected adoption: 25%
|
||||
- Range: 10-40%
|
||||
- Key: Make it optional (don't force)
|
||||
|
||||
## Top Hot Leads
|
||||
1. Stadtwerke München (100K households, €120K budget, Ready Now)
|
||||
2. Stadtwerke Köln (80K households, €100K budget, 2-month timeline)
|
||||
3. Stadtwerke Hamburg (120K households, €150K budget, 3-month timeline)
|
||||
|
||||
## Risk Factors
|
||||
- SAP/Oracle competition (but they're slow)
|
||||
- DSGVO compliance needed (doable)
|
||||
- Integration complexity (manageable)
|
||||
|
||||
## Next Steps
|
||||
1. Schedule pilots with top 3 Hot Leads
|
||||
2. Get signed LOI (Letters of Intent)
|
||||
3. Begin development in Week 5
|
||||
4. Deliver MVP in 12 weeks
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Key Metrics to Track
|
||||
|
||||
After validation, you have:
|
||||
|
||||
```
|
||||
√ Market Size: €X (sum of budgets from interviews)
|
||||
√ Win Rate: Y% (Hot Leads / Total)
|
||||
√ Sales Cycle: Z months (from interviews)
|
||||
√ Product-Market Fit Score: __ / 10
|
||||
√ Competitive Landscape: [Summary]
|
||||
√ Go-to-Market Strategy: [Clear approach]
|
||||
```
|
||||
|
||||
These become your baseline KPIs.
|
||||
|
||||
---
|
||||
|
||||
## What NOT to Do
|
||||
|
||||
❌ **Don't pitch too hard**
|
||||
- Interviews are for listening, not selling
|
||||
- If they're interested, they'll ask for more
|
||||
|
||||
❌ **Don't overcommit**
|
||||
- "We can integrate with anything" - No, be honest
|
||||
- "We can do custom features" - Not in MVP
|
||||
|
||||
❌ **Don't ask leading questions**
|
||||
- "You have problems with meter reading, right?" (Yes)
|
||||
- Better: "Walk me through your process" (more honest)
|
||||
|
||||
❌ **Don't ignore red flags**
|
||||
- "Maybe next year" = Not a hot lead
|
||||
- Lukewarm interest is not enough
|
||||
|
||||
❌ **Don't over-engineer based on feedback**
|
||||
- "We'd want X, Y, Z features"
|
||||
- Don't add them to MVP - they add time/cost
|
||||
- Just build #1 really well
|
||||
|
||||
---
|
||||
|
||||
## Success Looks Like
|
||||
|
||||
✅ You have 5+ Hot Leads wanting to pilot
|
||||
✅ You have 3+ Letters of Intent (LOI)
|
||||
✅ You understand the real problem deeply
|
||||
✅ You have clear competitive positioning
|
||||
✅ You know your Unit Economics (€15-30K CAC, €80-120K ACV)
|
||||
✅ You're confident in 20%+ adoption rates
|
||||
✅ You can articulate WHY Stadtwerke need this
|
||||
|
||||
If you have all of this, you're ready to build.
|
||||
|
||||
---
|
||||
|
||||
**Document Status:** Ready to execute
|
||||
**Time to Complete:** 3-4 weeks
|
||||
**Output:** GO/NO-GO + 5+ pilot customers (if GO)
|
||||
|
||||
Reference in New Issue
Block a user