Operator Document · Per-applicant use
Bitcoin Storm · Sub-Affiliate Onboarding · Checklist v1.0

From contract
to day fourteen.

Onboarding checklist + welcome pack
What this document is for

You've contracted a new sub-affiliate. The next fourteen days set the tone for the eighteen-month engagement. This document is the checklist you run per new sub-affiliate, plus the templated communications you send them at each stage. Run cleanly, onboarding takes about ten minutes of your time per sub-affiliate. Run sloppily, it consumes thirty minutes and produces an inconsistent experience that the sub-affiliate brings up six months later when something has gone wrong.

The document has two parts. Part A is the checklist itself — fourteen line items the Lead Operator works through across two weeks. Part B is the welcome pack — the four templated communications you send to the sub-affiliate at the stages flagged in Part A. The templates are written to be sent verbatim with only the bracketed personalisation fields replaced.

Part A · The Checklist
Fourteen items, two weeks
Day 1 · Contract signed

The first twenty-four hours.

Move on contract signing immediately. The candidate has just made a commercial decision and is at peak engagement — capitalise on it.

Day 1 · Within 24 hours of signed contract
Send the Welcome Email. See Part B, Template 1. Personalise with the sub-affiliate's first name, primary channel, and the start date confirmed in their contract. Time: 3 minutes · Trigger: contract signed
Generate their unique referral link & promo code. Use the format thebitcoinstorm.io/?ref=XXX where XXX is a 4–6 character alphanumeric tag derived from their handle. Promo code: same format, uppercase. Record both in the master sub-affiliate registry. Time: 2 minutes · Trigger: contract signed
Counter-sign their House Rules. They signed at contract stage; you counter-sign and email the executed copy back. Keep both signed copies on file. Time: 2 minutes · Trigger: contract signed
Add them to the sub-affiliate registry. Single entry: name, contact, channel, referral link, promo code, contract start date, gate dates (Month 2 / Month 4 / Month 9 / Month 18), tier (set to "Tier 1 · pre-delivery"). Time: 2 minutes · Trigger: contract signed
Days 2–3 · First materials

The first asset bundle.

By day three the sub-affiliate has read the welcome email, has their link, and is ready to start. Get them their first batch of approved Library assets.

Days 2–3
Send the Initial Library Bundle. See Part B, Template 2. The first bundle contains five Library entries appropriate to their channel (X, podcast, newsletter, etc.). Pick from existing Library entries; do not create new ones for an individual sub-affiliate. Time: 4 minutes · Trigger: Day 1 complete
Send the One-Page Reference Card. See Part B, Template 3. The reference card is the everything-they-need-to-know summary on a single page. Sent as a PDF or HTML attachment alongside the Initial Library Bundle email. Time: 1 minute · Trigger: included with Library bundle
Open a private Telegram or Signal channel for them. Each sub-affiliate gets a direct line to the Lead Operator. Not a group chat (group chats become noise). One-to-one. State the response-time expectation in the welcome email. Time: 2 minutes · Trigger: Day 1 complete
Days 4–7 · First posts & verification

Watching the first activity.

By day seven the sub-affiliate should have made at least one post using the approved Library assets. Watch for it.

