You'd think this needs a 2-hour ops review every Friday — Tycoon Agent has it ready every Monday with the actual numbers, not vibes.
The short answer
Tycoon Agent answers "how are OKRs tracking" by reading your Notion OKR doc, joining each Key Result to live data, and projecting end-of-quarter outcome. She fetches the OKR from your Notion workspace, parses each KR (numeric target, deadline), routes the metric source to the right system — MRR to Stripe, signups to PostHog, organic traffic to GA4, NPS to your Typeform — and computes "actual vs pace." An OKR pacing at 1.0 is on track; <0.85 is at risk; <0.6 is at-risk-of-miss. For every yellow or red KR she proposes one specific fix grounded in your data. Output is a Lark message with a stoplight per KR, the projected end-of-quarter number, and the next action for each at-risk item. Updates every Monday automatically; on-demand any other time.
How Tycoon Agent actually does it
- Pull and parse OKRs
Fetch the current quarter OKR page from Notion. Parse each KR for: target metric, target value, deadline, owner.
Notion
- Wire each KR to live data
Route to source: MRR→Stripe, signups→PostHog, organic clicks→GSC, NPS→Typeform, support CSAT→Zendesk. Pull current actual + 4-week trend.
StripePostHogGSCZendesk
- Compute pace and projection
Pace = (actual / target) × (days_elapsed / total_days)⁻¹. Project EOQ outcome by linear extrapolation, flag if trend is non-linear (S-curve, plateau).
- Stoplight + diagnose
Green ≥0.95, Yellow 0.6-0.95, Red <0.6. For each yellow/red, identify the bottleneck: not enough top-of-funnel? Conversion dropped? Churn spiked?
- Recommend one fix per at-risk KR
Specific, actionable, owned. e.g. "Q2 MRR pacing 0.71. Bottleneck = trial→paid down 22%. Fix = ship the 3-step onboarding revamp by next Friday."
Lark
What it looks like in chat
YouHow are this quarter's OKRs tracking?
Tycoon AgentPulled Q2 OKRs from Notion. 47 days elapsed of 91. Snapshot: 🟢 **KR1 — $200K MRR by EOQ.** At $148K, pacing 1.04. Projecting $208K. Safe. 🟡 **KR2 — 5,000 paying users.** At 2,640, pacing 0.81. Projecting 4,520 — 480 short. Bottleneck: signup→paid is 11.2% (was 14.1% in Q1). Fix: ship the pricing page A/B (already in your Linear backlog, owner @rin). Budget 1 sprint. 🔴 **KR3 — Launch Enterprise tier.** Spec done, zero engineering started. 44 days left, ~30 days of work. Won't ship at current rate. Fix: cut scope to MVP (no SSO, no audit log) — shippable in 18 days. Or push to Q3 and replace this KR with something tractable. 🟢 **KR4 — NPS ≥ 50.** At 54. Holding. Two at-risk. Want me to draft the cut-scope spec for KR3 or just push it to Q3?
What you get back
A weekly Lark message with stoplight rating, current actual, projected EOQ outcome, bottleneck diagnosis, and one specific fix per at-risk KR.
Cadence: Weekly Monday 9am, plus on-demand and event-driven (any KR drops > 10% week-over-week).