Strategy & Planning

How to track okr progress weekly as CPG Founders

Strategy & PlanningFor CPG Founders3 apps10 steps~20 min to set up

Your OKRs probably live in a Notion doc someone updated in January and hasn't touched since. Or a Google Sheet with color-coded cells that made sense when you built it but now requires 20 minutes of archaeology to understand what's on track. As a CPG founder, your Q-level objectives span co-packer fill rates, retail velocity, DTC conversion, and cash runway — not the kind of thing that maps cleanly onto generic goal-tracking templates. You know a key result is slipping two weeks before the quarter ends, but only because you happened to open the right tab. Nobody on your three-person team has a 'review OKRs' task because it always falls through as a founder job.

Build this on Starch → See the apps used

Strategy & PlanningFor CPG Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A weekly OKR review cadence where every key result has a current status, a responsible owner, and the last update — pulled from a single source of truth instead of five disconnected docs

A Task Manager that converts stale or at-risk key results into assigned action items automatically, so nothing falls through between Monday check-ins

A searchable archive of every weekly OKR review and the decisions made in it, so when your ops manager asks why you deprioritized the foodservice channel in Q2, the answer is findable in 30 seconds

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

Task Manager Knowledge Management Meeting Notes

Data sources & config

Task Manager (currently in development — request beta access) tracks OKR key results as prioritized tasks with due dates and P1–P4 flags. Knowledge Management connects to Notion via Starch's scheduled sync so existing strategy docs are searchable from day one; new OKR review summaries are written directly into Starch's wiki. Meeting Notes captures your Monday OKR standup via real-time transcription — no separate integration required. Google Calendar connects via Starch's scheduled sync to surface your Monday recurring block automatically.

Prompts to copy

Build me a weekly OKR tracker for a CPG brand. Key results this quarter include: gross margin above 42%, retail velocity of 1.8 units/store/week across 200 doors, DTC subscription retention above 68%, and co-packer on-time delivery above 90%. Show each KR with owner, current value, target, status (on track / at risk / off track), and last updated date.

Every Monday at 8am, remind me to update each key result and flag any that haven't been touched in more than 7 days as stale. Create a P1 task for any KR marked off track.

Create a Knowledge Management page called 'Q3 2026 OKRs' and write a structured summary of this week's OKR review: what's on track, what's at risk, decisions made, and owner accountability updates. Link it to our team wiki under Strategy > OKR Archive.

Transcribe our weekly Monday OKR review call and extract all action items with owners and due dates. Save the transcript and summary to the OKR Archive in Knowledge Management.

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

Walkthrough

Step-by-step

1 Open Starch and describe your quarter: type in your 3–4 objectives and each key result with owner, current baseline, and target. Starch builds a structured OKR tracker customized to your CPG brand — co-packer performance, retail velocity, cash runway, DTC retention, whatever your quarter actually looks like.

2 Connect Google Calendar via Starch's scheduled sync. Starch reads your Monday standup block and uses it to anchor weekly review reminders — no manual scheduling required.

3 Set up a Monday 8am automation: 'Every Monday, show me each key result's current status, flag anything not updated in 7 days as stale, and create a P1 task for any KR marked off track.' Starch queues the reminders and task generation automatically.

4 Before your Monday OKR review, update each key result's current value directly in the tracker — fill rate from your co-packer's portal (Starch can automate that read through browser automation if they have a web dashboard), retail velocity from your distributor reports, DTC retention from Shopify or your ESP.

