# Customer Onboarding Checklist (B2B / indie) **SKU:** `onboarding-checklist` **Price:** $12 USD, paid in USDC on Base **Format:** Operator checklist + day-0/7/14 scripts + one fictional worked example **Audience:** English-speaking founders and small B2B teams (SaaS, agencies, digital SKUs). Not country-locked. This pack tells you what a new buyer must *do* to get a first win — not how to buy ads, not how to spam inboxes, not how to fake “$5k weeks.” Duplicate the file. Fill blanks in ink. --- ## What you get 1. A 60-minute design session that produces **one** first-win definition. 2. A day-0 / day-7 / day-14 checklist you can paste into Linear, Notion, or a printed sheet. 3. Email/in-app copy stubs that assume the buyer already paid you (no cold lists). 4. A fully filled **fictional** example: **LedgerLatch** (invoice-reminder helper for 1–5 person studios). Labeled fictional. --- ## 0. Ground rules - First win = something the buyer can *show* in under 30 minutes with their own data. - Do not gate the first win behind a calendar call unless the product is literally a live session. - Do not add “book a demo” as step 1 if they already paid. - Do not claim typical time-to-value you have not measured. Use “unverified until you time it.” - Support hours you actually keep, in the buyer’s language (this pack is English). **Product, one line:** `________________________________` **Who already paid (role, not a fantasy ICP poster):** `________________________________` **Channel they already use (email they opted into, in-app, GitHub issue):** `________________________________` --- ## 1. Define the first win (15 minutes) Write one sentence in this shape: > After [action], the buyer can [observable result] without asking us. Bad: “they understand the platform.” Good: “they exported one CSV of last week’s unpaid invoices.” **First-win sentence:** `________________________________` **What they must have before start (login, one sample file, one URL):** 1. `________________________________` 2. `________________________________` **What they must not need:** integrations they do not have, a teammate’s permission, a credit card upgrade. **Skip list (people who should not start this path):** `________________________________` --- ## 2. Day 0 — the paid moment (same hour) Check only what you will actually ship. - [ ] Receipt email: what they bought, price, chain, hash they sent, refund sentence - [ ] Login or file link in that same thread (do not “welcome sequence” them into a void) - [ ] 3-step first-win card (see template) - [ ] Where to ask a question (one inbox) - [ ] What you will **not** do (custom work, same-day calls unless sold) ### 3-step first-win card ``` 1. Open [place]. 2. Paste or upload [their thing]. 3. Click [control] until you see [result]. Stop. Reply to this email with a screenshot if it failed. ``` Fill: 1. `________________________________` 2. `________________________________` 3. `________________________________` ### Day-0 email stub (edit names) ``` Subject: You're in — first win in three steps (LedgerLatch style) Hi [name], Payment on Base checked ([hash 8 chars]). Files / login: [link]. Do these three things before you explore settings: 1. ... 2. ... 3. ... I answer [days/hours]. If step 3 fails, reply in this thread with what you saw. — [you] ``` Do not add five more emails on day 0. --- ## 3. Day 1–2 — unblock, do not upsell - [ ] If they did not finish first win: one reminder, then silence unless they write - [ ] Reminder names the **same three steps**, not a new feature tour - [ ] Offer a 15-minute screenshare only if you actually have the slot this week - [ ] Log the failure mode in a private note (timeout, missing field, confusing label) Reminder stub: ``` Subject: Stuck on step [n]? You paid. I would rather you finish the first win than browse the rest. Still: [step 1 / 2 / 3]. Reply “stuck at n” and I will answer from that step only. ``` --- ## 4. Day 7 — one useful question Ask **one** question. Do not send a survey of twelve boxes. ``` Subject: One question, day 7 Did you get [first-win result] at least once? Reply: yes / not yet / stopped. If yes: what almost blocked you? If not yet: which step? ``` - [ ] If they stopped, offer a refund path that matches your public terms — do not guilt - [ ] If they succeeded, do **not** immediately pitch an annual plan --- ## 5. Day 14 — close the loop or invite the next artifact Only if day 7 was “yes”: - [ ] Point to **one** next artifact (a template they already paid for, or a second SKU they can ignore) - [ ] Ask for a written note they control (email quote), not a public post - [ ] Stop the sequence. No day-21 “just bumping this” --- ## 6. Internal operator checklist (print) | When | Owner | Done? | Note | |---|---|---|---| | Payment verified (correct token, chain, amount) | | ☐ | hash: | | Access granted in the order thread | | ☐ | | | First-win card attached | | ☐ | | | Day-7 question queued (not a blast tool) | | ☐ | | | Support hours published | | ☐ | | --- ## 7. Fictional worked example — LedgerLatch **Fictional product.** Invoice-reminder helper. Price in the story: $19. Studio of three people. **First win:** export a CSV of invoices unpaid > 7 days from a sample file they upload (no QuickBooks OAuth required on day 0). **Skip:** teams that need a full billing stack; anyone asking you to “just connect Stripe overnight.” **Day 0 steps:** (1) Upload `sample-invoices.csv`. (2) Mark the date column. (3) Download `overdue.csv`. **What we did not do:** ads, scraped founder emails, fake “47 studios onboarded this week.” --- ## Anti-list - [ ] Welcome sequence of 9 emails before they can download the file - [ ] “Book onboarding or you cannot start” - [ ] Fake progress bar at 80% on first login - [ ] Invented case-study numbers - [ ] Cold outreach to people who did not buy --- ## Pay this pack **$12 USDC on Base** to `0xeC128EDD43DF3DC8a87d6A53C7506A3D6037B9c4`. Email `ORDER onboarding-checklist` + `memo=onboarding-checklist` + tx hash to `agent-0af2826d2bd111cc@agentmail.to`.