Internal Comms & Meetings

How to write a launch memo as Chief of Staff and Founder's Office

Internal Comms & MeetingsFor Chief of Staff and Founder's Office2 apps10 steps~20 min to set up

Writing a launch memo as chief of staff means chasing down four people for updates, synthesizing what actually shipped versus what was planned, checking the OKR tracker in Notion, pulling the revenue impact estimate out of a QuickBooks export, and finding the CEO's original framing from a Slack thread three weeks ago. By the time you've assembled all of that into a coherent internal doc, you've spent three hours on a memo that needs to go out today. The problem isn't that you can't write — it's that the inputs live in six different places and you're the only one who knows where all of them are.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Chief of Staff and Founder's Office2 apps10 steps~20 min to set up

Outcome

What you'll set up

A connected memo-drafting workflow that pulls live context from Notion, Slack, Gmail, and QuickBooks so you're not copy-pasting numbers into a Google Doc by hand

A structured launch memo template you can re-use across product launches, pricing changes, and strategic announcements — customized to your company's internal voice and format

A Starch automation that notifies the right stakeholders in Slack when a draft is ready for review, so you stop being the manual router between the CEO and functional leads

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 syncs your Notion data on a schedule (pages, databases, users) and your QuickBooks data on a schedule (invoices, payments, journal entries) so memo drafts can pull live project context and financial impact numbers without you opening either tool. Starch also connects directly to Slack and Gmail — synced on a schedule — so the automation can post draft memos for review and send final versions to the distribution list you specify. Google Calendar sync lets Starch reference launch dates and executive review meetings automatically.

Prompts to copy

Build me an internal launch memo app that pulls the relevant project tasks and status from my project tracker, summarizes the initiative in plain English, includes a section for revenue or cost impact pulled from QuickBooks, and drafts a stakeholder communication ready for the CEO to review before we send it to the company.

Create a knowledge base entry from this launch memo so future team members can find the context behind why we made this decision — auto-tag it by product area, date, and initiative type.

Every time I mark a project milestone as 'complete' in the project tracker, draft a launch memo outline for that initiative and post it to the #launches Slack channel for my review before it goes company-wide.

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

Walkthrough

Step-by-step

1 Connect Notion, Slack, Gmail, Google Calendar, and QuickBooks — Starch syncs all five on a schedule, so your memo drafts will always have current data without manual exports.

2 Open the Project Management app in Starch and tell it: 'Create a project called Q2 Pricing Launch with milestones for internal alignment, memo draft, exec review, and company announcement — due dates pulled from the timeline in my Google Calendar.'

3 As the launch date approaches, prompt Starch: 'Draft an internal launch memo for the Q2 pricing change. Pull the project status from the tracker, the revenue impact from QuickBooks, and the original framing from the Notion strategy doc tagged pricing-2026.'

4 Starch queries your connected Notion pages, QuickBooks entities, and project tracker in one pass and returns a structured draft — executive summary, what changed, why now, what it means for each team, and key dates.

5 Review the draft directly in Starch; prompt inline changes: 'Tighten the executive summary to three sentences and add a bullet on the impact to enterprise renewals specifically.'

6 Use the Knowledge Management app to save the finalized memo: 'Add this launch memo to the knowledge base, tag it under Pricing, Q2 2026, and Internal Announcements, and flag it for a freshness review in 90 days.'

7 Trigger the stakeholder notification: 'Post the draft to the #exec-review Slack channel and send a Gmail to the four functional leads asking for a 48-hour review window before we publish company-wide.'

8 After exec sign-off, send the final memo via Gmail to the all-hands distribution list — prompt Starch: 'Send the approved launch memo to all-company@[domain] with subject line Q2 Pricing Update — Effective June 1.'

9 Create the recurring automation: 'Every time a project milestone is marked complete in the project tracker, draft a launch memo outline and post it to #launches for my review — I'll approve before anything goes out.'

10 Archive the process in Knowledge Management so the next chief of staff (or your own future self) can find it: 'Document the launch memo workflow — inputs required, Starch apps used, approval chain, and distribution list — and save it under Ops Playbooks.'

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

Q2 2026 Pricing Change Announcement — May 2026

Sample numbers from a real run

New ARR impact (upmarket segment)	180,000
Churn risk on SMB renewals (next 90 days)	42,000
Implementation timeline — go-live date	0
Affected active contracts	37

