Front Stoop: Less scramble. More evening.

Recommendation

Lead with the evening handoff, not with a list of organizing features. Start with working couples who repeatedly coordinate a fixed after-work responsibility; make dual-career parents with pickup and dinner handoffs the first recruitment segment. Test non-parent couples alongside them before narrowing paid targeting. The central proposition is “Know what's next. Know who's got it.” The emotional payoff remains “Less scramble. More evening.”

For the first two weeks, a small team should do four things: interview eight households; show the animated launch preview; test whether people understand Evening Brief and accepted coverage swaps; prepare a truthful, measurable preview destination. No paid acquisition until that destination, consent flow, and measurement work. Start with Instagram/Facebook short video and direct, permission-based research recruitment. Add a tightly bounded Search experiment only after intent and landing-page comprehension are demonstrated. Do not launch every channel in this plan.

Status and assumptions — researched September 17, 2026 (UTC). Repository inspection at commit 19cc4e1c426f09c87e68055ac808356dd4558bf4 found that README says the live site remains offline and deployment is paused. Household mail/calendar workflows are synthetic. This is repository evidence, not an independently verified public uptime result. No public URL, working waitlist, real mailbox/calendar integration, pricing, or launch date was verified. Existing local promotional artifacts are separate from this campaign. All recommendations below are proposals; nothing has been published or purchased. Budget geography: US, English, USD; not a demographic claim. Capability pages and ad eligibility must be rechecked before launch.

1. Audience and research

All audience language below is proposed copy, not quotations from customers. Validate it in interviews. Avoid gender-based task ownership, judgments about partners, or assumptions that all professionals are parents.

Interview design: recruit eight households: four beachhead, two non-parent couples, two irregular schedules. Where possible hear from both adults separately, then together, with consent. Ask about the last actual coordination miss, where the information lived, how a handoff was accepted, what they already like about their system, and which part felt like extra work. Do not ask “Would you use this?” as the primary signal. Show the preview only after hearing the problem. Ask participants to explain what is real today, name the next step, and reenact a fictional ownership change. Record anonymous themes, not household message contents. Planning allocation: eight 30-minute interviews plus synthesis, with proposed $25/household incentive (not spent). A convenience sample validates language, not market size.

Beachhead falsification: if fewer than five of eight interviewed households report a recurring handoff problem, or the secondary cohort finds the story materially clearer, revise the segment before buying reach. If participants expect automatic inbox connection after viewing, revise the creative/disclosure before testing conversion.

2. Positioning and competitive frame

Category: an evening coordination workspace for busy households. Value proposition: Front Stoop's demonstrated workflows bring tonight, tomorrow, and visible responsibility into a clearer shared picture, with understandable, reversible message organization. Intended outcome: less effort reconstructing the plan and fewer assumptions about who is handling it. These are intended benefits, not measured results.

Messaging hierarchy:

1. Hook: “Work's done. Why is life still sending assignments?”
2. Job: “Know what's next. Know who's got it.”
3. Proof: Evening Brief + Coverage Board, including request → pending → accepted.
4. Supporting reassurance: preview organization choices, inspect reasons, and undo.
5. Payoff: “Front Stoop. Less scramble. More evening.”
6. CTA: “Watch the launch preview.” Use the local preview for review; connect this CTA only to an approved, working preview destination before distribution.

“Your workday ended. Your second shift shouldn't be sorting everything out” is a strong long-form opening. Test “second shift” against “evening handoff”: the former may resonate with care labor but feel heavy or parent-specific. “Know what's next…” is the recommended explanatory line because it names two demonstrated jobs. No research here proves one copy line outperforms another.

Feature → advantage → benefit → proof boundary

Competitive alternatives, checked September 17, 2026

Competitor facts are from their official product pages; opportunity statements are our positioning hypotheses. Absence from a cited page is not proof a competitor lacks a capability. Avoid “only,” “first,” or blanket superiority claims.

Do not compete on AI claims, guaranteed time savings, integrations, certifications, user counts, or price. A truthful comparison page should list source dates, actual demonstrated support, “not verified” where appropriate, and who might reasonably prefer the alternative.

3. Full channel opportunity map

