DUO Product Target — What We Have · What We Want · How We Get There

Prepared by Revenue | 2026-08-08 | For: Duo 2.0 redesign kickoff (Marcus, Manager, Builder, Operator)

Source of truth for inventory: `projects/duo/audit/` (full site dump, 2026-08-08)

Status: **DRAFT for decision** — open decisions in §4

0. One-Page Summary

We have a live, content-rich marriage product on duo.bz (Compass diagnostic, 28-day program, 67 lessons, strong brand) that is technically a pile of hand-built React apps inside WordPress — brilliant content, fragile delivery, zero backend, and a membership gate that is client-side only.

We want Duo 2.0: a real product with the loop Assessment → Relationship Profile → Personalized Journey → Learning + Couple Activities → AI Coach → Progress/Check-ins → Next Recommendation — subscription-based, account-backed, built on the salvageable IP already on the site, *not* a port of its pages.

We get there in 4 phases: design (2 wks) → build (6 wks) → commerce/accounts (parallel) → launch & growth. Audit is already done. The existing projects/duo/ Next.js app is the seed — but it needs the assessment engine, real accounts, and one canonical curriculum.

1. What We Have

1.1 Live product (duo.bz) — audited 2026-08-08, full dump in `projects/duo/audit/`

Assets worth keeping (the salvage):

**The Compass**12-dimension couple diagnostic: questions, 3–5 options each (+10…−10), scoring ranges w/ insight copy + actions, Partner A/B model`compass_dims.json`, `apps/co2.app0.js`
**Zone model**4 zones: Flourishing “The Eight” (≥80) · Growth “The Solid Fifteen” (≥60) · Stability “The Broader Twenty-Three” (≥40) · Restoration “The Seventy-Seven” (<40), each with positioning copy`apps/co2.app0.js`
**Flight Plan**3 priority tracks (Structural Damage / The Drift / The Stall) w/ root-cause copy, timelines, primary+secondary module routing, legacy projection`apps/co2.app0.js`
**28-Day curriculum (WP)**28 sections, 4 phases (Foundation→Structure→Transformation→Sustainability), each w/ prep/shared/carry steps + course correction`sections28.json`, `apps/28d.app0.js`
**67 lessons**Content library: Foundations 22, Connection 17, Household 19, Assessment 4, Repair 0. Recurring pattern: hook question → symptom picker → content → Script → Apply this → notes + solo-spouse guidance`posts_1.json`, `apps/*.app0.js`
**Content hubs + Router**Pillar hubs (Definition / Why it matters / Signs / Try this / Go deeper / Safety Valve / Faith Layer) + “Where Does It Hurt?” Fundamentals Router`apps/fh2*.app0.js`, `apps/fu2.app0.js`
**Couple tools**Capacity Check (90/10 battery declaration), Delta Detector (partner gaps), Compass Rose radarembedded in apps
**Brand**“Join the Twenty-Three”, 4 pillars, science+faith positioning, book + infographics`pages.json` (home-3), `media_1/2.json`
**Commerce**Book product $9.90→$7.90 (WooPayments/Stripe) · “28 Days Plan” $19/mo auto-renew (Paid Member Subscriptions)`products.json`, register page
**Media**129 items: book cover, full-color book PDF, 11 infographics, ~25 stock, ~91 legacy junk`media_1/2.json`

Known defects (fix in 2.0, don’t port): client-side-only member gating (program source publicly served) · all progress/answers in localStorage (no accounts) · Compass “go deeper” links point to empty pages · no build step (Babel-in-browser) · copy-paste app sprawl (≥2 divergent Compass instances, 2 divergent 28-day structures) · 91 legacy media files · Jetpack Protect captcha locks out even legitimate logins.

1.2 Existing Duo 2.0 seed — `projects/duo/` (Next.js)

