Strategy & Planning

How to track okr progress weekly as Small RevOps Teams

Strategy & PlanningFor Small RevOps Teams3 apps12 steps~24 min to set up

Every Monday you're rebuilding the OKR status update by hand. You pull pipeline numbers from HubSpot, paste quota attainment from a Sheets model the CRO last touched six weeks ago, check Apollo for sequence activity, and then format all of it into a slide or a Slack message before the 9am forecast call. The actual tracking lives in four places that don't talk to each other. When a rep asks 'are we on track for the quarter?' you know the answer is somewhere in those four places, but surfacing it takes 45 minutes you don't have. Half your Monday morning is data assembly, not analysis.

Build this on Starch → See the apps used

Strategy & PlanningFor Small RevOps Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A weekly OKR progress app that pulls live pipeline from HubSpot, sequence activity from Apollo, and revenue data from Stripe into one view — so Monday's status update takes minutes, not a morning

An auto-generated summary of where each key result stands against target, with a flag on any KR that's more than 15% off pace, delivered to Slack before the forecast call

A searchable history of every weekly OKR snapshot so when the CRO asks 'when did pipeline start slipping?' you can show the exact week, not guess

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 Knowledge Management Task Manager

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners — and syncs your Apollo contacts, accounts, and sequence data on a schedule. Connect Stripe from Starch's integration catalog; the agent queries revenue and subscription data live when the app runs. Slack is connected from Starch's integration catalog so the agent can post the weekly summary. Knowledge Management stores the historical snapshots inside Starch. Task Manager surfaces the exception alerts inside Starch.

Prompts to copy

Build me a weekly OKR tracker that pulls open pipeline and stage-weighted deal value from HubSpot, total new contacts enrolled in sequences from Apollo, and MRR and new customer count from Stripe. For each key result, show current value, target, percent to goal, and a red/yellow/green status. Refresh every Monday at 7am and post a summary to the #revops Slack channel.

Every week after the OKR app runs, save a snapshot of each key result's status to a Knowledge Management page called 'OKR Weekly Log — Q[quarter] [year]'. Tag each entry with the week date so I can search by week and see how any KR has trended over the quarter.

When any key result drops below 70% of its weekly pace target, create a P1 task in Task Manager assigned to me with the KR name, current value, gap to target, and a link to the relevant HubSpot view.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, stages, owners, and close dates on a schedule. This is the pipeline foundation for every KR tied to revenue or new business.

2 Connect Apollo — Starch syncs your contacts, accounts, and sequence enrollment data on a schedule. If a KR is 'X demos booked from outbound,' this is where that number lives.

3 Connect Stripe from Starch's integration catalog so the agent can query MRR, new customers, and churn live when the weekly app runs.

4 Connect Slack from Starch's integration catalog so the OKR summary can post to #revops or a private channel before Monday's forecast call.

5 Describe your OKR structure to Starch in plain language: 'We have four key results this quarter — pipeline created, demos booked, deals closed, and MRR added. Here are the Q2 targets for each.' Starch builds the tracking logic from that description.

6 Tell Starch what 'on pace' means for your team: 'We're 8 weeks into a 13-week quarter. Any KR below 61% of target is yellow; below 50% is red.' The app applies that logic automatically each week.

7 Set the weekly automation to run Monday at 7am. It pulls fresh HubSpot pipeline, Apollo sequence activity, and Stripe revenue, calculates percent-to-goal for each KR, and posts the formatted summary to Slack.

8 Tell Starch to save each week's snapshot to a Knowledge Management page. Prompt: 'After the OKR app runs each Monday, append a dated entry to the Q2 OKR Log page showing each KR's name, current value, target, and status.' Now you have a searchable quarter-long audit trail.

9 Set up the exception rule in Task Manager: any KR that's more than 15% behind weekly pace creates a P1 task with the gap, the current number, and a link to the underlying HubSpot view so you can investigate without clicking around.

10 Before the quarterly business review, describe the slide you need: 'Build a summary of Q2 OKR performance — one slide per key result, showing weekly trend, final attainment, and a one-sentence annotation on what drove the result.' Starch assembles it from the log data in Knowledge Management.

11 If a KR owner asks 'what was our pipeline number in week 4?' you search the Knowledge Management log — it returns the exact snapshot, not a vague memory.

12 At the end of each quarter, tell Starch to archive the OKR log and scaffold the next quarter's tracker: 'Create a Q3 OKR tracking app with these four key results and these targets.' The structure carries over; you just update the numbers.

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 OKR Check-In — Week 7 of 13

