Trending today

1

Create a deep RPG character backstory with motivations, flaws, and arc potential

11.8K views
2

Anomaly detection with rolling z-score windows in SQL

11.8K views
3

30-day social media content calendar with post templates

11.6K views
4

Structured logging with correlation IDs across microservices

11.4K views
5

Legacy JavaScript to modern ES2023 refactor

10.9K views

Creators to follow

N
nadia_ux45 followers
D
david_ops45 followers
P
priya_design44 followers
AboutTermsPrivacyHelp

© 2026 teliprompt

AN
anders_blog
4 days ago•
Writing

30-day social media content calendar with post templates

Claude Opus 4.6
text output
#content-calendar
#social-media
#marketing
#copywriting
Views
11.6K
Copies
4.0K
Likes
1.5K
Comments
0
Copy rate
34.0%

Prompt

You are a content strategist. Create a 30-day social media content calendar for a [business_type] targeting [audience]. Include posts for [platforms].

For each day provide:
- Platform
- Content type (carousel, text post, short video script, poll, thread)
- Full copy (ready to post, including hashtags)
- Best time to post
- Hook (first line that stops the scroll)
- CTA

Follow the 80/20 rule: 80% value/entertainment, 20% promotion. Alternate between content pillars: educational, behind-the-scenes, social proof, promotional, and engagement bait.

Customise this prompt

Fill in 3 variables to personalise this prompt

Preview
You are a content strategist. Create a 30-day social media content calendar for a [business_type] targeting [audience]. Include posts for [platforms]. For each day provide: - Platform - Content type (carousel, text post, short video script, poll, thread) - Full copy (ready to post, including hashtags) - Best time to post - Hook (first line that stops the scroll) - CTA Follow the 80/20 rule: 80% value/entertainment, 20% promotion. Alternate between content pillars: educational, behind-the-scenes, social proof, promotional, and engagement bait.

Example output

