Internal Comms & Meetings

How to write a weekly team update as Small Marketing Teams

Internal Comms & MeetingsFor Small Marketing Teams3 apps12 steps~24 min to set up

Every Friday afternoon, someone on your three-person marketing team spends 90 minutes copy-pasting numbers into a Google Doc. HubSpot for MQL count and deal velocity. GA4 for sessions and conversion rates. Meta Ads and Google Ads for spend and CPL. Customer.io or Klaviyo for email open and click rates. None of it is connected, so you're manually reconciling last week's pipeline contribution, trying to explain why MQL volume dipped, and hoping you didn't transpose a number before the Slack message goes to the CEO. The update is always late, always a little wrong, and always the last thing you want to do at 4pm on a Friday.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Marketing Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A weekly report app that pulls HubSpot deals, GA4 sessions, and ad spend into one structured summary — described in plain language, built by Starch

An automated Monday morning Slack message to your CEO with the prior week's pipeline contribution, MQL count, CPL by channel, and one-sentence narrative on any notable change

A running archive of every weekly update so you can answer 'what happened in March?' in 30 seconds instead of digging through old Slack threads

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

Growth Analyst Email Agent Project Management

Data sources & config

HubSpot is a scheduled-sync provider — Starch syncs your HubSpot contacts, companies, and deals on a schedule so the weekly report always pulls fresh deal and MQL data. Google Analytics 4, Meta Ads, and Google Ads are connected from Starch's integration catalog; the agent queries them live when your report runs. Slack is also connected from Starch's integration catalog for the automated Monday morning message. Gmail is a scheduled-sync provider used by the Growth Analyst starter app for any email performance context you want to include.

Prompts to copy

Build me a weekly marketing report that pulls last week's MQL count and deal velocity from HubSpot, sessions and goal completions from GA4, and spend plus CPL from Meta Ads and Google Ads. Show a comparison to the prior week for each metric and flag anything that moved more than 15% in either direction.

Every Monday at 8am, send a Slack message to #marketing-updates with last week's pipeline contribution summary, top channel by CPL, and a one-sentence explanation of any metric that moved more than 15% week-over-week.

Create a task for me to review the weekly update draft every Friday at 3pm and assign it to myself with a Friday due date.

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

Walkthrough

Step-by-step

1 Connect HubSpot from the scheduled-sync setup in Starch — deals, contacts, and owners sync automatically on a schedule, so your MQL count and pipeline data are always current without any manual export.

2 Connect Google Analytics 4, Meta Ads, and Google Ads from Starch's integration catalog; the agent queries each one live when your weekly report runs, so you're always looking at real numbers, not a week-old snapshot.

3 Connect Slack from Starch's integration catalog so Starch can post your Monday morning summary to whatever channel your CEO actually reads.

4 Start from the Growth Analyst app in the Starch App Store — it's built for exactly this kind of cross-source marketing summary and gives you a working skeleton to customize rather than starting from a blank prompt.

5 Tell Starch what you want: 'Build me a weekly marketing report that shows last week's MQL count and deal velocity from HubSpot, sessions and goal completions from GA4, and spend plus CPL from Meta Ads and Google Ads. Compare each metric to the prior week and flag anything that moved more than 15%.'

6 Review the first output with your team — adjust which metrics matter most, rename any labels to match your internal language (your CEO calls them 'new opps,' not 'deals created'), and save the updated version.

7 Set up the Monday morning automation: 'Every Monday at 8am, pull last week's data from the weekly report app, write a three-paragraph summary with one paragraph per channel cluster, and post it to #marketing-updates in Slack.'

8 Add a Friday afternoon task in the Project Management app — 'Review weekly update draft, Friday 3pm, assigned to me' — so the review step doesn't get skipped when the week gets busy.

9 Use the Email Triage app to catch any reply from the CEO or your VP of Sales asking follow-up questions about the update — it flags high-priority incoming messages and drafts a response you can send in one click.

10 After four weeks, tell Starch to add a trend line: 'Add a four-week rolling average for MQL count and CPL by channel to the weekly report so we can see direction, not just last week's snapshot.'

11 When you onboard a new contractor or agency, share the archived weekly updates from inside Starch instead of forwarding old Slack messages — every update is stored and searchable by date, metric, or channel.

12 At the end of each quarter, tell Starch: 'Pull all 13 weekly updates from Q1, calculate average CPL by channel, total pipeline contributed, and MQL-to-opportunity conversion rate for the quarter' — your QBR data is already there, no new export needed.

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

Week of March 10–14, 2026 — MQL dip investigation

Sample numbers from a real run

HubSpot MQLs (week)	38
Prior week MQLs	57
GA4 sessions (week)	42,300
Meta Ads spend	4,200
Google Ads spend	3,100
Meta CPL	74
Google CPL	61
Pipeline contributed ($)	127,000

