agentsUpdated·Falk Gottlob··updated ·5 min read

OKR Progress and Prediction Agent

Daily OKR tracking with outcome scoring. Weekly confidence predictions for OKR achievement. See what's on track and what needs intervention.

agentsstrategyokrs
Helpful?

OKR Progress and Prediction Agent
Try it live
See this agent running in the sandbox

Stream a simulated run, inspect the notifications it would send on Slack and email, and see exactly where it sits in the 7-stage PM OS flow. No password required.

The short version

The OKR Tracker agent gives you daily progress scoring and weekly confidence predictions for every key result. Daily at 4 PM, it pulls the latest metrics from Amplitude, Mixpanel, and Salesforce, scores each OKR against the trajectory needed, and flags anything off-track. Friday at 3 PM, it runs the confidence model: "you're at 65% of target with 4 weeks left, current velocity puts you at 82%, here's what would need to change to hit 100%." The point is to stop being surprised at the end of the quarter and catch slippage at week 5 when you can still course-correct. Set up the metrics feeds, then ask which Q2 OKR has the lowest confidence score today.

You set OKRs quarterly. You check them maybe twice. At the end of the quarter, you're surprised by the results.

The problem is visibility. If you're tracking manually (spreadsheets, quarterly reviews), you're always behind. You find out about slippage weeks after it happened. By then it's too late to course-correct.

The OKR Tracker agent maintains real-time visibility. Daily at 4 PM, it pulls the latest metrics for each OKR, scores progress, and flags anything off-track. Weekly it predicts: given current velocity, will you hit this OKR? If not, what do you need to do to get back on track?

How It Works

The agent connects to your metrics sources and runs continuous scoring:

Daily snapshot: Pulls the latest values for each OKR's key results. If you're tracking "reduce churn by 2%," it pulls yesterday's churn number. If you're tracking "increase enterprise ARR by $2M," it pulls recent close data from Salesforce.

Progress scoring: Compares current progress against the trajectory needed. At week 5 of a 13-week quarter, you should be roughly 38% of the way to your goal. If you're at 25%, you're off-track.

Weekly prediction: Using current velocity, the agent models: will you hit this OKR? How confident are you? What would need to change? "You're at 65% of target with 4 weeks left. If you maintain this velocity, you'll hit 82% of goal. To hit 100%, you need to accelerate 25%."

Red flags: Anything trending in the wrong direction, or confidence dropping below 50%, gets highlighted.

Data Sources and Setup

Prerequisites: Complete the Claude setup guide first. You'll need:

  • Metrics platform: Amplitude, Mixpanel, or custom dashboard that tracks your OKR metrics daily
  • CRM: For revenue-based OKRs (ARR, pipeline, win rate)
  • Analytics: For product-based OKRs (activation, retention, feature adoption)
  • Your OKR document: Goals, key results, target numbers, and what "success" means
  • Experiment tracking: To understand which initiatives are driving which metrics

Schedule: Daily at 4 PM (score tracking). Weekly Friday at 3 PM (confidence prediction).

The Claude Prompt

You are tracking our OKR progress and predicting achievement likelihood.

Here are our Q2 OKRs:
[OKR LIST: goals, key results, target numbers, definitions]

Here's the current metrics snapshot (as of today):
[METRICS: current values for each OKR, historical trend for past 4 weeks]