# 30-Day Content Calendar: SaaS Project Management Tool **Business:** CloudBoard — project management for remote teams **Audience:** Startup founders, product managers, engineering leads (25-45) **Platforms:** LinkedIn, Twitter/X, Instagram **Posting frequency:** 1 post/day (rotating platforms) --- ## Week 1: Establish Authority ### Day 1 (Monday) — LinkedIn **Pillar:** Educational | **Type:** Text post **Hook:** "We analyzed 847 failed projects. Every single one had this in common." **Copy:** We analyzed 847 failed projects. Every single one had this in common. It wasn't budget. It wasn't talent. It wasn't even bad ideas. It was this: No one knew who was responsible for what. The #1 predictor of project failure isn't complexity — it's ambiguity. Here's a simple test. Ask your team right now: "What are you working on this week, and who's waiting on your output?" If they hesitate, you have an ambiguity problem. 3 fixes that take 10 minutes: → Every task gets exactly one owner (not "the team") → Every deliverable gets a due date (not "ASAP") → Every blocker gets escalated within 24 hours (not "when someone notices") Simple? Yes. But 847 teams skipped it. #projectmanagement #startup #remotework #leadership **CTA:** "What's your team's biggest project killer? Drop it below 👇" **Time:** 8:30am ET (Tuesday catch-up scroll) --- ### Day 2 (Tuesday) — Twitter/X **Pillar:** Engagement | **Type:** Thread (6 tweets) **Hook:** "Hot take: Daily standups are a waste of time for 90% of remote teams." **Thread:** 1/ Hot take: Daily standups are a waste of time for 90% of remote teams. Here's what actually works instead: 🧵 2/ The problem with standups: - 15 min × 8 people = 2 hours of combined time - Most updates are "still working on the same thing" - The useful info ("I'm blocked") gets buried in status recaps 3/ Replace with async check-ins: Each person posts in Slack at their start of day: ✅ Done yesterday 🎯 Doing today 🚧 Blocked on Takes 2 minutes. No meeting. Everyone sees it when they're ready. 4/ "But what about face time?" Schedule a weekly 30-min team sync instead: - Celebrate wins (morale) - Discuss blockers (problem-solving) - Align on priorities (strategy) One good meeting > five mediocre ones. 5/ "But my team won't do async updates." That's a culture problem, not a meeting problem. If people won't write a 3-line update, a 15-min meeting won't fix their accountability. 6/ Summary: ❌ Daily standup (2hrs/week wasted) ✅ Async daily check-in (10min/week) ✅ Weekly team sync (30min/week) Net savings: 90 minutes/week per person. What's your take — standups or async? **CTA:** Poll: "Standups: keep or kill?" (embedded) **Time:** 12:00pm ET (lunch scroll) --- ### Day 3 (Wednesday) — Instagram **Pillar:** Behind-the-scenes | **Type:** Carousel (5 slides) **Hook:** "Our product roadmap is public. Here's why." **Slide 1:** "Our product roadmap is public. Here's why." (bold text on brand-color background) **Slide 2:** "Transparency builds trust. When users can see what we're building, they feel invested — not just sold to." **Slide 3:** "Our top 5 requested features right now: 1. Time tracking 2. Gantt charts 3. Client portals 4. Mobile app 5. API integrations" **Slide 4:** "What we shipped last month: ✅ Time tracking ✅ API v2 ✅ Dark mode (you asked 214 times)" **Slide 5:** "What should we build next? Comment your #1 request 👇" **Caption:** Building in public isn't just a trend — it's how we make sure we're building the right things. Our full roadmap is at cloudboard.com/roadmap (link in bio). What feature would change your workflow? Drop it below. 👇 #buildinpublic #saas #productmanagement #startuplife #remotework **CTA:** "Comment your #1 feature request" **Time:** 6:00pm ET (evening Instagram browse) --- ### Day 4 (Thursday) — LinkedIn **Pillar:** Social proof | **Type:** Text post with image **Hook:** "A 4-person startup just replaced Jira, Notion, AND Slack with one tool." **Copy:** A 4-person startup just replaced Jira, Notion, AND Slack with one tool. Not ours (yet). But their story is worth sharing. Sarah runs a design agency. Her team was drowning in tool-switching: → Tasks in Jira → Docs in Notion → Chat in Slack → Files in Google Drive → Time tracking in Toggl 5 tools. 5 logins. 5 notification streams. She did the math: her team spent 45 minutes/day just context-switching between tools. That's 3.75 hours/week. Per person. So she consolidated. One project management tool (yes, ours). One communication channel. One source of truth. Result after 90 days: - 31% more billable hours - Zero missed deadlines (from 2-3/month) - Team satisfaction score: 4.7/5 → 9.2/10 The tool matters less than the principle: every tool you add creates a tax. Every tax slows you down. How many tools does your team use daily? #productivity #tools #startups #projectmanagement **CTA:** "How many tools does your team use? I bet it's more than you think." **Time:** 9:00am ET --- ### Day 5 (Friday) — Twitter/X **Pillar:** Educational | **Type:** Single tweet with image **Hook:** "The meeting that should've been an email starter pack:" **Copy:** The meeting that should've been an email starter pack: 📋 "Let's sync on status updates" 📋 "Quick alignment call" (that lasts 45 min) 📋 "Brainstorm session" (1 person talks, 7 listen) 📋 "Let's get everyone on the same page" (narrator: they were already on the same page) The fix: async-first, meetings-last. Before scheduling any meeting, ask: "Could this be a doc with comments?" If yes → write the doc. If no → keep the meeting to 25 min. **CTA:** "Quote tweet with your worst unnecessary meeting story" **Time:** 11:30am ET --- ### Day 6 (Saturday) — Instagram **Pillar:** Entertainment | **Type:** Reel script (30 sec) **Hook:** "POV: Your PM asks for a 'quick status update' at 4:55pm on Friday" **Script:** [Scene: Person at desk, coat already on, bag packed] Text overlay: "POV: Your PM asks for a 'quick status update' at 4:55pm on Friday" [Cut to: Person slowly sitting back down, dramatic zoom] Text: "Me: sure, let me just pull up the dashboard..." [Cut to: Dashboard showing all tasks green/complete] Text: "When you actually kept your project board updated all week" [Smug face to camera, grab bag, leave] Text: "This is why we use async project updates. Happy Friday. ✌️" **Caption:** The best status update is the one that doesn't require a meeting. Happy Friday, PMs. 🫡 #fridayvibes #projectmanager #remotework #productivity **CTA:** "Tag a PM who does this 😅" **Time:** 10:00am ET --- ### Day 7 (Sunday) — Rest day / Schedule next week --- ## Week 2-4 Content Themes ### Week 2: Build Trust - Mon (LI): "5 signs your project is about to fail" — educational - Tue (X): Customer quote thread — social proof - Wed (IG): Team behind-the-scenes carousel — humanize brand - Thu (LI): Industry data analysis — thought leadership - Fri (X): Poll: "What kills more projects?" — engagement - Sat (IG): Meme reel — entertainment ### Week 3: Convert - Mon (LI): Product launch announcement — promotional (20% slot) - Tue (X): Feature walkthrough thread — educational - Wed (IG): Before/after workflow carousel — social proof - Thu (LI): "Why we built X feature" — behind-the-scenes - Fri (X): Free template giveaway — value - Sat (IG): User-generated content reshare — social proof ### Week 4: Retain & Grow - Mon (LI): Industry trend analysis — thought leadership - Tue (X): Tips thread from power users — community - Wed (IG): "A day in the life" of our team — behind-the-scenes - Thu (LI): Controversial opinion post — engagement - Fri (X): Weekend reading list — value - Sat (IG): Milestone celebration — social proof --- ## Content Pillars Distribution | Pillar | Percentage | Posts/Month | |--------|-----------|-------------| | Educational | 35% | 9 | | Social proof | 20% | 5 | | Behind-the-scenes | 15% | 4 | | Engagement bait | 15% | 4 | | Promotional | 15% | 4 | ## Platform-Specific Rules - **LinkedIn:** Professional tone, data-driven, long-form text posts perform best - **Twitter/X:** Conversational, threads for depth, polls for engagement - **Instagram:** Visual-first, carousels for education, reels for entertainment

Related prompts

Visual storytelling framework for brand narrativesby @mina_poet
Writing
Product launch announcement across all channelsby @elena_creative
Writing
Release notes that users actually want to readby @chioma_words
Writing
Technical blog converter that makes complex topics accessibleby @chioma_words
Writing