Confidential · Internal
Bitcoin Storm · Marketing Programme · April 2026

One operator,
one million users.

Lead-Operator Model 18-Month Delivery User-Funded Retainer
Abstract

This document specifies the marketing programme designed to secure one million paid founding participants within eighteen months of protocol launch. The programme is built around a single lead operator who owns delivery end-to-end, sources and contracts a cohort of up to fifty sub-affiliates, promotes a deputy layer from inside that cohort, and is paid through a user-funded retainer structure that ties compensation directly to the deliverable.

The founder personally funds the first four months of programme operations through a $500,000 bootstrap commitment covering the lead operator's $50K/month retainer, an early sub-affiliate retainer pool, the deputy stipend pool, and a contingency float. From month five onward, the retainer is paid from the $5 Operating Fee Reserve — the ring-fenced operational portion of each participant's $100 entry — on a running-balance basis. If users do not subscribe, the kitty does not fill, and the retainer is not paid. On delivery of the target, a $12M performance bonus is paid to the operator at Year 5 Bonanza Day from residual protocol surplus, capped at 15% of residual to preserve participant distribution structurally.

Section 01 · The Design Choice

Why one operator
beats five contractors.

There are two broad ways to structure influencer-led user acquisition at scale. The first is a committee-of-voices model: five hand-selected influencers, each with different audience segments, each contributing attributable paid users, coordinated by a programme manager. The second is a lead-operator model: one senior operator who already runs this kind of work commercially, builds out a cohort of small sub-affiliates from networks they've earned over years, promotes a deputy layer from inside the cohort, and owns delivery end-to-end.

The committee approach is conventional and works in principle. Three problems show up in practice. First, five new professional relationships all starting at launch creates coordination cost that scales super-linearly, and quality of coordination depends disproportionately on a programme manager being hired for the first time. Second, the five voices don't already work together — any team efficiency has to be built from scratch inside an eighteen-month window. Third, the commercial burn is front-loaded: five retainers plus a manager retainer is a fixed monthly commitment regardless of whether users are arriving or not.

The lead-operator model collapses those problems into one: a single experienced operator who already runs this work commercially, who has an existing network of voices they've vetted over years, and whose retainer is funded directly from subscription inflow rather than from a fixed monthly commitment.

"One operator with the right network and the right track record is worth more than five contractors starting from scratch — and costs meaningfully less in coordination, supervision, and founder attention." — Programme Design Rationale · April 2026

Section 02 · The Structure

One operator,
their own team.

The programme is built around a lead operator who owns delivery of the one-million-user target. That operator sources, contracts, and manages a cohort of up to fifty sub-affiliates, and promotes a five-person deputy layer from inside that cohort to handle day-to-day supervision.

The lead operator

One senior individual, experienced in running commercial crypto media at scale. Not a manager, not a marketing executive — an operator who themselves is a known voice in the space and has the network to pull in others. Reports directly to the founder. Full authority over execution.

$50K
Monthly
Retainer
$12M
Year 5
Bonus
18
Months
Maximum

The cohort underneath

Up to fifty sub-affiliates contracted by the lead operator. Each is a small operator with a real audience: a Bitcoin podcaster, a regional newsletter writer, a meetup organiser, a niche YouTube creator, a community manager. Each is capped at 10,000 paid users. Each operates on a tier-escalating retainer ($500/month at probation rising to $7,500/month at delivery) plus a 1 BTC bonus at Year 5 if they hit their cap. The lead operator sources, vets, contracts, and manages them; the Storm signs each contract directly.

Five of the highest-performing sub-affiliates are promoted to deputy roles, each overseeing approximately eight of the others. Deputies retain their own sub-affiliate retainer and 1 BTC bonus track; the deputy stipend ($3,000/month during bootstrap, ~$2,800/month from month five) is paid on top. Total deputy stipend pool across the engagement: $100,000 — $20K from the founder bootstrap, $50K from the Operating Fee Reserve. The deputy layer is not external: it is structurally a tier-up promotion within the cohort, which removes onboarding cost and keeps incentives aligned.


