Strategy & Planning

How to track okr progress weekly as Small Marketing Teams

Strategy & PlanningFor Small Marketing Teams3 apps11 steps~22 min to set up

Your three-person team owns five or six OKRs across demand gen, content, lifecycle, and events — and tracking progress means pinging four different people every Friday, pulling HubSpot deal data manually, checking a GA4 tab you last refreshed on Tuesday, and then copying numbers into a Google Sheet that the CEO barely reads. Nobody disputes that OKRs matter. What nobody has time for is the 90-minute weekly ritual of chasing updates, reconciling numbers across tools that don't talk to each other, and reformatting everything into a status doc before standup. By the time the slide is done, two of the numbers are already stale.

Build this on Starch → See the apps used

Strategy & PlanningFor Small Marketing Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A live OKR tracker app that pulls key results directly from HubSpot, GA4, and your ad platforms — so weekly progress is always a refresh away, not a manual assembly job

An automated weekly summary that lands in Slack or Gmail every Monday morning with a plain-English read on where each key result stands, what moved, and what's at risk

A searchable knowledge layer where OKR definitions, owner assignments, measurement methodology, and historical updates live — so new contractors and the CEO asking 'how do we define an MQL again?' both get an instant answer

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

CRM Growth Analyst Knowledge Management

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals) and syncs Gmail on a schedule for email signal. Google Analytics 4, LinkedIn Ads, Google Ads, Customer.io, and Slack are connected from Starch's integration catalog — the agent queries them live when your OKR app or weekly automation runs. Notion is also available as a scheduled-sync provider if your team keeps OKR documentation there. No BI tool or manual CSV export required.

Prompts to copy

Build me a weekly OKR progress tracker for our marketing team. Pull HubSpot for MQL count, SQL conversion rate, and pipeline sourced. Connect Google Analytics 4 from the integration catalog for organic sessions and demo request conversion rate. Connect LinkedIn Ads and Google Ads from the integration catalog for blended CAC. Show each key result as a progress bar against target with a week-over-week delta column.

Every Monday at 8am, generate a plain-English OKR status summary: for each key result, one sentence on where we stand, one sentence on the biggest mover since last week, and a red/yellow/green status flag. Post it to our #marketing-team Slack channel.

Build a knowledge base for our OKR program. Store the definition of each key result, how it's measured, who owns it, and a log of weekly check-in notes. Let me add updates via chat — 'MQL target is 120, we're at 94 as of April 18' — and surface them in search so the CEO can pull context without asking me.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs contacts, companies, and deals on a schedule. Map your MQL stage, SQL stage, and pipeline-sourced deal field so the OKR tracker knows what to count.

2 Connect Google Analytics 4 from Starch's integration catalog. Identify the goal event or conversion you're using for demo requests or free-trial signups — that becomes your conversion-rate key result.

3 Connect LinkedIn Ads and Google Ads from Starch's integration catalog. If Meta Ads is also part of your paid mix, connect it the same way. The agent queries spend and conversion data live when your CAC key result updates.

4 Tell Starch: 'Build me a marketing OKR tracker with five key results: MQL volume, SQL conversion rate, pipeline sourced, organic sessions, and blended CAC. Show target, current value, percent to goal, and week-over-week delta for each.' Starch builds the app.

5 Review the generated app. If your MQL definition is non-standard — say, a deal stage rather than a contact lifecycle stage — tell Starch: 'An MQL in our HubSpot is any deal that enters the Qualified stage with lead source = Inbound. Update the MQL count logic.' Starch adjusts.

6 Set up the weekly automation: 'Every Monday at 8am, pull the latest values for all five key results, compare to last Monday's snapshot, generate a red/yellow/green status for each, and post a summary to #marketing-team in Slack.' Test it manually before Monday.

7 Open the Knowledge Management app. Create an OKR definition page for each key result — measurement methodology, owner, target, and any known data quirks (e.g., 'HubSpot pipeline figures exclude deals owned by Sales Ops'). Tell Starch: 'Auto-categorize new entries under the relevant OKR and flag any definition page that hasn't been updated in 30 days.'

8 Wire the weekly check-in workflow: after the Monday Slack post goes out, each OKR owner replies in thread with their commentary. Tell Starch: 'Every Monday at 9am, pull replies from the #marketing-team channel on the weekly OKR post and log them as check-in notes in the Knowledge Management app under the relevant key result.'

9 Build the CEO-facing view: 'Build a read-only dashboard that shows all five key results, current status, and a one-sentence commentary from this week's check-in. Make it shareable via link without requiring login.' Use this instead of reformatting a Google Sheet before every leadership sync.

10 Add an alert layer: 'If MQL count week-over-week drops more than 15%, or CAC increases more than 20% in a single week, send me an email with the key result name, the delta, and the last three weeks of history.' Now you know before the CEO asks.

