B Babelio Playbook 13 / 24
Refresh: quarterly EN · RU
Operating System · Artifact 13

Operating Cadence

The meeting rhythm for a tiny pre-seed team, with agendas pre-baked. At this stage there is exactly one drumbeat that matters: the weekly validation review where we read the three numbers that decide whether Babelio is real — sessions/user/week (North Star), loop factor K, and field-work progress.

Core rhythm
Weekly
North Star
Sessions/user/wk
Make-or-break
K≥0.3
No-meeting day
Wed
PurposeA meeting rhythm with agendas pre-baked, so that as the team grows from 2 to 5, no conversation has to be reinvented and the validation numbers get read on a fixed beat.
Bar for goodA new exec on day one knows where every conversation happens — and could run the Monday validation review from this page without asking the founder.
Right-sizingWe are pre-seed with 2 people (founder + audio/OS engineer — see 11-hiring-plan.html). Most rows below are two people in a 30-minute call, not a board ceremony. The all-hands and MBR scale up as we hire; they exist now as a 5-minute version so the muscle is built early.

The cadence grid · five rhythms

Five rhythms, from a daily 5-minute pulse to annual planning. The weekly validation review is the load-bearing one while we are pre-PMF — everything else feeds it or reads off it. Each links to a pre-baked agenda below.

Rhythm When Duration Who attends Agenda
Daily async pulse Daily, 10:00, written 5 min Whole team (2→5) → template
Weekly validation review load-bearing Mon, 09:30 45 min Founder + engineer (+ growth lead later) → template
Bi-weekly all-hands Every 2nd Fri, 15:00 30 min Whole team + advisors invited → template
Monthly business review 1st Mon of month, 14:00 90 min Whole team (founder leads) → template
Quarterly OKR refresh Last week of quarter ½ day Whole team + lead advisor → template
Annual planning Once / year, Dec 2 days, offsite Whole team + advisors extends OKR ↗
Monthly retro Last Fri of month, 16:00 45 min Whole team, no advisors format ↓
Read this grid as a hierarchy The daily pulse feeds the weekly review; the weekly numbers roll up into the monthly business review; the MBR trend sets up the quarterly OKR refresh; the quarter feeds annual planning. A decision can be made at any level, but it must be logged the same way (see the decision-log flow below) and it routes to an owner per 15-decisions-raci.html.

Five agenda templates

Each meeting has a fixed agenda. Run it from top to bottom; the minute-budget is a guide, not a cage. Every template ends in a defined output that gets written down — meetings without an artifact decay.

Daily async pulse

5 minwritten, Slack/threadwhole team
  1. YesterdayOne line: what shipped / what I learned (interviews done, installs onboarded).async
  2. TodayThe single most important thing — tied to this week's validation goal.async
  3. Blocked?If yes, @-tag the unblocker. A blocker open >24h auto-escalates to the weekly review.async
OutputA written thread, no call. No status meetings — if it can be a message, it is a message.

Weekly validation review

45 minMon 09:30founder + engineer
  1. North Star read — sessions / user / weekThe one number. Is the immersion learner coming back to subtitle/mine daily? Trend vs last 4 weeks. Source: usage ledger (14-kpi-dashboard.html).8 min
  2. Loop factor K(shares per activated user) × (installs per shared card). Is the sentence-mining-card loop alive? K≥0.3 = prove it; K<0.15 = demote to paid CAC (growth.md §3). The make-or-break number.8 min
  3. Field-work progressAgainst the 4-week validation plan (growth.md §7 / 17-90-day-plan.html): interviews done this week, paying/LOI count, activation rate, install-completion rate. Read the kill-criteria out loud.12 min
  4. Engineering against the wedgeNative-desktop capture / subtitle-default progress. Anything blocking the next learner cohort getting hands on it?8 min
  5. Decisions & next-week commitLog every decision (flow below). Each person names their one most-important thing for the week.9 min
OutputThree numbers logged (NSM, K, field-work), any kill-criterion that fired flagged to the risk register (16-risk-register.html), and a one-line per-person commit.

Bi-weekly all-hands

30 minevery 2nd Fri 15:00whole team + advisors
  1. Where we are vs the wedge thesisOne slide: are immersion learners pulling? NSM + K trend, plain language.8 min
  2. Wins & learningsBest customer quote of the fortnight + the most surprising thing we learned (Mom-Test verbatim welcome).7 min
  3. What's nextThe next two weeks in one sentence per person, tied to the 90-day plan.7 min
  4. Open floor / AMAAnything. Advisors get the floor first. Questions collected async beforehand.8 min
OutputA short written recap posted async so anyone (advisor, future hire) can catch up in 2 minutes. This recap is the seed of the monthly investor update (18-investor-update-m1.html).

Monthly business review

90 min1st Mon 14:00whole team
  1. KPI dashboard read, top to bottomAll 15-20 metrics from 14-kpi-dashboard.html: acquisition → activation → retention → revenue → efficiency → AI cost. Flag every red-line crossed.25 min
  2. Cohort & retention curveD1 / D7 / D30 against target (08-retention.html: aim D30 12%+). Is the aha-moment (first shared card) firing?15 min
  3. Cash & runwayBurn vs plan, runway months, next hire trigger status (10-financial-model.html). Are we on the fundable curve or the bootstrap curve?15 min
  4. OKR mid-flight checkEach KR rated green/yellow/red against its checkpoint date (12-okrs.html). Reds get a recovery owner.15 min
  5. Top-3 decisions / debateThe biggest open questions of the month, with a forcing function: a decision is made today, logged, with an owner — or it is explicitly parked with a re-open date.20 min
