Internal Comms & Meetings

How to write an exec brief as Professional Services Founders

Internal Comms & MeetingsFor Professional Services Founders4 apps11 steps~22 min to set up

Writing an exec brief sounds simple — summarize where the engagement stands, what's at risk, what needs a decision. But at a 12-person consultancy you're pulling from four different places: the HubSpot deal record, a Gmail thread from Tuesday where the client changed scope, a Notion doc the senior wrote two weeks ago, and your own memory of last week's call. By the time you've stitched it together it's 45 minutes gone and you still have to make it readable. Client-facing briefs get recycled decks with the date changed. Internal briefs don't exist — you just talk. When a partner asks 'where are we with Meridian?' you're reconstructing it live.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Professional Services Founders4 apps11 steps~22 min to set up

Outcome

What you'll set up

A brief-generation workflow that pulls the HubSpot deal status, recent Gmail threads, and meeting notes into a structured draft in under 5 minutes

A searchable archive of every exec brief you've produced, linked to the client and engagement, so 'where are we with Meridian' has a real answer

A reusable brief template that formats scope, risks, decisions needed, and next steps consistently — so client-facing updates don't require a senior to lose their Friday

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

Email Agent Meeting Notes Knowledge Management Presentation Agent

Data sources & config

Starch syncs your Gmail data on a schedule so threads are ready to query without manual export. Connect HubSpot from Starch's integration catalog — the agent queries your deal records, contact notes, and pipeline stage live when the brief runs. Google Calendar is synced on a schedule so meeting history is available for context. Notion connects from Starch's integration catalog so any engagement docs or prior deliverables the agent references are pulled live. No new tools required — your existing stack stays in place.

Prompts to copy

Pull the last 14 days of Gmail threads tagged or from the Meridian Capital domain, summarize the key asks, scope changes, and anything I haven't replied to yet

Take the transcript from our Meridian kickoff call and the two check-ins since — extract decisions made, open action items, and anything the client said that contradicts the original SOW

Write a 400-word internal exec brief for the Meridian Capital engagement: current status, scope drift risks, decisions I need to make this week, and the three things a new partner would need to know to run the next client call

Turn that brief into a 6-slide client-ready update deck — status summary, work completed, open items, risks, decisions needed from client, and next milestone with date

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

Walkthrough

Step-by-step

