Internal Comms & Meetings

How to write a launch memo as Solo Media and Creator Founders

Internal Comms & MeetingsFor Solo Media and Creator Founders3 apps10 steps~20 min to set up

You just wrapped a product launch — new paid tier, merch drop, whatever it is — and now you need to write the internal memo that actually explains what happened. Your subscriber numbers are in Beehiiv. Revenue is in Stripe. The sponsor deal you negotiated is buried in a Gmail thread from three weeks ago. Your Notion editorial calendar has the original plan. None of these talk to each other, so writing a coherent 'here's what we launched, here's what it cost, here's what landed' memo means you're copying numbers out of four tabs, triangulating dates from memory, and hoping you don't miss the Stripe payout that hit two days late. For a 1-2 person media business, this takes three hours minimum. It usually doesn't get written at all.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Solo Media and Creator Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A launch memo that pulls actual numbers — Stripe revenue, subscriber delta, sponsor terms — from your real data instead of your memory

A repeatable process so the next launch memo takes 20 minutes instead of a morning

A shareable internal doc or slide format your co-founder, future hire, or investors can read without needing context from you

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

Presentation Agent Knowledge Management Email Agent

Data sources & config

Starch syncs your Stripe data on a schedule (charges, payouts, and subscription events), so revenue numbers are already pulled in when Presentation Agent drafts the memo. Connect Gmail from Starch's integration catalog — the agent queries your inbox live to surface sponsor correspondence, payout confirmations, and any subscriber milestone emails from the launch window. Notion connects from Starch's integration catalog so the agent can query your editorial calendar live to pull the original launch plan. The finished memo lives in Knowledge Management (Notion-backed) for future reference.

Prompts to copy

Write a launch memo for our April paid tier rollout. We added 340 paid subscribers at $9/month, total new MRR is $3,060. Launch date was April 8. Our main sponsor (Morning Brew network) paid out $4,200 for the issue. Include a section on what worked (subject line A/B test, Wednesday send), what didn't (the upsell CTA placement), and what we'd do differently. Format it as a one-pager I can share with my co-host.

Save this launch memo to our knowledge base under 'Launch Post-Mortems > April 2026 Paid Tier Launch' and tag it as a template for future launches.

Search my Gmail inbox for any emails related to the April launch — sponsor confirmations, Stripe payout receipts, or subscriber milestone notifications — and summarize what happened in chronological order so I can include it in the memo.

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

Walkthrough

Step-by-step

1 Connect Stripe — Starch syncs your Stripe data on a schedule, so charges, payouts, and new subscription counts from your launch window are already available without any manual export.

2 Connect Gmail from Starch's integration catalog — the Email Agent queries your inbox live to find sponsor confirmation threads, payout receipt emails, and any subscriber milestone notifications sent during the launch period.

3 Connect Notion from Starch's integration catalog — the agent queries your editorial calendar live to pull the original launch plan, so the memo can compare what you planned versus what shipped.

4 Open Email Agent and give it a date range: 'Find all emails related to our April 8 launch — sponsor deals, Stripe receipts, any subscriber milestone emails — and give me a timeline.' Review the summary for anything you want to include or exclude.

5 Open Presentation Agent and describe the memo you want: the launch name, the key numbers (subscriber delta, new MRR, sponsor payout), what worked, what didn't, and the format — one-pager, slide deck, or both.

6 Presentation Agent drafts the memo with sections for Launch Overview, By The Numbers, What Worked, What Didn't, and Next Time. Every figure it uses comes from your connected Stripe and Gmail data, not a blank template.

7 Review the draft and type any corrections directly: 'The upsell CTA section is wrong — move it to What Didn't Work and add a note that we're testing a new placement in May.' Starch revises inline.

8 If you want a slide version for your co-host or a future investor conversation, prompt: 'Convert this memo into a 6-slide deck — one slide per section — export as PDF.' Download and share.

9 Open Knowledge Management and save the memo: 'Save this to Launch Post-Mortems under April 2026 Paid Tier Launch, tag it as a reusable template, and note which subject line and send day performed best.' It's searchable for any future hire or for yourself six months from now.

10 Set a follow-up reminder in Email Agent: 'Flag me in 30 days if I haven't sent a sponsor recap email to the Morning Brew contact.' The agent will surface it even if the original thread is buried.

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

April 2026 Paid Tier Launch — The Operator Brief

Sample numbers from a real run

