Internal Comms & Meetings

How to write a launch memo as Event Agency Founders

Internal Comms & MeetingsFor Event Agency Founders3 apps12 steps~24 min to set up

You spend the night before a big launch — a new venue partnership, a seasonal package, a rebrand — writing a memo in Google Docs that half your team won't read and vendors will never see. You copy numbers out of your HoneyBook pipeline, paste a handful of bullet points from a Slack thread, manually format a timeline, and send it to a Gmail thread that immediately gets buried. There's no single source of truth for what's live, what's changing, and who needs to act. The memo takes 90 minutes and is out of date by the next morning. For a 3-5 person agency, that's real money sitting in a Google Doc.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Event Agency Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A repeatable launch memo workflow where Starch pulls your live pipeline data, open proposals, and key dates, then drafts a structured memo your team and vendors can actually act on

An Email Agent that sends the right version of the memo to the right audience — internal team, venue partners, or clients — without you writing three separate emails

A project management board that turns the action items in the memo into tracked tasks with owners and due dates, so the launch doesn't stall after the send

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Project Management Knowledge Management

Data sources & config

Starch connects directly to Gmail so the Email Agent can send finalized memos and track replies in your existing threads. Google Calendar syncs on a schedule so Starch knows your go-live dates and can flag scheduling conflicts in the memo. Connect Google Drive from Starch's integration catalog; the agent queries it live to pull in the latest mood board links, timeline docs, or proposal PDFs referenced in the memo. Notion syncs on a schedule if your team uses it for SOPs, so Starch can cross-reference existing documentation before drafting.

Prompts to copy

Draft a launch memo for our Spring Corporate Season Package. Include: what's new (the rooftop venue partnership with Terrace & Co.), pricing change from $8,500 to $9,200 for half-day buyouts, updated A/V package now bundled in, and go-live date of May 1. Audience is my internal team of 4. Tone is direct. Keep it under one page.

Create a version of this memo for external distribution to our top 12 venue partners. Strip the internal margin notes, replace the pricing rationale with a brief feature summary, and draft a one-paragraph email I can send from Gmail introducing the update.

Turn the action items in this memo into project tasks: assign 'Update HoneyBook proposal template' to me, due April 22; assign 'Brief catering contacts on new package' to Sarah, due April 25; assign 'Update website pricing page' to Marcus, due April 28. Flag all three as high priority.

Save this memo to our Knowledge Management wiki under 'Package Launches > Spring 2026' and tag it with 'venue-partners', 'pricing', and 'spring-season'.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Open Starch and describe your launch in plain language — the new package, the venue, the price point, the go-live date, and who needs to know. Starch drafts the full memo structure before you've opened a Google Doc.

2 Starch queries your Gmail threads live to surface any outstanding vendor quotes or venue confirmations that should be referenced in the memo — so you're not digging through 40 threads to make sure you haven't missed something.

3 Review the draft. Starch pulls your Google Calendar (scheduled sync) to confirm the go-live date doesn't land on a conflict and flags it if it does.

4 Tell Starch which sections need a different tone for external audiences: 'rewrite the pricing section for venue partners — remove the margin math and lead with the bundled A/V value.' It outputs a clean external version in one pass.

5 Hand the external version to the Email Agent. Prompt it to draft a send-ready email introducing the memo to your venue partner list, in your voice, with a one-sentence subject line that doesn't read like a newsletter.

6 Email Agent sends via Gmail. Replies from partners thread automatically back into your inbox, and Email Agent flags anything that needs your attention — a venue asking for a site visit, a caterer with a pricing question.

7 Back in the internal memo, tell Starch to convert every action item into a project task: owner, due date, priority. Tasks appear in your Project Management board immediately — no copy-paste, no separate Asana entry.

8 Assign tasks to your team directly from the board. Starch lets you do it by prompt: 'assign the HoneyBook template update to me, due April 22, urgent.' Done.

9 Save the final memo to Knowledge Management under the right package and season tags. Next time you launch a similar package, Starch can reference this memo as a template rather than starting from scratch.

10 Set a follow-up reminder in Email Agent for 72 hours after the send: 'if any of the 12 venue partners haven't replied, draft a polite nudge.' Starch handles the tracking so you don't have to keep a mental checklist.

11 On go-live day, run a quick prompt: 'summarize what's been confirmed, what's still outstanding, and who hasn't responded to the launch memo.' Starch gives you a one-paragraph status read without you opening a single tab.

12 After the launch, update the Knowledge Management entry with what changed — actual partner response rate, any pricing objections, lessons for next time. That institutional memory stays searchable for your next hire or your next launch.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Spring 2026 Corporate Season Package Launch — April 2026

Sample numbers from a real run