Section 03 · What The Operator Has To Sell

The founding cohort
is the real product.

The operator's deliverable is one million paid founding participants. The protocol is designed so that those first one million participants receive structural advantages that close by code once the millionth slot is filled. This is not a marketing flourish layered on top of the protocol — it is encoded in the smart contract before launch and cannot be extended, repeated, or recreated. The founding cohort is a single, time-bounded category, and the operator's deliverable and the participant's benefit are mechanically the same target.

This alignment is the operator's strongest asset. Every other crypto launch promises early-bird advantages that turn out to be discretionary, extendable, or quietly diluted. The Storm's founding-cohort advantages are encoded, on-chain, and verifiable. The operator can sell that without caveat.

The two founding-cohort advantages

Founding Cohort — What the First 1M Receive
1
3× daily ticket multiplier — every day, for five years. The first one million participants receive three entries in every daily BTC draw, every day, for the full five-year cycle. Once the millionth slot is filled, the multiplier closes by code. Post-founding participants enter at the standard one-ticket rate. There is no path back into the founding cohort once it closes — not by referral, not by waitlist, not by founder discretion.
2
275 BTC founding draw — exclusive, sealed at Year 5. An additional sealed Year 5 BTC distribution available only to the founding cohort. 275 BTC distributed across founding-cohort-only winners via VRF. Post-founding participants are not eligible. The mechanism is exclusive by code, not by promise.
Daily Ticket
Multiplier
275
BTC Founding
Draw
1M
Cap At Which
Both Close

Why this matters for the campaign

The founding-cohort mechanic gives the operator three things most crypto user-acquisition campaigns cannot honestly offer: genuine scarcity, time-bound urgency, and structural fairness. Genuine scarcity because the founding cap is enforced by code, not by promise. Time-bound urgency because the cohort closes when the millionth slot is filled — there is no "limited time" softness about it. Structural fairness because non-founders are not excluded from the protocol, only from the founding-specific advantages — they enter at the standard rate, on standard terms, with full participation in the daily draws.

The campaign message writes itself: be in the first million, get a 3× advantage in every daily draw for five years, plus exclusive entry to the 275 BTC founding draw — or wait, miss the cohort entirely, and enter at standard rate after. The operator is not selling a token, a yield, or a forecast. They are selling a structurally-bounded category of participation that disappears at a specific number.

What this means for delivery

The operator's KPI (1M paid users in 18 months) is the same number at which the founding cohort closes. There is no commercial daylight between the operator's job and the participant's benefit. This alignment makes the campaign honest in a way the space rarely permits — every paid participant is a paid founding participant until the cap is hit. There is no point at which the operator must change message, soften urgency, or pivot to a secondary cohort to keep generating user flow.

If the cap is hit before month 18, the engagement closes successfully and the operator's bonus locks in. If month 18 arrives without the cap being hit, the engagement closes with the founding cohort partially filled — non-founders begin entering at standard rate from that point onward, but the operator's bonus does not pay. The mechanic gives the operator a hard, public, verifiable target the protocol itself reinforces.

"Every other early-bird programme in crypto is a marketing claim. The founding cohort is a contract clause that closes at a specific number, on-chain, with no override." — Programme Design Note · April 2026
Note on the underlying mechanic: Both the 3× daily ticket multiplier and the 275 BTC founding draw are specified in the protocol's economic model and are encoded in the launch canister. They are not adjustable by founder action after deployment. The operator can confirm both mechanics directly from the protocol whitepaper before signing.

Section 04 · How It's Funded

Founder for four months,
users after that.

The retainer funding structure is the most important feature of the programme. Rather than a fixed monthly burn, retainer payment is tied directly to subscription inflow. If users don't come, the payment doesn't either.

Cost line Amount Funded by
Operator retainer, months 1–4 $200,000 Founder $500K bootstrap
Sub-affiliate retainer pool, months 1–4 $90,000 Founder $500K bootstrap
Deputy stipend pool, months 3–4 $30,000 Founder $500K bootstrap
Float / contingency $180,000 Founder $500K bootstrap
Operator retainer, month 5 onward $50,000 / month Operating Fee Reserve — running balance
Sub-affiliate retainers, month 5 onward Per cohort tier Operating Fee Reserve
Deputy stipends, month 5 onward ~$2,800/mo × 6 Operating Fee Reserve ($270K balance of $300K total)
Operator Year 5 bonus (if target hit) $12,000,000 Year 5 residual surplus
Sub-affiliate 1 BTC bonuses (per delivering sub-affiliate) 1 BTC each Year 5 residual surplus (within 15% cap)
Deputy 1 BTC cohort bonus (per qualifying deputy) 1 BTC each (6 BTC total) Year 5 residual surplus (alongside cohort bonuses)

The running-balance mechanic

From month five onward, the $5 Operating Fee Reserve — the ring-fenced operational portion of every paid participant's $100 — accumulates in a running balance. Good months build the balance; lean months draw from it. As long as the running balance exceeds the operator's $50K monthly retainer plus sub-affiliate retainers and deputy stipends due that month, payments are made in full. If the balance is insufficient, payments are proportional.

If users aren't subscribing

The balance empties. No payment is made. The operator is paid by the pipe they are hired to fill; if the pipe is dry, neither the operator nor the Storm has cash available. This is deliberate. The operator accepts this risk because the Year 5 bonus is the real upside; the Storm accepts it because it removes the fixed-burn problem entirely.

Month 5 baseline

To fully fund the $50K operator retainer from a single month's Reserve inflows requires 10,000 paid users that month ($50K ÷ $5). With sub-affiliate retainers and deputy stipends running in parallel (~$17K/month for the six deputies plus the active sub-affiliate cohort), the baseline required climbs to roughly 14,000–18,000 paid users per month, depending on cohort tier mix. This is the performance floor the operator must maintain from month five onward, averaged across good and lean months.

$500K
Founder
Bootstrap
16K
Users / mo
Baseline
$1.6M
Max Programme
Burn (18 mo)
On the $1.6M maximum: This assumes eighteen full months at $50K/month to the operator, the full sub-affiliate retainer envelope, and the full $300K deputy pool, less the $500K founder contribution, less the portion covered by Reserve. In practice the actual Storm spend is meaningfully less than this — most of the burn is from the subscription inflow, not from Storm capital. The only cash the Storm is at risk of losing is the founder's $500K bootstrap commitment.

Section 05 · Year 5 Bonus Structure

Real money for real delivery.

The Year 5 bonus pool is the primary economic incentive for the programme team. It is concentrated on the lead operator, with separate 1 BTC bonuses for each delivering sub-affiliate.

Role Year 5 Bonus Conditions
Lead operator $12,000,000 1M paid users within 18 months AND protocol settles profitably
Each delivering sub-affiliate 1 BTC each Sub-affiliate hits their 10,000-user cap. Up to 50 sub-affiliates eligible.
Programme total cap 15% of residual surplus Operator bonus paid first if residual is tight; sub-affiliate BTC bonuses pay from what remains within the cap.

Payment waterfall — what residual surplus actually means

Year 5 residual surplus is the profit remaining after two prior obligations have been settled in full: the 2,100 BTC purchase, and the pro-rata distribution to all participants. Whatever is left at that point is the residual. In the protocol's design scenarios this residual is large — potentially in the hundreds of millions or billions, depending on BTC price at settlement. The bonus pool draws from this residual only.

The 15% cap on programme bonuses exists to preserve participant capital structurally. In high-residual scenarios — the cases the protocol is designed to produce — the cap is far above what the programme actually pays, so it is not the binding constraint. The $12M operator bonus and the sub-affiliate 1 BTC bonuses are paid in full.

