Strategy & Planning

How to set quarterly okrs as CPG Founders

Strategy & PlanningFor CPG Founders3 apps11 steps~22 min to set up

Quarterly OKR planning for a CPG founder usually means a two-hour Sunday session with a blank Google Slides deck, a Notion doc nobody has looked at since last quarter, and a spreadsheet of last quarter's numbers that's already three weeks stale. You're trying to set meaningful targets for velocity at Target, deduction recovery rate, co-packer on-time delivery, and FBA in-stock rate — but the data lives in five different places and you haven't had time to pull it together. By the time you've set OKRs, you've already lost a day you needed for a broker call and a reformulation review.

Build this on Starch → See the apps used

Strategy & PlanningFor CPG Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A living OKR document built directly from your actual operational data — Stripe revenue, Plaid cash position, and Shopify sell-through — so targets are grounded in real numbers, not gut feel

A searchable knowledge base where each OKR links to the context behind it: co-packer performance notes, deduction dispute history, and last quarter's retrospective, all findable in seconds

A meeting cadence where your quarterly OKR kickoff and weekly check-ins produce structured notes, assigned action items, and a timestamped archive — so nothing falls through the cracks between you, your ops lead, and your broker

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

Knowledge Management Meeting Notes Task Manager

Data sources & config

Starch syncs your Stripe data on a schedule for revenue and subscription metrics; Starch syncs your Plaid data on a schedule for cash runway and burn context; connect Notion from Starch's integration catalog for last quarter's retrospective docs (the agent queries it live when the Knowledge Management app needs historical context); connect Google Sheets from Starch's integration catalog for existing velocity and deduction trackers. Meeting Notes uses Google Calendar (Starch syncs your Google Calendar data on a schedule) to automatically surface the right meeting context.

Prompts to copy

Create a Q3 2026 OKR document for a CPG brand. Objectives should cover: retail velocity growth at our top 3 grocery accounts, deduction recovery rate improvement, FBA in-stock rate, and gross margin per SKU. For each objective, create 2-3 measurable key results. Pull in context from our Q2 retrospective notes and flag any key result where we didn't have a baseline metric last quarter.

Transcribe and summarize today's Q3 OKR planning call with my ops lead and broker. Extract every committed action item, who owns it, and by when. Tag any items related to our Target reset or the reformulation timeline separately.

Create a recurring weekly OKR check-in task every Monday morning. For each objective, remind me to update the confidence score and note any blockers. Flag any key result that's more than 15% off pace.

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

Walkthrough

Step-by-step

1 Pull your Q2 actuals before you write a single OKR. Tell Starch: 'Summarize Q2 performance across Stripe revenue, Plaid ending cash balance, and our Shopify sell-through rate by SKU.' Use this as the opening section of your OKR doc so every target has a starting point.

