One shared family week so nobody forgets whose Wednesday it is — grandma, dad and продлёнка all see who picks up Vanya today, get a 30-minute heads-up, and tap 'I have him' so school stops calling.
Problem
Working mums in Russia and Belarus rely on a fragile chain of grandparents, an older sibling, продлёнка and the husband to pick the child up from school, juggling it across WhatsApp with relatives — every few weeks the chain breaks and the kid sits alone in the school corridor past closing time.
Audience
Working mothers in RU/BY large cities with primary-school kids (1–4 grade) and no single fixed pickup adult, instead a hybrid rota of 3–4 caregivers (grandma + spouse + продлёнка + older sibling). Roughly 2–3M households.
Reasoning
Source signals
- SIG-20260426-ru-by-family-logistics-svodnaya-tablica-deti-kruzhki-peremescheniya: "если у вас двое или больше детей, это единственный способ выжить"
- SIG-20260426-ru-by-family-logistics-pervoklassnik-prodlenka-logistika: "дайте пожалуйста совет по логистике первоклассника"
- SIG-20260426-ru-by-family-logistics-rabotayuschie-mamy-zabrat-iz-shkoly: "как все координировать"
- SIG-20260426-ru-by-family-logistics-babushka-dedushka-koordinatsia-deti: "одна активная бабушка двое детей и трое внуков"
- SIG-20260426-ru-by-family-logistics-roditelskii-chat-vazhnoe-teryaetsa: "важные сообщения теряются" (cross-cluster)
What we ship
**Core features (MVP)**
- Per-child weekly timeline with 30-min slots: school → продлёнка → kruzhok → home, and WHO is responsible for each transition
- Family adult roster (mum, dad, grandma, grandpa, older sibling, nanny) with colour tags
- Push notification 30 min before each transition — to the responsible adult
- "I have the kid" ack button — status visible to all family adults
- Telegram bot mirror — grandma without iPhone gets the same reminders
- Substitution templates: "grandma can't on Wed — who covers?" → broadcast, first ack wins
**Primary user flow**
1. Mum registers via Telegram bot (or web), creates "family", adds child
2. Invites adults by link (grandma, dad, nanny) — each with own profile and colour
3. Fills weekly template: "Mon продлёнка till 17, grandma picks up at 17, drives to самбо by 18"
4. Each day, 30 min before each slot — notification + ack button
5. After 7 days — pricing trigger: "you stopped forgetting each other — upgrade to Pro at 199₽/mo to add a second kid"
**What it looks like**
- **Landing page**: "Stop calling grandma at 16:55 'do you remember?'" + weekly grid screenshot + CTA "Create family for free"
- **Main app screen**: vertical day timeline for the child, colour blocks per responsible adult, ack checkbox
- **Notification**: "🚸 In 30 min pick up Vanya from school №12. Responsible: grandma. ✓ on my way"
**MVP build plan (12 days)**
- Day 1-3: backend, schema (Family, Child, Adult, Slot, AckEvent), JWT auth
- Day 4-7: PWA with weekly grid, templates, drag-and-drop slots
- Day 8-10: Telegram bot, Web Push, ICS export
- Day 11-12: ЮKassa subscription, landing, Cloudflare Pages deploy
Reasoning
Five of the 14 SIGs in this cell describe the same underlying pain: a multi-adult human chain around one school-age kid that breaks every couple of weeks. Existing tools are either generic family calendars (Google Calendar, ClanPlan, SingularityApp) that don't model "pickup responsibility transitions with acks", or official school apps (Госуслуги Моя школа) that stop at the school gate. The combination of "RU/BY school-day rhythm + multi-adult ack model + Telegram-first delivery (Telegram is the main messenger, not WhatsApp)" is white space, and the technical scope fits a 12-day solo build.
Quick competitive read
5 competitors profiled (CMP files):
- **Дневник.ру / Моя школа** (CMP-071-dnevnik-ru) — federal/regional electronic school journal, ~80% of RU schools. Covers "what's at school", stops at school gates. Zero UX competitive pressure (monopoly). We layer logistics ON TOP of their data.
- **Яндекс.Семья** (CMP-071-yandex-semya) — Yandex Plus family bundle, 399₽/mo. Doesn't build kid logistics; structural threat in 12-24 months. Defended by speed-to-market + Telegram-channel ownership + RU-school specificity.
- **Telegram family bots** (CMP-071-telegram-family-bots) — long tail of solo-built bots; prove pain + Telegram-first acceptance, but no ack-button, ICS, ЮKassa subscription. We build the productized version of what 5,000 families already cobble together.
- **Cozi + FamilyWall** (CMP-071-cozi-familywall) — western incumbents (~20M+5M households). Blocked from RU (Stripe, AppStore, no-ru-locale). Used as TAM benchmark and price anchor ($39.99/yr ≈ 340₽/mo).
- **SingularityApp** (CMP-071-singularityapp) — RU GTD with family workspace, 299₽/mo. Adjacent, not direct. We undercut by 100₽ on Pro and own school-vertical specificity.
**White space**: no app combines "pickup chain + ack model + Telegram delivery + RU-school-day rhythm + ЮKassa subscription" simultaneously. Competitive pressure 5-6/10. Market density: medium.
Initial pricing hypothesis
Freemium: 1 kid + 3 adults free. Pro 199₽/mo: up to 4 kids + unlimited adults + 90-day ack history + custom substitution templates. Family-Plus 349₽/mo: + Yandex.Calendar integration + shared "things to bring tomorrow" list.
Distribution hypothesis
(1) RU Telegram channels for mums ("Мел", "Никакого Стресса", "Большой ребёнок") — organic post + 2-3 paid placements at 5-10k₽; (2) comment-marketing on eva.ru, baby.ru, u-mama.ru existing pain threads; (3) SEO for "график пикапа из школы" + "общий семейный календарь продлёнка"; (4) VK targeted ads on mums of 1-4 grade kids with district + working-status filter.
Source signals (5)
SIG-20260426-ru-by-family-logistics-pervoklassnik-prodlenka-logistika:SIG-20260426-ru-by-family-logistics-roditelskii-chat-vazhnoe-teryaetsa:SIG-20260426-ru-by-family-logistics-rabotayuschie-mamy-zabrat-iz-shkoly:SIG-20260426-ru-by-family-logistics-svodnaya-tablica-deti-kruzhki-peremescheniya:SIG-20260426-ru-by-family-logistics-babushka-dedushka-koordinatsia-deti: