Three files, written from doing the work rather than reading about it. Short on theory, specific about what to do and in what order. You download it and use it. No course, no subscription.
Land in the inbox, not the spam folder.
The 25-point pre-send checklist with the exact SPF, DKIM, DMARC and rDNS records to paste. The 21-day warm-up schedule in day bands, with volumes, the per-mailbox ceiling and the warning signs that mean stop. The spam-trigger audit for what actually gets filtered now. Bounce triage tables including the quiet failures that mean you are already in trouble. The recovery plan for when you are already in the spam folder, and the point at which a domain is worth abandoning. Seven templates that read like a person wrote them, and the legal floor across CAN-SPAM, GDPR and CASL in operator language.
What to say, when to say it, and what to do when it breaks.
The pre-launch work that actually decides how a launch goes, the launch sequence hour by hour, and the announcement thread structure that decides whether technical readers believe the rest. The channel map for web3 including an honest section on KOLs. AMA preparation as a credibility test. The quiet period from day 3 to day 30 that looks like failure and is not. How a token distorts every metric you have, and incident communication from the twenty-minute first statement through to the post-mortem.
Marketing to people who hate marketing.
Why developer marketing is structurally different and the four normal-marketing assumptions that sink you. The channel map with what each channel is genuinely good for. Documentation as the primary marketing surface. The launch sequence for a developer-facing product. The habits this audience punishes and rewards. Web3-specific traps, and which popular metrics are actively misleading for developer products. Written from running social and content for developer-infrastructure projects including Ankr, zkSync and SKALE.
Payment is handled by Stripe; card details never touch this server. Files download immediately on the next page, and that page keeps working, so you can come back to it later.