1 Connect Gmail (scheduled sync) and HubSpot (live query from Starch's integration catalog) so Starch has access to your client threads and deal records from day one.

2 Use the Meeting Notes app to transcribe and archive your next client call — Starch will extract decisions, action items, and any scope language the client used.

3 After the call, open the Email Agent and type: 'Summarize the last 10 emails from the Meridian Capital thread, flag anything where scope or timeline changed, and list what I haven't responded to.' Review and confirm the summary — this becomes the first input to your brief.

4 Pull the relevant HubSpot deal record into the same session — the agent queries it live and brings in deal stage, close date, contract value, and any notes your team logged.

5 Add context from Notion — type: 'Fetch the Meridian engagement doc from Notion and pull the original SOW scope and deliverable list.' The agent queries Notion live and appends it to the brief context.

6 Type your brief prompt into Starch: 'Write an internal exec brief for Meridian Capital — include current engagement status, where scope has drifted from SOW, decisions I need to make this week, and what a partner needs to know to run the next client call.' Starch drafts against your real data, not a blank template.

7 Review the draft — edit the decisions-needed section directly in Starch, then save it to Knowledge Management so it's archived under the Meridian client record with a timestamp.

8 If you need a client-facing version, hand the internal brief to the Presentation Agent: 'Turn this into a 6-slide client update deck with status, completed work, open items, risks, client decisions needed, and next milestone.' Export to PowerPoint or PDF.

9 For weekly recurring briefs across multiple clients, set up an automation: every Monday at 8am, pull last week's Gmail and Calendar activity for each active HubSpot deal and generate a draft brief per client, then Slack you the summaries.

10 As briefs accumulate in Knowledge Management, they become searchable context — when a partner asks about Meridian three months later, they search and get the full history of every brief, decision, and status update without asking you.

11 Before a retainer renewal conversation, run: 'Show me all exec briefs for Meridian from the last six months, list the recurring risks we flagged, and summarize how scope has evolved.' You walk into that meeting with evidence, not impressions.

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

Meridian Capital — March 2026 QBR Prep Brief

Sample numbers from a real run

Original SOW value (Stripe invoice)	48,000
Scope additions logged in HubSpot notes	11,500
Unbilled work (utilization gap, not yet invoiced)	6,200
Renewal opportunity flagged in pipeline	52,000

It's the Wednesday before a Thursday QBR with Meridian Capital. You have 40 minutes. You open Starch and ask the Email Agent to summarize the last 21 days of Gmail threads from the client — it surfaces three threads: a scope expansion request from Feb 28 that you acknowledged but never formally documented, a delayed deliverable you promised by March 14 (today), and an unanswered question about the Phase 2 timeline from their CFO. You pull the HubSpot deal record live — the deal is still at 'Proposal Sent' from December because nobody updated it. You pull the Meridian Notion doc — the original SOW scope is three workstreams; Meeting Notes from the February 18 check-in shows a fourth was verbally added. Starch drafts an internal brief in 90 seconds: current status (Phase 1 delivered, Phase 2 scope undefined), $11,500 in verbal additions not documented, one overdue deliverable, one unanswered CFO question, and two decisions needed before QBR — whether to formalize the scope expansion as a change order or include it in the renewal, and what to tell the CFO about Phase 2 timeline. You spend your 40 minutes editing the brief and preparing your position, not finding the information. The Presentation Agent turns it into a 6-slide QBR deck. You walk in prepared. The renewal conversation opens at $52,000.

Measurement

How you'll know it's working

Time from 'prep for client meeting' to ready-to-send brief (target: under 10 minutes)

Number of scope changes formally documented before billing discussions (currently: most are verbal and forgotten)

Retainer renewal rate and whether briefs are created before renewal conversations vs. improvised in the meeting

Senior hours spent on internal and client reporting per week (target: recover 2–3 hours of billable time)

Unanswered client emails older than 48 hours (a proxy for brief quality — missed threads become surprises)

Comparison

What this replaces

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

Kantata / Projector / Deltek

Built for 200-person firms with dedicated PMO staff — implementation takes a quarter, costs $15k–$40k/year, and still requires someone to write the narrative brief by hand.

ChatGPT or Claude (standalone)

Drafts well but has no connection to your actual HubSpot deals, Gmail threads, or Notion docs — you're pasting context manually every time, which defeats the purpose.

Notion AI

Great for editing docs that already live in Notion, but it can't pull your HubSpot deal stage or Gmail threads in — you're still assembling inputs by hand before writing.

Manual (Google Docs + copy-paste)

Free and flexible, but 45 minutes per brief adds up to 3+ hours a week across active clients, and the outputs are inconsistent enough that a new partner can't rely on them.

On Starch RECOMMENDED

One platform — email agent, meeting notes, 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

Does Starch store my client emails and meeting transcripts permanently?

Gmail syncs on a schedule and messages are queryable through Starch. Meeting transcripts generated by the Meeting Notes app are archived in your Starch workspace. Starch is not SOC 2 Type II certified today, so if a client has strict data-handling requirements in their MSA, check that before connecting their threads.

My pipeline lives in a Google Sheet, not HubSpot. Can Starch still pull deal context?

Yes. Connect Google Sheets from Starch's integration catalog — the agent queries it live when building your brief. You can describe exactly which columns map to client name, deal stage, contract value, and notes. If you eventually move to HubSpot, the same workflow transfers.

What about Harvest or Float for utilization data — can those feed into the brief?

Harvest and Float are reachable from Starch's integration catalog of 3,000+ apps, so the agent can query them live when your brief runs. Describe what you want — 'pull this month's logged hours for the Meridian project from Harvest and include utilization vs. budget in the brief' — and Starch builds it.

The Presentation Agent is listed as 'currently in development' — what do I do for client decks now?

The Presentation Agent is in development; request beta access to get notified when it launches. In the meantime, Starch drafts the brief text and you paste it into your existing Google Slides or PowerPoint template. The value of having the content ready is most of the work — the formatting step is minor.

Can I set this up to run automatically before every client call on my calendar?

Yes. Starch syncs your Google Calendar data on a schedule. You can build an automation: 'For every client call on my calendar, 2 hours before it starts, pull the Gmail threads, HubSpot deal record, and last brief for that client, and draft an updated status summary — then Slack it to me.' Describe it in plain language and Starch builds the automation.

Will this work if different clients are managed by different people on my team?

If your team logs activity in HubSpot and Gmail, Starch can pull it regardless of who owns the deal or thread. For meeting notes, whoever has the Meeting Notes app running on the call generates the transcript. The Knowledge Management archive is shared across your workspace, so the brief history is accessible to anyone you give access — not locked in the founder's head.