Only in low-residual scenarios does the cap bind. If residual surplus is below approximately $66.7M, the $12M operator bonus alone reaches the 15% cap. In that case, bonuses pay proportionally — operator first, sub-affiliate BTC bonuses from what remains within the cap. If residual is zero — the case where the protocol settles exactly at the BTC threshold with nothing extra — no bonuses are paid, regardless of whether the user target was hit. Participant capital is always senior; the bonus pool draws only from genuine surplus.

"Participant capital is senior. Always. The bonus pool is a tax on surplus, not a claim against principal. In the scenario where the protocol only just works, participants are protected and the programme team gets nothing — which is the correct alignment."

Section 06 · Key-Person Risk

Honest about the
single point of failure.

Concentrating delivery on one lead operator introduces real key-person risk. If the operator exits mid-engagement, the programme collapses in a way that a five-voice programme wouldn't. This is not dismissed or rationalised; it is managed through four specific contractual safeguards.

Contractual Safeguards
1
Minimum deputy layer within 90 days. The operator must have promoted at least three deputies from the contracted sub-affiliate cohort within the first 90 days of launch. This ensures the programme is never a single-person operation in practice, even while it is a single-operator contract on paper.
2
Replacement obligation on voluntary exit. If the operator voluntarily exits before the 1M-user target is hit, they must introduce a qualified replacement operator. Bonus entitlement is forfeited if this obligation is not met. This makes a mid-engagement walk-out economically painful.
3
Dashboard ownership. All performance data, attribution infrastructure, and campaign records are owned by the Storm (not by the operator personally). Continuity infrastructure survives any change of operator.
4
Pro-rated bonus if target hit before exit. If the operator delivers the 1M-user target during their tenure and subsequently exits on good terms, the Year 5 bonus is locked in. This protects them against a Storm attempting to avoid the bonus via post-delivery termination.

Section 07 · Sequencing

Critical path to launch.

Execution Sequence
1
Counsel review on bonus structure. Hassans confirms the bonus structure (concentrated on one operator at $12M) does not disrupt the protocol's classification analysis. Timeline: 2–3 weeks.
2
Founder-led operator outreach. Direct approach to preferred lead candidate. Mutual NDA. Initial conversation. Term sheet shared only after NDA and initial mutual interest confirmed.
3
If preferred candidate declines: secondary candidates approached in sequence (not in parallel). Each receives the same term structure. Agency RFP (existing document) activated only as tertiary fallback.
4
Contract negotiation. Both sides' counsel involved from draft stage. Term sheet converted to binding engagement agreement. Does not activate until Gibraltar authorisation is in place.
5
Operator sources sub-affiliates and identifies deputy candidates. From day of engagement activation. Storm supports with product information, regulatory framing memos, protocol documentation — but does not select or veto operator's choices.
6
Launch. Operator and supporting team active from protocol launch date. Retainer commences. Attribution tracking goes live. Weekly reporting to founder.
7
Month 3 gate. Operator presents performance data and makes a recommendation on whether the programme is tracking. Founder decides whether to continue, request renegotiation, or terminate.
8
Delivery or month 18. Programme ends at whichever comes first: 1M paid users secured, or month 18 reached.

Section 08 · Bottom Line

A sharper bet, with
a cleaner kill switch.

The programme is built to minimise founder capital at risk, maximise operator alignment with delivery, and tie retainer spending directly to user acquisition performance. The $12M Year 5 bonus is meaningful enough to attract a top-tier operator without the Storm committing to fixed monthly burn that exists independently of user flow.

The trade-off is key-person risk, managed structurally through four contractual safeguards. The Storm's downside if the programme fails completely is bounded at the founder's $500K bootstrap commitment. The upside if the programme succeeds is a million paid founding participants, a working protocol, and a Year 5 settlement that rewards everyone on the same conditions.

Either outcome is bounded. Either outcome produces useful information. The programme is a calculated bet, not a hope.

"The right lead operator will make the programme. The wrong one will sink it. Everything rides on the first conversation." — Programme Specification · Final Paragraph