# Go-To-Market Product Notes

This document records decisions that affect implementation and future website
copy. It is not customer-facing legal text.

## Initial US plan catalogue

| Plan | Monthly | Annual prepay | Production sites | Commercial differentiator |
| --- | ---: | ---: | ---: | --- |
| Solo | $15 | $119 | 1 | Core site agent, audit logs, BYOK AI Chat |
| Growth | $39 | $299 | 10 | Central chat analytics, multi-site jobs, 10 client seats |
| Agency | $89 | $699 | 30 | Growth features plus white-label visitor chat and 30 client seats |

All plans use a 7-day WooCommerce trial. The proposed 30-day guarantee must be
implemented in WooCommerce policy/workflow and reflected in reviewed Terms
before it is advertised as a customer promise.

## Product language

- Lead with outcomes: saved maintenance hours, safe bulk changes, customer
  support outside business hours, and visible approval/audit controls.
- Do not lead with MCP, embeddings, or internal architecture in primary sales
  copy. Explain those only in technical documentation.
- AI Chat is BYOK: customers pay their own AI provider and the provider key
  remains encrypted in their WordPress site.

## Client seats and white label

Client seats are restricted SaaS users for an agency customer's site scope. They
must never receive the agency's provider key, billing access, organization-wide
site list, MCP secrets, or broad write permissions. White-label controls change
the public chat attribution/branding only after the SaaS entitlement is active.

## Future limited-time lifetime promotion

A promotional lifetime deal is not an unlimited perpetual entitlement. Before
running AppSumo or another marketplace, implement a dedicated Woo product and a
`LIFETIME` SaaS subscription interval with a fixed `accessEndsAt` no later than
five years after purchase. The exact duration, transfer rules, refunds, support
scope, and service-continuity language require reviewed Terms before launch.

## Launch channels

Use marketplace validation and short product demonstrations alongside SEO. The
first website should prioritize concrete before/after workflows; later content
can target qualified comparison and automation-intent searches.