Already in the repo and deployable:

  • **Next.js 16 + React 18**, Supabase client wired (`lib/supabase.js` — note: anon key committed, see §4.7), Vercel config
  • **ProgramShell** component library: 4-week/28-day structure, phases (Diagnosis → Safety & Repair → Connection → Mission & System), faith toggle, progress bar, persistence hooks (localStorage)
  • **Days 1–3 fully built** (State of the Union, Defensiveness Detox, The Inventory) with exercises + AI Coach widget + faith integration; **Days 4–28 content spec’d** in `data.jsx`, placeholder rendering
  • **EmailCaptureGate** (locked days 3–7), **AICoachWidget**, Supabase lib
  • ⚠️ **The app’s 28-day structure differs from the WP site’s** (app: Gottman-style titles — Softened Startup, Four Horsemen Deep Dive, Emotional Bids…; WP: The Brutal Assessment, Identify Your Pattern, Stop the Bleeding…). Same underlying concepts, two curricula. **Must reconcile to one canonical structure** (decision §4.4).
  • 1.3 Strategy assets (May 2026 docs)

  • **Vision: “Relationship OS”** — one brand across dating → marriage → repair (`offering-doc-duo.md`)
  • **Flywheel:** social content → duo.bz → free Compass → email → 28 Days → directory/dating (`duo-bz-strategy.md`)
  • **Personas:** the 2AM searcher, the church small-group leader, the dating-app refugee
  • **Pricing proposals:** $67/$147/$347 one-time packages (May) vs $19–29/mo subscription (current site) — **unreconciled, needs decision (§4.1)**
  • **Future lines:** DUO Directory ($39/mo pros), DUO Dating ($24/mo) — Year 2+ per strategy docs
  • 1.4 What we do NOT have yet (gaps 2.0 must close)

    1. No accounts/auth backend (Supabase anon key only — no auth flow, no couples table)

    2. No assessment engine in the app (Compass exists only as WP-embedded JS)

    3. No payment/subscription integration in the app (WP-only today)

    4. No server-side gating

    5. No real AI coach (widget UI exists; no backend logic)

    6. No email/nurture wiring (Klaviyo present on WP, unused in app)

    7. No analytics on user journeys

    8. Two unreconciled 28-day curricula + forked Compass instances

    2. What We Want

    2.1 Product vision

    **DUO 2.0 is the relationship operating system: one product that takes a couple from assessment to lasting partnership — assessment-first, personalized journey, AI-supported, subscription-based.**

    Guiding principles (from Marcus’s direction, 2026-08-08):

  • **Audit now. Redesign next. Convert last.** (Audit done.)
  • **Do not port the 21 WP pages** — extract and classify (classification matrix in `DUO-SITE-AUDIT.md` §4).
  • The product loop is the architecture:
  • Assessment → Relationship Profile → Personalized Journey → Learning + Couple Activities → AI Coach → Progress/Check-ins → Next Recommendation
    

    2.2 The loop, mapped to what we already have

    **Assessment**Compass 12 dims, options, P1/P2, skipIfNoKidsRebuild engine (not port UI)
    **Relationship Profile**Zone assignment, Delta Detector, category breakdown, Compass RoseCouple profile object (Supabase)
    **Personalized Journey**Flight Plan tracks + timelines; fu2 router; 28-day steps as journey templatesJourney engine
    **Learning + Activities**67 lessons (hook→symptom→content→script→apply), hub entries, Capacity CheckStructured learning modules
    **AI Coach***New* — ground in existing diagnostic language + course-correction patternsLLM w/ safety rails (§4.2)
    **Progress/Check-ins**28d progress model (done/notes/course correction/sprint review)Account-backed persistence + check-in cadence
    **Next Recommendation**Flight Plan routing + fu2 + delta prioritiesRecommendation engine

    2.3 Target customers (unchanged from offering doc, validated by site)

    1. The 2AM searcher — married 5–20 yrs, drifting/crisis, one partner initiating. Book → Compass → 28-day.

    2. The church/community leader — wants curriculum; multiplies reach.

    3. The deliberate dater (Year 2+) — values-aligned matching → DUO Dating → marriage prep.

    2.4 Business model (target)

  • **Freemium:** free Compass + profile (lead gen, email capture) → **paid per-couple subscription** for journey + AI coach + check-ins
  • **Book ($7.90–9.90)** stays top-of-funnel; infographic PDF as premium asset
  • **Tier optionality** (decision §4.1): single subscription vs guided cohorts upsell
  • Year 2+: Directory (pro subscriptions) + Dating (premium)
  • **Entitlement model:** everything server-gated by plan; no client-side secrets
  • 2.5 Success metrics

  • **Activation:** Compass completed → profile created (target ≥40% of assessment starts)
  • **Journey:** % starting a journey within 7 days of profile; % completing Week 1; % reaching Day 28/graduation
  • **Couple engagement:** both partners active in first 14 days (the P1/P2 model is our moat)
  • **Retention/Revenue:** week-4 retention, MRR, churn, NRR; $19+/mo ARPU target
  • **North star:** *weekly active couples making measurable journey progress* (proxy: completed steps + check-ins per couple/week)
  • 3. How We Get There

    Phase 0 — Audit ✅ DONE (2026-08-08)

    Full dump + classification in projects/duo/audit/ (report: DUO-SITE-AUDIT.md).

    Phase 1 — Design (wk 1–2) · Owner: Manager + Builder, Revenue inputs funnel/pricing

    Deliverables:

    1. Assessment schema — 12 dimensions from compass_dims.json → question bank, options, scoring (P1/P2), zone thresholds

    2. Content schema — lessons/hubs/28-day steps → learning-module schema (pillar, dimension, pattern, phase, difficulty, safety flag)

    3. Canonical curriculum — reconcile the two 28-day structures + 67 lessons into one journey graph (decision §4.4)

    4. Journey engine design — zones/tracks → module sequences; fu2-style routing as “next step” logic

    5. AI Coach spec — scope, safety rails (crisis → professional help), grounding in existing copy

    6. Data model — Supabase: couples, profiles, assessment_responses, journey_progress, check_ins, entitlements

    7. Pricing + Stripe plan design — decision §4.1

    Phase 2 — Build (wk 3–8) · Owner: Builder (+ Developer)

    1. Assessment app (12 dims, P1/P2 flow) — rebuild of co2 engine in Next.js

    2. Profile + zones + delta visuals (Compass Rose)

    3. Journey engine (from 28d + fu2 + ProgramShell; replace localStorage with Supabase auth)

    4. Learning components — extend ProgramShell with the lesson pattern (hook → symptom → content → Script → Apply → notes)

    5. AI Coach — wire AICoachWidget to backend (decision §4.2)

    6. Check-ins + Next Recommendation (delta + flight plan + router)

    7. Migrate/classify content — 67 lessons + 28 sections + hub entries into the new schema (classification matrix is the input)

    Phase 3 — Commerce & Accounts (parallel, wk 3–6) · Owner: Builder + Operator

    1. Stripe subscriptions + entitlements; server-side gating (fixes the audit’s security finding)

    2. Migrate WP subscribers/orders (WooCommerce + PMS export → Supabase/Stripe)

    3. Klaviyo nurture wiring (Compass → email → trial → paid)

    4. Marketing pages rebuilt from the audit’s “keep” list (home, pillars, book) — Revenue

    Phase 4 — Launch & Growth (wk 9+) · Owner: Revenue, with Operator on partnerships

    1. Funnel live: free Compass → profile → trial → subscription

    2. Book synergy + infographic PDF premium; Amazon + direct sales

    3. Church/therapist partnerships (Operator) + DUO-certified pilot (Year 2)

    4. Content engine: 67 posts → social/SEO calendar

    5. Cohort launches for guided tier (if approved)

    4. Open Decisions (need Marcus/team — these block Phase 1 items)

    4.1**Pricing model**(a) $19/mo per-couple subscription (current site) · (b) one-time $67–347 packages (May strategy) · (c) hybrid: sub + paid cohort upsellDesign §1.7, Phase 3
    4.2**AI Coach**(a) real LLM now (DeepSeek keys available) · (b) rules-based scripts first, LLM later · safety rails for crisis users either wayPhase 2 §5
    4.3**Platform**Web-first (current Next.js) vs Expo mobile — and when. (Earlier thread referenced Expo as the eventual target.)Phase 2 scope
    4.4**Canonical curriculum**Which 28-day structure wins (WP’s 28 sections vs app’s Gottman 28 days), or a merged thirdPhase 1 §3
    4.5**duo.bz role**Keep as marketing home (recommended) vs migrate everything to app domainPhase 4
    4.6**Year-2 lines**When (if) to start Directory / DatingRoadmap
    4.7**Supabase anon key**Committed in `lib/supabase.js` — rotate + harden (RLS) before launchPhase 2

    5. Risks

  • **Content forks** — if 4.4 isn’t resolved, we ship a third divergent curriculum
  • **AI safety** — relationship-crisis users + LLM = real harm potential; safety rails are non-negotiable (crisis detection → human/professional resources)
  • **Client-side gating today** = free-ride risk until Phase 3 lands
  • **Partnership reliance** (church/therapist) needs Operator ownership
  • **Dating/directory** are new markets with big competitors — do not start before core loop is proven (Year 2)
  • **Amazon dependency** for book — direct sales path needed (audit has the PDF asset to enable this)
  • 6. Immediate Next Steps (this week)

    1. Marcus/team: approve target doc + answer decision log §4 (pricing + curriculum at minimum)

    2. Manager/Builder: Phase 1 design kickoff, using projects/duo/audit/ as source of truth

    3. Revenue: pricing proposal (4.1) + funnel draft for the redesign conversation