How to use: copy the PROMPT into Claude first, then paste the BRIEF after it. One copy button each.
You are reviewing a business concept for a solo founder in Pittsburgh, PA (background: manufacturing/construction operations and project coordination; builds and sells one-file web apps; coached youth baseball 12 years and is currently running his own son's college recruiting; his own nine-person extended family spans four households). Your job is NOT to encourage him. Be an adversarial reviewer: attack the assumptions, find what the brief missed, and price-check its claims against real sources where you can. Attack these assumptions hardest: 1. Families will pay $25–40/month plus a $99–199 setup fee for coordination, when Cozi, shared Google Calendar and a Skylight display are free or one-time costs — and when a general AI assistant is $20/month. 2. The concierge test proves demand. Three friendly families using a free hand-run service for two weeks may just be polite; and the founder running it by hand does not prove the automated system works or that strangers will pay. 3. The moat is setup labor. If the moat is labor, the business scales slowly and margins stay thin; if AI assistants get good enough to set themselves up for a family, the moat disappears entirely. Which is it, and over what time horizon? 4. Parents will hand a small company their kids' schedules, locations and school information. Is the trust barrier priced into this model at all? 5. Retention: a subscription whose value is "nothing went wrong this week" gets cancelled in quiet months and when the sports season ends. Does the model survive seasonality and quiet weeks? 6. Channel: leagues and schools as distribution — will they actually hand a paid service access to their families, or is that a hope dressed as a channel? Return, in this order: - A verdict: BUILD / BUILD SMALLER / DON'T BUILD, in one paragraph. - The three weakest assumptions, ranked, each with the cheapest real-world test the founder could run in Pittsburgh within 60 days to prove or kill it, including a kill criterion. - Any competitor, prior failure, or market fact the brief missed (check at least: Cozi, Skylight Calendar, Famly, Ohai or similar AI family assistants, and any "family chief of staff" startups that already tried this). - What evidence would change your verdict. Be specific. No generic startup advice.
CONCEPT BRIEF — "The Family Chief of Staff" (working title, not final) ONE LINE: A done-for-you daily system that runs a busy family's logistics: it collects the day's inputs (school emails, coach texts, schedules, flyers) and delivers one morning page per household — who's where, who's driving, what's missing, what breaks today if nobody acts. No app to maintain, no log to feed. THE PROBLEM: Middle-class families — two working parents, kids at all ages, school/daycare/youth activities — are overloaded and overlooked. The coordination load lands on one parent (usually the most-loaded one) and eats evenings. Every organizing tool creates an admin job that lands on that same parent. Families break on exceptions, not routine: the practice that moved, the permission slip due Friday, the ride that fell through. The bottlenecks are CAPTURE (flyers, school apps, coach texts, emails) and VISIBILITY (one page everyone sees), not intelligence. "Yes, they can get an AI assistant and get organized — but can they?" Setting one up, teaching it the family, and keeping it fed for months is a second job; tired people don't finish self-serve systems. WHAT THE SYSTEM DOES (THE DAILY LOOP): - Evening intake: the system gathers inputs — school/coach emails forwarded to a family address, photos of flyers texted in, calendar sync. At concierge stage this is human-operated; later, AI-assisted extraction with human review. - Overnight processing: deduplicate, resolve conflicts (two kids, one car, one parent), assign owners by family defaults (who drives Tuesdays, which car), flag exceptions and deadlines. - Morning delivery (~6 AM): one household page + short per-person texts — today's plan, rides, what's due, what changed. No app to open; it arrives where families already read (text + a web page). - Evening lookahead (~7 PM): tomorrow preview, so the night isn't spent planning. - Exceptions, live: a practice moves at 4 PM → updated page + text to the driver. The change finds the family; the family doesn't hunt for it. - Weekly layer: a Sunday plan page (the week ahead). It also feeds a monthly family meeting: wins, goals and problems surfaced from the week instead of remembered in the room. WHO IT'S FOR: - Beachhead: youth-sports families — the highest coordination load per household (multiple teams, coach texts, tournaments), concentrated in seasons, reachable through leagues and schools. The founder coached youth baseball for 12 years and is running his son's recruiting now. - Second market: sandwich-generation families coordinating an aging parent's care alongside kids. - Not for: single-person households, or families who already run a tight shared calendar (control group, not customers). BUSINESS MODEL: - Subscription per family: $25–40/month (to be tested). Anchor: one evening of coordination saved per week is worth more than that to a two-income household. - White-glove onboarding/setup fee: $99–199 — a setup session that maps the family (people, schools, teams, defaults, drivers), done FOR them, not by them. (The "AI assessment" model from founder podcasts, pointed at households.) - Delivery: SMS + web page + optional Sunday print page for the fridge. - No app download. No App Store. The family never installs anything. HOW IT STARTS (CONCIERGE → SYSTEM): - Phase 0 (weeks 0–8): concierge MVP — the founder and his assistant operate it BY HAND for 3 families, 2 weeks each. No code. Tests: do they read the morning page? Do they beg to keep it? How much time did it actually save? - Phase 1 (months 2–6): semi-automated — intake automation (email forwarding rules, calendar sync), human review before every delivery. 20–30 paying families in Pittsburgh, recruited through youth-sports leagues (the founder is separately building a handbook product sold to leagues, which is a relationship channel), schools, and family networks. - Phase 2 (year 2): productized system — AI extraction + human QA; expand metros via league/school channels; the weekly family-meeting feed ships. - Phase 3: add-ons — meal planning from the week's schedule, ride coordination with other families, elder-care module. WHAT MAKES IT DIFFERENT FROM "JUST GET CHATGPT/CLAUDE": - Setup is done FOR the family; the system arrives knowing the family's defaults. - It is proactive: exceptions find you. An assistant waits to be asked; this system pings. - Multi-person by design: one page everyone sees, per-person texts. - Delivered in channels families already read (text), not an app they must open and feed. COMPETITORS / ADJACENT (AS THE FOUNDER SEES THEM): - General AI assistants (ChatGPT, Muse, Gemini): the gap is setup + maintenance + proactivity. - Family organizer apps: Cozi (free, app-based, requires the family to maintain it — the exact failure mode this product escapes), Skylight Calendar (hardware calendar — display only, no intelligence), shared Google Calendar (free, same maintenance problem). - Human help: personal/VA services — expensive, not daily-systematic. - The pitch: the only option where the work is done FOR the family instead of by it. HONEST EXPOSURES (AS THE FOUNDER SEES THEM): - Service-heavy: every family is custom; onboarding is labor; margins depend on automation arriving before labor eats them. - Privacy: kids' schedules, locations, schools — the most sensitive data category. Trust and data handling ARE the product; one breach story kills it. The system must be consent-first. - Retention: value must be visible weekly; a quiet week can feel like "nothing happened" unless time saved is shown. - The moat is labor, not technology: slow to scale; shrinks if AI assistants learn to set themselves up. - Founder fit: the founder is the prototype user, but operating a daily service for 30 families is a different job than building one-file apps; staffing and QA are a real business, not a release. - Acquisition: families are hard to reach and skeptical of sharing kids' data; leagues/schools channels need relationships, not ads. - Seasonality: sports families churn when the season ends; the product must hold value in the off-season (school + work + life, not just sports). WHAT A WIN LOOKS LIKE: 3 concierge families beg to keep it after 2 weeks · 20 paying families in Pittsburgh within 6 months · retention above 80% at 3 months · setup cost paid back in under 3 months per family. FOUNDER REALITY: Solo founder, no outside capital, Pittsburgh. Builds one-file web apps today (a small storefront of them is live); this is a service + hosted system with ongoing daily operations — a company, not a file. The prototype is the founder himself: he has run his own life this way (an AI assistant wired into his Gmail, calendar and his son's GameChanger schedules) for two months, and his extended family is nine people across four households — he is the target customer, which cuts both ways.
Prepared Nov 18, 2026. Business concept only — contains no personal information.