Oma trägt ein, wann sie Zeit hat — du buchst, ohne zu fragen. Schluss mit dem 'Bittstellerin'-Gefühl.

Source signals

• SIG-20260426-dach-family-logistics-grandparent-childcare-availability-coordination — "Daher die Frage nach der App wo sie selber eintragen kann und ich oder mein Mann sehen es dann. Ich möchte keine Bittstellerin sein und ihr nachlaufen."

What we ship

**Core features (MVP)**

• **Helper-side broadcast UI**: Oma opens app → big button "Diese Woche bin ich frei" → picks slots in a week-grid (Mon/Tue/Wed 14-17, Fri from 16). Senior-optimized UI.
• **Parent-side claim UI**: parents see slots, tap "Wir nehmen Mi 14-17 — Lukas vom Kindergarten abholen" → Oma gets push "Bestätigung benötigt"
• **Recurring availability**: "Ich bin jeden Montag von 14-18 Uhr frei (außer Schulferien)"
• **Multi-helper**: Oma + Opa + neighbor → one slot pool, parents claim
• **Shift-aware**: for grandmas with variable retail/care shifts — weekly push reminder "Trag deine Slots für nächste Woche ein" at her preferred time
• **No-app fallback**: Oma without the app = WhatsApp-link share to a single-page "tippe deine Slots hier" web form (no signup)

**Primary user flow**

1. Discovery: SEO "Oma Pickup Kalender ohne ständig fragen", urbia.de + babyforum.at communities

2. Parent onboarding: create family, add Oma by phone → she gets SMS link

3. Core moment: Oma on Sunday evening taps "Mi 14-17 frei" → couple gets push "Oma hat Slots eingetragen — buchen?"

4. Pricing trigger: free for 1 helper + 2 children; €3.99/mo for 2+ helpers or recurring rules

**What it looks like**

• **Landing page**: hero "Du fragst nicht mehr — Oma trägt selbst ein. Endlich keine Bittstellerin." Sub-hero split-screen Oma's view (large buttons) vs parent's view (compact)
• **Helper UI**: 7-day grid with very large fields, tone "Wann hast du Zeit für die Enkelkinder?", no usecase-jargon
• **Parent UI**: weekly grid "available / booked / free", one-tap claim
• **Output / notification**: ICS sync with Google/Apple Calendar both sides + push 30 min before slot

**MVP build plan (7 days)**

• Day 1: schema (family, helper, parent, slot, booking), auth with phone-number-only login
• Day 2-3: helper-side senior UI (large fonts, big buttons, simplified flow)
• Day 4-5: parent-side claim UI, push notifications, ICS export
• Day 6: WhatsApp-link share fallback for no-app helpers
• Day 7: DE landing, Stripe, deploy to CF Pages

Reasoning

**This is the cleanest white-space wedge** of all the DACH family-logistics SIGs:

• Brave search returns 0 direct competitors with the broadcast-from-helper pattern
• babyforum.at, urbia.de, shubidu.com — three sources in the SIG explicitly describe the gap
• Existing family-calendar apps (Familywall, TimeTree, Cozi, Famanice) all assume **symmetric peers**, not helper/parent asymmetry

**Semantic wedge:**

We flipped the subject-object: instead of "parent asks" → "helper declares". This removes the social debt, not just optimizes the workflow. It's **Mental Load reduction via UX pattern**.

**Why it works in DACH:**

• Strong cultural value of "ich will keine Bittstellerin sein" (urbia.de quote — this is the literal phrasing used)
• High retention in multi-generational families (grandmas often >65, not super tech-savvy → senior-mode UI matters)
• Shift-work grandparents (care, retail) — large sub-cohort (~30% of DACH retirees in active family help), needs variable scheduling

**Stack-fit:** SUPER-fit. 7-day build. Minimal AI. Main technical risk is senior UX (need usability tests with real grandmas — fine for phase 2).

**Why consumer not founder:** audience is families, not businesses. Willingness-to-pay through "gift-from-children-to-grandma" psychology — mom pays €3.99/mo to make it easy for her mother-in-law.

Quick competitive read

• **Familywall, TimeTree, Cozi, Famanice, FamCal, Apple Family**: all peer-symmetric calendar apps. **None** have a helper-broadcast pattern.
• **shubidu.com** (Swiss): markets a "separate column for grandparents" — close, but it's just a column in a shared calendar, not a helper-self-service model
• **Doodle**: voting-style, no recurring availability. Too generic.
• **Calendly**: B2B booking — overkill, not for consumer-family.
• **Sittercity / Care.com**: paid babysitter marketplace — different audience (paid stranger, not family helper)
• **Direct competitive pressure**: **very low — white space**

Initial pricing hypothesis

**Free for 1 helper + 2 children + 4 weeks ahead.** **€3.99/month** or **€29/year** for multi-helper (Oma+Opa+aunt), unlimited recurring rules, history. Sensitive price for DACH — sits in the same wallet slot as Spotify-Familie. Could experiment with **gift sub** ("verschenk Oma den Familien-Kalender").

Distribution hypothesis

1) **DE-SEO**: "oma kann wann pickup", "großeltern verfügbarkeit kalender", "schwiegermutter ohne fragen"

2) **urbia.de + babyforum.at + parents.at**: organic posts in "Kinderbetreuung" subforums — the original SIG post is already there

3) **Seniorenmagazine**: guest article in DE "Apotheken Umschau" / Senioren-Lebenshilfe — reach the Großeltern audience directly

4) **DACH mom-influencers**: target mama-bloggers in Berlin/Vienna/Zurich who post on work + Mental Load