2 Open Knowledge Management and tell Starch to build a Q3 OKR hub. Seed it with your Q2 retrospective from Notion (connected live from Starch's integration catalog), your current co-packer scorecard, and any broker feedback from the last quarter.

3 Draft your four to five objectives in natural language — don't worry about format. Tell Starch: 'Write objectives and key results for retail velocity, deduction recovery, FBA in-stock rate, and gross margin. Make each key result a number we can measure monthly.' Starch structures the doc.

4 For each key result, flag the data source. Tell Starch: 'For each KR in the OKR doc, note whether we track this in Stripe, Plaid, Shopify, or a manual spreadsheet, and flag any KR where we currently have no live data source.'

5 Run your OKR kickoff call with your ops lead and broker. Use Meeting Notes to capture the session — it transcribes in real time and generates a summary with key decisions and action items the moment the call ends.

6 Review the extracted action items from Meeting Notes. Anything with a deadline goes into Task Manager. Tell Starch: 'Create tasks from the Q3 OKR kickoff notes — assign each action item a P1–P3 priority and a due date based on what was discussed.'

7 Publish the OKR document to your shared Knowledge Management space. Tell Starch: 'Auto-categorize this under Strategy > Q3 2026 and link it to our Q2 retrospective. Tag it so any search for deduction recovery or FBA also surfaces this doc.'

8 Set your weekly check-in structure. Tell Starch: 'Create a recurring Monday task to update confidence scores on all Q3 KRs and note any blockers. Send me a Slack summary of any KR more than 15% off pace.' Starch connects to Slack from Starch's integration catalog and sends the digest automatically.

9 Before your first monthly business review, tell Starch: 'Pull the current status of all Q3 OKRs from the Knowledge Management hub, surface any action items from Meeting Notes that are overdue, and draft a one-page summary I can share with my investors.'

10 At mid-quarter, run a formal check-in call through Meeting Notes. Tell Starch to compare this quarter's discussion against the Q3 OKR kickoff transcript and flag any objectives where the team's focus has drifted from the original intent.

11 Close the quarter by telling Starch: 'Build a Q3 retrospective document in Knowledge Management. For each objective, show the target KR, the actual outcome, and pull in any relevant meeting notes or task completion data from the quarter.' This becomes the seed document for Q4 OKR planning.

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 OKR Planning Session — June 2026

Sample numbers from a real run

Objective 1: Retail velocity	0
KR1 — Increase units/store/week at Kroger from 4.2 to 6.0	0
KR2 — Reduce out-of-stocks at Target from 18% to 8%	0
Objective 2: Deduction recovery	0
KR1 — Dispute 100% of invalid deductions within 14 days of receipt	0
KR2 — Recover $28,000 in outstanding deduction claims by Sept 30	0
Objective 3: FBA in-stock rate	0
KR1 — Maintain 94%+ in-stock rate on top 5 ASINs through peak season	0
Objective 4: Gross margin per SKU	0
KR1 — Increase blended GM from 38% to 42% by reformulating SKU-004	0

Going into Q3 planning, the founder pulled Stripe data (synced automatically by Starch) showing $340K in Q2 revenue — up 22% QoQ — and Plaid data showing $180K ending cash, about 6 months of runway at current burn. Rather than starting from a blank slide, they told Starch: 'Build a Q3 OKR doc grounded in our Q2 actuals. Objectives should cover retail velocity at Kroger and Target, deduction recovery from our KeHE invoices, FBA in-stock rate across our top 5 ASINs, and gross margin improvement tied to the SKU-004 reformulation.' Starch drafted the full OKR structure in under three minutes, pulling in context from the Q2 retrospective stored in the Knowledge Management hub (originally captured from Notion via the live integration). The planning call with the ops lead and broker was transcribed by Meeting Notes, which flagged four action items: two deduction disputes to file with KeHE by June 15, a co-packer capacity confirmation for Q3 production runs, and a Target buyer follow-up on the fall reset. All four landed in Task Manager with P1 or P2 priority and owner assignments before the call recap was done.

Measurement

How you'll know it's working

Velocity (units per store per week) by retail account — Kroger, Target, Sprouts

Deduction recovery rate and dollars outstanding by distributor (UNFI, KeHE)

FBA in-stock rate by ASIN through peak season

Gross margin per SKU, tracked against reformulation and co-packer cost changes

OKR confidence score week-over-week (are you on pace or drifting?)

Comparison

What this replaces

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

Notion + Google Slides + manual data pull

You can build the same OKR doc by hand, but connecting it to live Stripe and Plaid data requires manual exports every time, and nothing automatically surfaces stale KRs or extracts action items from planning calls.

Lattice or Betterworks

Purpose-built OKR platforms with strong manager/direct report workflows, but they don't connect to your CPG operational data (velocity, deductions, FBA metrics), cost $8–$15 per seat per month, and assume a larger team structure than most CPG founder-operator setups.

Monday.com or Asana for goal tracking

Good for tracking task-level work against goals, but OKR structure requires configuration, there's no automatic connection to your financial or retail data, and meeting notes still live somewhere else entirely.

A spreadsheet and a shared Google Doc

Zero cost and fully flexible, but nothing detects when a KR goes stale, extracts action items from calls, or links historical context — and the friction of maintaining it means it gets updated once a quarter if you're lucky.

On Starch RECOMMENDED

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

Can Starch pull my actual retail velocity numbers into the OKR doc, or do I have to enter them manually?

It depends on where your velocity data lives. If you track it in Google Sheets, connect Google Sheets from Starch's integration catalog and the agent queries it live. If your broker or retailer portal has a web interface, Starch can automate that through your browser — no API needed. Plaid and Stripe data (cash position, DTC revenue) sync automatically on a schedule, so those numbers are always current without any manual export.

What happens to the OKR document between quarters — will it just get buried?

Knowledge Management keeps every OKR doc searchable and linked to the context around it. When you start Q4 planning, tell Starch to pull the Q3 retrospective and surface any KRs that carried over as unfinished. You can also search for any topic — 'deduction recovery' or 'reformulation' — and find the relevant OKR, meeting note, and action item history in one place.

Is Meeting Notes useful if my planning calls are internal — just me and one ops person?

Yes. The value isn't the transcript itself — it's the structured action item extraction and the searchable archive. When you're three months into the quarter and someone asks 'didn't we decide to file that KeHE dispute by June 15?' you can search the planning call and find the exact moment the decision was made, who said what, and what was agreed.

Does Starch store my financial data? I'm not SOC 2 certified so I need to be careful about vendor compliance too.

Starch is not SOC 2 Type II certified today. That's worth knowing before you connect sensitive financial accounts. For CPG founders who are working toward retail or foodservice partners with compliance requirements, it's a real consideration. The honest answer is that if SOC 2 Type II is a hard requirement right now, Starch isn't there yet — it's on the roadmap.

Can I use Starch to build a board-ready OKR presentation at the end of the quarter?

Presentation Agent — currently in development, request beta access to get notified when it launches — will build polished slide decks from a text description. Until then, you can tell Starch to draft a one-page OKR summary in Knowledge Management that you export to Google Slides manually. The data assembly and narrative is the hard part; the slide formatting is straightforward.

My OKRs have never survived contact with the actual quarter — is there something in Starch that keeps them alive?

Task Manager's recurring task structure and the weekly Slack digest are the accountability mechanism. You set a Monday check-in task that prompts you to update each KR's confidence score, and if a KR goes more than 15% off pace, Starch flags it proactively. It doesn't force discipline — but it makes the weekly check-in low-friction enough that you'll actually do it instead of waiting until the end-of-quarter scramble.