Nurture: ONE's own run

The decision

We nurture one silence: Brian made a key and then went quiet, with no payment link and no sale. Brian is a person or an agent. The lesson's three silences map onto him. He never got going, or he stalled with a link, or he went to Stripe or Coinbase. Each gets one move.

Every message fires on an event plus a wait, never a bare timer. It asks for one action. No discount, no deadline: the key never expires. Sold appears once, in the last message. The older nurture sequence was written for a different buyer, and none of that audience is reused.

The honest limit: a key lives on its owner's machine and ONE never sees it. We reach only people who confirmed an email or opened ONE's chat. Everyone else is unreachable, by design.

What we built

The three silences

Never got going: key made, no link. Move: show the next single step.
Stalled: a link exists and nobody paid it. Move: pay it yourself on practice money.
Went elsewhere: said so in message 5. Move: one polite close.

Timing. Let W be one wait beat, a workflow delay step. Start W at the wait key-onboarding already uses and tune it from the first cohort. Message 1 follows the last key-onboarding mail by W. Gaps then run W, W, 2W, 2W, 4W. Before each send, check the crossing; if the action is done, skip to the next rung.

Message 1. Keep it on paper

Subject A: Your key is made. Now what does it do? (38)
Subject B: Keep your ONE key on paper (26)
Preview: 24 words. One sheet of paper. Nothing else to lose.
Body: You made a key on your own machine. ONE never saw it, so ONE cannot get it back for you. One thing now: write the 24 words on paper. If the laptop dies, the paper brings back the key and the wallets. Keep it where you keep a passport. We will never ask for your 24 words. Anyone who does is not us.
The one action: write the words down. CTA: Open /keys, https://one.ie/keys
Chat line: Have you written your 24 words on paper yet?
Done when: the keep step fires (a keep, not proof of paper).

Message 2. Make the link

Subject A: What do you want to be paid for? (32)
Subject B: Make your first payment link (28)
Preview: A name and a price. That is all it takes.
Body: To be paid you need a key and something to be paid for. You have the key. Add one product: a name and a price. Press Storefront link. That link is what your agent sends. Do not wait for it to be good. Make it, then change it.
The one action: make one product and one link. CTA: Make the link, https://one.ie/products
Chat line: What do you sell? Give me a name and a price and I will make the link.
Done when: a product row exists.

Message 3. Pay it yourself

Subject A: Pay yourself. Watch it land. (28)
Subject B: Test your link before a buyer does (34)
Preview: Practice money, a real receipt.
Body: Your link exists and nobody has paid it, you included. Open it. Pay with Stripe's test card, 4242 4242 4242 4242. Nothing real moves: ONE runs on practice money until payments go live. Your shop counts the sale only when it reads it back, and you get a receipt with a transaction link.
The one action: pay your own link once. CTA: Open my link, {{storefront_link}} (VERIFY the merge field exists)
Chat line: Pay your own link with the test card. I will show you the receipt.
Done when: the shop reads the practice sale back.

Message 4. Give your agent a key

Subject A: Most agents can only talk (25)
Subject B: Let your agent send your link (29)
Preview: Yours can be paid.
Body: Your agent can send the link in a chat, in an email, or to another agent. It needs a wallet of its own first. Run npx oneie where your agent works. It gets its own key and its own addresses, and a limit that only you can raise.
The one action: run the one line. CTA: npx oneie
Terminal line (proposed, not built): Your agent can sell and be paid. Here is how.
Done when: the agent's wallet exists.

Message 5. The honest question

Subject A: Should I stop writing to you? (29)
Subject B: Did you go with someone else? (29)
Preview: One word is enough.
Body: I have written a few times about your key and I do not want to be noise. Did you go with Stripe, Coinbase or something else? Reply "else". Good luck, and your key still works if you come back: it never expires and ONE cannot open it. Still on it? Reply "on" and name where you are stuck: key, link or agent.
The one action: reply with one word.
Routing: "on" goes to the team. "else" starts the close.

Message 6. The last note

Subject A: The last note about your key (28)
Subject B: Your key works whenever you come back (37)
Preview: No expiry. No catch.
Body: This is the last email in this series. Your key does not expire, so waiting costs nothing. The key, the wallets and the payment links are free. If you want to learn to sell with your agent beside you, there is Sold: a course where people and agents learn to sell together. $100, with one month of the community. The first chapters read free at https://one.ie/learn. Reply "less" to hear from us rarely, or "stop" and we stop.
The one action: read a chapter, or reply.

The polite close for the went-elsewhere silence. Reply sent once: "Thanks for trying ONE. Your key is yours and it works if you return." After that, one release note when something real changes, never a timer.

How each message closes

Action done: mark the path from key to link to sale, then move to the next rung.
Unsubscribe, bounce or complaint: warn, suppress at once.
Silence after message 6: dissolve the sequence and fade the contact.
Any invented deadline is a warn at weight 1.0 and is never sent.

Footer on every email. One click stops these: {{unsubscribe_url}}. Postal address: VERIFY (a gap today).

Receipts

key-onboarding already sends two mails to anyone who confirms their email from the key flow: "Your ONE key: what to do next", then "Put your key to work" (one.ie/web/src/lib/workflow-templates.ts:1031). Our six start after those. Not edited.
No email names a wallet address, and the 24-word line stays (text/key.md:1816).
Probed 2026-11-12, HTTP 200: one.ie/keys, /w, /get-key, /learn, /learn/setup, /sold.
https://one.ie/products returns 302 to /w/shop; /cards returns 302 to sign-in. /learn/saas/one returns 404, so the record page is not on production yet.
pay.one.ie/status read ok, network testnet, 2026-11-12. Hence "practice money" in message 3.

Still open

No wire finds a dormant key holder. audience:winback is the likely door. VERIFY.
The key flow's events carry nothing about the key. VERIFY how "no product yet" is joined to a confirmed email.
"Put your key to work" sells credits at $1 for 1,000. That belongs to the old offer and clashes with message 4. Replace it before this sequence runs.
Reply routing and a "less" opt-down: VERIFY a receiver exists.
Stripe's test card for a key holder who has not connected /cards: VERIFY.
"Free" is said of the key, wallets and links only. "0% fees" is not printed: ONE takes nothing from a card sale and the card network takes its fee. Tony says "0% fees"; flagged.
No open rates, no cohort, no reactivation number. None invented. Sold purchase end to end is unverified.

Do it yourself