Internal Comms & Meetings

How to write a launch memo as Small RevOps Teams

Internal Comms & MeetingsFor Small RevOps Teams3 apps11 steps~22 min to set up

Your team of two is the only one who knows where the real launch information lives — and it's spread across a HubSpot deal record, a Slack thread from three weeks ago, a Google Doc the CRO shared once, and a quota spreadsheet you rebuilt last quarter. When a new product, territory change, or comp update goes out, you're the ones writing the internal memo, chasing down the right numbers from Stripe or QuickBooks, reconciling what Apollo says about pipeline against what HubSpot actually shows, and formatting all of it into something the 30 reps will actually read before the Monday forecast call. That's four hours of work that could have been two paragraphs.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small RevOps Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A connected data layer pulling from HubSpot (scheduled sync), Apollo (scheduled sync), and Gmail (scheduled sync) so your launch memo auto-populates with real pipeline numbers, rep counts, and sequence activity — no copy-paste from five tabs

A reusable memo template app that drafts territory announcements, quota updates, and product launch briefs from a plain-English description, then formats them for rep consumption

A distribution step that sends the finished memo through Gmail and logs it in your CRM so you have a record of what was communicated, when, and to whom

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

Sales Agent CRM Project Management

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) and your Apollo data on a schedule (contacts, accounts, sequences). Gmail is also synced on a schedule so sent memos are logged and follow-up threads are trackable. Salesforce and Pipedrive can be connected from Starch's integration catalog; the agent queries them live when the memo app needs current pipeline figures. Google Sheets (where your quota model lives) connects from Starch's integration catalog the same way.

Prompts to copy

Pull from HubSpot: total open pipeline by territory as of today, broken down by rep, stage, and average deal size. I need this as a table I can paste into a launch memo.

Draft a 400-word internal launch memo announcing the Q3 territory realignment. Use the pipeline table above. Audience is 30 AEs. Tone: direct, no fluff. Include what changes, what stays the same, and the three things reps need to do before Friday.

Create a task for each section of the launch memo that still needs a fact-check: quota numbers from the comp model, new territory assignments, and the effective date. Assign them to me, due Wednesday.

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

Walkthrough

Step-by-step

1 Connect HubSpot to Starch — it syncs on a schedule, so deal data, owner assignments, and stage history are always current without you manually exporting anything.

2 Connect Apollo from Starch's integration catalog so sequence activity and contact-level engagement data are queryable when you're writing context into the memo (e.g., 'reps on the mid-market sequence sent 340 touches this month').

3 Connect Gmail — Starch syncs it on a schedule so you can pull sent-memo history, track replies, and set follow-up reminders without leaving the workflow.

4 Tell Starch's Sales Agent CRM app to pull a pipeline snapshot: open opps by rep, stage, and territory as of today. This becomes the data table that anchors your memo's numbers.

5 Open a new app session and type your memo brief in plain English — who the audience is, what changed (territory split, quota update, product launch), and what you need reps to do. Starch drafts the memo against the live pipeline data it just pulled.

6 Review the draft. If a number looks wrong, ask Starch to re-query HubSpot for that rep's pipeline directly — no switching tabs, no manual lookup.

7 If the quota model lives in Google Sheets, connect it from Starch's integration catalog and tell Starch to pull the new quota targets by rep and fold them into the memo's 'what changes' section.

8 Use the Email Triage app to draft the distribution email: 'Send this memo to all AEs on the mid-market team. Subject line: Territory Update — Effective Monday. BCC me and log it in HubSpot as a note on the Q3 Territory Realignment deal.'

9 Create tracking tasks in the Project Management app — one per open question (comp confirmation, territory map sign-off, legal review of the new quota language) so nothing falls through before the memo goes out.

10 After sending, tell Starch to monitor Gmail replies for the next 48 hours and flag any rep who responds with a question that hasn't been answered, so you can close the loop before the forecast call.

11 Archive the final memo version as a Notion page (Starch syncs Notion on a schedule) so it's searchable the next time someone asks 'what did we tell the team when we changed the territories in Q3.'

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

Q3 2026 Territory Realignment Memo — June 2026

Sample numbers from a real run

Open pipeline pulled from HubSpot at time of memo	4,200,000
Deals affected by territory reassignment (12 opps moving between reps)	1,100,000
Average deal size referenced in memo body	87,500
Apollo sequence touches cited (mid-market, last 30 days)	340
Reps receiving the memo	30

