3 · Business & legal readiness

TL;DR

Objective — make the business side real, not a placeholder: a customer needs something to land on, a way to pay, and the legal pages that make billing legitimate, because technical green is necessary but not sufficient.

User part + done-when

👤 User part — the cloud accounts are people-only: generate the legal policies from a template service, create the products/prices in the payment provider’s dashboard, and flip to live keys; an agent can wire the integration and webhook handlers but can’t click “create product.”

Done when the landing page, /privacy + /terms + contact route, transactional email, pricing/payment flow, and analytics + social meta are all live and verified on the real domain.  ·  ⏱ ~2–3 hr  ·  🔀 mixed (👤 dashboards + policy generation, 🤖 integration).

Background

A customer also needs something to land on, a way to pay, and the legal pages that make billing legitimate. Build and test the entire flow on test keys first — live keys are the very last switch.

flowchart LR
  Land[Landing page] --> Pay[Test-mode checkout]
  Pay --> Legal[Terms · Privacy · Refund]
  Legal --> Live[Switch live keys last]

Steps

1. Build the landing page

A real entry point (a route in the app, a marketing site, or a one-pager) covering the seven sections: hero with value proposition, problem, top-three solution, how-it-works, pricing, social proof, and a footer CTA. Unauthenticated visitors see it; authenticated users redirect to the dashboard.

1. Publish the landing page with all seven sections and the authenticated-user redirect.

   • ✅ Unauthenticated visitors see the landing page; authenticated users redirect to the dashboard.

2. Publish legal pages

Privacy Policy at /privacy, Terms of Service at /terms, Cookie Policy (if EU/UK traffic), Refund / cancellation policy (if selling), plus a working contact route. Cross-check the full legal bar from Phase 10 sign-off and Phase 7 legal — don’t drop pages the earlier gate required.

Who does this

👤 User generates the Privacy Policy and Terms from a reputable template service — a person picks and approves the policy text; an agent then wires the routes.

1. Wire /privacy, /terms, /cookies (or generator-hosted cookie policy), /refund (if selling), and a contact route, all reachable from the footer.

   • ✅ Legal pages and the contact route load and are linked in the footer; cookie + refund pages match the Phase 10 bar when applicable.

3. Wire transactional email

Set the from-address and from-name, then wire the core templates: welcome, payment succeeded, payment failed, trial-expiring, and re-engagement. Confirm each actually delivers (check SPF/DKIM/DMARC pass).

1. Send a test of each core template and confirm authentication passes.

   • ✅ Welcome, payment-succeeded, payment-failed, trial-expiring, and re-engagement emails deliver with SPF/DKIM/DMARC passing.

4. Configure pricing & payment

Choose a model (a free tier plus a premium trial is the safe default), create the products and prices in the payment provider, wire the billing integration and webhook handlers (checkout.session.completed, customer.subscription.deleted, invoice.payment_failed), and add the trial/subscription gating middleware. Test the full path with the provider’s test cards and webhook forwarder before switching to live keys.

Who does this

🔀 User + Agent — 👤 User creates the products and prices in the payment provider’s dashboard; an agent wires the billing integration, webhook handlers, and gating middleware.

1. Create the products/prices, then wire the webhook handlers. Listen for checkout.session.completed, customer.subscription.deleted, and invoice.payment_failed, and add the trial/subscription gating middleware.

   • ✅ The full path clears with the provider’s test cards and webhook forwarder, and gating middleware enforces the trial/subscription.

5. Install analytics & social meta

Install analytics with sign_up, trial_started, and purchase events, and add Open Graph + Twitter Card tags (with a 1200×630 image) so shared links preview correctly.

1. Fire the three events and add the social tags.

   • ✅ sign_up, trial_started, and purchase events register, and a shared link previews with the correct OG/Twitter card.

Live keys are the last switch

Build and test the entire payment flow on test keys. Swap to live keys only after the end-to-end test passes — and confirm the keys in both .env and any in-database settings table agree.

Checklist

Do not mark this step done until every box below is checked.

• 🤖 Landing page — seven sections live; authenticated users redirect to the dashboard.
• 👤 Legal pages — /privacy, /terms, and contact route live and footer-linked.
• 🤖 Transactional email — all five core templates deliver; SPF/DKIM/DMARC pass.
• 🔀 Pricing & payment — products/prices created (👤), integration + webhooks wired and tested.
• 🤖 Analytics & social meta — sign_up/trial_started/purchase fire; OG/Twitter cards preview.

→Next step

Support & onboarding