Priority definitions: “Launch now” means the first approved execution wave after the appropriate destination/consent gate; it is not permission to publish. Where a channel can begin as research today, that is stated. “Test later” needs evidence/dependencies. “Deprioritize” gets no initial budget. All costs are planning assumptions, not platform quotes or market benchmarks. L/M/H effort means roughly 1–2 / 3–6 / 8–16 hours per week when active, excluding the initial flagship. Do not sum every row into staffing: only activate the chosen few. Funnel D=discovery, C=consideration, V=conversion, A=activation, R=retention, F=referral.

Small-team operating limit: three original short videos per week total, adapted to selected destinations; one carousel/checklist; one founder post; one permission-based email every two weeks; two 20-minute community listening sessions. Initial distribution: Instagram/Facebook, optional TikTok/Shorts reuse, founder LinkedIn. Don't promise custom daily content on every network.

4. Campaign ideas

Series template: 0–2s one everyday question, 2–7s escalating physical gag, 7–12s one illustrative workflow, 12–15s relieved callback + brand. Rotate who asks/accepts across episodes. Never make a gender or a less technical partner the joke. Shares are a hypothesis, not a virality promise.

5. Ready-to-use copy

These are review-ready drafts. Replace destination tokens only after a real approved destination exists; no placeholder may ship.

Meta ads

A — recognition. Primary: “Work's done. Dinner, pickup and tomorrow have entered the chat. Meet Front Stoop's illustrated launch preview: a clearer picture of what's next and who's got it. Synthetic demo; no real mailbox connected.” Headline: “Less scramble. More evening.” Description: “Watch the launch preview.” Button: Learn More.

B — handoff. Primary: “A request isn't a handoff until someone accepts. See Front Stoop's Coverage Board and Evening Brief in a fictional household evening.” Headline: “Know who's got it.” Description: “An illustrative product preview.” Button: Learn More.

C — non-parent couple. Primary: “Two workdays. One dinner decision. And an errand you both thought the other had. See the Front Stoop launch preview.” Headline: “Make tonight clearer.” Description: “Illustrative demo. Synthetic data.” Button: Learn More.

Avoid “You are an overwhelmed parent” or individualized claims about a viewer's circumstances. These examples describe situations.

Google responsive search ad draft

Verified current limits: up to 15 headlines of 30 characters and four descriptions of 90 characters; minimum three headlines and two descriptions. Assets must work in any combination. Pin availability disclosure in Description 1 so launch-preview context is retained. Google RSA documentation. Character counts are generated in search-ad-assets.csv.

Headlines: Front Stoop Launch Preview; Less Scramble. More Evening.; Know What's Next; Know Who's Got It; A Clearer Evening Handoff; Preview Evening Brief; See The Coverage Board; Tonight And Tomorrow; Make The Handoff Clear; Household Plans, In View.

Descriptions:

• Watch an illustrative launch preview. Synthetic data. No real mailbox connected.
• See tonight, tomorrow and who is handling what in Front Stoop's demo workflows.
• Preview Evening Brief and Coverage Board for a clearer picture of the evening.
• Explore understandable message organization with preview, choice and undo.

Suggested intent clusters: “shared household organizer,” “family responsibility planner,” “couples planning app.” These are hypotheses, not keyword-volume findings. Start narrow; review queries twice weekly. Exclude jobs, shift employment, porch construction, real estate, stoop repair, and unrelated free printable queries from product-intent campaigns. A separate helpful-guide campaign may legitimately target worksheets. No competitor trademarks in ad copy or implied affiliation. Final URL remains unset until approved and tested.

TikTok/Reels scripts

15s teaser: 0–3 laptop snap + rain of cards: “Work's done. Why is life still sending assignments?” 3–6 two figures point at one DINNER card: “I thought you had it.” 6–10 ownership card settles: “Know what's next. Know who's got it.” 10–15 brand and “Watch the launch preview.” Persistent illustrative-demo label; readable final disclosure. Burn captions, don't depend on trending licensed music.

30s handoff cut: 0–4 opening question; 4–8 shared “I thought you had it”; 8–13 Evening Brief; 13–21 Coverage Board request → pending → accepted; 21–24 stoop payoff; 24–30 brand, preview CTA and disclosure. Exact rendered timing/script is in the production package.

X / Threads posts

