Internal Comms & Meetings

How to write a launch memo as Educators, Coaches, and Course Creators

Internal Comms & MeetingsFor Educators, Coaches, and Course Creators3 apps10 steps~20 min to set up

Every six weeks you run a new cohort and write the same launch memo from scratch: what's included, who it's for, what students need to do on day one, what the schedule looks like, what the community link is. You're pulling dates from Google Calendar, enrollment numbers from Stripe, curriculum details from Notion, and community links from a Slack message you sent yourself three months ago. You write the memo in a Google Doc, then manually paste pieces of it into a ConvertKit broadcast, a Circle post, and a Kajabi announcement. By the time it's live, the Calendly link has changed and the Notion page is one version behind. The memo you wrote is already wrong.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Educators, Coaches, and Course Creators3 apps10 steps~20 min to set up

Outcome

What you'll set up

A launch memo template that auto-populates cohort dates from Google Calendar, enrollment count from Stripe, and curriculum structure from Notion — so you're filling in context, not hunting down facts

A one-prompt workflow that turns that populated memo into a Kajabi announcement, a ConvertKit broadcast intro, and a Circle community post without you copy-pasting anything

A repeatable six-week launch rhythm documented in Starch's Knowledge Management app so your ops helper (or future hire) can run it without asking you every question

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

Knowledge Management Project Management Email Agent

Data sources & config

Starch connects directly to Google Calendar (scheduled sync) to pull cohort session dates and Calendly booking windows. Starch syncs your Stripe data on a schedule to pull enrollment counts and revenue by product. Starch connects directly to Notion (scheduled sync) to read curriculum pages and databases. ConvertKit and Kajabi are connected from Starch's integration catalog; the agent queries them live when the automation runs. Circle is automated through your browser — no API needed.

Prompts to copy

Pull my upcoming cohort dates from Google Calendar, the last 30 days of Stripe charges filtered to my 'Cohort Spring 2026' product, and the top-level pages from my Notion curriculum database. Draft a 600-word internal launch memo covering: what's in this cohort, who enrolled (count and any notable segments), the week-by-week schedule, day-one logistics for students, and the three things I need to communicate before kick-off.

Take this launch memo and write three separate outbound versions: (1) a 200-word Kajabi announcement for enrolled students, (2) a ConvertKit broadcast intro paragraph for the waitlist, and (3) a Circle community post welcoming the new cohort. Keep the tone warm but direct. Do not repeat the same opening sentence across all three.

Save the finalized launch memo, the three outbound versions, and the step-by-step process I followed this cycle to my Knowledge Management app under 'Cohort Launch Playbook.' Flag any steps that took more than 30 minutes so I can automate them next time.

Create a launch week task list in Project Management: task for each outbound post going live, task for Calendly link audit, task for Notion curriculum publish, task for Zoom link distribution, task for Circle onboarding post. Set all tasks due the Monday before cohort start.

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

Walkthrough

Step-by-step

1 Connect Google Calendar, Stripe, and Notion in Starch — all three sync on a schedule, so your cohort dates, enrollment data, and curriculum structure are always current before you start.

2 Connect ConvertKit and Kajabi from Starch's integration catalog so the agent can query them live when it's time to push outbound versions of the memo.

3 Connect Circle through browser automation — Starch posts to your community through your browser, no Circle API required.

4 Open Starch and type your first prompt: ask it to pull this cohort's dates, Stripe enrollment count, and Notion curriculum outline, then draft the internal launch memo. Review the draft — your job is to add the one or two things only you know (a story, a specific student outcome you're promising, a policy change).

5 Once the memo reads right, type the second prompt: ask Starch to write the three outbound versions — Kajabi announcement, ConvertKit broadcast intro, Circle welcome post — from the memo. Each should be distinct in opening and length.

6 Review the three outbound versions. Edit for voice. This should take ten minutes, not an hour, because the facts are already right.

7 Use Project Management to create your launch week task list in one prompt: due dates, assignees (yourself or your ops helper), and a Calendly link audit task you always forget until day one.

8 Save the full memo, the outbound versions, and this cycle's process notes to Knowledge Management under 'Cohort Launch Playbook.' Starch auto-categorizes and makes it searchable.

9 Six weeks from now, open the playbook, pull up the same prompt sequence, change the cohort name and dates, and run it again. The framework is already there; you're only updating what changed.

10 After two or three cycles, ask Starch to flag which launch tasks consistently take the longest — use that list to decide what to automate or delegate next.

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 Cohort Launch — 6-Week Writing Course

Sample numbers from a real run

