Marketing & Growth

How to send a weekly marketing report as Small RevOps Teams

Marketing & GrowthFor Small RevOps Teams3 apps12 steps~24 min to set up

Every Friday afternoon you're copying pipeline snapshots out of HubSpot, pasting rep activity rows from Apollo, cross-referencing LinkedIn touch data you half-remember, and building a 'weekly marketing report' that's really just a Frankenstein doc assembled in Google Slides or Sheets. By the time you send it, Monday's already started. The CRO wants attribution. The VP of Marketing wants channel ROI. The AE team wants to know which sequences are actually converting. You have three tabs open, two exports in progress, and a Slack message asking for 'just a quick number.' There's no single place where HubSpot deals, Apollo sequence performance, Gmail engagement, and campaign spend live together. So you build it manually, every week, from scratch.

Build this on Starch → See the apps used

Marketing & GrowthFor Small RevOps Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A weekly marketing report that automatically pulls HubSpot deal movement, Apollo sequence performance, and Gmail engagement into one view — no manual exports, no Slack data requests.

A Growth Analyst digest that emails your team a plain-English summary of what changed in pipeline and conversion this week, with specific callouts on which channels drove the most qualified activity.

A standing automation that runs every Friday at 4pm, compiles the report from live data, and posts a summary to a Slack channel so the Monday forecast call has something real to reference.

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 Growth Analyst LinkedIn Automation

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) and your Apollo.io data on a schedule (contacts, accounts, sequences). Gmail is synced on a schedule for thread engagement signals. Salesforce and Pipedrive are reachable from Starch's integration catalog; the agent queries them live when the report runs. LinkedIn enrichment data is pulled through browser automation — no LinkedIn API required. Slack is synced on a schedule and used for the outbound report post.

Prompts to copy

Build me a weekly marketing report that pulls this week's new deals created and stage changes from HubSpot, sequence reply rates from Apollo, and email open rates from Gmail. Group the pipeline movement by source — inbound, outbound sequence, LinkedIn — and show me a week-over-week comparison for each channel.

Set up a Growth Analyst digest that emails me every Friday at 4pm with a summary of what changed in our funnel this week: new leads created, deals advanced, conversion rate by source, and the top three Apollo sequences by reply rate. Flag anything that moved more than 20% in either direction.

Add a Slack automation that posts the weekly report summary to #revenue-team every Friday at 4:30pm and tags me if any channel shows a week-over-week drop greater than 15%.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your HubSpot contacts, companies, deals, and owners on a schedule. This is the foundation of every channel attribution view in the report.

2 Connect Apollo.io — Starch syncs your Apollo accounts, contacts, and sequences on a schedule. Sequence reply rates and step-level performance flow directly into the report without any CSV export.

3 Connect Gmail — Starch syncs your Gmail messages and labels on a schedule, giving the report visibility into email engagement at the thread level without leaving your inbox.

4 If your team also uses Salesforce or Pipedrive, connect either from Starch's integration catalog; the agent queries them live when the weekly report runs.

5 Open the Sales Agent CRM starter app and describe the weekly marketing report view you actually need — deal source breakdown, stage velocity by channel, sequence-to-opportunity conversion rate — in plain language. Starch assembles the data model from your connected sources.

6 Add the Growth Analyst app and point it at your HubSpot deal data and Apollo sequence data. Tell it the three questions you want answered every week: which source drove the most qualified pipeline, which sequences converted best, and what moved most in conversion rate.

7 Set the Growth Analyst to email a digest every Friday at 4pm to the RevOps distribution list. The digest writes itself from the connected data — no template to maintain.

8 Build a Slack automation: tell Starch to post a plain-text summary of the weekly report to #revenue-team every Friday at 4:30pm, pulling the top-line numbers from the same HubSpot and Apollo sync.

9 Add an alert rule — if any channel's week-over-week pipeline contribution drops more than 15%, the automation tags you directly in Slack rather than burying it in the digest.

10 For LinkedIn attribution, use the LinkedIn Automation app to pull connection and message engagement data through browser automation. Map LinkedIn-sourced contacts back to HubSpot deal records by email so the attribution view accounts for social touches.

11 Schedule a monthly review prompt: tell Starch to generate a month-over-month summary comparing the four most recent weekly reports, highlighting trend lines in sequence performance and inbound conversion. Use this to prep the CRO's monthly pipeline review instead of rebuilding slides from scratch.

12 Publish the report app to your internal Starch workspace so any rep can open it, see their own pipeline contribution by source, and stop asking RevOps for 'just a quick list.'

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 Pipeline Report

