पाठशाला Pathshala · संचालन Sanchālan, Operations · Lesson 05 · Start

The founder’s operating cadence: daily, weekly, monthly, quarterly

A ten-person company has no COO. The calendar is the COO. Four rhythms, about six fixed hours a week, and the rule that protects the other thirty-four.

Pathshala, The Founder Library · 11 October 2026 · 8 min read

Somewhere between the sixth and the twelfth hire a company stops being something a founder can hold in their head. Decisions that used to happen over lunch now need a meeting, and the meetings multiply until the founder is in eight hours of them a day and nobody is building anything. The fix is not fewer meetings. It is a small number of fixed ones that happen at the same time every week whether or not anyone feels like it, so that everything else can be left alone.

This lesson lays out the four rhythms a ten-person company runs on, what each meeting is for and how long it takes, the calendar they add up to, and the single rule that protects the hours they do not use.

Why a cadence beats a calendar full of meetings

Patrick Lencioni’s Death by Meeting makes an argument most founders resist until they have lived the alternative: the problem with meetings is not that there are too many but that they are all the same meeting. A conversation about a bug in production, a conversation about whether to enter Mumbai, and a conversation about who is unhappy should not share an agenda, and when they do the urgent one eats the others. His remedy is four distinct meetings on four rhythms: a daily check-in, a weekly tactical, a monthly strategic and a quarterly review, each with its own length and its own kind of question.

The second argument is Keith Rabois’s, from his Startup School lecture How to Operate: a founder’s job past the first few hires is to edit and delegate, with transparency and a dashboard everyone can see. Editing requires reading the same page at regular intervals. A founder who reviews the numbers when something feels wrong is reacting; one who reviews them at ten every Monday is operating. The cadence is what converts the first into the second.

Daily: five minutes, then silence

Lencioni’s daily check-in is five minutes, standing, in which each person says what they are working on today. No problem is solved in it; problems are noted and taken to the right meeting. At ten people this is the whole company; at 9:30 it is over by 9:35 and the day begins. A remote team does the same thing in a chat thread by 9:30, and the founder reads it.

The founder’s own daily ritual is shorter still: read yesterday’s numbers before the check-in, which takes four minutes if the [weekly page](/library/weekly-metrics-review-one-page-one-hour) has a daily view and which is the earliest point at which a broken deployment or a stalled funnel can be noticed. Then the rule that makes the rest of the day possible. Paul Graham’s Maker’s Schedule, Manager’s Schedule observes that a single meeting can blow a whole afternoon by breaking it into two pieces each too small to do anything hard in, and that for someone on the maker’s schedule a meeting is like throwing an exception. Half the people in a ten-person company are makers, and the founder usually is too. So mornings after the check-in are never booked. Every fixed meeting in this lesson sits in the afternoon or at the very start of the day, and when a customer insists on 11 am the founder takes it alone.

Weekly: the four meetings that run the company

The metrics review, Monday, one hour. Eight numbers on one page, read in silence, explained by their owners, with decisions recorded before the hour ends; the previous lesson covers it in full. Lencioni’s weekly tactical has the same shape, a lightning round of one-minute priorities, a review of progress against the established metrics, and a real-time agenda built from what the numbers showed, and he puts it at forty-five to ninety minutes. One hour, fixed.

Commitments, Monday, thirty minutes, straight after. Christina Wodtke’s Monday commitments are a single document with four squares: the three or four most important things to be done this week towards the quarter’s objective; what is coming next month that others should prepare for; confidence in each OKR on a scale of ten, and whether it moved; and two health metrics the team has chosen to protect. It is, in her phrase, first and last a conversation tool, so the updates are short and most of the half hour is argument about whether this week’s three things are the right three.

One-on-ones, thirty minutes each, weekly. A founder with four direct reports spends two hours a week in them, which is the largest fixed block in the calendar and the one most often cancelled, so it is the one to defend. The report owns the agenda; the founder asks what is in the way and what they are not being told. Problems noticed in the daily check-in are solved here. Four of them fit in two afternoon blocks, Tuesday and Thursday from four.

