Captures the rituals
Every meeting in your cadence — daily huddle, weekly L10, monthly governance, quarterly rocks — captured as it happens. No re-typing. No back-fill.
Operating Model · any model. yours by default. any modelyours, supported2026
Most operating models live on slides. Relote runs them as code.
EOS, Scaling Up, Holacracy, OKRs, 4DX, or your own. Pick a starting point. We capture the rhythm from chat, hold it across weeks, and surface what drifts. The framework, installed — or your own framework, learned.
§ 01 · Pick a model
Click any tab. The page updates live.
A few starting points. Yours, fully supported.
EOS · Traction
EOS, run as code.
Six core components. Quarterly rocks. Weekly L10. V/TO at the heart of it. The Traction system, kept honest.
Cadence
Annual
V/TO refresh · 2-day offsite
Quarterly
Rocks set · scorecard reviewed
Weekly
L10 · 90 minutes · IDS
Daily
Issues raised in chat, not held
How Relote runs it
Relote captures every L10. Rocks tracked against weekly evidence. Issues from chat surface in the next L10’s IDS list. People analyzer signals live in the People page.
relote · L10 leadership · weekly
Scorecard ✓ Weekly revenue $148k → $155k on track ◐ NPS 42 → 46 on track ! Sales velocity 18d → 24d off Rock review (Q2) ✓ Ship payments v3 maya 45/60 days ◐ Hire 3 SDRs raj 1 of 3 ! Launch EU region kai drift 12d People analyzer ✓ All seats GWC-positive (this quarter) Issues (raised this week) • Onboarding doc out of date · @ada • Security review backlog · @jin • Q3 rock candidates · @ren To-dos from last L10 ✓ 6 of 7 closed · 1 carried (#payments-v3)
A live file in your repo. Switch models and the artifact swaps with it.
Scaleup · Verne Harnish
Scaling Up, the meeting cadence held.
OPSP. Daily Huddle. Weekly Tactical. Monthly Strategic. Quarterly Theme. The Rockefeller Habits, in motion.
Cadence
Annual
OPSP refresh · 3HAG roadmap
Quarterly
Theme set · KPIs reviewed
Monthly
Strategic · 1–2 days
Weekly
Tactical · 60–90 min
Daily
Huddle · 15 min · numbers
How Relote runs it
OPSP and 3HAG live as markdown in your repo. Daily huddle stand-ups read from chat. KPIs surface from your stack — not re-typed into a deck. Quarterly theme tracked against shipped work.
relote · daily huddle leadership · 11:30
Q2 Theme: "Land EU" day 47/90 · on theme KPIs (yesterday) pipeline $2.4M +3% trial → paid 18.2% flat bookings $48k +12% What’s up (24h) ada shipping payments-v3 staging by EOD jin blocked: legal review (escalating) raj hired SDR #2 · starts Mon kai EU vendor selected (legal in flight) Stuck • LIN-2980 still in review (3rd day)
A live file in your repo. Switch models and the artifact swaps with it.
Holacracy · HolacracyOne
Tensions processed. Roles, not titles.
Circles, roles, accountabilities. Tactical and governance meetings. Tensions surfaced and processed, not buried.
Cadence
Per-circle
Tactical · weekly · checklists & projects
Per-circle
Governance · monthly · roles & policies
As needed
Tensions logged the moment they surface
Continuous
Lead Link priorities updated in repo
How Relote runs it
Every tension raised in chat is captured as a structured proposal. Tactical and governance agendas write themselves. Roles, accountabilities, and policies live as markdown — searchable, diff-able, owned by you.
relote · governance product circle · monthly
Open tensions (5)
T-204 · designer · "Reviewer role unclear on docs PRs"
proposed: amend Doc-Editor accountability #3
author: @lin · raised 2026-04-19
T-211 · pm · "No role owns onboarding analytics"
proposed: new role "Onboarding Analyst"
author: @raj · raised 2026-04-22
T-219 · eng-lead · "Spec review SLA exceeded 4x"
proposed: amend policy 2.4 (timeboxed review)
Recently processed
T-198 ✓ adopted · "Privacy Lead reports up monthly"
T-201 ✓ tabled · returns next governance cycle A live file in your repo. Switch models and the artifact swaps with it.
OKRs · Doerr
OKRs that actually move.
Objectives. Key Results. Cadence. The Doerr framework — without quarterly amnesia.
Cadence
Quarterly
Set OKRs · top-down + bottom-up draft
Monthly
Confidence check · 1–5
Weekly
Progress evidence · linked to KRs
Daily
Commitments tagged to a KR
How Relote runs it
Every commitment in chat gets auto-tagged to its KR. Confidence drift surfaces before the monthly check-in. KRs without evidence in two weeks get flagged. Cascade across teams stays consistent — same KR worded the same in every doc.
relote · OKRs company · q2
OBJECTIVE 1 · Become the default for AI-native ops KR1 10 paying installs by EOQ 6/10 conf 7/10 ↑ KR2 $1M ARR run-rate $720k conf 6/10 → KR3 2 case studies published 1/2 conf 8/10 ↑ OBJECTIVE 2 · Ship a robust install pipeline KR1 Provision time < 90 min 84 min conf 9/10 ✓ KR2 Zero P0s in install (8 wks) 2 P0s conf 3/10 ↓ KR3 3 self-serve runbooks 2/3 conf 7/10 → ⚠ KR2.2 confidence dropped from 6 → 3 this week. Cause: incident INC-204 · post-mortem due Mon.
A live file in your repo. Switch models and the artifact swaps with it.
4DX · 4 Disciplines
WIGs. Lead measures. Cadence of accountability.
Wildly Important Goals. Lead and lag measures. Compelling scoreboard. Weekly accountability — every team, every week.
Cadence
Quarterly
1–2 WIGs set per team
Weekly
WIG session · 30 min · commit & report
Daily
Lead-measure activity logged
Continuous
Scoreboard visible to the team
How Relote runs it
Lead measures pulled from your tools, not self-reported. The scoreboard is a live page, not a screenshot. Weekly commitments captured from the WIG session — every team, every week. Misses surface immediately, not at quarter-end.
relote · wigs sales · weekly
WIG · "Close $400k new ARR by 2026-06-30"
lag: $182k of $400k 46% on pace
Lead measures (this week)
outbound demos booked 24/20 ✓ +20%
follow-ups < 24h 88%/95% ◐ -7%
decision-maker calls 11/15 ! -27%
Commitments (this week)
ada book 8 demos ✓ done
raj qualify 5 inbound ◐ 3 of 5
jin close globex ! pushed to next wk
kai revive 4 dormant deals ✓ done
Next session: Mon 09:30 · 30 min A live file in your repo. Switch models and the artifact swaps with it.
Yours · Custom · hybrid
Or whatever you actually run.
Most teams don’t run any model purely. Tell us your rituals — the meetings, the owners, the artifacts — and Relote learns them. New model? Bring it. We’ll hold it like the others.
Cadence
Define
Tell us your meetings, owners, artifacts
Capture
Relote captures from those meetings’ first day
Surface
Commitments and signal route to your channels
Iterate
AI officer tunes the rhythm with you
How Relote runs it
Your operating system gets the same first-class treatment as EOS or Scaleup. Markdown templates, one-line scripts to run them, and a fractional AIO who knows your rhythm. No retrofitting your company onto somebody else’s framework.
relote · custom rhythm acme · weekly
Rituals (your config) Mon 09:00 · Pulse · 20m · whole co Tue 10:00 · Customer review · 45m · ada, jin Wed 14:00 · Squad standup · 30m · per squad Thu 11:00 · 1:1 (rotating) · 30m · managers Fri 16:00 · Demo Friday · 30m · whole co Inputs ✓ Slack #pulse · #customers · #squads-* ✓ Granola · last 7 days ✓ Linear · in-progress Templates → pulse-summary.md (auto-drafted Sun 18:00) → customer-roundup.md → demo-friday.md AIO sync · Wed 14:00
A live file in your repo. Switch models and the artifact swaps with it.
§ 02 · How it holds
Same brain. Different rhythm. The model, lived.
A
B
Holds the commitments
Every promise, every rock, every WIG, every KR. Tagged to its source meeting. Surfaced when due. Re-raised when it drifts.
C
Reports the rhythm
The COO’s weekly view writes itself. Every model has its own one-page roll-up. Every roll-up traces back to evidence.
Pick the model. Relote holds it. Your team lives it.
§ 03 · Ownership
Your model. Your data. Your repo.
A
Markdown templates, in your git
Every L10 agenda, every OPSP, every X-matrix — committed to a repo on your server. Versioned. Diff-able. Yours.
B
Switch models without losing context
Adopt OKRs in Q1, layer 4DX on top in Q3. The history doesn’t reset. The repo carries.
C
Fractional AI officer included
Someone who knows your model and tunes Relote to your reality. Not a chatbot. A person on your team.
§ 04 · Begin
Stop running your operating model in a deck.
Pick the model that fits your team. We install it, run it, and sit alongside you while it takes hold.