MQL volume dropped from 57 to 38 week-over-week — a 33% decline that would normally trigger a full manual investigation across HubSpot, GA4, and both ad platforms. Instead, Starch's weekly report flagged it automatically (threshold: 15% movement) and surfaced the likely cause: Google Ads sessions were down 18% because a broad match keyword group got paused mid-week by an automated budget rule. Meta spend held steady at $4,200 and CPL actually improved from $81 to $74, so paid social wasn't the issue. Pipeline contribution still came in at $127,000 because the deals already in HubSpot were advancing — so the CEO message on Monday led with 'pipeline healthy, MQL dip is a paid search mechanical issue, fixed Friday' rather than a vague 'volume was soft.' Total time to produce the update: under 10 minutes to review and approve the Starch draft, down from 90 minutes of manual assembly the week before.

Measurement

How you'll know it's working

MQL count week-over-week and vs. monthly target

Pipeline contribution in dollars (marketing-sourced deals created or advanced)

CPL by channel (Meta, Google, LinkedIn) with week-over-week delta

Email engagement rate (open + click) for any nurture sequences that ran that week

Time to produce and distribute the weekly update (a process health metric, not a vanity metric)

Comparison

What this replaces

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

Manual Google Doc + copy-paste from HubSpot, GA4, and ad platforms

Free but costs 60–90 minutes of someone's Friday afternoon, is error-prone when you're joining three number sources manually, and produces a one-time artifact with no memory or trend layer.

Looker Studio (Google Data Studio) dashboard

Good at visualization once it's set up, but requires someone who can build connectors and maintain the schema; no narrative generation, no Slack delivery, and no 'why did this change' explanation — you still write that part yourself.

HubSpot Reports + custom dashboards

Strong for HubSpot-native metrics like MQL count and deal velocity, but can't pull in GA4 sessions or Meta/Google ad spend without a paid integration, so you're still manually reconciling cross-channel attribution.

Notion AI or Google Docs with manual data paste

AI can help you write the narrative once you have the numbers, but you still have to gather the numbers yourself — it doesn't connect to HubSpot or your ad platforms.

On Starch RECOMMENDED

One platform — growth analyst, email agent, 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 Customer.io for lifecycle email, not Gmail. Can Starch include email performance metrics in the weekly update?

Yes. Customer.io is available through Starch's integration catalog — connect it and the agent queries your campaign performance data live when the report runs. You'd tell Starch: 'Include last week's open rate and click rate for any Customer.io campaigns that sent, and flag any sequence where click rate dropped more than 10 points week-over-week.' If you're on Klaviyo or Mailchimp, those are also in the integration catalog and work the same way.

We don't use HubSpot — we're on Salesforce. Does this still work?

Salesforce is available from Starch's integration catalog and the agent queries it live. You won't get the scheduled-sync depth that HubSpot gets (where data is pre-stored in Starch), but for weekly MQL count and pipeline contribution numbers, a live query at report-generation time is exactly what you need.

Can Starch explain *why* a metric changed, or does it just show the numbers?

It can do both. Starch pulls the data and can generate a narrative explanation — but it's pattern-matching against the numbers across your connected sources, not reading your media buyer's mind. If MQL volume dropped because a keyword got paused, and Starch can see that Google Ads sessions also dropped that week, it will surface that correlation. If the cause is something outside your connected data (a sales team process change, a bad landing page you haven't connected), it will flag the anomaly and note what it can and can't explain.

Is my HubSpot and ad platform data stored in Starch, or is it just queried when the report runs?

Depends on the source. HubSpot is a scheduled-sync provider — Starch syncs your deals, contacts, and company data on a schedule and stores it so the report can run fast and compare across time. GA4, Meta Ads, and Google Ads are queried live from Starch's integration catalog each time your report runs — the data isn't stored in Starch long-term. That means your weekly trend history lives in the HubSpot-backed data; for ad platform trend analysis, the report queries fresh each Monday.

What if I want the report to go to different people in different formats — a short Slack summary for the CEO and a detailed breakdown for the marketing team?

You can set up two separate automations. Tell Starch: 'Every Monday at 8am, post a three-bullet Slack summary of pipeline contribution, top CPL channel, and one notable change to #exec-updates' and separately 'post the full weekly breakdown with all metrics and week-over-week deltas to #marketing-team.' Same underlying data, two different outputs, both automated.

Is Starch SOC 2 certified? We'd be piping HubSpot deal data and ad spend through it.

Starch is not SOC 2 Type II certified today. If your company has a strict data security policy that requires SOC 2 for any tool handling CRM or ad data, that's worth checking with your IT or legal team before wiring up the integrations.