The CRO decides on a Thursday afternoon that the mid-market territory is getting split: the Southeast goes to the team that's been running it, and the new Northeast patch goes to two reps currently sitting on a $1.1M book of open deals that will need to be transferred. You have until Monday morning to write the memo, get it approved, and make sure nobody shows up to the forecast call confused about who owns what. Normally this is a Friday afternoon of spreadsheet archaeology. Instead, you tell Starch to pull all open HubSpot deals currently assigned to the two reps, sorted by stage and close date — that's the $1.1M figure. You describe the memo: audience is 30 AEs, the change is the Northeast territory split, here are the two reps getting new patches, here are the 12 opps transferring, effective Monday. Starch drafts it in under two minutes. You spend 20 minutes editing tone and adding context about the comp treatment for in-flight deals. The Email Triage app handles distribution to the full AE list with a BCC to the CRO, and logs the send in HubSpot. By Friday at 5pm, the memo is out, the CRO has approved it, and you have a task in Project Management to confirm with finance that the quota credit transfer is reflected in the comp model before the Monday call.

Measurement

How you'll know it's working

Time from CRO decision to memo distributed to reps (target: under 4 hours for a standard territory or quota update)

Percentage of memo data points sourced directly from live system of record vs. manually entered (target: >80% auto-populated)

Rep acknowledgment rate within 48 hours of memo send (tracked via Gmail reply monitoring)

Open questions closed before next forecast call (tracked in Project Management task completion)

Number of 'can you clarify the memo' Slack requests received after send (a proxy for memo clarity)

Comparison

What this replaces

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

Google Docs + manual HubSpot export + Gmail

You can draft the memo in Docs and export pipeline data from HubSpot manually, but every number is a snapshot in time — if a deal moves between your export and when you hit send, your memo is already wrong, and you have no log of what was communicated.

Notion + Zapier

Notion is a fine place to store the finished memo, and Zapier can trigger basic notifications, but neither drafts the memo from your connected pipeline data or handles the distribution-and-logging step without significant setup and ongoing maintenance.

ChatGPT or Claude with copy-pasted data

A general-purpose LLM will draft clean prose if you paste in the right context, but you're still doing the data gathering manually — every HubSpot export, every Apollo number — and there's no loop back to your CRM when the memo goes out.

Salesforce + Quip or Salesforce + Slack Canvas

If your org is Salesforce-native, Quip or Slack Canvases can surface deal data next to a doc, but the setup is Salesforce-admin-level work and you still write the memo by hand; it doesn't draft from a brief.

On Starch RECOMMENDED

One platform — sales agent crm, founder inbox, project 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

We use Salesforce, not HubSpot. Does this work?

Yes. Connect Salesforce from Starch's integration catalog — the agent queries it live when your memo app needs pipeline figures. You won't get the scheduled-sync depth that HubSpot users get (where deal history is stored in Starch and always queryable), but for a point-in-time pipeline pull to anchor a launch memo, live query is exactly what you need.

Our quota model is a Google Sheet the CRO updates manually. Can Starch pull from it?

Connect Google Sheets from Starch's integration catalog; the agent queries it live when the memo app runs. Tell Starch which tab and which columns hold the quota targets and territory assignments, and it pulls them into the memo without you copying anything.

Will Starch actually log the sent memo back in HubSpot so we have a record?

Starch syncs Gmail on a schedule, so sent emails are visible in Starch. For logging back to HubSpot specifically — as a note or activity on a record — tell Starch to do it as part of the automation and it will query HubSpot from the integration catalog to write the note. It is not a one-click 'log to CRM' button today; you configure it as a step in the workflow.

Is Starch SOC 2 certified? We have a security review before adding new tools.

Not yet — Starch is not SOC 2 Type II certified as of today. If your security review requires it, that's an honest blocker to flag upfront rather than after setup.

How do we handle memos that need legal or finance review before going out?

Use the Project Management app to create a review task with a due date and assignee (e.g., 'Legal sign-off on quota credit language — due Thursday 5pm'). Starch won't auto-gate the send on task completion, but you'll have a clear checklist visible before you trigger the distribution step in Gmail.

Can Starch handle the actual writing or do we still need to edit everything?

Starch drafts from your brief and your live data — the output is a real draft, not a fill-in-the-blank template. For a standard territory or quota memo, most RevOps teams find they're editing for tone and org-specific context rather than rewriting structure. The more specific your prompt (audience, what changed, what reps need to do, tone), the closer the first draft is to sendable.