# StackPilot Start Here — Launch Path Brief

Status: local-only decision brief. This file does not approve deployment, email capture, checkout, analytics, account creation, terms acceptance, outreach, payment/tax/KYC work, or public listing.

## Review order before choosing a path

Run the launch-path decision through the evidence row before treating any route as ready:

1. **Approved feedback rows** — only Tim-approved reviewer responses count.
2. **Synthesis memo** — keep exact quotes separate from Hermes interpretation.
3. **Feedback revision worksheet** — make the smallest safe edit to one surface at a time.
4. **Public-page copy pack** — review manual-first, free-magnet, and paid-path language as copy only.
5. **Visual QA checklist** — confirm mobile readability, safety locks, no-live fields, and launch-decision gates.

Free-download and paid-product setup remain queued decisions. This brief does not connect forms, capture, checkout, deployment, analytics, accounts, marketplace listings, or payment/tax/KYC systems.

## Recommendation

Use **Path A: manual validation first**.

Reason: the Start Here system now has enough local product proof — guide route, router, 7-day pack, fictional samples, launch review card, validation kit, synthesis memo, feedback revision worksheet, public-page copy variants, visual QA checklist, contact sheet, and ZIP. The next revenue-relevant unknown is not another page. It is whether a beginner understands the promise and which objections block the first real launch.

## Path comparison

### Path A — Manual validation first

Use now.

- Tim approves exactly who may see the pack.
- Tim sends or personally controls the ask.
- Hermes may prepare scripts, logs, objection buckets, and synthesis templates.
- No email provider, checkout, analytics, deployment, account creation, terms acceptance, or outreach automation is needed.

Primary question: “Does this help a beginner understand the first seven operating files for an AI-assisted solo business?”

### Path B — Free lead magnet

Use later only if approved manual validation and synthesis show people want the pack but are not purchase-ready.

Requires approval for:

- email provider,
- privacy/unsubscribe language,
- delivery test,
- public deployment,
- analytics decision,
- final headline and CTA.

### Path C — Paid product

Use later only if approved reviewer language includes purchase intent or strong willingness-to-pay signal.

Requires approval for:

- price,
- checkout platform,
- refund/terms/support language,
- payment/tax/KYC handling,
- delivery test,
- marketplace/public listing rules.

## Tim approval fields before manual validation

- Approved reviewer type or exact reviewers:
- Maximum batch size:
- Who sends the message:
- Which link/file may be shared:
- Exact ask:
- Feedback questions:
- What must not be claimed:
- Where approved responses will be logged:

## Hermes-safe next work

Allowed:

- refine local copy variants,
- improve fictional sample artifacts,
- update local README, manifest, and ZIP,
- prepare decision/synthesis memos,
- verify local routes and no-live-field safety.

Blocked:

- sending, posting, DMing, contacting, or outreach,
- connecting email capture, checkout, analytics, deployment, public downloads, marketplace listings, or accounts,
- accepting terms,
- using payment, tax, legal, KYC, identity, or private customer details,
- claiming real proof, testimonials, revenue, or customer results before approved human testing.

## Evidence to collect later

After Tim-approved manual review only:

- exact confusion words,
- strongest objection,
- artifact readers find most valuable,
- missing proof request,
- whether anyone asks for a free download or paid version,
- revise / retest / free lead magnet / paid product decision.