1. “Laptop: closed. Dinner question: open. Tomorrow question: also open. Front Stoop's launch preview explores a clearer evening handoff. Illustrative demo, synthetic data.”
2. “A tiny household design rule: ‘Can you take dinner?’ and ‘Yes, I've got dinner’ are two different states. We're building that distinction into Front Stoop's Coverage Board demo.”
3. Thread: “1/ What if the evening started with three answers: tonight, tomorrow, who's got it? 2/ Front Stoop's Evening Brief and Coverage Board demonstrate that idea with fictional household data. 3/ A requested swap stays pending until accepted. 4/ Watch the launch preview when the approved link is available. Less scramble. More evening.” Remove sentence 4's link instruction before publication and insert actual working CTA.

Instagram carousel

Cover: “Work's done. Why are there more assignments?” Slide 2: laptop shuts; endless receipt unrolls. Slide 3: “What needs attention tonight?” with Evening Brief. Slide 4: “Who has it?” with dinner owner. Slide 5: “A request is not an accepted handoff.” show pending/accepted states. Slide 6: “Less scramble. More evening.” + launch-preview CTA. Keep “Illustrative demo · synthetic data” on feature slides; full mailbox disclosure on final. Alt text should describe the action and meaningful card labels.

Reddit participation, useful without a link

General response: “One thing you could try is separating the task from the handoff: write the task, its current owner, and whether a proposed change has actually been accepted. For example, ‘dinner — Alex; swap requested from Sam; pending’ avoids treating a question as agreement. A shared note or paper can do this. Try it for three evenings and see whether it reduces follow-up questions.”

If discussing the product and rules permit: “Disclosure: I work on Front Stoop, a household coordination project. Our demo explores this exact distinction, but it uses fictional data and isn't a connected inbox. Happy to explain the workflow here; no need to sign up.” Do not pretend to have used it as an independent customer. No unsolicited DMs, disguised links, or repeated posting after removal. Read each community's current rules before participating.

Creator brief

Audience: two adults making the evening work, with optional parent-specific variant. Deliverables proposed: one 30s vertical, three alternate two-second hooks, clean master, captioned master, thumbnail. Story: both adults are capable; the system of questions is the joke. Demonstrate only fictional cards. Say “launch preview” and label synthetic/demo visuals. No claims of saved hours or personal usage unless independently true and approved. Clearly disclose paid relationship in spoken/on-screen/platform tools as applicable. Use original or appropriately licensed audio; specify organic and paid usage term, geography, editing rights and Spark/partnership permissions in writing before contracting. Proposed fee $250–750 per asset is a negotiation assumption, not a market quote. Evaluate audience relevance, comment quality, story clarity and on-camera warmth, not follower count alone. No outreach or purchase has been made.

Short email sequence (only after explicit opt-in)

Email 1, immediately. Subject: Your evening deserves a clearer start. “Thanks for asking to hear about Front Stoop. The launch preview shows a fictional household getting a clearer view of tonight, tomorrow and who's handling what. It's an illustrative demo; no real mailbox is connected. Watch the launch preview: [approved preview link]. What's the question your household repeats most often?”

Email 2, day 3. Subject: A request isn't an accepted handoff. “Try this tonight: give one responsibility a current owner. If plans change, keep that owner until the other person accepts the swap. A note on the fridge works. Our Coverage Board demo makes that distinction visible. See the fictional handoff: [approved preview link].”

Email 3, day 7. Subject: Tonight. Tomorrow. Who's got it? “Before the evening gets busy, write down one thing for tonight, one thing for tomorrow, and who owns each. That's the idea behind Front Stoop's Evening Brief and Coverage Board. Want to give feedback on the preview? Reply with what was clear and what wasn't.”

Email 4, day 14. Subject: What should we make clearer? “We're still learning from households about the evening handoff. If you'd like to help, reply and we can arrange a short preview conversation. No real mailbox connection is needed for the fictional demo.” All messages require sender identification, working unsubscribe/preferences, and no assumed product availability. Suppress the series on opt-out. Do not send a “welcome to your account” email to a preview subscriber.

6. Conversion, activation, retention and referral

Prelaunch preview experience

Hero: “Know what's next. Know who's got it.” Supporting copy: “Explore how Front Stoop's Evening Brief and Coverage Board bring tonight, tomorrow and household responsibilities into a clearer picture.” Primary CTA: Watch the launch preview (opens this actual video locally for review; future web button opens approved embedded video). Beside CTA: “Illustrative demo. Synthetic data. No real mailbox connected.”

