Strategy & Planning

How to track okr progress weekly as Chief of Staff and Founder's Office

Strategy & PlanningFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

You're the one person who knows whether the company is actually on track — and every Monday you're pulling that picture together manually. Engineering's OKRs live in a Notion doc that was last edited six weeks ago. Sales KRs are theoretically in HubSpot but the reps update them inconsistently. Finance numbers to back up 'we hit 80% of revenue target' come from QuickBooks or a Stripe dashboard you have to log into separately. By the time you've chased down five functional leads on Slack, reconciled three spreadsheet versions, and formatted a progress summary for the CEO, it's Wednesday. The weekly OKR review meeting is in two days and the slide still says 'TBD' next to three key results.

Build this on Starch → See the apps used

Strategy & PlanningFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

Outcome

What you'll set up

A live OKR progress dashboard that pulls real numbers from HubSpot, Stripe, QuickBooks, and Notion automatically — so the Monday morning update is waiting for you, not the other way around

A weekly summary automation that drafts the exec-ready OKR status report with RAG status, owner, and delta from last week — sent to Slack before your 9am standup

A single place where every OKR owner's update, every action item from last week's review, and every supporting metric lives together — searchable, timestamped, and not in anyone's inbox

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

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) to power revenue and pipeline KRs. Starch syncs your QuickBooks data on a schedule (invoices, payments, journal entries) for any financial KRs tied to ARR or burn. Starch syncs your Notion data on a schedule so OKR documentation pages stay current. Starch syncs your Slack data on a schedule so the weekly summary can be posted automatically to the right channel. Google Sheets or Airtable can be connected from Starch's integration catalog and queried live if functional leads track their own KRs there.

Prompts to copy

Build me an OKR tracker that shows each objective, its key results, current progress as a percentage, RAG status, owner, and last-updated date. Pull deal data from HubSpot for the revenue KRs, and let me manually input or override progress for engineering and product OKRs that don't have a direct data feed.

Every Monday at 7am, generate a weekly OKR progress report: for each key result, show this week's number vs target, the delta from last week, and flag anything below 70% on pace as red. Post the summary to our #exec-team Slack channel and save it to the OKR knowledge base.

Create a page in the OKR knowledge base for each objective this quarter. Auto-populate each page with the key results, owner, progress history week-over-week, and any action items created during our weekly review meeting.

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

Walkthrough

Step-by-step

1 Connect HubSpot and QuickBooks — Starch syncs both on a schedule so deal pipeline, closed revenue, and financial actuals are always current without you logging into either platform.

2 Connect Notion — Starch syncs your Notion workspace so any OKR docs, wikis, or product roadmap pages your team maintains feed into the same dataset.

3 Connect Slack — Starch syncs your Slack workspace so automated summaries can be posted to #exec-team or any channel without you copying and pasting.

4 Tell Starch to build your OKR tracker app: describe each objective, the key results, who owns them, and which ones have a live data source vs. need manual input. Starch builds the app; you fill in the gaps once.

5 Set up the weekly automation: every Monday at 7am, Starch reads current progress across all connected KRs, calculates delta vs last week, assigns RAG status, and drafts the executive summary.

6 Use the Knowledge Management app to create an OKR archive — each weekly report is saved automatically so you can pull up exactly where Q3 stood in week 6 when a board member asks in week 11.

7 After your weekly OKR review meeting, any action items or decisions get captured and linked to the relevant key result in the knowledge base — no more hunting through Slack threads for what was decided.

8 For OKRs owned by functional leads (engineering sprint velocity, product feature shipped count), share a simple input form that writes directly into the Starch app — they enter their number once, it populates everywhere.

9 Set a secondary automation: if any KR drops below 60% on-pace with fewer than 6 weeks left in the quarter, Starch sends a direct Slack message to the OKR owner and you, asking for a written response plan by EOD Friday.

10 Before each board meeting, pull the quarter-to-date OKR history from the knowledge base and use it as source material to describe the progress narrative — Starch surfaces the right numbers so you're not rebuilding the story from scratch each time.

11 At quarter close, Starch generates a final OKR retrospective summary: which KRs hit, which missed, the week-by-week trend for each, and owner-level completion rates — ready to paste into the investor update or board deck.

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

Q3 2026 Week 7 OKR Review — Thursday Morning, 8:47am

Sample numbers from a real run

O1: Grow ARR to $8.2M — KR1: Close $680K new ARR in Q3	412,000
O1: KR2: Expand 12 existing accounts by 20%+	7
O2: Ship 3 core product features — KR1: Features shipped	2
O3: Hit 92% gross retention — KR1: Churned ARR this quarter	34,000
O4: Hire 8 net new headcount — KR1: Offers accepted	5