Friday wins, thirty minutes. Wodtke’s Friday session is where every team shows something it made or moved that week, beyond the makers, every team should share something, and the company learns what each discipline does. It costs half an hour and a plate of samosas and it is the only meeting in the week whose purpose is morale. Companies that skip it discover in month nine that nobody outside engineering knows what engineering did.

Monthly: the close and one strategic question

Two things happen every month and neither moves. The books close by the fifth working day, as the [bookkeeping lesson](/library/bookkeeping-from-day-one) sets out; the Indian startup median is twelve to eighteen working days and five is achievable from the first month if it is designed for. The founder reads the pack the day it arrives with three questions at the top: did the bank reconcile, what moved more than fifteen per cent, what is the runway. The investor update goes out in the second week, one page, built from the pack and the weekly page, and it goes out whether the month was good or bad because the months it is skipped are the months investors remember.

The third monthly meeting is Lencioni’s monthly strategic: a select number of critical issues, with a few hours per issue. At ten people the number is one. Whether to raise prices, whether to open a second city, whether to stop a product line: one issue, two to three hours, a document written beforehand by whoever proposed it, and a decision at the end or a named reason there is not one. The issues come from a list the founder keeps during the weekly meetings, where strategic questions are parked rather than argued. The monthly strategic is the only meeting in the cadence that may be moved, because it should be held when the document is ready and not before.

A company of ten cannot afford a COO. It can afford six hours a week at fixed times, and that is most of what a COO does.

Quarterly: objectives, grades and a half-day away

The quarter opens with objectives set in week one: three for the company, each with three measurable results, which the [OKR lesson](/library/okrs-for-team-of-ten) covers. It has a mid-quarter check in week seven, an hour in which the confidence scores are read honestly and one objective is allowed to be rewritten if the world changed. It closes with grading in week thirteen, an hour in which each result is scored and a short retrospective asks what the company learned about its own estimates. Lencioni’s quarterly review covers four topics: strategy, team behaviour, personnel and the competitive landscape; at ten people that is a half-day out of the office, after the grading and before the next quarter’s objectives are written, and it is the one time in the quarter the founders talk about who is thriving and who is not. If there is a board or a lead investor, the quarterly review with them follows the grading and uses the same numbers.

The founder’s week, added up

Daily check-in, twenty-five minutes across the week. Metrics review, one hour. Commitments, thirty minutes. Four one-on-ones, two hours. Friday wins, thirty minutes. A founder review on Friday afternoon, an hour alone with the page and the parked list, writing what next week’s page should show. About six hours of fixed meetings, nine with the monthly and quarterly items averaged in, out of a forty-hour week in which thirty-one are unbooked. Before adopting it, count the meetings in last month’s calendar. A founder of a ten-person company who does this honestly usually finds twenty hours a week or more, most of them one problem at a time with whoever happened to be free. The cadence does not add meetings. It replaces them.

Putting it in the calendar this week

Today: create the recurring events, every one of them, with the agenda in the invitation and the attendees fixed. Daily check-in at 9:30. Metrics review Monday at ten, commitments at eleven. One-on-ones Tuesday and Thursday from four. Friday wins at five, founder review at 5:30. The close on the first five working days, the pack read on the fifth, the investor update on the second Monday, the monthly strategic as a placeholder in week three, and the four quarterly items at the ends of the quarter. This week: hold every one of them even though the page is half-built and nobody knows the agenda; the first month is practice. Next month: check what was cancelled and by whom. The founder is usually the answer, and the one-on-ones are usually the casualty.

Then the rule, which is the whole lesson: the fixed meetings do not move for anyone, and nothing else is booked in the mornings. A company that holds both for a year has an operating system. A company that holds neither has a founder who is very busy.

The hours above are a starting point for a company of eight to fifteen people with four or five direct reports to the founder; a company of three needs the Monday review and little else, and a company of forty needs the next lesson. The sources are below; Graham’s essay takes six minutes and should be read by everyone who books meetings.