Write an internal all-hands announcement
Address concerns in the memo itself — they'll come up in Q&A anyway.
by @whitney · recommended tool Claude · 0 unlocks
0
You'll need
CONNECTORS
Google Drive
EXAMPLES · WHAT THIS PROMPT PRODUCES
Sample output
**Subject: We're acquiring Tidepool — what it means for all of us** Team, Today we signed an agreement to acquire Tidepool, a 30-person analytics company based in Austin. The deal closes in about six weeks. **Why now.** We've heard the same thing from customers for two years: they love our platform but struggle to turn their data into decisions. Tidepool has spent five years solving exactly that. Building it ourselves would've taken 18+ months; this gets it into customers' hands this year. **What it means for you.** In the near term, almost nothing changes about your day-to-day. Over the next quarter, our product and Tidepool's teams will plan integration together — not as "us and them," but as one team. There will be new opportunities to work on the analytics layer; we'll share how to raise your hand soon. **What stays the same.** Your role, your manager, your comp, and our remote-first policy are all unchanged. This is additive — we are not reducing headcount as part of this deal. **I know acquisitions bring uncertainty.** It's fair to wonder about your team, your roadmap, or your future here. I'd rather address that directly than let it sit. We're not consolidating roles, and no one is being asked to relocate. **What's next.** I'll host an all-hands Thursday at 11am ET to walk through this and take live questions. Drop questions early in #ask-leadership — anonymous is fine, and I'll answer the hard ones first. More soon, Devin
PRICE HISTORY0 cr · current
PROMPT TEMPLATE · v1.0.0
Draft an internal memo announcing <WHAT>. Audience: full company. Structure: what we're announcing → why now → what it means for you → what stays the same → what's next → how to ask questions. Tone: direct, no corporate speak, acknowledge concerns honestly.
RESULTS · WHAT PEOPLE GOT
0Sign in to show colleagues what this case produced.
No results posted yet. Used this case? Show colleagues what it produced.
DISCUSSION
0 commentsSign in to join the conversation.
No comments yet — be the first.
MORE LIKE THIS