Sample numbers from a real run

Pipeline Created (target: $2.4M)	1,380,000
Demos Booked from Outbound (target: 120)	71
Deals Closed (target: 28)	18
Net New MRR (target: $85,000)	52,000

It's Monday at 7:05am. The OKR app already ran. In Slack: Pipeline Created is at $1.38M against a $2.4M quarterly target — 57.5% with 53% of the quarter gone, yellow. Demos Booked is at 71 of 120 — 59%, also yellow, and the Apollo sync shows sequence reply rate dropped from 4.2% to 2.8% in week 6, which explains it. Deals Closed is at 18 of 28 — 64%, green, tracking ahead of the linear pace. Net New MRR is at $52K of $85K — 61%, green but thin. Task Manager has one P1 sitting there: 'Pipeline Created is 15% below weekly pace — current $1.38M, need $1.47M by EOW to stay on track — HubSpot stage 3+ view linked.' You walk into the 9am forecast call with all four numbers, the trend, and a specific action item. Nobody had to ask you to pull anything.

Measurement

How you'll know it's working

Percent-to-goal for each key result at the current week of the quarter (not just end-of-quarter)

Weekly pipeline created vs. linear pace target (HubSpot deals by create date)

Outbound sequence-to-demo conversion rate (Apollo sequences → HubSpot meetings booked)

Net new MRR added in the quarter (Stripe new subscriptions minus churned MRR)

KR exception rate — how many key results are in red or yellow status in a given week, tracked over the quarter as an early warning signal

Comparison

What this replaces

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

Notion + manual Slack posts

Notion is fine for storing the OKR doc, but someone still has to update the numbers manually each Monday — there's no sync from HubSpot or Apollo, so it's only as fresh as the last time a human touched it.

HubSpot Goals / Dashboards

HubSpot can track pipeline-specific KRs well, but the moment you have a KR that spans Apollo outbound, Stripe MRR, and HubSpot pipeline in a single view, you're back to exporting and stitching in Sheets.

Google Sheets with IMPORTDATA or manual entry

Sheets is where most small RevOps teams live today — flexible but entirely manual to update, and there's no alerting logic or Slack push unless someone builds it with Apps Script, which becomes its own maintenance burden.

Salesforce / CRM-native reporting

If your OKRs are purely pipeline metrics, Salesforce reports work — but Salesforce doesn't know about Apollo sequences, Stripe MRR, or anything outside the CRM, and building cross-system OKR views in SFDC typically requires a BI tool or a lot of custom objects.

On Starch RECOMMENDED

One platform — sales agent crm, knowledge management, task manager 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 from Notion and write updates back?

Starch syncs your Notion pages and databases on a schedule, so it can read your existing OKR structure. Writing back to Notion is possible through Starch's integration catalog. That said, most teams find it simpler to let Starch own the weekly snapshot in Knowledge Management and keep Notion as the 'published' view for the broader team — you post the Slack summary either way.

Our pipeline KRs live in Salesforce, not HubSpot. Does Starch work with Salesforce?

Yes — connect Salesforce from Starch's integration catalog; the agent queries your pipeline, opportunities, and stage data live when the app runs. Starch syncs HubSpot directly on a schedule, which gives slightly deeper real-time refresh, but Salesforce through the integration catalog handles the standard deal and pipeline queries you'd need for OKR tracking without any issues.

What if a KR is qualitative — like 'launch new territory model by end of quarter'? Can Starch track that?

Tell Starch how you want to track it: 'KR4 is binary — it's either done or not. Mark it green if there's a Notion page tagged territory-model published before June 30, otherwise red.' Starch can combine a Notion sync check with a manual override you control. Qualitative KRs are just a different input, not an unsupported case.

Is the historical OKR log actually searchable, or is it just a list of pages?

The Knowledge Management app has AI-powered search across all stored pages. You can ask 'what was our demo-booked number in week 4 of Q2?' and it returns the relevant snapshot entry, not a list of pages to click through. That's the point of storing the weekly snapshots there rather than in a folder.

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

Not yet — Starch is not SOC 2 Type II certified today. That's an honest answer. If your company has a hard compliance requirement before connecting CRM data, you'll want to flag that. SOC 2 is on the roadmap; it's just not done yet.

We don't want to rebuild this from scratch every quarter. Can the OKR tracker carry over?

Yes. Tell Starch: 'Archive the Q2 OKR log and create a Q3 tracker with these four key results and updated targets.' The structure — the Slack automation, the Knowledge Management log, the Task Manager exception rule — carries over. You update the target numbers and the quarter label. That's it.