Here's the quarter timeline:
[TIMELINE: today's date, weeks elapsed, weeks remaining]

For weekly predictions, here are our recent initiatives:
[INITIATIVES: experiments, launches, changes that might affect metrics]

Please analyze and report:

1. **Progress Scorecard** (for daily reports)
   For each OKR:
   - Key result name
   - Target number
   - Current progress
   - % of goal achieved
   - On track / at risk / off track?
   - Trend (improving / stable / declining)?

2. **Detailed Progress Analysis** (for weekly reports)
   For each OKR:
   - Progress to date
   - Velocity (rate of progress per week)
   - Trajectory: if current velocity continues, what % will you achieve?
   - Confidence: % chance you hit 100% of goal
   - What would need to change to hit goal?

3. **At-Risk OKRs** (PRIORITY)
   - Which OKRs are below 50% confidence?
   - For each at-risk OKR:
     - Why is it slipping? (metric stalling, wrong initiative, external blocker?)
     - What's the gap between needed velocity and current velocity?
     - What could course-correct? (new initiative? reprioritization? better execution?)

4. **Off-Cycle Opportunities**
   - Are any OKRs likely to overachieve (>120%)?
   - Are there quick wins that could push at-risk OKRs over the line?
   - Should you reallocate effort from overachieving OKRs to at-risk ones?

5. **Initiative Impact**
   - Which initiatives are moving which OKRs?
   - Are your biggest efforts producing the biggest results?
   - Any disconnects (expected big impact but little metric movement)?

6. **Next Week Recommendations**
   - What should the team focus on?
   - For at-risk OKRs, what's the highest-leverage action?

Format clearly: I should be able to see at-a-glance which OKRs are on track and which need attention.

What You Get

Instead of quarterly surprises:

  • Real-time visibility: You know OKR status every day, not at the end of the quarter
  • Early warning: At-risk OKRs get flagged weeks early, when you can still course-correct
  • Confidence scoring: Not just "on track" but "82% likely to hit goal given current velocity"
  • Predictive: You see what's going to slip before it actually slips
  • Initiative ROI: You see which investments are moving the needle

Real outcomes:

  • You catch metric declines immediately instead of at end-of-quarter review
  • You course-correct mid-quarter instead of missing targets
  • You allocate effort to what actually matters based on real metrics, not guesses

For the full agent fleet and scheduling details, see Your AI Agent Fleet.

Share this post

Also on Medium

Full archive →

Frequently asked

How does an OKR tracking agent prevent end-of-quarter surprises?+

It pulls metrics daily and scores each key result against the trajectory needed. At week 5 of a 13-week quarter, you should be roughly 38% of the way to your goal. If you are at 25%, the agent flags it immediately. You find out about slippage at week 5 when you can still course-correct, not at week 13 when the quarter is over.

What is confidence scoring and how does the OKR agent calculate it?+

Confidence scoring is the predicted probability that you hit 100% of the OKR goal given current velocity. If you are at 65% of target with 4 weeks left and maintaining current pace, the agent models that you will hit 82% of goal, giving you roughly 60% confidence of hitting 100%. It also tells you what would need to change to close the gap: accelerate 25%, or reallocate effort from an overachieving OKR.

What data sources does the OKR tracker agent connect to?+

A metrics platform (Amplitude, Mixpanel, or a custom dashboard) that tracks your OKR metrics daily, a CRM for revenue-based OKRs like ARR and pipeline, analytics for product-based OKRs like activation and retention, your OKR document with goals, targets, and success definitions, and experiment tracking to understand which initiatives are driving which metrics.

How does the agent handle OKRs that are overachieving?+

It flags OKRs likely to exceed 120% of target as overachieving and asks whether effort should be reallocated to at-risk OKRs. The weekly prediction section includes a dedicated off-cycle opportunities review: which quick wins could push a lagging OKR over the line, and which overachievers have freed up capacity that could be redirected.

What does a weekly OKR prediction report look like?+

For each OKR: current progress, velocity (progress per week), trajectory (what percent you will hit if velocity holds), confidence score (probability of hitting 100%), and a specific recommended action for at-risk OKRs. The at-risk section lists every OKR below 50% confidence with a root-cause hypothesis (metric stalling, wrong initiative, external blocker) and a highest-leverage corrective action.

About the author

Falk Gottlob

Falk Gottlob

Product Executive · Founder, Falkster.AI

Thirty years shipping product at Microsoft Research, Adobe, Salesforce (Marketing Cloud / Quip / Slack), and several startups including one $6.5B exit and one acquired by Microsoft. Now CPO at Smartcat and founder of Falkster.AI, writing this notebook from the boardroom, not the keyboard.

Comments (0)

Sign in with LinkedIn to leave a comment.

Sign in with LinkedIn
  • Be the first to comment.

Keep Reading

Posts you might find interesting based on what you just read.