Page sequence: 15s hook → full preview → three steps (see evening, check owner, accept handoff) → actual availability → honest FAQ → optional consent-based research interest form once built. No logos, testimonials, countdowns, fake scarcity, pricing, or unimplemented signup. Form specification: email, optional segment, separate unchecked marketing permission, purpose and deletion contact. Preview must be watchable without a lead gate. Confirm success and deliver the promised preview; don't silently enroll a mailing list. A static story board without a functional consent backend remains a prototype and must not collect data.

FAQ: “Is it live?” Repository currently says offline; this is a preview. “Does it connect my email?” No real mailbox is connected in this demo. “Does a swap notify someone?” The synthetic demo changes state; don't promise real messages. “Are gift prices current?” Stored snapshots are not live tracking. “What does it cost?” Pricing has not been verified or announced here.

Prelaunch activation proxy is preview comprehension, not product activation: viewer correctly names the next evening action, its owner, and that the data is synthetic. Qualified demand = an explicitly consenting adult in the target household segment who reports a recurring coordination problem and requests updates or research participation; count once per household where it can be established without collecting unnecessary details.

Postlaunch, conditional on released capabilities

Onboarding proposal: explain product mode and permissions → choose a fictional sample or approved real-data setup → review one evening → assign one responsibility → demonstrate pending versus accepted swap → invite another member only if actual multi-user sharing is released. Never build the habit around connecting an unavailable integration. Let users skip inbox setup and see the conceptual value first if supported.

Initial value event: household reviews a Brief and confirms at least one meaningful responsibility owner. Shared value event: two eligible members participate and one handoff is explicitly accepted. Neither is currently a proven real-household production event. Instrument only as capabilities ship.

Retention: user-selected evening cadence; quiet days stay quiet; weekly optional reflection on upcoming coverage; contextual reminder only for genuinely pending user-chosen action. No fabricated urgency, message-content analytics, or daily notifications by default. At day 7 ask “Was the evening clearer?” and “What did you still coordinate elsewhere?” Treat answers as qualitative, not causal proof.

Referral trigger: after three distinct useful evenings and a positive voluntary response, offer “Know another household that might like this?” with a preview link. No cash incentive until unit economics and abuse controls are known. Household invitations are activation, not net-new household referrals. Keep both metrics separate.

7. Budget and experiments

All budgets below cover 90 days, are unspent planning scenarios, and exclude tax. Media and sponsorship purchases require explicit approval. Labor valued at $60/hour is an opportunity-cost assumption. Production excludes team labor to avoid double counting; it covers external editing/audio/creator deliverables if commissioned. No forecast of paying customers is possible without pricing and production conversion data.

Lean external production assumption: $400 editing adaptations + $200 audio/art refinement. Moderate: four $500 creator assets + $1,000 editing. Growth: eight $750 assets + $2,000 editing. These are examples, not commitments. Reallocate reserve only after evidence. With no approved public destination, media spend remains $0, regardless of scenario.

Planning math, not sourced performance benchmarks: model paid-social CPM $12–24, outbound CTR 0.7–1.2%, landing-page lead conversion 3–8%, 60% of raw leads qualified. CPC = CPM/(1,000×CTR): $1.00 best case to $3.43 worst case. Qualified CPL = CPC/(lead CVR×0.60): $20.83 to $190.48. At $900, roughly 4–43 qualified leads under these assumptions, not a guarantee. Search CPC planning range $2–5, lead CVR 4–10%, 70% qualified: qualified CPL $28.57–178.57. Do not mistake a preview lead for a customer or apply revenue ROAS without revenue.

First three tests and decision rules

1. Comprehension before clicks (days 3–10). Eight household interviews; randomize initial hook order across participants. Proceed if at least six correctly explain the two core jobs and at least seven understand synthetic/non-connected status. If not, revise once and test with four fresh households. This is a usability gate, not a statistically representative survey.
2. Hook A vs B (weeks 3–4, only after approval). Same audience, destination, length, spend and placements; vary only first three seconds. Up to $600 total. Aim for 3,000 impressions and 30 outbound clicks per variant; cap spend even if sample is not reached. Directional winner needs ≥20% better outbound CTR without poorer qualified-preview rate. Below these counts, label inconclusive; don't force a winner. Stop immediately for misleading expectations. Hold user-level overlap as low as tools reasonably allow.
3. Handoff-first vs Brief-first landing narrative (weeks 5–6). Stable winning hook, random split, one CTA. Target 100 qualified landing sessions per variant before judgment. Primary: qualified leads/session; secondary: correct comprehension and preview completion. Adopt ≥25% relative lift only if quality doesn't decline and uncertainty is reported; otherwise keep the simpler page and collect more. With low samples, use interviews rather than claiming significance.

