Solanasis — LinkedIn “First Post After the Shift” Playbook (MD Guide for Another AI)
Purpose: A reusable guide another AI can follow to generate and iterate Solanasis launch/shift posts on LinkedIn.
Context: First public post after shifting/launching Solanasis, with the ORB-first strategy (“Resilience Checkup” / restore-testing hook).
1) Objective (what the first post must do)
- Name the shift: Solanasis launch / repositioning.
- Signal what you stand for: no fear marketing, practical deliverables, fundamentals-first.
- Lead with one wedge: Resilience Checkup (10 days) + real restore test + 30/60/90 plan.
- Invite engagement with a question people can answer easily.
Success signals:
- Comments (especially “tested / not tested / unsure”)
- DMs asking for the one-pager
- Calls booked from warm network
2) The core positioning phrases (use or remix)
- “Backups don’t matter until you restore.”
- “‘Probably fine’ is not a security plan.”
- “Make the fundamentals boring again so teams can move fast without gambling.”
- “No fear marketing. No jargon Olympics. We’ll tell you what matters, what doesn’t, and what to do next.”
3) The wedge offer summary (keep short)
Resilience Checkup (10 business days):
- One real restore test (safe scope)
- Risk register (prioritized, evidence-backed)
- 30/60/90 action plan with owner types
- Exec summary (1–2 pages) leadership/board-friendly
- Maturity scorecard + restore runbook
Do NOT pitch fractional roles first in the initial post.
Sell the checkup → convert later.
4) 7 Post Options (copy-ready patterns)
Option 1 — Contrarian hook (best for engagement)
Angle: restore testing as the uncomfortable truth.
CTA: comment “tested / not tested / unsure.”
Core structure:
- Hook line: backups ≠ recovery
- 1–2 lines why this matters
- Solanasis launch line
- Offer in 1 sentence
- Engagement question
Option 2 — Founder “why now” announcement (clean + credible)
Angle: official launch + mission.
CTA: “What risk do you wish you cleaned earlier?”
Core structure:
- Launch statement
- Why Solanasis exists (short)
- Pattern you’ve seen (small risks compound)
- Question prompt
Option 3 — Mini-story (relatable)
Angle: “the day you need it is the day you learn you don’t have it.”
CTA: “What’s your org’s ‘we should really…’?”
Core structure:
- Short lesson
- Why it led to Solanasis
- Invite comments
Option 4 — Offer-forward (direct but tasteful)
Angle: list bullet deliverables.
CTA: comment “checkup” for one-pager.
Core structure:
- Solanasis launch
- Offer name + timeframe
- 4–5 bullets
- Simple CTA
Option 5 — Short manifesto (brand voice)
Angle: “Because…” lines.
CTA: “Which system do you not fully trust?”
Core structure:
- Punchy “Because…” list
- One sentence mission
- One question
Option 6 — Checklist education (saves + shares)
Angle: 5 questions every org should answer.
CTA: “Which is hardest?”
Core structure:
- Numbered checklist
- “Launching Solanasis…” line
- Ask which is hardest
Option 7 — Poll (fast engagement)
Poll: “When was your last successful restore test?”
Choices:
- Within 90 days
- 3–12 months
- 12+ months
- Not sure / never tested
Post text:
- Solanasis launch
- Why you’re asking
- Promise to share a mini playbook after
5) Recommendation logic (which option to use first)
- If you want comments fast: start with Option 1.
- If you want official + calm: start with Option 2.
- If you want low effort engagement: use Option 7 (Poll).
Suggested sequencing:
- Day 1: Option 1 or 2
- Day 3: the other (1 ↔ 2)
- Day 7: Option 6 (checklist) or Option 7 (poll)
6) Image guidance (stock-friendly, non-cringe)
Best-performing image styles for this message
- Calm operations desk still life
- notebook, pen, checklists (unreadable), laptop blurred, coffee ring
- Clean server room / network closet
- soft lighting, neutral, no “cyber attack” vibes
- Normal meeting (ops/IT/leadership)
- planning, whiteboard, collaboration
- Abstract structure / reliability metaphors
- bridges, steel beams, knots, “structure” imagery
- Minimal branded text card
- “Backups don’t matter until you restore.” + Solanasis logo
Stock search terms (copy/paste)
- “operations desk notebook coffee”
- “IT admin desk checklist”
- “business continuity planning”
- “server room clean” / “data center hallway soft light”
- “team incident response meeting”
- “system diagram notebook”
- “workflow checklist paper”
- “calm office desk night”
Avoid (looks spammy)
- hoodies, neon padlocks, green code rain
- dramatic “cyber attack” thumbnails
- generic handshake stock photos
7) AI instructions (how another AI should generate posts)
Inputs it should ask for (if missing)
- Tone preference: punchy vs calm vs smartcuts
- Target audience: SMB vs nonprofit vs MSP partners
- Location focus: Colorado first or broader
- CTA preference: comments vs DM vs booking link
Output requirements
- 1 post = 6–14 lines max (LinkedIn scannable)
- Clear hook in first 1–2 lines
- One wedge offer sentence
- One engagement question
- Optional CTA (comment keyword)
Safety/credibility guardrails
- No fear-mongering or exaggerated claims
- No “we guarantee no incidents”
- Avoid jargon; keep it plain English
- No “AI-native” bragging; keep that internal
8) Quick template the AI can fill (universal)
Hook:
- “Backups don’t matter until you restore.”
Context:
- “Most orgs don’t find out restore gaps exist until the worst week of the year.”
Launch:
- “I’m launching Solanasis to make the fundamentals boring again.”
Offer:
- “Our entry offer is a 10-day Resilience Checkup: real restore test + 30/60/90 plan.”
Engagement question:
- “When was your last successful restore test end-to-end?”
CTA:
- “Comment ‘checkup’ and I’ll DM the one-pager.”
9) Next iteration suggestions (after the first post)
- Post a short follow-up sharing anonymized poll results (“here’s what I’m seeing”)
- Share a “restore drill” mini-checklist (value post)
- Share a “red flags we see” list (admin sprawl, forwarding rules, etc.)
- Invite MSP partners explicitly in a separate post (partnership angle)