PairPlay — the spec

PairPlay is a digital marketplace for couples who want to spend less time staring at screens and more time actually connecting. It sells downloadable activity packs, conversation decks, and games — purpose-built for two people navigating both the everyday and the hard stuff. The primary operators are small creator teams (2–10 people) producing and listing the content; couples are the end buyers.

---

Decisions locked

---

The core loop

1. A couple lands on the site via a shared link or social post.
2. They optionally take a short quiz ("What does your relationship need right now?") that surfaces a recommended product.
3. They browse the shop — filtered by category (activities, games, conversation decks) — and select an item.
4. They check out via the payment flow and receive an instant download or access link.
5. They use the asset together offline or at home.
6. A post-purchase prompt encourages them to share the product page, feeding the next couple into step 1.

---

v1 scope

Simple shop — A product grid displaying digital assets (activity packs, games, conversation decks) with cover image, short description, price, and a buy button. Lives on the main storefront page and individual product pages.

Quiz — A short questionnaire (5–8 questions) that maps couple context — mood, relationship goal, time available — to a recommended product or curated shortlist. Lives on a dedicated Quiz page linked prominently from the homepage.

Blog / content hub — A lightweight editorial section housing articles, tips, and external links relevant to couples. Serves SEO and builds trust before a purchase decision. Lives on a /blog route with individual post pages.

---

Deliberately later

• Randomized activity picker by mood/energy level — needs a larger content library to make randomization feel non-repetitive; v2 once catalog depth justifies it.
• Timer and scoring / difficulty toggle / leaderboard — gamification layer that belongs after core purchase behavior is validated.
• Activity library searchable by duration — search infrastructure makes sense once SKU count outgrows a single scrollable grid.
• Photo/video capture and proof of completion — requires moderation tooling; introduce when community features are scoped.
• Share results to Slack or Teams — relevant to a team/workplace context; revisit if audience data shows that use case emerging.
• Offline-playable activity card download — a packaging and design cost; prioritize once bestsellers are identified and worth the production investment.

---

Data model sketch

• users — id, email, password_hash, created_at, referral_source
• products — id, title, description, category, price_cents, file_url, cover_image_url, published_at
• orders — id, user_id, created_at, total_cents, payment_status, stripe_payment_intent_id
• order_items — id, order_id, product_id, price_cents_at_purchase
• downloads — id, order_item_id, user_id, downloaded_at, token
• quiz_responses — id, user_id (nullable), answers_json, recommended_product_id, created_at
• posts — id, title, slug, body_markdown, published_at, external_link (nullable)

---

Screens

• Homepage — hero, value proposition, featured products, quiz entry point, and blog teaser.
• Shop / product grid — browsable catalog with category filters.
• Product detail — full description, preview images, price, and buy button.
• Quiz — stepped questionnaire with a results page showing recommended products.
• Checkout — payment form (Stripe) with email capture for account creation.
• Account / downloads — order history and active download links for purchased assets.
• Blog / post — content hub index and individual article view.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are all here.
• Keep it as the single source of truth while you build, so every decision gets checked against what is actually locked.