New venue partnership (Terrace & Co. rooftop buyout)	9,200
Previous half-day corporate package rate	8,500
Bundled A/V upgrade (previously à la carte add-on)	1,400
Internal team affected (coordinator, sales lead, web/ops)	3
External venue partners receiving memo	12
Time to first memo draft (Starch vs. manual Google Doc)	0

Priya runs a 4-person corporate events agency in Chicago. Every spring she launches an updated seasonal package, and every year it takes her a full evening to write the memo, a separate pass to rewrite it for partner-facing language, and another hour to track down whether everyone actually saw it. This April, she opened Starch and typed: 'Draft a launch memo for our Spring Corporate Season Package — we added a rooftop venue partnership with Terrace & Co., raised the half-day buyout from $8,500 to $9,200, and bundled in A/V that used to be a $1,400 add-on. Go live May 1. Internal audience first.' Starch produced a structured draft in under two minutes. She asked for an external version stripped of margin context, then handed it to Email Agent, which drafted a 4-sentence intro email to her 12 venue partners in her voice. Partners started responding within the hour — two requested site visits, one had a pricing question. Email Agent flagged all three and drafted replies. Priya's coordinator, Sarah, and ops lead, Marcus, each had tasks on the Project Management board before lunch: proposal template update, catering brief, website pricing page. The whole memo cycle — draft, external version, email send, task creation — took 35 minutes instead of 3 hours. The memo lives in Knowledge Management under 'Package Launches > Spring 2026' and will serve as the template for the fall cycle.

Measurement

How you'll know it's working

Time from launch decision to memo sent (target: same business day, not next morning)

Venue partner response rate within 72 hours of memo send

Action items with assigned owners and due dates vs. items left as vague bullets

Number of follow-up threads that fall through the cracks (target: zero with Email Agent reminders)

Reuse rate: how many future memos reference a saved Knowledge Management template vs. starting from scratch

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Google Docs + Gmail manually

You own every word and every send, which means you're the bottleneck — no automatic task creation, no partner tracking, and the doc is stale the moment you hit send.

HoneyBook or Dubsado internal notes

Good for client-facing workflows but not built for team memos or vendor broadcasts — no task management, no wiki, no version you can reuse next launch cycle.

Notion standalone

Great for storing finished memos but you still write them from scratch, manually create tasks elsewhere, and send emails separately — three tools doing what Starch chains into one described workflow.

ChatGPT or Claude for drafting

Solid at writing the memo text if you paste in all the context manually, but it doesn't know your Gmail threads, your calendar, or your project board — you're still the integration layer.

Cvent or Social Tables

Enterprise-grade event ops platforms with launch workflow features, but built for teams with dedicated admins and budgets that dwarf a 4-person agency's reality.

On Starch RECOMMENDED

One platform — founder inbox, project management, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Can Starch pull my existing HoneyBook proposals or client data into the memo automatically?

Starch connects to 3,000+ apps through its integration catalog, and the agent can query HoneyBook live when your memo workflow runs — so it can surface open proposal counts, client names, or package details without you copying them manually. You describe what you want in the memo and Starch pulls the relevant data in.

Will the Email Agent actually sound like me, or will my venue partners clock that it's AI-written?

The Email Agent drafts in your voice based on the context you give it and your existing email style. You review before anything sends — it's a one-click send from a draft you've approved, not an autonomous blast. You'll want to read the first few before you trust the pattern.

What if my team uses Notion for documentation — will Knowledge Management conflict with that?

Starch syncs your Notion data on a schedule, so it can read what's already in your Notion workspace and cross-reference it when building a new memo. You don't have to abandon Notion — you can use Starch's Knowledge Management for net-new launch content and keep pulling from Notion for existing SOPs.

Is Starch SOC 2 certified? We handle corporate client data.

Starch is not SOC 2 Type II certified today. If your corporate clients have formal vendor security requirements that mandate SOC 2, that's worth knowing upfront. It's on the roadmap.

Can I send the memo to clients through Starch, or just to my internal team and vendors?

You can send to any email address via Gmail — internal team, venue partners, or end clients. You'd just prompt Starch to draft a client-facing version with appropriate tone and detail level, then Email Agent sends it from your Gmail account. Replies come back to your normal inbox.

What happens to the memo after the launch? I want to reuse it as a template next season.

Save it to Knowledge Management with descriptive tags ('spring-season', 'venue-partners', 'pricing'). Next time you're launching a similar package, tell Starch: 'use the Spring 2026 launch memo as a starting point and update it for Fall 2026.' It reads the saved version and drafts the update rather than starting blank.

Can Starch track whether my venue partners actually opened or replied to the memo email?

Starch connects directly to Gmail and can surface reply activity — who responded, who hasn't, what they said. It won't give you open-tracking pixels (that's an email marketing tool feature), but it will flag which of your 12 partners have replied and prompt you on the ones who haven't after 72 hours if you set that reminder.