Solanasis Docs

solanasis_newsletter_content_playbook

6 min read

Solanasis Newsletter + Content Distribution Playbook (AI-Ready)

Purpose: A clear, repeatable newsletter format + multi-channel content strategy that creates heartbeat on the website while maximizing discovery (Substack) and maintaining list ownership/control (Brevo).

1) The real decision (don’t blur these)

You’re optimizing three separate goals that look like one:

  1. Ownership + control of the audience
    • Deliverability, segmentation, automations, portability, compliance.
  2. Distribution + discovery
    • Network effects, recommendations, platform-native readers.
  3. Website “pulse” + credibility
    • SEO, proof of work, internal linking, conversion paths.

Rule: Choose one canonical home for each goal so you don’t end up with a messy half-solution.

2) Platform roles (what each is best at)

Brevo = Email Engine + List Control

Use Brevo when you care about:

  • Segmentation (by persona, industry, list source).
  • Automations (welcome sequence, re-engagement).
  • “One list to rule them all” for future marketing + sales ops.

Substack = Discovery Engine + Reader Experience

Use Substack when you care about:

  • Being found in Substack’s ecosystem.
  • Low-friction subscribe + reading flow.
  • Optional paid path later.

Website = Canonical Archive + Trust Builder

Use the website when you care about:

  • Credibility for a consulting firm.
  • Conversion (book a call, request assessment).
  • SEO and long-term compounding.

Option A (Recommended): Website = Canonical + Brevo = Send + Substack = Syndicate

Write once → publish on website → send via Brevo → syndicate to Substack.

Why it wins:

  • You own your email list (Brevo).
  • Your site has the real heartbeat (fresh posts + CTAs).
  • Substack becomes top-of-funnel distribution without controlling your business.

4) Syndication strategy (how to duplicate without stepping on yourself)

Preferred approach (low SEO risk)

  • Website: Full post (canonical).
  • Substack: Excerpt (30–60%) + unique intro + link to full post.

This creates multiple vectors without making it a direct mirror.

If you insist on full duplication

Use one of these buffers:

  • Delay: repost full content on Substack 7–14 days later, or
  • Rewrite: change title + opening + section order so it’s not a perfect duplicate.

Rule: Always include “Read the full piece on Solanasis.com” with a clean link.

5) The “heartbeat” newsletter format (web + email friendly)

Site structure

  • Content hub: /field-notes/ or /ops-notes/
  • Newsletter landing page: /newsletter/
    • Promise, cadence, subscribe form, archive, and a single CTA.
  • Every post is an “Issue” (even if it’s weekly/biweekly).

Issue template (repeatable, high-signal)

  1. Title / Subject
    • “The thing everyone ignores until it hurts: ___”
  2. Why this matters (1 short paragraph)
    • Tie to risk, resilience, or operational drag.
  3. The Breakdown (3 bullets)
    • What’s happening, why it breaks, what it costs.
  4. The Fix (5–9 steps)
    • Concrete, do-able, “today/tomorrow” level.
  5. Drop-in Asset
    • Checklist snippet, micro-SOP, script, or “copy/paste” policy.
  6. Single CTA
    • Book a call / request assessment / quick diagnostic.

Rule: One issue = one core idea. Don’t cram.

6) CTA strategy (don’t dilute the ask)

Pick one CTA per issue:

  • “Book a 30-min resilience quick scan.”
  • “Request a Security Assessment.”
  • “Get a Disaster Recovery Verification.”
  • “Ask about Responsible AI implementation.”

Placement:

  • Website: mid-article CTA block + end CTA.
  • Email: one CTA button + one plain-text link.
  • Substack: CTA + link back to full post.

7) An AI-managed workflow that stays sane

Canonical source file

Use one canonical draft source per issue:

  • A single Markdown file in your local repo or
  • A WordPress draft (export to MD if needed).

Channel variants (generated from the canonical)

  • Website version: full post, headings, internal links, primary CTA.
  • Brevo email version: tight intro + “Read online” + CTA.
  • Substack version: excerpt + link to full + subscribe link.
  • LinkedIn version: hook + 6–10 lines + 1 takeaway + link.

Rule: Humans should only approve content. AI does formatting + variants.

8) Editorial guardrails (what to publish)

4 “lanes” that match Solanasis services

  1. Security Basics that actually matter
    • MFA, password hygiene, browser/DNS hardening, backups.
  2. Operational Resilience
    • DR testing, incident readiness, “what breaks first,” tabletop drills.
  3. Systems that play nice together
    • Integrations, identity, access, data flow, documentation.
  4. Responsible AI implementation
    • Policies, safe enablement, rollout plans, vendor risk.

80/20 rule

Every issue should include:

  • One practical “do this today” fix.
  • One “if you have time” upgrade.

9) Metrics that matter (keep it simple)

Website

  • Pageviews on Field Notes
  • CTA clicks (book/diagnostic)
  • Organic search queries expanding over time

Email

  • Open rate trend (direction matters more than exact %)
  • Click-through rate (CTR)
  • Unsubscribes per send

Substack

  • Subscribers gained per month
  • Post views + read time
  • Conversions back to website (via link clicks)

10) 30-day rollout plan (minimal viable consistency)

Week 1: Foundations

  • Create /newsletter/ landing page.
  • Create /field-notes/ hub page.
  • Connect Brevo form + list.
  • Create 2 templates: Issue (web) + Issue (email).

Week 2–4: Publish cadence

  • Publish 1 issue/week (4 total).
  • Syndicate excerpt to Substack.
  • Post a LinkedIn variant.

Rule: Consistency > volume. One strong weekly post beats daily fluff.

11) “Instructions to another AI” (copy/paste)

System-level instruction

  • “Website is canonical. Brevo is email engine. Substack is syndication/discovery.”
  • “Generate channel variants from a single canonical MD.”
  • “One core idea per issue. One CTA per issue.”

Content-generation prompt

  • “Write a Solanasis Field Note about: [TOPIC].”
  • “Use the issue template: Why it matters → Breakdown (3 bullets) → Fix (5–9 steps) → Drop-in asset → CTA.”
  • “Include 2 internal links placeholders: [LINK: Service] and [LINK: Related Field Note].”
  • “Create 3 variants: Website, Brevo email, Substack excerpt.”

Substack excerpt rule

  • “Publish 30–60% of the content only, with a unique intro and a link to the full post.”

12) Voice + style checklist (Dmitri-aligned)

  • Default to we/our voice.
  • Keep paragraphs 1–3 sentences, usually 1–2.
  • Warm, grounded confidence; no hype.
  • Use simple language, explain jargon.
  • Problem → broken system → better way → practical steps.
  • Close with gratitude + an invitation.

Appendix A: Example issue skeleton

Title: The backup illusion (and how to stop gambling)

Why this matters:
Most orgs have backups, but almost none can restore cleanly under pressure.

Breakdown:

  • Backups exist, but restores fail.
  • Credentials and encryption keys get lost.
  • Nobody tests restores when it’s calm.

Fix (steps):

  1. Pick one “golden system” to test monthly.
  2. Document restore steps.
  3. Validate RTO/RPO (time to restore / acceptable data loss).
  4. …
  5. Repeat and expand.

Drop-in asset:
A 10-point restore test checklist.

CTA:
Want us to verify your DR plan in your real environment? Book a 30-min scan.

End.

Graph View