New paid subscribers (April 8–14)	340
New MRR added	3,060
Sponsor payout (Morning Brew network, Issue #47)	4,200
Total launch-week revenue	7,260
Stripe processing fees	211
Net launch-week revenue	7,049

You launched the paid tier on April 8 with a Wednesday send. By Friday you had 340 new paid subscribers at $9/month — $3,060 in new MRR. The Stripe payout confirmation hit your inbox on April 10, which Email Agent surfaced when you asked for a launch timeline. Sponsor revenue from Issue #47 (Morning Brew network, confirmed in a Gmail thread from March 28) was $4,200, bringing total launch-week revenue to $7,260 before fees. Presentation Agent pulled all three numbers into the memo automatically, then added a 'What Worked' section noting that your Wednesday send outperformed your usual Tuesday by 12% open rate — a data point from your own notes in Notion that the agent pulled from the editorial calendar. The final one-pager took 25 minutes to produce. The PDF version is saved in Knowledge Management under Launch Post-Mortems so your co-host can reference it without calling you.

Measurement

How you'll know it's working

New paid subscribers added during launch window

New MRR from the launch (and cumulative MRR impact at 3 months)

Sponsor payout received vs. contracted amount

Open rate and click rate on the launch issue vs. your rolling 90-day average

Time from launch close to memo published (your meta-metric for ops efficiency)

Comparison

What this replaces

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

Google Docs + manual copy-paste from Stripe and Beehiiv

Free and familiar, but every number has to be pulled by hand from separate dashboards — a 2-hour job that still produces a doc with no live data behind it.

Notion AI

Good for drafting prose if you paste the data in yourself, but it has no connection to Stripe, Gmail, or your actual launch metrics — you're still doing the data assembly.

ChatGPT with copy-pasted context

Faster drafting than writing from scratch, but you're manually exporting CSV files and pasting email excerpts — the integration work is still all on you.

Beehiiv / Substack built-in analytics exports

Accurate subscriber and open rate data for your newsletter, but no Stripe revenue, no sponsor deal context, and no memo format — you still have to synthesize across tools yourself.

On Starch RECOMMENDED

One platform — presentation agent, knowledge 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

I use Beehiiv for my newsletter — can Starch pull my subscriber data from there?

Beehiiv is reachable through Starch's integration catalog (queried live when your app runs) or through browser automation — no API needed. You can tell Starch exactly what to pull: 'Get my subscriber count and open rate from Beehiiv for the week of April 8' and it will include those numbers in the memo. If Beehiiv's integration isn't available in the catalog, Starch can automate it through your browser instead.

Does Starch store my Stripe and Gmail data, or is it just reading it when I ask?

Stripe syncs on a schedule — Starch keeps a copy of your charges, payouts, and subscription events in its database so they're available instantly when you build an app or run a memo. Gmail is queried live from Starch's integration catalog when you ask the Email Agent to search it — messages aren't stored in Starch. One honest note: Gmail's OAuth consent screen currently shows the underlying connector's name rather than Starch; that's on the roadmap to fix.

I don't have a co-founder. Can I still use this as a solo creator?

Yes — the memo is still useful as a forcing function for yourself. A lot of solo operators use launch post-mortems the same way: you write it, save it to Knowledge Management, and you have a searchable record of what your actual numbers were so that in six months you're not guessing. It also becomes the brief if you ever bring on a sponsor manager, an editor, or an investor.

What if my launch involved a product I sell through Gumroad or LemonSqueezy, not Stripe?

Gumroad and LemonSqueezy are reachable via Starch's browser automation — no API needed. You can include a step that says 'go to my Gumroad dashboard, find total sales for April 8–14, and add that to the memo.' It works the same way Starch would book a WeWork room from your calendar — through the browser, without requiring a formal API connection.

Is Starch SOC 2 Type II certified?

Not yet — that's an honest limit worth naming. Starch is not SOC 2 Type II certified today. If that's a hard requirement before you connect a Gmail or Stripe account, it's a real consideration. For most solo and small-team creator businesses it doesn't come up, but you should know.

Can I use this same setup for every launch, or do I have to rebuild it each time?

Once the connections are set up and the Knowledge Management template is saved, future launches reuse everything. You prompt Presentation Agent with the new numbers and date range, it drafts a new memo in the same format, and you save it under a new entry in your launch archive. The second memo takes under 20 minutes.