FerroxLabs newsletter
When to use. When the user runs (or wants to run) a recurring newsletter as an owned-audience asset, distinct from triggered email sequences.
Procedure (stub). Newsletter is a cross-stage owned channel — its job is to maintain mental availability between purchase windows. Pick a cadence (weekly is the common floor for active growth, biweekly is the sustainable minimum), a single recurring format (essay, link round-up, framework breakdown, behind-the-scenes), and one CTA per send. Treat the subject line as a separate craft item routed to Copy. Measure by long-run open-rate trend, click-through to the single weekly CTA, and reply rate (proxy for relationship depth). Coordinate with email-sequences skill so triggered flows and newsletter sends do not overlap on a given subscriber on a given day.
Status. Default tier: user-toggle. Full procedure deferred to Phase 2. Until then, the channel-strategy skill handles cross-channel decisions.