# Running a pilot with Wake

> A pilot is a named company we invite, onboarded with every step pre-done that can be pre-done. Thirty days, free, one site. The company does three things: claim the desk from the invite link, confirm the host, deploy one file. Wake does the rest.

## What a pilot gets

- A **pre-filled desk**: the invite link `/wake/pilot/<code>` already knows the site, the hosting stack and the readiness score. Claiming it is one sign-in; the site field is locked to the pilot host.
- **Three ways to confirm ownership**, pick the easiest: a `<meta name="wake-verify">` tag on the homepage, a DNS TXT record, or a well-known file. After the intro call Wake can also **vouch** for the host, so the Verify button passes on the first press.
- **The collector file for your stack first.** Wake reads the homepage response headers once (Next.js on Vercel, Cloudflare, Express…) and puts the matching file on top: `nextjs-middleware.js`, `cloudflare-worker.js` or `express.js`. Each already carries the ingest key and the endpoint; the site secret stays in your environment.
- **An engineer handoff page** at `/wake/pilot/<code>/brief.md`: what Wake is, where the site stands today, the three steps, the CLI commands. No secrets in it, safe to forward.
- **A playbook for their AI tool** at `/wake/pilot/<code>/playbook.md`: a deep scan of the site turned into ordered tasks with the exact files to add (llms.txt from their own pages, robots groups, agent card, JSON-LD, the collector for their stack) and a curl per task. Save as `wake-playbook.md`, point Claude Code or Cursor at it. The signed-in version on the desk also carries the ownership tag and the ingest key.
- **A checklist** on the Install screen: claimed → ownership → collector → first agent → AI connected. The same list is what we watch on our side.
- Everything a paying desk gets: agents, sessions, pages, where they stop, ranked fixes with evidence, alerts, benchmarks, the API, the MCP server and the CLI.
- A written review at day 14 and at the end.

## What we ask

- Deploy the collector within the first week. One file, one redeploy.
- Fix at least one friction item the desk ranks, so both sides see a before/after.
- Two 20-minute calls. Honest feedback, including where the desk was wrong.

## Timeline

| Day | What happens |
|---|---|
| 0 | Invite email with the pilot link and the brief. Readiness already run. |
| 0–2 | Claim the desk, confirm the host (or ask us to vouch), deploy the collector. |
| 2–14 | First agents land. Alerts and fixes start ranking. |
| 14 | Review call: what agents did, what to fix first. |
| 15–30 | Fix, recheck readiness, watch the before/after. |
| 30 | Closing review in writing. Decide together whether to continue. |

## Privacy, in one paragraph

The collector sends a timestamp, method, page class (never the URL), status code, operator family (from the user-agent, then discarded) and an opaque per-agent hint computed on your side with your own secret. Raw IP, user-agent, query strings, bodies, cookies, referrers and prompts never leave your infrastructure. Wake keeps the hostname, the account email, hashes of keys, and the pilot code. Full detail: [Privacy](/wake/docs/privacy).

## For the Wake operator

Pilots are minted from a terminal, never from the public site:

```bash
node scripts/with-local-credentials.mjs scripts/wake-pilot.mjs create https://example.com --company "Example" --contact "Ada"
node scripts/with-local-credentials.mjs scripts/wake-pilot.mjs list
node scripts/with-local-credentials.mjs scripts/wake-pilot.mjs vouch <code>
```

`create` runs the readiness check and the stack detection, prints the invite link, the brief link and the signup link. `vouch` is only for a host whose contact we have confirmed; it is recorded as the verification method `pilot` on the desk, visibly.