Couples-first

Summary

Every partner action in pattaya is symmetric; solo mode is a degraded state, not the default.

Why it matters

Every incumbent in this vertical — Flo, What to Expect, BabyCenter, Ovia, Peanut, iMumz, MyloFamily, BabyChakra — is mom-only. Partner is absent or a token bolted-on view. But the actual decision to have a kid, the emotional labour of trying, the operational load of postpartum are all shared between two humans.

Couples-first is the single sharpest wedge we have. It is also a CAC solution: two users per install; one paid seat covers the household-as-billing-unit; the partner is the world's best retention hook — a spouse nudging you beats any push notification.

Implications

• Symmetric UX — every action a partner can take, the other partner can take. No "wife primary, husband secondary" hierarchy.
• No solo-first polish — solo mode (surface-mobile-home-solo) is a re-invite prompt, not a great product. If a user runs solo for more than 14 days without inviting a partner, the paywall gets sharper, not softer.
• Household is the billing entity — see household-as-billing-unit.
• Shared surfaces are the default — surface-mobile-home-shared is Home. The AI briefing addresses both partners by name.
• Partner permissions — a partner can view all shared entries; can never view private entries; can never delete the other's data.
• Marketing — every headline is "the two of you," never "for moms."

Related

• household-as-billing-unit — the billing consequence
• ai-not-community — why the "community" is your partner, not strangers
• motivation-is-ritual — the retention hook that only works because it's shared
• persona-undecided-couple — the persona this concept was born from
• 2026-07-27-couples-first-wedge — the ADR

Sources

• .context/raw/deep-research-2026-07-27.json — competitor scan
• .context/wiki/synthesis/competitors.md