Internal Comms & Meetings

How to write an exec brief as Small RevOps Teams

Internal Comms & MeetingsFor Small RevOps Teams2 apps12 steps~24 min to set up

You're two people supporting 30 reps, and every week the CRO asks for an exec brief before the forecast call. You pull pipeline numbers from HubSpot, paste them into Sheets, manually cross-reference Apollo sequence data, check Gmail threads for deal context, and then stitch it into a slide or a doc that's stale by the time it lands in the CRO's inbox. The brief takes 3-4 hours to assemble — 90 minutes of pulling, 30 minutes of reconciling numbers that don't match, and an hour of formatting. Nobody has signed off on a standard template, so you rebuild it from scratch every Monday. When the CRO asks 'why is Acme still in Stage 3?' you're the one digging through notes to find out.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small RevOps Teams2 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated exec brief that pulls live pipeline, sequence activity, and deal-stage changes from HubSpot and Apollo into a structured, readable summary — drafted and ready before you've had your first coffee on Monday

A consistent format the CRO and leadership team actually recognize from week to week, with deal highlights, forecast delta vs. prior week, and top risks called out explicitly

A workflow where you review and approve the brief in 15 minutes instead of building it from scratch — so the 3-hour Monday morning task becomes a 15-minute edit

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 Email Agent

Data sources & config

Starch syncs your HubSpot data on a schedule — deals, contacts, owners, and stage history — so the brief always reflects current CRM state. Apollo.io is connected directly through Starch's scheduled sync, pulling sequence enrollment and activity data so you can cross-reference outreach cadence against deal health. Gmail is also synced on a schedule so Starch can surface relevant thread context for deals where the last touch was an email. The automation runs on a Monday morning schedule and drops the draft into your Email Agent queue for a final review before it sends.

Prompts to copy

Every Monday at 7 AM, pull this week's open pipeline from HubSpot — deals by stage, owner, close date, and amount — and compare it to last week's snapshot. Flag any deals that moved backward in stage, any that haven't had activity in 10+ days, and any that are forecast-commit but missing a next step. Format the output as an exec brief with a one-paragraph summary at the top, a pipeline table by stage, and a 'deals to watch' section with 3-5 bullets.

Draft an email to the CRO with the exec brief attached. Subject line: 'Weekly Pipeline Brief — [date]'. Body should be 3 sentences: total pipeline value, biggest change from last week, and one call-out about a deal at risk. Attach the full brief as an inline doc.

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

Walkthrough

Step-by-step

1 Connect HubSpot to Starch — Starch syncs your deals, contacts, owners, and stage history on a schedule. This is the foundation of every metric in the brief.

2 Connect Apollo.io — Starch syncs sequence enrollments and activity data so you can see whether deals have active outreach or have gone cold.

3 Connect Gmail — Starch syncs your inbox so it can pull in the most recent email thread context for any deal flagged in the brief.

4 Open the Sales Agent CRM app from the Starch App Store and fork it for your team's pipeline view — customize the stage names and owner fields to match your HubSpot setup.

5 Tell Starch what you want the brief to look like: describe the format in plain language — total pipeline by stage, week-over-week delta, deals without activity, forecast-commit deals missing a next step.

6 Set the automation to run every Monday at 7 AM. Starch pulls the latest synced data, runs the comparison against the prior week's snapshot, and drafts the brief.

7 Configure the 'deals to watch' logic — tell Starch your criteria: no activity in 10+ days, stage regression, or commit-category deals with no next step logged in HubSpot.

8 Wire the output to Email Agent. Tell Starch: 'Draft a Monday morning email to [CRO name] with the exec brief. Subject line: Weekly Pipeline Brief — [date]. Three-sentence summary in the body, full brief inline.'

9 Review the first three drafts manually before flipping to auto-send — this is where you catch formatting edge cases and tune the 'deals to watch' criteria to match what the CRO actually cares about.

10 Share the brief format with the CRO and get sign-off on the template once. After that, every week looks the same — which is the point.

11 For one-off 'can you pull me a list of...' requests, use the Sales Agent CRM app's natural-language query interface: 'Show me all deals in Stage 4 owned by the West territory reps with close dates in Q2.' Pull it in under 2 minutes instead of exporting from HubSpot and filtering in Sheets.

12 Once the weekly brief is stable, extend the same automation to a month-end version — same structure but with quarter-to-date attainment, rep-level pipeline coverage, and a forecast vs. quota table.

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

Monday Brief — Week of March 17, 2026

Sample numbers from a real run

Total open pipeline (Stage 2-5)	4,200,000
Forecast commit	1,100,000
Best case	870,000
Pipeline added WoW	215,000
Pipeline lost or pushed WoW	340,000
Deals with no activity 10+ days	11

