LinkedIn (professional, ~150 words): "Most agencies blame scope creep for missed deadlines. The data says it's usually something quieter: nobody agreed on what 'done' looks like at kickoff. We analyzed 200 completed agency projects and found that the ones finishing on time shared one habit... [link]"
Twitter/X (~240 chars): "Agencies that finish projects on time don't have better clients. They agree on 'done' before work starts. 3 questions we ask every kickoff: [link] 🧵"
Instagram (caption, visual hook): "The one question that prevents scope creep 👇 (swipe to see all 3) Most agencies never ask it at kickoff. Full breakdown at the link in bio."
Facebook (~80 words conversational): "We looked at 200 agency projects to find what on-time delivery actually had in common. It wasn't better tools or bigger teams. It was one kickoff habit. Worth a read if your deadlines slip more than you'd like. [link]"
Threads (casual, 2 short paras): "Hot take: scope creep is a kickoff problem, not a client problem. Read our breakdown — link in bio."
One launch, three native captions — Instagram, LinkedIn, and X, each in platform voice.
プロンプト 入力欄 3 件
We are launching on . Write launch captions for Instagram, LinkedIn, and X — one per platform, native to each.
Rules per platform:
- Instagram: hook first line (visible before "more"), 2–4 short paragraphs, 3–5 niche hashtags at the end, one emoji max per paragraph
- LinkedIn: no hashtag stuffing, first line must work as a standalone statement, end with one question to invite comments
- X: under 260 characters, no hashtags, one concrete number or claim
Product facts to use: [3 KEY FACTS OR FEATURES]
Audience:
What we want them to do: [CTA — e.g. join waitlist / start free trial]
出力例
INSTAGRAM
We spent 14 months killing our own best feature.
The old export flow took 9 clicks. People used it anyway — 40,000 times a month. That felt less like love and more like hostage behavior.
So we rebuilt it. One click, any format, works offline.
Launching Tuesday. Link in bio for early access.
#productdesign #saasfounder #buildinpublic #uxdesign
LINKEDIN
Most teams do not have an export problem. They have a nine-click problem.
[...] What is the most-used-but-most-hated feature in your product?
X
We rebuilt export from 9 clicks to 1. 40k exports/month just got 8 clicks shorter. Early access opens Tuesday.
ヒントFeed the model real usage numbers or a concrete "before" pain (like the 9 clicks) — captions built on one specific fact outperform adjective-stacked launch copy on every platform.
ChatGPTGeminiClaude
Instagram/LinkedIn carousel from a blog post
Turn a long post into a 7–9 slide carousel: one idea per slide, swipe-worthy pacing.
プロンプト 入力欄 2 件
Turn this article into a carousel of [7-9] slides for [PLATFORM — Instagram or LinkedIn].
Structure:
- Slide 1: a hook that names the payoff or the mistake (max 12 words)
- Slides 2 to N-1: ONE idea per slide, max 25 words each, no filler transitions
- Last slide: recap in 3 bullets + one CTA:
- After the slides, write the post caption (2 sentences + question)
Keep the numbers and concrete examples from the article; cut the storytelling.
Article:
出力例
Slide 1: Your onboarding email is why they never came back.
Slide 2: 63% of trial users open email #1. Only 11% open email #4. The sequence is the leak.
Slide 3: Email #1 job: one action, done in 90 seconds. Not a feature tour.
Slide 4: Subject lines with the user's goal beat product names 2:1 in our test.
Slide 5: Send #2 after the action happens, not 24 hours later. Behavior beats schedule.
Slide 6: One CTA per email. Two CTAs = half the clicks on both.
Slide 7: Recap — 90-second first win · behavior-triggered sends · one CTA. Steal our full sequence: link in comments.
Caption: We rewrote a 4-email onboarding sequence and doubled activation. The whole teardown is in the carousel. Which email in your sequence gets ghosted the hardest?
ヒントThe "max 25 words per slide" constraint is what makes output usable — without it models write paragraph slides that die in design. Tighten to 18 words for Instagram, loosen to 30 for LinkedIn.
ChatGPTGeminiClaude
A/B hook lines for one post
Ten first-line variants for the same post, split across proven hook patterns.
プロンプト 入力欄 3 件
Write 10 first-line hooks for a social post about , for .
Give exactly 2 hooks in each pattern:
1. Contrarian ("Everyone says X. It's wrong.")
2. Specific number/result
3. Mistake or loss framing
4. Direct question to the reader
5. Before/after snapshot
Max 12 words each. No emoji, no clickbait words (secret, shocking, insane). Audience: .
出力例
Contrarian
1. Posting daily is shrinking your reach, not growing it.
2. Your best content calendar is no content calendar.
Number/result
3. One caption format took us from 200 to 4,100 followers.
4. We deleted 60% of our posts. Engagement doubled.
Mistake/loss
5. You're losing followers in the first seven words.
6. That "link in bio" line costs you half your clicks.
Question
7. What made you unfollow the last brand you unfollowed?
8. Would you stop scrolling for your own post?
Before/after
9. Last March: 12 likes. This March: 1,200. Same product.
10. From ghost town comments to 80 replies — one change.
ヒントRun the 10 hooks past a colleague and ask them to point at one — do not describe, just point. The finger test kills committee-brain and picks the scroll-stopper faster than discussion.
ChatGPTGeminiClaude
Reply to comments in brand voice
Batch-draft comment replies that sound human, match brand tone, and never copy-paste thanks.
プロンプト 入力欄 2 件
Draft replies to these comments on our post.
Brand voice: [2-4 ADJECTIVES, e.g. warm, direct, lightly funny, never corporate].
Rules:
- Each reply is different — no repeated openers, no generic "Thanks for sharing!"
- Match the commenter's energy (short comment = short reply)
- Answer questions concretely; if we don't know, say so and route to
- Critical comments: acknowledge the specific point first, no defensiveness, offer the next step
- Max 2 sentences per reply unless a question needs more
Comments:
[PASTE COMMENTS, ONE PER LINE]
出力例
@mia.builds ("This is exactly what I needed today")
→ Timing is everything 🙌 What are you building with it?
@dev_karol ("Does it work with Notion?")
→ Not yet — Notion sync is on the Q3 board. The waitlist for beta is at the link in our bio.
@sceptical_sam ("Feels like every app promises this and none deliver")
→ Fair — the category has earned that. If you try it and it breaks the promise, tell us where; that feedback goes straight to the roadmap.
@lena.mkt ("price??")
→ Free plan + paid from $9/mo. Full breakdown: [pricing link].
ヒントPaste real comments verbatim including typos and usernames — the model mirrors register much better from raw material than from your summary of "someone asked about pricing."
Hi [Name] — really liked your post on cutting support onboarding time; the "shadow an expert" point matched what I keep hearing from support leads. I work in that space and would enjoy following your take. Either way, thanks for sharing it.
A support team told me their new hires were "useless for a month." Their words, not mine.
The problem wasn't the people. New reps were hunting through 400 pages of docs that changed every week — so they guessed, or pinged a senior rep, who then stopped doing their own job.
We gave them one answer layer trained on those same docs. First-week resolution rates went from 51% to 73%.
The lesson: onboarding speed is usually a findability problem, not a training problem.
Curious how other support leaders are tackling ramp time — what's worked for you?
The person we're looking for has probably built a sourcing function from scratch before — and has opinions about what they'd do differently.
[Company] is hiring a Head of Talent. We're 80 people, pre-IPO, and have never had a full-time recruiter. The next 18 months will add about 40 more. You'd build the process, pick the tools, and own the brand — no inherited playbook.
What we're not: a slow-moving machine where you manage a pipeline someone else designed.
What we are: a team that wants to hire well and is willing to invest in doing it right.
If this sounds like the kind of problem you want, the details are here: [link]
If it sounds like someone you know, tag them.
This week in class
We finished our unit on fractions with a hands-on measuring activity — students used rulers to divide paper strips and then compare and order the pieces. In writing, we drafted our first personal narrative and focused on one craft move: starting in the middle of the action instead of "One day..."
Coming up
Monday is a no-homework night (school picture retakes). Fraction quiz on Wednesday. Our book reports are due Friday, Nov. 8.
How to help at home
Ask your child to show you one fraction using anything at the dinner table — a divided pizza, a cut piece of fruit, whatever's there. Two minutes of real-world practice sticks better than a worksheet.
A moment worth sharing
During our narrative workshop, one student asked if they could write about a hard day instead of a happy one. The whole room got quieter when they read it aloud. That kind of courage is what writing class is for.