11 At end of quarter, tell Starch: 'Generate a one-page OKR retrospective for Q2 2026 marketing. Pull the week-by-week history for all five key results, highlight the three biggest inflection points, and draft a narrative summary I can paste into the board update.' This is the output you used to spend a half-day assembling.

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

Q2 2026 Week 6 OKR Check-in — Marketing Team

Sample numbers from a real run

MQL Volume (target: 120)	94
SQL Conversion Rate (target: 28%)	24
Pipeline Sourced (target: $480,000)	371,000
Organic Sessions (target: 18,000)	19,400
Blended CAC (target: ≤$310)	348

It's Monday morning. The Starch automation fires at 8am and posts to #marketing-team: MQL volume is 94 of 120 (yellow — 6 weeks left, 26 MQLs to close the gap), SQL conversion rate is 24% against a 28% target (red — down 3 points from last week after a batch of event leads came through at lower intent), pipeline sourced is $371K of $480K (yellow), organic sessions are 19,400 and already past the 18K target (green), and blended CAC is $348 against a $310 target (red — Google Ads CPL spiked mid-week). Before the 9am standup, you reply in thread: 'CAC spike is Google Brand campaign — CPCs up 18% since competitor started bidding on our name. Pausing tomorrow.' Starch logs that note in the Knowledge Management app under the CAC key result. When the CEO asks on Wednesday why pipeline is behind, you share the read-only dashboard link. She has context in 30 seconds. No reformatting required.

Measurement

How you'll know it's working

MQL volume and week-over-week trend by source

SQL conversion rate (MQL to SQL) by lead source or campaign

Marketing-sourced pipeline in dollars (HubSpot deals with marketing source tag)

Blended CAC across Google Ads, LinkedIn Ads, and organic (spend ÷ new customers attributed)

Organic sessions and demo-request conversion rate from GA4

Comparison

What this replaces

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

Google Sheets + manual exports

Gets the job done the first time you build it, but every Friday someone has to re-pull HubSpot, re-export GA4, and re-paste — the sheet is almost always stale by Monday and there's no alert when a number goes off the rails.

Looker Studio (free)

Good for static visualization once you've wired the connectors, but the connector setup takes engineering time you don't have, it doesn't generate natural-language summaries or Slack posts, and it can't hold your OKR definitions and check-in notes alongside the data.

Notion + manual weekly updates

Fine as a home for OKR documentation, but someone still has to fill in the numbers every week — Notion doesn't pull from HubSpot or GA4, so you're back to copying and pasting.

Databox or Klipfolio

Purpose-built for marketing dashboards with decent connector libraries, but you're paying for another tool, still need to define the metric logic yourself, and there's no AI layer that writes the Monday summary or logs check-in notes.

On Starch RECOMMENDED

One platform — crm, growth analyst, 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

We track OKRs in Notion today. Can Starch read that?

Yes — Starch syncs your Notion pages and databases on a schedule, so if your OKR doc lives there, the agent can read current values, pull owner fields, and incorporate them into your tracker. If you want to keep Notion as the source of truth and just add the automation and alerting layer on top, that's a valid setup.

Our MQL definition is custom — it's a HubSpot deal stage, not a contact lifecycle stage. Will the tracker get this right?

Tell Starch exactly how you define it when you build the app, or correct it after the first run: 'An MQL is any deal that enters the Qualified stage with lead source = Inbound or Marketing.' The agent updates the query logic. You may need to tweak this once — after that it's consistent every week.

Does Starch store historical OKR data so we can show a trend line?

For HubSpot (scheduled sync), Starch stores snapshots and can show week-over-week deltas. For live-queried apps like GA4 and LinkedIn Ads, the data is pulled fresh each time rather than archived. If you need multi-quarter trend lines from ad platforms, the honest answer is that Starch is better for current-state and short-window trend tracking than as a long-horizon data warehouse.

What if we use Customer.io instead of Mailchimp for lifecycle? Does that connect?

Yes — connect Customer.io from Starch's integration catalog; the agent queries it live. If email-sourced MQLs or lifecycle-driven pipeline are part of your key results, the tracker can pull that signal too.

Is this secure enough to share with our CEO or board?

Starch lets you generate a shareable read-only dashboard link. One honest limit: Starch is not yet SOC 2 Type II certified, so if your company has a policy requiring that certification for tools that touch revenue data, check with your security team before connecting HubSpot and ad spend.

We already have a Slack integration for HubSpot notifications. Will this conflict?

No — the Starch automation posts to a channel you specify, completely independently of whatever HubSpot-native Slack notifications you have running. You can run them side by side or consolidate once you see which summary format your team actually reads.