Starch pulled Monday's brief at 7:02 AM. Total open pipeline was $4.2M across 47 deals — down $125K net from the prior week after two deals pushed to Q3 (Northstar Logistics at $180K and Beacon Health at $95K) and three new deals entered Stage 2 from Apollo sequences totaling $215K. Forecast-commit sits at $1.1M with 18 days left in the month; the CRO's target is $1.4M, so the brief flagged a $300K gap and called out the three commit-category deals missing a logged next step in HubSpot. The 'deals to watch' section surfaced Acme Manufacturing ($220K, Stage 4, last email 14 days ago) and Ridgeline Partners ($150K, regressed from Stage 4 to Stage 3 after a champion left). The full brief was in the CRO's inbox by 7:15 AM. Total RevOps time spent: 12 minutes reviewing and approving the draft.

Measurement

How you'll know it's working

Time to brief delivery — target: in CRO inbox before 8 AM Monday without manual assembly

Forecast accuracy — delta between Monday commit call and actual month-end close, tracked week over week

Deal hygiene rate — percentage of open opportunities with a logged next step and activity in the last 7 days

Stage regression count — number of deals that moved backward in stage in a given week, flagged in the brief

Brief turnaround time — RevOps hours spent on exec brief per week (target: under 20 minutes from draft to send)

Comparison

What this replaces

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

HubSpot reports + manual Slides/Docs assembly

You already have HubSpot — but it doesn't write the brief, compare week-over-week automatically, or send the email; you're still doing all of that by hand every Monday morning.

Clari or Bowtie (dedicated forecast tools)

Purpose-built for forecast calls and strong on pipeline analytics, but they're another tool license, don't draft the written brief or send it, and don't pull in Apollo sequence context alongside CRM data.

ChatGPT with a copy-pasted pipeline export

Works for drafting prose but requires you to manually export, clean, and paste data every week — the data-pull problem is unsolved, so you're still doing the 90-minute setup before the AI can help.

BI tool (Looker, Metabase) + Slack export

Great for visualizations, but a dashboard isn't a brief — it doesn't write the summary paragraph, flag risks in plain English, or send a formatted email to the CRO without additional work on top.

On Starch RECOMMENDED

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

We use Salesforce, not HubSpot. Can Starch still pull the pipeline data for the brief?

Yes. Connect Salesforce from Starch's integration catalog — the agent queries it live when the automation runs. You won't get the same scheduled-sync depth as HubSpot (which syncs on a schedule and stores data in Starch), but for a weekly brief the live query is sufficient. Describe your Salesforce object structure to Starch and it will map to the right fields.

What if our deal stages in HubSpot don't match the default Sales Agent CRM template?

Fork the template and describe your stage names in plain language. Tell Starch: 'Our pipeline has five stages: Qualified, Demo Scheduled, Proposal Sent, Legal Review, Closed Won. Map the brief sections to these stages.' It will rebuild the template to match your setup.

Is Starch SOC 2 Type II certified? Our CRO will ask before we connect HubSpot.

Not yet — Starch is not SOC 2 Type II certified today. If your security review requires it, that's a legitimate blocker to flag. It's on the roadmap and worth asking the Starch team about current status.

Can the brief pull in data from LinkedIn touches alongside HubSpot and Apollo?

Yes. Starch syncs LinkedIn connection and message data on a schedule. You can tell Starch to include LinkedIn activity in the deal-context section of the brief — for example, flagging deals where the last meaningful touch was a LinkedIn message rather than a CRM-logged call.

What if the CRO wants the brief in a slide deck format instead of an email?

The Presentation Agent app is currently in development — request beta access to get notified when it launches. In the meantime, you can tell Starch to format the brief output as a structured Google Doc and pull it into Slides manually. It's an extra step, but the data assembly is still automated.

We don't want this to auto-send — we want to review it first. Can we set it up that way?

Yes, and that's actually the recommended starting point. Configure the automation to drop the draft into your Email Agent queue rather than auto-sending. You get the draft in your inbox at 7 AM, review it for 10-15 minutes, and hit send. Auto-send is an option once you trust the output, but manual-approve is the safer default for a brief that goes to leadership.

We get 'can you pull me a list of...' requests from reps all day. Can Starch handle those too?

That's one of the higher-ROI use cases. Once HubSpot and Apollo are connected, you can answer ad-hoc requests through the Sales Agent CRM's natural-language query — 'show me all Stage 3 deals in the Northeast territory with close dates before April 30' — and get a table back in under two minutes. No export, no filter, no Slack message to you required.