Sample numbers from a real run

New deals created (HubSpot, all sources)	18
Deals from outbound Apollo sequences	7
Deals from inbound (form fill + Gmail thread)	6
Deals from LinkedIn touches (browser-enriched)	5
Apollo sequence reply rate (week avg)	9
Stage 2→3 conversions (week)	11
Week-over-week pipeline value change (%)	22

The week of March 10th, your Growth Analyst digest landed in the RevOps inbox at 4pm Friday and flagged two things before you had to look for them: outbound Apollo sequences drove 7 of the 18 new deals created, but the reply rate dropped from 13% to 9% week-over-week — a 30% fall that triggered your Slack alert to #revenue-team. LinkedIn touches contributed 5 new deals when browser-enriched contact data was mapped back to HubSpot records, a channel that previously showed zero attribution because it lived outside the CRM. The Slack post had the top-line numbers in the channel by 4:30pm, the Monday forecast call opened with actual data instead of 'let me pull that up,' and the CRO's question about which sequences to pause was already answered by the time the meeting started. No Friday afternoon Sheets session. No manual slide.

Measurement

How you'll know it's working

New pipeline created by source (inbound vs. outbound sequence vs. LinkedIn) week-over-week

Apollo sequence reply rate and sequence-to-opportunity conversion rate by campaign

Stage velocity — average days in each deal stage, broken down by rep and source

Gmail engagement rate on outbound threads (replies, opens) tied to HubSpot deal records

Time-to-report: how long from Friday 4pm to report-in-Slack (target: automated, zero manual touch)

Comparison

What this replaces

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

HubSpot native reporting + Salesforce reports

Both give you data inside the CRM but can't join Apollo sequence data, Gmail engagement threads, or LinkedIn touches into a single cross-channel view without manual export work.

Google Sheets + manual CSV exports

Fully flexible but rebuilds from scratch every week; no automation, no alerts, and the model breaks every time territory or stage definitions change.

Looker or Tableau + data engineering

Handles large-scale historical analytics well, but requires a data team to build and maintain connectors — overkill for a 2-person RevOps team that needs answers on Friday afternoon, not a six-week BI project.

Apollo native reporting

Shows sequence performance accurately but lives in a silo — no view of how Apollo-sourced contacts move through HubSpot stages or what their Gmail thread history looks like.

On Starch RECOMMENDED

One platform — sales agent crm, growth analyst, linkedin automation 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 still work?

Yes. Connect Salesforce from Starch's integration catalog; the agent queries it live when your weekly report runs. You won't get the scheduled-sync depth that HubSpot users get — deal data is queried on demand rather than stored in Starch — but for a weekly report that's a feature, not a gap. You're always pulling from live Salesforce data, not a stale snapshot.

What does 'browser automation for LinkedIn' actually mean? Is it scraping?

Starch automates LinkedIn through your browser — it logs in as you and navigates the way you would. It reads connection and message data that's visible in your account. It doesn't bypass LinkedIn's login or scrape public pages without authentication. The LinkedIn Automation app uses this to enrich contact records and map LinkedIn touches back to CRM deals.

Will the Growth Analyst digest work if we're not using PostHog?

The Growth Analyst starter app is built around PostHog for product and traffic analytics. If you're not on PostHog, you can build a custom weekly digest app in plain language — describe the data sources you want (HubSpot, Apollo, Gmail) and what questions you want answered each week, and Starch assembles it from your connected data without needing PostHog at all.

Is Starch SOC 2 certified? We have to answer that for IT.

Not yet — Starch is not SOC 2 Type II certified today. That's worth knowing before you connect production CRM data. It's on the roadmap. If SOC 2 is a hard requirement for your IT team, you should flag that now rather than discover it post-setup.

Can this replace the Friday afternoon slide deck we send to the leadership team?

The report automation and Growth Analyst digest replace the data assembly part of that work — pulling numbers, doing the week-over-week comparison, identifying what moved. If leadership needs a polished slide deck, Presentation Agent (currently in development — request beta access) is built specifically to take a text description and build a formatted slide deck from it, including pulling in numbers from your connected data.

Our QuickBooks data would be useful for the marketing spend side of this report. Any limits there?

Starch syncs QuickBooks entity-level data — invoices, bills, payments, vendors, journal entries — on a schedule. One current limit: QuickBooks report views like P&L summaries and Transaction List are temporarily disabled while an upstream connector issue is fixed. Entity-level data syncs normally, so you can build spend breakdowns from raw transaction and vendor records.