30-Day Content Calendar
Generated from the Product Brain, in the Brand Kit voice. Edit, approve, then schedule — human-in-the-loop by default.
# Pushcast — 30-Day Post-Launch Content Calendar
~4–5 posts/week, sustainable for a solo founder. Every entry is seeded from a real item in Pushcast's own Product Brain. Channels: **X**, **LinkedIn (LI)**, **Changelog**, **Email**.
## Week 1 — Launch & the contrarian thesis
| Day | Channel | Format | Hook / angle | Seeded from |
|-----|---------|--------|--------------|-------------|
| Mon | X + LI | Launch thread | "I freeze at the blank tweet box, so I built a tool that reads my repo." | Positioning + the launch thread |
| Tue | X | POV / opinion | "Every marketing tool starts from your landing page. That's backwards." | Differentiator: marketing from code, not the page |
| Wed | Changelog | Feature spotlight | "How the Product Brain cites a real file for every feature." | Feature: Product Brain + evidence auditor |
| Thu | LI | Build-in-public | "Customer zero is the product itself: Pushcast markets Pushcast." | Step 11 recursion / self-Brain |
| Fri | Email | Digest | Week 1 recap: what shipped, what early founders said, one Brain that surprised someone. | JTBD: traction without becoming a marketer |
## Week 2 — Trust (the developer's objection)
| Day | Channel | Format | Hook / angle | Seeded from |
|-----|---------|--------|--------------|-------------|
| Mon | X | Behind-the-scenes | "'Code is read, not stored' is a line in the Mapper, not a policy page — here's the boundary." | Differentiator: stream-and-discard architecture |
| Tue | LI | Feature spotlight | The secrets denylist: what gets skipped before a model ever sees it. | Feature/signal: secrets denylist |
| Wed | X | Quick explainer | Minimal GitHub scopes + short-lived RS256 tokens — why we store only the installation id. | Feature: repo connect / §8 trust |
| Thu | Changelog | Spotlight | The evidence auditor: a hallucinated path fails the run. | Feature: evidence auditor |
| Fri | X | Build-in-public | A small thing I shipped this week (real changelog item → the loop in action). | Watcher/changelog cadence |
## Week 3 — The loop & control
| Day | Channel | Format | Hook / angle | Seeded from |
|-----|---------|--------|--------------|-------------|
| Mon | X + LI | Demo | The ten-minute morning: j/k/a/v/e — clearing a week of drafts in under two minutes. | Feature: keyboard approval loop |
| Tue | Email | Story | "git push is the only marketing skill you need" — the commit-driven engine, shown. | Feature: Watcher + digest |
| Wed | Changelog | Spotlight | The trust ladder: draft → scheduled-with-veto → autopilot, per channel. | Differentiator: trust ladder as code |
| Thu | X | POV | "AI that posts for you is a liability. AI that drafts for you is a co-founder." | JTBD: approve before anything goes out |
| Fri | LI | Build-in-public | Reflection: building a privacy-first dev tool as one person. | Brand: built by one, for one |
## Week 4 — Proof, breadth, and the ask
| Day | Channel | Format | Hook / angle | Seeded from |
|-----|---------|--------|--------------|-------------|
| Mon | X | Feature spotlight | The recorded provider: the whole pipeline runs (and is testable) with zero credentials. | Differentiator: recorded-provider mode |
| Tue | Changelog | Spotlight | Signals: one screen that answers "is it working?" — the funnel sentence. | Feature: Signals dashboard |
| Wed | LI | Customer story (template) | [TEMPLATE: a solo founder who saw their own Brain for the first time — fill with a real, consented quote.] | ICP: the shipping solo founder |
| Thu | X | Build-in-public | One-month-in: numbers I'm comfortable sharing + what I'm changing. | Build-in-public cadence |
| Fri | Email | Digest + ask | "A month of shipping loud." Recap + referral ask to other solo devs. | Positioning + ICP |
---
**Notes for the founder:**
- Customer-story entries are marked **[TEMPLATE]** — only publish with a real, consented founder.
- Week 2 (trust) is your highest-credibility content with the developer audience — don't skip it.
- Every changelog entry should also seed an X post and an email-digest line — that's the commit-driven engine doing its job on Pushcast itself.