Content Newsletter First Draft
Turn messy notes into a polished newsletter in your voice
I need to write a newsletter. Here are my raw thoughts:
[Dump your messy notes, voice memos, random ideas here]
My newsletter style:
- Conversational, like I'm talking to a smart friend
- Short paragraphs and sentences
- Personal stories and specific examples
- No corporate jargon or buzzwords
Write a first draft that:
1. Opens with a hook (not "In this issue...")
2. Has ONE clear main idea (not five)
3. Includes a specific story or example
4. Ends with something the reader can do or think about differently
5. Under 600 words
Don't clean up my voice. I'd rather sound human than polished.
→ Works best with real notes, not just a topic.
Content Twitter Thread From a Long Idea
Compress a 1,000-word idea into a 7-post hooked thread
Here's a long idea I want to turn into a Twitter/X thread:
[Paste the idea/article/notes]
Rules:
- 7 posts max
- Post 1 = hook (curiosity gap or counterintuitive claim)
- One idea per post
- No "thread 🧵" emoji nonsense
- End with one question that invites replies
- Plain language. No "leverage", "unlock", "scale".
→ Best when the long idea is already publish-quality. Garbage in, garbage thread.
Content Strip the AI Tells
Remove em dashes, generic openers, and AI smell from any draft
Edit this draft to remove all AI-tell language:
[Paste draft]
Rules:
- Delete every em dash (—) and en dash (–). Use commas, periods, or parens.
- Delete openers like "In today's fast-paced world", "It's important to note", "In conclusion".
- Delete weasel verbs: leverage, unlock, harness, navigate, dive into.
- Replace passive voice with active.
- Tighten any sentence over 22 words.
- Keep my voice. Don't replace specific examples with generic ones.
Return the edited draft only. No explanation.
→ Best on any draft AI wrote. Run before publishing anything customer-facing.
Email Client Status Update
Weekly client report in your voice, not corporate template
Write a weekly client status email for [CLIENT NAME].
Context:
- What we shipped this week: [list]
- What we're working on next: [list]
- Any blockers: [list]
- Current spend vs target: [numbers]
- Wins to celebrate: [list]
Tone:
- Warm-professional, operator to operator
- Short paragraphs, scannable
- Lead with results, not activity
- Always end with one clear ask or next step
- No em dashes, no "circle back", no "moving forward"
- Sign off: "Talk Monday."
→ Best when the wins list is specific. Numbers beat adjectives.
Email Sales Follow-Up After a Demo
Re-engage a lead 48 hours after a call without sounding desperate
Write a follow-up email to a prospect 48 hours after our demo call.
Context:
- Their main pain point: [pain]
- The piece of the product they reacted most strongly to: [feature]
- A specific objection they raised: [objection]
- Their next milestone: [milestone]
Rules:
- Subject line: 5 words max, references something specific from the call
- 4 short paragraphs max
- Address the objection directly, do not dodge it
- One concrete next step (calendar link or specific question)
- No "just checking in"
→ Best when you actually noted their objection. Vague pain → vague reply.
Research Competitor Teardown
Map a competitor in 10 minutes — positioning, weaknesses, gaps
I want to understand a competitor. Here's their site: [URL]
Do the following:
1. Read their homepage hero, top nav, and pricing page (if public)
2. Identify their core promise in one sentence
3. Identify the 3 most prominent claims/benefits they lead with
4. List signals of who their ICP is (industries, company size, persona)
5. Identify gaps: what they DON'T claim that I could own
6. Note their tone (formal, playful, technical) and content cadence
Output as bulleted markdown. Be specific. Quote their copy.
→ Best with one competitor at a time. Comparing five at once gives mush.
Research Customer Pain Mining
Extract real pains from raw transcripts, reviews, or Reddit threads
Below are raw inputs from real customers/prospects:
[Paste transcripts, reviews, Reddit comments, support tickets, etc.]
Do this:
1. Extract every distinct pain point as a one-sentence quote (use their exact words where possible)
2. Tag each pain with: a) urgency (high/med/low), b) frequency (how many sources mention it), c) which persona
3. Group similar pains into themes (no more than 7 themes)
4. For each theme, suggest one headline that would make that audience click
Output: themes table + headline ideas. Plain language only.
→ Best with 20+ raw inputs. Smaller samples produce overconfident themes.
Productivity Plan My Week From My Inbox
Turn inbox chaos + calendar into a 5-day prioritized plan
Here's my context for next week:
- Unread emails I need to act on: [paste subjects/key ones]
- Calendar events already scheduled: [paste]
- Standing commitments (recurring): [list]
- The 3 highest-leverage projects I'm running right now: [list]
- My energy pattern: [e.g., deep work mornings, calls after 2pm]
Build me a 5-day plan that:
1. Protects 2-3 hours/day of deep work for the top project
2. Batches calls/messaging
3. Doesn't overcommit (max 70% of the day, leave slack)
4. Lists each day's "one thing that must happen"
5. Flags anything I should decline or push to next week
Markdown table, day by day.
→ Best done Sunday night. Monday morning is already too late.
Productivity Decision Memo From a Mess
Turn 3 conversations and a Slack thread into a clear decision
I need to make a decision about [DECISION]. Context is scattered:
[Paste Slack threads, meeting notes, emails — anything relevant]
Write me a decision memo:
1. The question (one sentence)
2. The options (max 3, with one-line summary each)
3. The criteria that matter most (and why)
4. Score each option against each criterion (1-5)
5. The recommendation (one sentence + 3 reasons)
6. What we'd need to commit to before deciding
No hedge words. If the answer is uncertain, say so directly.
→ Best when you actually need a decision, not when you want validation.
Social Media LinkedIn Post From an Insight
Turn a real lesson into a LinkedIn post that does not sound corporate
I want to write a LinkedIn post about this insight/lesson:
[The insight + the story/data behind it]
Rules:
- Hook in line 1 (specific number, contradiction, or short story moment)
- 5-9 short lines, plenty of whitespace
- One concrete example, not a generic principle
- End with a question that invites a real reply
- No emojis. No "thoughts?" closer.
- Don't use the words "leverage", "unlock", "synergy", or em dashes.
→ Best with one concrete story. "I learned that..." beats "in general..."
Social Media Repurpose Long Post to 3 Short Ones
Get 3x mileage out of one good post
Here's a long post that did well: [paste]
Extract 3 standalone short posts from it. Each should:
- Make ONE point
- Work without context from the original
- Have a different angle (not just shorter versions of the same thing)
- Be under 100 words each
- End with no CTA, just the idea itself
→ Best with a post that already worked. Do not repurpose flops.