# StackPilot Start Here — Launch Review Card

Status: local draft only  
Product: StackPilot Start Here — 7-Day Worksheet Pack  
Purpose: choose the next validation path before any live system is connected.

## Hard stop

This card does **not** approve publishing, deployment, email capture, checkout, outreach, paid ads, analytics, account creation, terms acceptance, credentials, payment/tax/KYC details, or private identity/customer data.

AI/Hermes may draft, organize, compare, score, and create local files. Tim approves every external action.

## Review order before choosing a path

Use the same Start Here review order before deciding whether this becomes a manual test, free lead magnet, or paid product:

1. **Manual router** — confirm a beginner can choose the first manual from the stuck point.
2. **Sample artifacts** — confirm the fictional examples show what “done” looks like without fake proof.
3. **Manual validation kit** — prepare approved sharing, feedback capture, and objection logging.
4. **Launch review card** — choose WAIT, manual validation, free lead magnet, or paid product.
5. **System contact sheet** — verify pages, downloads, ZIP, manifest, and approval guardrails.

Decision states:
- **WAIT** if the router, samples, proof labels, or approval gates are still confusing.
- **Manual validation first** by default: Tim approves audience, wording, delivery method, feedback questions, and response log.
- **Free lead magnet later** only after email provider, privacy/unsubscribe language, deployment, delivery behavior, and analytics scope are approved.
- **Paid product later** only after checkout, support, refund/terms, tax/KYC/payment owner steps, delivery testing, and public listing copy are approved.

## Path A — Manual validation first

Best when: learning buyer questions and objections matters more than list size or revenue.

Tim approval fields:
- Exact audience or small test group.
- Exact wording of the share message.
- Delivery method.
- Feedback questions.
- Where responses are logged.
- What Hermes may prepare but not send.

Hermes-safe prep:
- One-page share script.
- Objection log.
- Feedback scorecard.
- Local delivery checklist.
- Follow-up notes for Tim to review manually.

Measure:
- Replies.
- Confusion points.
- Requested examples.
- Objections.
- Which manual/day creates interest.

Blocked without approval:
- Sending, posting, DMs, public page launch, email capture, analytics, accounts.

## Path B — Free lead magnet later

Best when: list-building is the priority and Tim approves the email/download system.

Tim approval fields:
- Email provider.
- Sender identity.
- Privacy and unsubscribe copy.
- Delivery email.
- Public URL/deployment.
- Analytics and click tracking scope.
- Download delivery behavior.

Hermes-safe prep:
- Landing copy.
- Thank-you page copy.
- Delivery email draft.
- Privacy checklist.
- QA script.
- No-hype proof/FAQ blocks.

Measure:
- Visits.
- Opt-ins.
- Download completion.
- Replies/questions.
- Unsubscribes.
- Source clicks.

Blocked without approval:
- Email capture, email-provider account setup, deployment, analytics, public download gate.

## Path C — Paid product later

Best when: direct revenue validation matters more than reach.

Tim approval fields:
- Price.
- Checkout platform.
- Refund/terms language.
- Support inbox/path.
- Delivery test.
- Payment/tax/KYC owner details.
- Public listing copy.

Hermes-safe prep:
- Listing copy.
- FAQ.
- Fulfillment email.
- Support macros.
- No-hype proof blocks.
- Launch QA checklist.

Measure:
- Checkout views.
- Purchases.
- Support questions.
- Refunds.
- Objections.
- First-user completion feedback.

Blocked without approval:
- Checkout, payment, public listing, marketplace upload, tax/KYC, terms acceptance.

## Recommended default

Manual validation first. It creates the cleanest learning with the fewest connected systems. The next real-world gate is Tim approving the audience, exact wording, delivery method, feedback questions, and response log.