5 During the review call, run Meeting Notes. It transcribes the call in real time, captures decisions ('we're deprioritizing foodservice this quarter to protect margin'), and pulls out action items with owners.

6 After the call, Starch generates a structured summary: on-track KRs, at-risk KRs with root cause, decisions made, and owners for each action item. Review it, make any edits, and save it.

7 Knowledge Management writes that summary into your team wiki under Strategy > OKR Archive — timestamped and tagged to the current quarter. Every future review adds a new entry to the same thread.

8 Any action item flagged in Meeting Notes that doesn't have a due date gets automatically added to Task Manager as a P2 or P3 item, assigned to the right person, and surfaced in the following Monday's review.

9 Mid-week, if a KR goes off track — say your co-packer misses two consecutive production runs and on-time delivery drops to 74% — Starch escalates it to P1 in Task Manager and adds a Slack notification (connect Slack from Starch's integration catalog; the agent queries it live) so you catch it before the week-end review.

10 At quarter close, ask Starch: 'Summarize all 13 weekly OKR reviews from Q3 2026. Which key results were chronically at risk? Which owners had the most overdue action items? What decisions did we make about the foodservice channel?' Knowledge Management surfaces the full archive and Starch writes the retrospective.

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 6 OKR Review — August 11, 2026

Sample numbers from a real run

Gross margin (target: 42%)	39
Retail velocity — units/store/week (target: 1.8)	1.6
DTC subscription retention (target: 68%)	71
Co-packer on-time delivery (target: 90%)	83

Going into Week 6, two of four key results are off track. Gross margin is sitting at 39% — 3 points below target — because a raw materials price increase in July wasn't fully offset by the price adjustment that went live August 1. Retail velocity is at 1.6 units/store/week across 187 doors, partly because the new Sprouts set didn't ship until Week 4 and those doors are still ramping. DTC retention is the bright spot at 71%, above the 68% target. Co-packer on-time delivery dropped to 83% after two missed production windows in Week 5. The Monday review call — transcribed by Meeting Notes — surfaces three action items: (1) ops lead to reforecast raw material costs and model two margin scenarios by Friday, P1; (2) sales lead to follow up with Sprouts buyer on velocity data from new doors, P2 due Thursday; (3) founder to call co-packer ops director about root cause of Week 5 misses before Wednesday. All three are written into Task Manager with due dates. The full summary — including the decision to hold pricing flat through September despite margin pressure — is saved to Knowledge Management under Strategy > OKR Archive > Q3 2026 > Week 6. Six weeks from now, when the board asks why margin recovery took a full quarter, the answer is one search away.

Measurement

How you'll know it's working

Retail velocity (units/store/week) by account and SKU

Gross margin % — tracked weekly against target, sensitive to input cost swings

Co-packer on-time delivery rate — anything below 88% starts affecting replenishment

DTC subscription retention rate — leading indicator of LTV and ad efficiency

OKR completion rate quarter-over-quarter — % of key results hit vs. set

Comparison

What this replaces

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

Notion OKR template

Flexible enough to start, but it doesn't create tasks from at-risk KRs, doesn't capture meeting decisions, and becomes a doc nobody updates after Week 3 unless someone owns the upkeep.

Lattice or Ally.io

Built for HR-led OKR programs at 50+ person companies; overkill for a founder-led team of 3–5 and priced accordingly — typically $8–12/user/month with an annual contract minimum.

Google Sheets + manual tracking

Free and fast to start, but connecting it to your actual operational data (co-packer delivery, retail velocity, DTC metrics) requires manual copy-paste every week, which is exactly how KR reviews get skipped.

Linear or Asana

Good task trackers, but they're not purpose-built for OKR structure — mapping key results to projects and checking them weekly requires workarounds that break down over a quarter.

On Starch RECOMMENDED

One platform — task manager, knowledge management, meeting notes 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

Can Starch pull my retail velocity or co-packer data in automatically so I'm not updating KRs by hand?

It depends on where that data lives. If your distributor or co-packer has a web portal you log into, Starch can automate reading from it through browser automation — no API needed. If your velocity data is in a spreadsheet or a system like SPINS, connect it from Starch's integration catalog and the agent queries it live. For your DTC data in Shopify, same approach — connect it from the catalog. You'd describe the automation: 'Every Monday morning, pull this week's retail velocity from my SPINS portal and update the velocity KR in my OKR tracker.' The goal is to reduce manual entry to zero, but the specific wiring depends on your stack.

Task Manager and Knowledge Management are listed as in development. What can I use right now?

Honest answer: Task Manager and Presentation Agent are currently in development — request beta access on the Starch site to get notified when they launch. While they're in beta, you can use Starch's natural-language app builder to describe a custom OKR tracking surface and task list — 'build me a task tracker with P1–P4 priority, due dates, and owner fields' — and Starch will assemble it. Meeting Notes captures your OKR review calls today. Knowledge Management (the Notion-connected wiki) is live and available now.

We use Notion for everything. Does Starch replace it or connect to it?

Starch syncs your Notion data on a schedule — pages, databases, users — so your existing Notion docs are searchable from inside Starch. You don't have to migrate anything. The typical pattern for CPG founders is: keep Notion as the existing archive, use Starch's Knowledge Management to surface it intelligently and write new OKR review summaries into a structured wiki that auto-categorizes and flags stale content.

Is Starch SOC 2 Type II certified? We're starting to share sensitive financial and operational data.

Not yet. Starch is not SOC 2 Type II certified today. If that's a hard requirement for your board or a retail partner's vendor assessment, you'll want to know that upfront. It's on the roadmap. For most early-stage CPG founders, the practical question is whether you're comfortable connecting your Stripe, Plaid, or QuickBooks data — same question you'd ask of any SaaS tool at this stage.

Can Starch automatically Slack the team our OKR status every Monday?

Yes. Connect Slack from Starch's integration catalog — the agent queries it live. Then describe the automation: 'Every Monday at 9am, post a summary of this week's OKR status to #leadership — include each key result, its current value vs. target, and any items marked at-risk or off-track.' Starch builds the automation and runs it on schedule.

What happens to my OKR history if a quarter goes badly and I want to do a post-mortem?

Every weekly review summary saved to Knowledge Management is timestamped, tagged to the quarter, and fully searchable. You can ask Starch: 'What were the top three reasons our co-packer delivery KR was off track in Q3?' and it searches across all 13 weeks of meeting notes, OKR updates, and decision logs to give you an actual answer — not a link to the right doc, the answer itself. That's the point of archiving decisions in a searchable wiki rather than a folder of PDFs.