Days 4–7
Verify their first post complies with House Rules. Check: disclosure (#ad / #paidpartnership) present? Approved language used verbatim or with permitted variations only? Referral link / promo code attached? Restricted-jurisdiction targeting absent? If any check fails, message them privately within 24 hours — do not call them out publicly. Time: 3 minutes · Trigger: first post detected
Confirm attribution is firing correctly. Check the protocol's admin canister or attribution dashboard to confirm clicks are being credited to their referral link. If not, escalate to engineering immediately — broken attribution is a contract-cancelling event for the sub-affiliate. Time: 2 minutes · Trigger: first post detected
Days 8–14 · Settling in

The first check-in.

By the end of week two the sub-affiliate is settled. Schedule the first monthly check-in call to set the cadence.

Days 8–14
Schedule the first monthly check-in call. 30 minutes, video, around the day-30 mark. Send a calendar invite with three discussion points: (1) how the first month has felt, (2) what's working / not working in the assets you've sent, (3) anything they need from you. Don't ask for performance numbers in the first month — the volume isn't there yet. Time: 4 minutes · Trigger: Day 7 complete
Send the Referral Request. See Part B, Template 4. New sub-affiliates know other operators in their niche. By day 10–14 they're settled enough to think about who else might be a fit. The ask is explicit, no bonus, no payment — just a one-line "if you know one or two operators who'd suit this, would you mention it to them or to me?". Time: 2 minutes · Trigger: Day 10 complete
Flag deputy-track candidates internally. If during onboarding the sub-affiliate has shown unusually strong audit signals (clean compliance record, high audience-quality scores, organised communication, willingness to be helpful to other applicants) — mark them as a deputy-track candidate in the registry. Six deputies will be promoted from inside the cohort around month three of operations to oversee groups of approximately eight sub-affiliates. The flag is internal only — no need to mention promotion possibilities to the sub-affiliate at this stage. Time: 1 minute · Trigger: Day 14 complete
Move them to "Tier 1 · active" in the registry. Update tier status. Day 14 marks the end of onboarding and the start of the standard delivery period. Their next gate is Month 2 (60 days from contract start, defined in their contract). Time: 1 minute · Trigger: Day 14 complete
File the onboarding record. One line in the Lead Operator's audit log: sub-affiliate name, contract date, onboarding completion date, anomalies if any. End of cycle. Time: 1 minute · Trigger: Day 14 complete
Total time budget per onboarding: ~28 minutes spread across 14 days. Across 50 sub-affiliates that is roughly 23 hours of total Lead Operator time over the recruitment cycle — a manageable load if cleanly batched. Without this checklist, the equivalent work fragments into ad-hoc messages and double-handling and consumes closer to 50 hours.
"The first fourteen days are the only fourteen days when their full attention is on you. Use them, then leave them alone."
Part B · The Welcome Pack
Four templates, sent verbatim
Template 1 · Day 1

The welcome email.

Sent within 24 hours of contract signing. Tone is warm but not gushing. The sub-affiliate just signed a serious contract; treat them as the operator they are.

Subject: Welcome to the Bitcoin Storm sub-affiliate programme · Send: within 24h of contract signing · To: new sub-affiliate

[First name] —

Welcome aboard. Your contract is countersigned and on file, and you are formally part of the Bitcoin Storm sub-affiliate programme as of [contract start date]. Below is everything you need for your first fourteen days.

Your unique referral link: thebitcoinstorm.io/?ref=[XXX]

Your promo code: [XXX]

Both are live. Use either or both in any post. The referral link captures click-through signups. The promo code captures users who heard about the protocol on a podcast or newsletter and arrived via search.

What happens next:

In the next two days you'll receive a separate email with your first batch of approved Storm Copy Library assets — five entries appropriate to your channel. Each entry includes the asset itself, the mechanic it explains, what you can do with it, and what you cannot. The format is the same for every Library entry; you only learn it once.

You'll also receive a one-page reference card that summarises the entire programme on a single page — pin it somewhere, refer back to it whenever you need to.

Your private channel with me is [Telegram / Signal at @handle]. Use it for anything — questions about an asset, attribution issues, post review before publishing if you want a second pair of eyes. I respond same-day during business hours.

Around day 30 we'll have a 30-minute video call to talk through how the first month has gone. I'll send the invite separately.

Your gates: Month 2 [date], Month 4 [date], Month 9 [date], Month 18 [date]. Each one is defined in your contract. The first one is the lightest; you don't need to be at scale by Month 2, you just need to be active and compliant.

Welcome to the programme, and thank you for joining.

[Lead Operator signature]
Lead Operator, Bitcoin Storm

Template 2 · Days 2–3

The initial library bundle.

Sent on day two or three. Five Library entries appropriate to the sub-affiliate's primary channel.

Subject: Your first Library bundle · Send: Day 2–3 · Attachments: 5 Library entries + reference card

[First name] —

Your first batch of approved assets is attached. Five entries selected for [primary channel: X / podcast / newsletter / etc.]. Each is a complete Library entry with the asset itself, what it explains, what you can do with it, and what you cannot.

How to use them:

Pick whichever resonates with your audience. Use the asset verbatim, or pick one of the permitted variations within each entry. Attach your referral link or promo code. Add the disclosure required by your jurisdiction (House Rules Section 03 covers this).

Pace: maximum one Bitcoin Storm post per day on any given platform. Minimum three days between repeats of the same Library entry.

I'll send you a fresh batch every two to three weeks, plus any time we have a campaign moment that needs specific assets (founding-cohort milestones, regulatory updates, etc.).

Also attached: One-Page Reference Card. Everything you need on one page. Pin it somewhere visible.

Anything unclear, message me on the private channel.

[Lead Operator signature]

Template 3 · The reference card

The one-page summary.

Sent as an attachment with Template 2. This is the everything-they-need-to-know-on-one-page document. Either built as a separate stand-alone PDF / HTML page or pasted inline as below. Below is the textual content; the design follows the house style of the rest of the document family.

Format: standalone one-page PDF or HTML · Attached to Template 2 · For sub-affiliate ongoing reference

Bitcoin Storm Sub-Affiliate — Reference Card

Your details

Name: [Full name]
Channel: [Primary channel]
Referral link: [ref-link]
Promo code: [code]
Gates: Month 2, Month 4, Month 9, Month 18
Cap: 10,000 paid users

What you do

Use approved Library entries to introduce the protocol to your audience. Attach your link or code. Add the required disclosure for your jurisdiction. Watch your gate dates.

What you never do

Never describe the protocol as a lottery, gamble, investment, or guaranteed return. Never rewrite mechanics in your own words. Never recruit US persons. Never post without disclosure. Never combine the asset with any third-party product. The full list is in the Sub-Affiliate House Rules, Section 02.

When something goes wrong

Anything — user complaint, regulator contact, press contact, mistaken post, attribution dispute — you forward to me on the private channel within 24 hours and we resolve it together. Self-reported errors are treated more leniently than discovered errors. Always.

Direct line

[Lead Operator name] · [Telegram / Signal / email] · Same-day response, business hours.

Template 4 · Day 10–14

The referral request.

Sent toward the end of the onboarding window. The new sub-affiliate has had two weeks to settle, has seen how the programme works, and is in the right frame of mind to think about who else might fit. The ask is light, no pressure, no bonus.

Subject: A small ask · Send: Day 10–14 · To: new sub-affiliate

[First name] —

Two weeks in. Hope the assets are landing well with your audience.

One small ask: as you've now seen how the programme is structured, you'll have a sense of who else in your space might suit the role. We're still building out the cohort — capped at fifty in total. If one or two operators come to mind who'd be a credible fit, would you either mention the programme to them, or send me their handle and I'll reach out directly? Either works.

No bonus, no commission — just a quiet way for the cohort to grow through the right people. Operators referred in this way tend to be stronger on average than cold-sourced applicants because they've passed an informal pre-filter from someone whose own outcome depends on the network's quality.

If nobody comes to mind, that's also fine. Don't force it.

Either way — talk to you on the day-30 call.

[Lead Operator signature]

Document use: This checklist + welcome pack is run per new sub-affiliate. Across the full cohort of fifty the Lead Operator runs through it fifty times. The templates are designed to be sent verbatim with bracketed personalisation only — deviation is permitted but slows the work and produces inconsistency. Updates to the templates require seven days' notice to anyone holding the document and should be coordinated with the founder.