OutputA one-page MBR memo: the dashboard snapshot, the cash line, OKR rag-status, and the decisions made. This memo is forwarded ~as-is as the monthly investor update.

Quarterly OKR refresh

½ daylast week of quarterwhole team + lead advisor
  1. Score the quarter that endedGrade every KR 0.0–1.0 (12-okrs.html). Honest, not aspirational. What did the number actually say?45 min
  2. Re-read the strategy memoDoes the wedge (00-strategy-memo.html) still hold given the quarter's data? Has any kill-criterion fired? Pivot / persevere call.45 min
  3. Set 3-4 objectives for next quarterEach objective with 3 measurable KRs, a baseline, a target, an owner, and a mid-quarter checkpoint date. Outcomes, never activities.60 min
  4. Defend each objective in one paragraph"We picked this OVER X because Y." If you can't defend it, cut it. Re-balance the experiment backlog (09-experiment-backlog.html) to fund the objectives.30 min
OutputNext quarter's OKRs committed in 12-okrs.html with owners and checkpoints, plus a pivot/persevere decision logged. Annual planning is this same template run over two days with a 12-month horizon.

Decision-log flow

Any meeting can produce a decision. The rule is: a decision that isn't logged didn't happen. This is the four-step path from "we decided" to a row in the log — so the same debate never gets re-run.

Step 1 · in the meeting
Name it

Someone says out loud: "Decision:" and states it in one sentence. Reversible or not? Who's the DRI? If nobody is accountable, it's not a decision yet.

Step 2 · same day
Log it

Append a row to the decision log in 15-decisions-raci.html using the template below. Append-only — never edit a past row, supersede it.

Step 3 · route
Match to RACI

Check the decision-type against the RACI matrix. Was the right person Accountable? If a recurring type keeps reaching the founder, push it down to a documented owner.

Step 4 · close loop
Tripwire?

If the decision was forced by a crossed red-line, link it to the risk register tripwire (16-risk-register.html) so the cause is traceable, not just the fix.

Decision-log row template (paste into 15-decisions-raci.html)
DateYYYY-MM-DD — when the call was made
DecisionOne sentence, in plain language
Owner (DRI)The one accountable person
RationaleWhy this OVER the alternative — the part future-us forgets
Reversible?Yes (two-way door — decide fast) / No (one-way — slow down)
Re-open dateIf parked or experimental — when we revisit
Two-way vs one-way doors A 2-person team's biggest risk is over-deliberating reversible calls. Reversible (two-way door): decide in the meeting, log, move on (e.g. which community to seed first). Irreversible (one-way door): entity choice, the audio-engineer equity grant, a public pricing commitment — these slow down and get a re-open date even when chosen.

Retro cadence · Start / Stop / Continue

Last Friday of every month, 45 minutes, whole team, no advisors and no investors in the room — this is the one meeting that is purely about how we work, not what the numbers say. Format: Start / Stop / Continue, on the process, not on people.

Start

What should we begin doing? A habit, a check, a ritual that would have caught a miss this month.

e.g. "Start recording every learner interview so we can re-listen for verbatim pain."
Stop

What is costing time without moving a validation number? Kill it explicitly.

e.g. "Stop polishing the landing page before the wedge interview kill-criterion is cleared."
Continue

What worked and must not be dropped as we get busier? Protect it.

e.g. "Continue hand-onboarding every install via Loom — it seeds the loop and clears install friction."
Retro rules Each item gets one owner and one action or it's noise. The retro produces at most 3 process changes per month — more than that and none stick. Items are about the system, never a person. Last month's actions are reviewed first: did Start/Stop actually happen?

No-meeting day

✦
Wednesday is sacred — zero internal meetings, all day

The moat is built by one rare engineer writing CoreAudio/WASAPI capture code (10-financial-model.html load-bearing line). That work needs uninterrupted maker-time, not a calendar sliced into 30-minute fragments. So Wednesday has no internal meetings — no syncs, no all-hands, no retro. Deep work only.

The one exception: live customer interviews and learner onboarding calls are always allowed on Wednesday — talking to immersion learners is the highest-leverage thing a pre-PMF team does, and it's not an "internal" meeting. The ban is on us meeting us.

Cross-references
  • 12-okrs.htmlThe quarterly OKR refresh runs against these objectives; the MBR reads KR mid-flight status.
  • 14-kpi-dashboard.htmlNorth Star, loop K, and the full metric set the weekly review and MBR read from.
  • 15-decisions-raci.htmlWhere every logged decision lands and which owner each decision-type routes to.
  • 16-risk-register.htmlTripwires that a crossed red-line in the weekly review escalates into.
  • 17-90-day-plan.htmlWeek-by-week field-work that the weekly validation review tracks progress against.
  • growth.md §3, §7The loop-factor K thresholds (K≥0.3 / K<0.15) and the 4-week validation plan the weekly review runs.
Babelio · Operating Cadence · Playbook 13/24 Refresh quarterly · re-tune the rhythm as the team grows past 5