How to set quarterly okrs with AI

Strategy & Planning3 AI tools7 steps6 friction points

Setting quarterly OKRs means translating a company's strategy into a handful of measurable commitments that every team can actually work toward. For most operators, this happens four times a year in a sprint of leadership meetings, document drafts, and back-and-forth until something sticks. It sounds like a clean process on paper. In practice it involves synthesizing performance data from last quarter, aligning stakeholders with different priorities, and writing objectives that are ambitious but not detached from reality.

AI feels like a natural fit here because the hardest part of OKR setting isn't formatting — it's thinking through what to prioritize and how to word it. You're essentially asking: given what we know about our business, what should we commit to? That's a reasoning task, and LLMs are good reasoning partners. They can help you pressure-test whether a key result is actually measurable, suggest objective framings you hadn't considered, and give you a structured draft to react to instead of a blank document.

ChatGPT, Claude, and Gemini can all contribute meaningfully to this workflow today. Give them context about your company, last quarter's results, and current strategic priorities, and they'll generate solid draft OKRs you can iterate on. They can also challenge your logic ('is this KR actually in your control?'), help cascade company OKRs down to team level, and turn a rough leadership discussion into polished language. What they can't do is reach into your actual business data without you pasting it in first.

Strategy & Planning3 AI tools7 steps6 friction points
AI walkthrough

How to do it with AI today

A practical walkthrough using ChatGPT, Claude, and other off-the-shelf LLMs — what they're good at, what you'll have to do by hand.

Tools that work for this
ChatGPTClaudeGemini
Step-by-step
1 Pull your context together before opening any AI tool: last quarter's OKRs and how you performed against them, any key metrics (revenue, churn, pipeline), and 2-3 strategic priorities you've already identified for the coming quarter. The more specific this input, the less generic the output.
2 Open Claude or ChatGPT and paste your context in a single message. Include company stage, team size, last quarter's wins and misses, and the strategic bets you're considering. Ask the model to propose 3-5 draft Objectives with 2-3 Key Results each, formatted as a table.
3 Read the draft critically and ask follow-up questions in the same thread. Use prompts like 'Is KR2 under Objective 1 actually measurable with the data we'd have?' or 'Make Objective 3 more specific to a B2B SaaS company at $2M ARR.' Iterate until the structure feels right.
4 Copy the best draft into a shared doc (Google Docs or Notion) and run a leadership review. After the session, paste the discussion notes back into Claude and ask it to reconcile the draft with what the team agreed — this is faster than rewriting from scratch.
5 Once company-level OKRs are finalized, ask the model to cascade them to each team or function. Provide the team's specific responsibilities and constraints, and ask for 2-3 team-level OKRs that ladder into each company objective.
6 Use a final prompt pass to check internal consistency: paste all OKRs in one message and ask the model to identify overlaps, gaps, or key results that aren't measurable within the quarter. Fix what it flags.
7 Export the final OKR set to wherever your team tracks them — a doc, a spreadsheet, a project tool. That part is manual; the AI doesn't have write access to anything.
Prompts you can copy
We're a 12-person B2B SaaS company at $2.1M ARR. Last quarter we hit 94% of net new ARR target but missed NPS by 8 points. Our Q3 priorities are expansion revenue, reducing churn, and shipping a self-serve onboarding flow. Draft 4 company-level OKRs with 2-3 measurable KRs each.
Here are our draft company OKRs for Q3. We have a 4-person engineering team, a 2-person CS team, and 3 AEs. Cascade these into team-level OKRs for each function. Be specific about what each team would own.
Review these 5 OKRs and flag any key results that are not measurable within a single quarter, any that overlap, and any company priorities that don't have coverage. Suggest fixes.
Our leadership team debated these OKRs and landed on the following changes: [paste notes]. Revise the OKR set to reflect the decisions made. Keep the format consistent.
Rewrite these 3 objectives so they describe outcomes, not activities. The current versions sound like project plans. We want language that describes what will be true if we succeed.
Reality check

Where this gets hard

The walkthrough above works — until your numbers change, the LLM hallucinates, or you have to re-paste everything next month.

Every run starts from scratch — you paste last quarter's results manually because the LLM has no connection to your actual metrics, CRM, or financial data.
The model has no memory between sessions; the carefully structured OKR format you iterated on in week one won't be what you get when you return in week four for a mid-quarter check-in.
Output consistency drifts if multiple people on your team are prompting separately — you end up with three slightly different OKR frameworks that need to be reconciled by hand.
There's no live link to task or project data, so tracking whether OKRs are on course requires another manual paste — pulling status from Jira, Linear, or a spreadsheet each time you want a progress read.
Meeting decisions don't feed back automatically; after every leadership session you have to copy notes into the LLM context window and re-run the reconciliation prompt yourself.
Nothing is stored or versioned in the tool — the history of how your OKRs evolved, what was debated, and why decisions were made lives only in your chat history until you close the tab.

Tired of the friction?

Starch runs the whole workflow on live data — no copy-paste, no hallucinated numbers, no re-prompting next month.

See the Starch version →
Starch alternative

The same workflow on Starch

Starch is an agentic operating system — an agent builds and runs the persistent apps and automations your OKR workflow depends on, connected to your live business data, so you're not re-running the same prompt chain every quarter from a blank context window.

The Knowledge Management app gives your OKRs a permanent home: current objectives, prior quarters, decisions and rationale — all searchable by anyone on the team without digging through old docs or Slack threads.
Connect Notion, Linear, or Jira from Starch's integration catalog; the agent queries your actual project and task data live when you ask for a mid-quarter progress read, instead of requiring a manual export.
Meeting Notes transcribes your OKR planning sessions in real time, extracts key decisions and action items automatically, and archives them in searchable history — so 'what did we agree on in the Q3 kickoff?' has an actual answer.
Describe the OKR tracker you want in plain English — 'build me a view that shows each objective, its owner, the three KRs, current status, and a confidence score updated weekly' — and Starch builds it as a persistent app, not a one-off prompt.
Presentation Agent (currently in development — request beta access) will let you describe a quarterly OKR review deck and get a complete slide set with current data pulled in, without spending a Sunday night in Google Slides.
Automations run on a schedule: ask Starch to send a weekly Slack summary of OKR status pulled from your connected tools — task completion rates, pipeline movement, whatever your KRs actually track — so the team stays aligned without a manual reporting loop.
Get closed-beta access →
Toolkit

Starch apps for this workflow

Pick your role

See this workflow by operator

Run set quarterly okrs on Starch

You're on the list! We'll be in touch soon.