Follow-up email
Subject: Recap + next steps: Website relaunch check-in (launch now April 15)
Hi team,
Thanks for jumping on today's website relaunch check-in. Here's a quick recap so we're all on the same page.
Key decisions:
- April 15 is now our firm launch date. We're moving it from April 1 so the copy has time to be finished. Please plan around April 15.
- The pricing page will be simplified before launch. Jen felt the current version is crowded.
Action items:
| Owner | Action | Due |
|---|---|---|
| Marcus | Share a simplified version of the pricing page design | Thursday |
| Dana | Ask Tom (Sales) for the product descriptions and send them to Raj | Today |
| Raj | Finish all website copy once the product descriptions arrive | The 5th |
Open questions / still to decide:
- Blog migration: Should we move all the old posts, or only the top 20? We'll decide this next week.
Next steps: We'll meet again next Tuesday at the same time. Let me know if I missed anything.
Thanks, Dana Lee Marketing Director
Short version (Slack/Teams)
Website relaunch recap: April 15 is now the firm launch date (moved from April 1). Marcus: simplified pricing page by Thursday. Dana: get product descriptions from Tom in Sales to Raj today. Raj: all copy done by the 5th. Still open: blog migration (all posts or the top 20?). We'll decide next week. Next check-in: next Tuesday, same time.
Check before sending
- "By the 5th": I assumed Raj meant April 5, since that falls before the April 15 launch. The transcript doesn't name the month, so please confirm.
- Relative dates: The transcript doesn't give the meeting date, so "today," "Thursday," and "next Tuesday" stay as they were said. Adjust them if you send this on a later day.
- Tom's details: The transcript only says "Tom on sales." Add his last name if that helps the team.
- Blog migration owner: No one was assigned to make the call. It's listed as an open question for next week. Add an owner if you'd like one.
- Left out: I omitted Marcus's personal note about being out Friday afternoon. Mention it separately if the team needs to know.
Made by a Donkley AI worker. AI can make mistakes; please review before you rely on it.