Why this is in the vault
Dickie Bush lays out a concrete, repeatable system for newsletter beginners: the "10 Magical Ways" framework maps directly to 10 starter issues (Tips, Stats, Steps, Lessons, Benefits, Reasons, Mistakes, Examples, Questions, Personal Stories). The piece then goes deeper on how to execute each format — specificity as the primary value driver, stacking multiple magical ways inside a single section, and using subheads as the real promise-delivery mechanism. Practical enough to apply immediately, niche-agnostic.
⚠️ Sponsorship
PS section promotes Substack Starter Kit — Ship30for30's own paid product ("$2M+ in newsletter revenue"). Self-serving upsell; the framework content itself stands independently.
Core framework: 10 Magical Ways
Write your first 10 newsletters as one issue per format:
| # | Format | Example angle (bookkeeping) |
|---|---|---|
| 1 | Tips | Save $2,500 in bookkeeping expenses |
| 2 | Stats | Why bookkeeping is worth the spend |
| 3 | Steps | Get books ready for tax season |
| 4 | Lessons | Hiring a bad bookkeeper taught me… |
| 5 | Benefits | Disciplined bookkeeping all year |
| 6 | Reasons | Don't hire a big firm — here's why |
| 7 | Mistakes | Mistakes costing owners $10k+ at tax time |
| 8 | Examples | Bookkeepers crushing it for clients |
| 9 | Questions | Ask these before hiring |
| 10 | Personal Stories | Times my bookkeeper let me down |
Each issue = 3–7 of the chosen format. Topic stays constant; the lens rotates.
Key principles extracted
Specificity is the value. A newsletter's quality is visible from subheads alone. Vague subheads ("Are you any good?") = low value. Specific subheads ("Have you ever had a client deal with a lawsuit?") = high value. The writing between subheads is secondary.
The 80% rule. Subject line + subheads + specificity = 80% of the newsletter's value. The prose fills in the remaining 20%.
Stack the ways inside sections. A single section can layer multiple magical ways (e.g., a Question subhead followed by Reasons why + a Mistakes callout). Stacking is what makes content feel dense and valuable.
Three permission rules for starting:
- Nothing is a marriage decision — you will iterate
- Sequence doesn't matter — readers don't read linearly
- Don't obsess over perfection — ship and learn
Mapping against Ray Data Co
Strong mapping. Ray is building audience-facing content (newsletter, HQ, Sanity Check) where the "nothing to say" paralysis is a real friction point. The 10 Magical Ways framework is immediately applicable to:
- Sanity Check — each data story can be instantiated as Steps, Stats, or Mistakes rather than invented from scratch. The framework prevents blank-page paralysis for Sanity Check topics.
- RDCO newsletter bootstrap — if/when Ray launches a standalone RDCO newsletter, the 10-issue runway removes the "what do I write about" blocker entirely.
- Agent-generated content scaffolding — the framework is structured enough to prompt a subagent: "generate 3–7 [Tips/Stats/Questions] on [topic]" maps directly to the format.
The principle that readers "buy into the niche, not the sequence" is relevant to RDCO's content strategy: consistency of topic > rigid editorial calendar order.
Related
- [[~/rdco-vault/06-reference/]] — newsletter and writing craft reference collection
- [[Sanity Check]] — primary RDCO publication where this framework applies most directly
- [[~/rdco-vault/02-sops/]] — content production SOPs where this framework could be codified