Enrolled students (Stripe, last 14 days)	34
Revenue this cohort (Stripe)	23,800
Cohort sessions (Google Calendar)	6
Curriculum modules (Notion)	12
Outbound assets drafted by Starch	3
Minutes from first prompt to published memo	40

On a Tuesday afternoon before the Spring 2026 cohort, you open Starch and type one prompt asking it to pull the six session dates from Google Calendar, the 34 enrolled students and $23,800 in revenue from Stripe, and the 12-module outline from your Notion curriculum database. Four minutes later you have a 620-word internal launch memo with the schedule, day-one logistics (Zoom link, Circle invite, what to read before session one), and a summary of who enrolled. You spend 15 minutes adding two sentences about what you're doing differently this cohort versus last. Then you type the second prompt and get back a Kajabi announcement, a ConvertKit intro paragraph for the 180-person waitlist, and a Circle welcome post — all distinct, none of them starting with 'I'm so excited.' You edit the ConvertKit version for four minutes because the tone was slightly off. Total time: 40 minutes. Last cohort, this same process took you most of a Thursday. The Knowledge Management app now holds the finalized memo and the exact prompt sequence you used, so when your ops helper asks 'how do we do the launch memo?' next cycle, the answer is already written down and not living in your head.

Measurement

How you'll know it's working

Time from cohort close to launch memo published (target: under 2 hours)

Consistency of outbound assets — same core facts across Kajabi, ConvertKit, and Circle without manual reconciliation

Launch task completion rate by Monday before cohort start (all Calendly, Zoom, and Notion links audited)

Percentage of launch playbook steps documented in Knowledge Management vs. living in the founder's head

Student day-one confusion emails (proxy: if they email asking for the Zoom link, the memo failed)

Comparison

What this replaces

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

Google Docs + manual copy-paste

Free and you already have it, but you're personally hunting down every date, enrollment number, and curriculum link each cycle — the document is only as accurate as your memory.

Notion template with manual fill-in

Good for storing the finished memo, but Notion won't pull your Stripe enrollment count or Calendar dates for you — you still do all the data gathering by hand.

ConvertKit or Kajabi native broadcast tools

Fine for sending the outbound version to students, but they don't help you write the internal memo or produce three platform-specific variants from one source of truth.

Jasper or ChatGPT for drafting

Can draft memo copy if you paste in all the context yourself — but you still have to manually collect dates from Calendar, numbers from Stripe, and structure from Notion before you can give it anything to work with.

On Starch RECOMMENDED

One platform — knowledge management, project management, email agent 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

My course platform is Kajabi, not something I see listed as a scheduled sync. Can Starch still reach it?

Yes. Kajabi is connected from Starch's integration catalog — the agent queries it live when your automation runs. It's not a scheduled sync the way Stripe or Google Calendar is, but for reading enrollment pages and publishing announcements, live queries work fine for this workflow.

What if my Notion curriculum database has a messy structure — lots of nested pages and no consistent format?

Starch syncs Notion pages and databases on a schedule and can work with inconsistent structures, but the cleaner your Notion is, the better the memo draft will be. If your curriculum outline is one well-organized database, the agent can pull it accurately. If it's scattered across 40 sub-pages, you may want to point it at a specific top-level page rather than the whole workspace.

Can Starch actually post to Circle, or does it just draft the post for me to copy?

Starch automates Circle through your browser — no Circle API needed. It navigates Circle the same way you would, finds the right space, and posts. You review and approve the draft first; Starch handles the clicking.

I don't use ConvertKit — I use Mailchimp. Does that work?

Yes. Mailchimp is available from Starch's integration catalog; the agent queries it live. You'd connect it the same way and use it in place of ConvertKit in the prompts.

Is my Stripe data stored somewhere, or is Starch pulling it fresh each time?

Starch syncs your Stripe data on a schedule — charges, customers, invoices, and subscriptions are stored in Starch's database and refreshed automatically. So when you run the launch memo prompt, it's reading from a current local copy, not making a live Stripe API call in real time.

I'm not SOC 2 certified either — does it matter that Starch isn't?

Starch is not SOC 2 Type II certified yet. If you're running a consumer course business with payment data handled by Stripe and student data in Kajabi, this is unlikely to block you — those platforms handle their own compliance. If you're running B2B corporate training where enterprise clients ask for your vendors' compliance documentation, it's worth knowing upfront.

Will the Knowledge Management app replace my existing Notion docs?

It doesn't have to. Starch's Knowledge Management app is good for storing the playbooks and process docs you want to be AI-searchable inside Starch — like your launch checklist and memo templates. Your actual curriculum can stay in Notion. The two coexist; Starch syncs your Notion content on a schedule so the agent can read it.