Scaling gate: two consecutive weekly cohorts meeting a provisional $50 qualified CPL ceiling, ≥70% lead qualification, and no material product misunderstanding. This ceiling is a learning budget guardrail, not an LTV-derived CAC target. Require at least 20 qualified leads before scaling spend; lean scenario may never reach this gate. Increase no more than 20% every three days; monitor quality and cohort mix. Stop a variant after $150 with zero qualified leads; investigate destination friction and attribution before declaring no demand. Pause channel after two controlled revisions fail the ceiling. Postlaunch add sustained activation and retention thresholds before growth spending: provisional ≥40% household activation within seven days and ≥30% week-four meaningful use among activated households; validate denominator and sample ≥30 activated households. These thresholds are management hypotheses, not industry standards.

8. Ninety-day execution calendar

Roles: G growth/founder (decisions, research, channels); C creative/editor (animation and adaptation); P product/engineering (truth and measurement); O community/operations (consent and scheduling). One person may fill several roles; weekly lean capacity ≈10 hours combined. Production work in this delivery reduces setup load, but recruitment and approvals still take real time.

First two weeks, day by day

Weeks 3–13

Each active week: three originals maximum, one reusable educational asset, one founder note, 40 minutes of community listening, Friday learning review. Email every other week at most unless user-triggered. If product stays offline for all 90 days, replace acquisition/activation weeks with private preview research; do not describe that work as a successful launch.

9. Measurement and learning

Proposed event names: preview_start, preview_50, preview_complete, research_interest_submitted, marketing_opt_in, brief_reviewed, coverage_owner_confirmed, swap_requested, swap_accepted, household_invite_accepted, referral_activated. Maintain event dictionary with trigger, source, allowed properties, dedup key and mode (synthetic, test, production). Production events require engineering implementation; this delivery doesn't instrument the app. Never send message text, sender addresses, household names, calendar titles, wish-list contents or notes to ad platforms. Use anonymous identifiers and aggregate reporting.

UTM convention: utm_source=instagram, utm_medium=organic_social or paid_social, utm_campaign=fs_evening_handoff_2026q4, utm_content=receipt_hookA_15s_v1. Search uses paid_search; creators use distinct source names and creator. Do not put personal data in query strings. QR print and partners get distinct codes. Retain first-known and latest-known touch where consent supports it, plus optional “Where did you hear about us?” Don't attribute an entire household's later action twice because two members saw ads.

Weekly Friday 30-minute review: data integrity and denominator first; compare spend → visits → qualified demand; review five comments/interviews; separate cohort mix from creative effects; log one decision and its evidence; choose only one major variable for next week. Keep a learning ledger: hypothesis, version, dates, spend, sample, result, uncertainty, decision, owner. Browser privacy, cross-device use, partner sharing, dark social, view-through modeling and small samples limit attribution. Do not add platform-reported conversions together as unique people. Use periodic holdouts when scale permits; before then, label directional observations honestly.

Evidence and launch boundaries

Repository sources: README.md; docs/evening-brief-screen.md; docs/evening-brief-rules.md; docs/coverage-board.md (including ITP-243 accepted swaps); docs/junk-guard-actions.md; docs/sender-rule-crud.md; docs/itp-310-wish-list-plan.md; docs/itp-354-wish-list-sharing.md. Product claims must track current implementation rather than old issue descriptions alone. The rendered cards are original illustrations, not captured product screens.

Evidence register and source links are in sources.md. Competitor and platform descriptions are bounded summaries of official sources, not independent effectiveness studies. No invented testimonials, quantified outcomes, commercial pricing, users, integrations, AI features or security certifications appear in campaign copy. Every spend amount and performance target is labeled an assumption. Public distribution, ad launch, outreach, publication, and production deployment remain unperformed and require the user's explicit authorization.