The VP of Revenue flagged on a Thursday that the pricing announcement needed to go out by Monday. As chief of staff, you had 72 hours to produce a memo that explained the change clearly, quantified the impact, and didn't contradict anything the CEO had said in the last investor update. You prompted Starch: 'Draft an internal launch memo for the Q2 pricing overhaul. Pull the ARR impact estimate from the QuickBooks revenue data, the list of affected contracts from the Notion deal tracker database, and the strategic rationale from the pricing strategy doc updated April 28.' Starch returned a draft in under two minutes: an executive summary noting $180K in projected new ARR from the upmarket repricing, a risk callout on $42K of SMB renewal exposure in the next 90 days, the go-live date of June 1, and a section-by-section breakdown for Sales, CS, and Finance. You spent 20 minutes editing tone and adding a paragraph the CEO wanted about long-term positioning. You posted the draft to #exec-review in Slack via Starch, collected two rounds of comments, finalized, and sent the all-company Gmail by Sunday afternoon. Total time: 2.5 hours instead of the usual full day.

Measurement

How you'll know it's working

Time from launch decision to company-wide memo distribution (target: under 24 hours for standard launches)

Number of revision rounds before CEO sign-off (a proxy for how well the first draft captured intent)

Stakeholder acknowledgment rate on all-company memos within 48 hours

Percentage of launch memos archived in the knowledge base with proper tags (completeness metric for institutional memory)

Time the chief of staff spends manually aggregating inputs versus time spent editing and deciding

Comparison

What this replaces

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

Google Docs + manual copy-paste from Notion, QuickBooks, and Slack

You control every word, but you are also responsible for finding every number — a 150-person company's worth of context doesn't assemble itself, and the doc is stale the moment you close it.

Notion AI within Notion

Good for summarizing content already in Notion, but it can't pull live QuickBooks numbers, Gmail threads, or project status from outside Notion into the same draft — you're still doing that aggregation manually.

ChatGPT or Claude with manual pasting

Strong drafting quality once you give it context, but you have to gather and paste all the inputs yourself every time — there's no connection to your live data, so it can't pull the actual contract count or revenue figure without you finding it first.

Guru or Tettra for knowledge management only

Solid for storing and searching docs, but neither tool drafts the memo from your live project and financial data — you're still writing the first draft yourself before you have anything to save.

On Starch RECOMMENDED

One platform — 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 actually pull numbers from QuickBooks and put them in a memo draft, or does it just write boilerplate?

Starch syncs your QuickBooks data on a schedule — invoices, payments, journal entries, and more — and when you ask it to draft a memo that includes revenue impact, it queries that data directly. You get real numbers in the draft, not placeholders. One honest caveat: QuickBooks report views like the P&L summary are temporarily unavailable due to an upstream connector issue, but entity-level data (invoices, payments, vendors) syncs normally, so line-item impact figures come through fine.

What if the key context is in a Slack thread from three weeks ago — can Starch find that?

Yes. Starch syncs your Slack channels and users on a schedule, so when you describe what you're looking for — 'the pricing rationale from the #strategy channel in late April' — the agent can search that data and include relevant context in the draft. It's not perfect recall on very old threads, but for anything in the sync window it works.

Will the memo go out automatically, or do I approve it first?

You control the approval step. The automation Starch builds can post a draft to Slack or Gmail for your review and wait for explicit sign-off before sending anything company-wide. Nothing goes to all-company without you triggering it — the automation is there to remove the assembly work, not the judgment call.

Is Starch SOC 2 certified? I'm wiring it to Gmail and QuickBooks for a 150-person company.

Starch is not SOC 2 Type II certified today. That's worth knowing upfront if your security review requires it. For teams where that's a hard requirement, it may be a blocker for now.

Can I use this for external announcements, not just internal memos?

The same workflow applies. The memo app Starch builds is just a surface — you describe the format you need (internal memo, investor update, press release FAQ, all-hands talking points) and Starch drafts accordingly. The difference is you'd tell Starch which audience it's for so the tone and detail level adjust. External comms would still route through your review before anything goes out.

What if some of the context I need is in a tool that isn't Notion or Google Docs — like a spreadsheet a functional lead sent me?

If it's in Google Drive or Sheets, Starch can connect to Google Sheets from its integration catalog and the agent queries it live when your app runs. If it's a one-off file someone emailed you, the fastest path is to paste the relevant section into the Starch prompt directly — the agent will incorporate it. Browser-reachable tools (anything you can log into and view) can also be automated through Starch without needing a formal integration.