It's Thursday at 8:47am. The CEO has a board observer call at 10. You open Starch's OKR tracker — the Monday automation already ran, so the numbers are current as of this morning's HubSpot sync. O1 KR1 shows $412K closed against a $680K target with 6 weeks left in Q3: on pace at 61%, flagged red. The dashboard shows the delta from last week was only $28K, which is below the weekly run-rate you need. Starch already sent a Slack message to the VP of Sales on Monday asking for a response plan — she replied with a note about three deals slipping to Q4, which is now saved in the OKR knowledge base under O1. You open that note, copy the two-sentence summary, and paste it into your talking points for the observer call in under 90 seconds. O2 shows 2 of 3 features shipped — the third is in final QA. O3 gross retention is tracking well: $34K churned against a $180K threshold. O4 headcount is 5 of 8 offers accepted. The full summary — including week-over-week deltas, RAG statuses, and owner notes — was in #exec-team at 7:02am. You didn't write a word of it.

Measurement

How you'll know it's working

OKR on-pace rate: percentage of key results at or above expected progress at mid-quarter

Weekly update completion rate: how many OKR owners submitted their progress update by Monday close

Time-to-summary: how long from Monday morning to exec team having the OKR status in hand

Red KR response rate: percentage of flagged key results that have a documented recovery plan within 48 hours

Quarter-end hit rate: percentage of key results that closed at 70%+ of target

Comparison

What this replaces

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

Notion OKR template + manual Slack updates

Works for tracking structure but the numbers are always as stale as the last person who remembered to update them — Starch connects to the actual data sources so progress is current without anyone doing data entry.

Lattice or Workboard

Purpose-built OKR tools with check-in workflows, but they sit in yet another silo — your HubSpot deal data, QuickBooks actuals, and Notion docs don't feed them automatically, so you're still manually reconciling numbers.

Google Sheets OKR tracker

Maximum flexibility and zero cost, but the automation layer is either missing or built on fragile App Scripts that break when someone changes a column header — Starch gives you the same flexibility with a real data connection underneath.

BI tool (Looker, Tableau, Metabase)

Great for visualizing data you already have in a warehouse, but standing one up requires a data engineer and doesn't solve the problem of collecting qualitative OKR updates from functional leads or posting summaries to Slack.

On Starch RECOMMENDED

One platform — 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

Some of our OKRs don't have a data source — they're qualitative or owned by a functional lead who tracks them in their head. Can Starch still help?

Yes. The OKR tracker Starch builds can mix data-connected KRs (where progress is pulled automatically from HubSpot, Stripe, or QuickBooks) with manually updated KRs where an owner types in their progress. You can also set up a simple prompt-based check-in: Starch messages the owner on Slack each Monday asking for their number, and the response writes into the tracker. The automation handles the follow-up; you just see the result.

We use a mix of tools — some teams track work in Jira, others in Notion, others in Google Sheets. Can Starch pull from all of them?

Starch syncs your Notion data on a schedule. Jira and Google Sheets can be connected from Starch's integration catalog; the agent queries them live when your OKR app needs the data. If a team tracks something in a web-based tool that doesn't have a formal API, Starch can automate it through your browser — no API needed. In practice, most growth-stage companies can wire up the tools that matter for OKR tracking without hitting a wall.

Is Starch going to replace the conversation in our weekly OKR review? I still need the meeting.

No, and it shouldn't. The meeting is where judgment happens — why a KR is red, what the recovery plan is, whether the target was realistic. Starch handles the data collection and summary so that conversation starts with everyone already looking at the same current numbers instead of spending the first 20 minutes getting aligned on what they are.

How does the knowledge base stay up to date if my team keeps editing OKR docs in Notion?

Starch syncs your Notion data on a schedule, so changes your team makes in Notion flow into the Starch knowledge base automatically. The sync cadence means there's a small lag — not real-time instant — but for weekly OKR tracking that's not a meaningful constraint. If something changes mid-week that's urgent, you can trigger a manual refresh.

Is Starch SOC 2 certified? We'll get a question from our Head of Security.

Not yet — Starch is not currently SOC 2 Type II certified. That's an honest limit worth knowing before you route sensitive financial data through it. SOC 2 certification is on the roadmap. If your security review requires it today, that's a real constraint.

We're already paying for Lattice for performance reviews. Do we need both?

Depends on how you use Lattice. If OKR tracking in Lattice is working and your team actually updates it, you might not need Starch for this specific workflow. Where Starch adds something Lattice doesn't is the data connection layer — Starch can pull HubSpot deal data, QuickBooks actuals, or Notion docs into your OKR view automatically, and it can post summaries to Slack on a schedule. If you're manually bridging those gaps today, that's the problem Starch solves.