# Stripe SKUs — create after connecting Stripe

**When:** create this single SKU as soon as the Stripe account is connected (Day 1 of the runbook), so a "yes" never waits on setup. **Drafts only** — no link is sent and nothing is charged until the owner explicitly approves (operating rule 3, Payment role).

## The 1 SKU (exact)

| # | Name (SKU / product name) | Price | Billing | Stripe line type |
|---|----------------------------|-------|---------|-------------------|
| 1 | **Website Audit Report** | **$99.99** | **One-time** | Payment link / one-time price |

There is exactly one product. No other SKUs exist — no builds, no subscriptions, no bundles.

## Setup note

- Create the payment link **after** connecting Stripe (Day 1), named exactly `audit-report-9999`.
- Create it in **test mode** and keep it there until the owner approves going live. Nothing is sent or charged before that approval.
- **Drafts only:** the link stays un-sent (or marked draft) until a customer says "yes" and the owner approves the send.

## Stripe ID

- `audit-report-9999` — Website Audit Report, $99.99 one-time

## Customer-facing description (the line the buyer sees at checkout)

- "Website audit report for <Business> — full fix list of everything we found, ranked by impact, each with a concrete fix. $99.99 one-time. PDF emailed after successful payment."

## Rules

- **Never** write "lifetime", "unlimited", "discount", or misleading wording — the checkout must read exactly like the catalog: $99.99 one-time, PDF after payment.
- Test the link with a $0/Stripe test charge before it is ever offered to a customer.
- Approvals only: the owner must approve the exact charge language + amount before any link is sent to a customer (Payment role, Approval Flags).