पाठशाला Pathshala · मन Man, The founder · Lesson 06 · Start
Time: the founder’s week, designed
A founder’s week is the only budget that cannot be raised. Design it before the week designs you: maker mornings, afternoons for customers, one block for thinking, and an audit of where the hours actually went.
Pathshala, The Founder Library · 11 October 2026 · 8 min read
Every other budget a founder manages can be increased. Cash can be raised, people can be hired, a market can be widened. The week has eighty-four waking hours between eight and eight and it will have eighty-four next year. Most founders spend it the way it arrives, in whatever order the phone decides, and then describe the result as being busy.
This lesson gives the week a design. It names the three kinds of hour that move a company, puts each where it does the most work, and then does the thing almost nobody does, which is to check at the end of the week where the hours actually went. The figure in the middle is the week as a grid; the sections around it are why the blocks sit where they do.
Two schedules, one person
Paul Graham’s Maker’s Schedule, Manager’s Schedule is the shortest essay a founder needs on this subject and the most ignored. The manager’s schedule runs in units of an hour; the day is cut into blocks and a meeting is just one block spent differently. The maker’s schedule, the one programmers and writers live on, runs in units of half a day at least, because you cannot write or program well in units of an hour. An hour is barely enough to get started.
The two schedules collide when the manager calls a meeting in the middle of the maker’s afternoon. Graham’s line is exact: a single meeting can blow a whole afternoon by breaking it into two pieces each too small to do anything hard in. For someone on the maker’s schedule a meeting is like throwing an exception; it does not switch the task, it switches the mode of working, and the mode is expensive to re-enter.
A founder is the only person in the company who is permanently on both schedules. The product needs maker hours. The customers, the team, the bank, the accountant and the landlord all need manager hours, and they all think an hour is a reasonable unit. Left undesigned the week becomes entirely manager time, because manager time is what other people ask for, and the product work migrates to the evenings, where it is done badly and called commitment. The design exists to stop the migration.
Three kinds of hour that move the company
Adora Cheung, in her Startup School talk on prioritising your time, reduces founder work to the tasks that move the primary metric, almost always revenue or active users, and finds that those tasks always come in two forms: talking to users and building the product. Everything else she calls fake progress: conferences, awards, networking, the things that feel like work and photograph well. The design below adds a third kind of hour that she describes without naming, which is the weekly act of deciding what the first two should be.
Maker hours are the product: code, design, writing, the sales deck, the financial model, anything that needs an uninterrupted half-day. They go in the mornings. Sam Altman’s note on productivity is explicit about why: the first few hours of the morning are the most productive of the day, and he does not let anyone schedule meetings then. Twenty to thirty hours a week is a serious maker budget for a founder who also has to sell; above forty and nobody is talking to customers.
Sales and user hours are the other half of Cheung’s pair: calls, visits, demos, customer interviews, onboarding people by hand, the follow-up that closes. They go in the afternoons, where meetings belong anyway, and they are batched so that the maker block survives. Fifteen hours a week is a floor in the first year, not a ceiling. A founder who finds this number drifting toward five is building something nobody has asked for.
Thinking hours are one block, not a scatter: the weekly review of the number, the honest look at what moved it and what did not, the plan for next week, the decision log from the lesson on [decisions](/library/decisions-reversible-irreversible-how-fast). Altman’s version is lists on paper rewritten often; Cheung’s is a weekly grading of every task by impact and difficulty before any of it is started. Three to five hours at the end of the working week, and the trick is that it is the only block that nobody else will ever ask for, so it is the first to disappear unless it is drawn on the grid.
Everything else, the admin, the email, the compliance, the calls that are neither sales nor product, fits in what remains. If what remains is nothing, the design has a problem and the answer is not a longer day. It is a shorter list.
Designing the week, not the day
The unit of design is the week because that is the unit at which the three kinds of hour can be given their own territory. A day cannot hold a maker morning, a sales afternoon and a thinking block without each squeezing the others. A week can hold five or six maker mornings, the same number of customer afternoons, and one half-day at the end that is nobody’s but yours.
Three rules make the design hold. No meetings before lunch, said once to everyone and then kept, which means not answering messages in the morning either; the phone face down is the cheapest productivity tool there is. Meetings go at the edge of the day, which is Graham’s own trick: he holds office hours at the end of the day so that they are never an interruption to anything. For a founder the edge is the afternoon, and the sales calls, the team check-in and the accountant all go there in a row. Short or long, never medium. Altman’s observation is that most meetings are best at fifteen to twenty minutes or at two hours, and the default forty-five-minute slot is the worst of both: too short to decide anything hard and long enough to break an afternoon.
The grid stops at eight in the evening on purpose, and the design treats sleep and exercise as part of the week rather than what is left of it. Altman calls sleep the most important physical factor in his productivity and exercise the second. This is not wellness advice. It is capacity management: a founder who works until midnight is spending Thursday’s hours on Wednesday, and Thursday notices. The weeks in which the design is abandoned for a crisis should be countable on one hand in a year and followed by a weekend that is actually one.
Manager time is what other people ask for. Maker time is what nobody asks for. The week has to be designed because only one of those has a lobby.
The audit: where the hours actually went
A design is a hypothesis. The audit is the experiment, and Cheung’s version of it is the one to run. For one week, write down what you did in every hour, in detail, and against each hour note what you expected it to do for the primary metric and what it actually did. Her warning from running it with founders is that you will be surprised by how much was low-value work, and that the cause is not laziness. It is autopilot and the small pleasure of finishing something quick.
Then put the audit beside the grid. Count the maker hours that happened against the ones that were drawn; they are almost always fewer and they are almost always shorter, two hours where the block said four, because something came in at ten. Count the sales hours; they are usually fewer too, and the reason is usually that a customer conversation is harder than a product task and the week found a way to avoid it. Count the thinking block; in most first audits it did not happen at all. Then look at where the missing hours went. The answer is nearly always the fourth category, the everything else, and within it nearly always messages and meetings that someone else called.
The move is to close the gap on the design’s side, not the plan’s. If the maker block keeps breaking at ten, the fix is the rule about the phone, not a smaller block. If sales afternoons keep turning into admin, the fix is to book the customer calls on Monday for the whole week so that the afternoons are already spoken for. If the thinking block keeps vanishing, move it to the morning of the last working day, where it is protected by the no-meetings rule, and accept the lost maker morning as the price. A design that is adjusted to what actually happened is still a design. A design abandoned because it did not survive contact is just the old week with a diagram.
What the design does not do
It does not make the week longer, and it should not. The founder who reads this and sets the sliders to a hundred hours has misread it. Graham’s founders in What Startups Are Really Like say a startup never stops and that there is a limit to how much of the emotional swing a person can take; the design is how the hours that do exist are spent, not an argument for more of them. It does not replace saying no, which Altman calls being ruthless about and which is the only way the fourth category shrinks. And it does not survive a co-founder who is not on the same grid. Agree the design together, including whose afternoon takes the accountant, or the two of you will spend the maker mornings interrupting each other.
A weekly ritual, Friday at four
Make the thinking block the audit. Every week, in the last working hours, three lines: the number against last week; the hours as they were spent against the grid, from the calendar or from a log; one change to next week’s design. Book the customer calls for the coming week before leaving. Then stop, because the block that ends on time is the proof that the design is real. Once a quarter, run Cheung’s full hour-by-hour log again for a week, and read the four quarterly logs together at the end of the year. A founder who does this has something very few people in any job have, which is a record of where a year actually went, and the only honest basis for deciding where the next one should.
Nothing here is medical advice; the sentences about sleep are a founder’s arithmetic, not a doctor’s. The sources are below. Graham’s essay takes five minutes and Altman’s ten, and they are the most useful fifteen minutes a founder can spend on a Monday morning before the first block starts.