Stay consistent
The five-hour founder week for people with a job
4 min read
Five hours a week is enough to build a startup on the side if you spend them on one outcome: about three hours making the offer or the product, ninety minutes talking to users, and thirty minutes writing down what happened. The hours need a repeating place on the calendar. Extra heroic Sundays do not replace that.
People ask for a system that finds them more time. The more reliable move is to decide the time is small and make the work fit. Five hours will not build a platform. Five hours will finish a landing page, ten outreach notes, or one paid delivery. Stack those weeks and you have a company sketch that is real.
Put the five hours in the same places
- Tuesday, 90 minutes after dinner: build or deliver. Phone in another room.
- Thursday, 90 minutes: the second build block, continuing Tuesday’s artifact.
- Saturday morning, 90 minutes: customer conversations, outreach, or a user call. Mornings beat a tired Saturday night.
- Sunday, 30 minutes: the log. What shipped, who replied, what next week’s single outcome is.
That is five hours. Move the days if your life requires it. Keep the ratio: most of the time on the artifact, a real slice on customers, a short written review. If a meeting at work destroys Thursday, the block moves to Wednesday. It does not get donated to email.
One outcome on the Sunday note
Write the week’s outcome before the first block. “Send the audit to two pilots.” “Publish the pricing page and write ten notes.” “Fix onboarding so a new user reaches the first result.” If the sentence needs “and,” split it and keep half.
During the build blocks, work only on that sentence. Ideas that arrive mid-week go on a list you are not allowed to open until Sunday. This is how a five-hour week beats a twenty-hour week full of restarts.
Two sample weeks
Productized service week: Tuesday drafts the deliverable template. Thursday completes client one’s memo. Saturday sends five notes to people who match the buyer. Sunday records who replied and sets next week’s cap.
Product week: Tuesday ships one user-visible change. Thursday writes the empty-state copy and deploys it. Saturday watches two people try it, or watches the session recording. Sunday decides whether the next week is a fix or a sales week. For a fuller offer design, read the productized service guide.
Tell one person the Sunday note is coming. A calendar reminder is easy to swipe away. A person who expects the note is the rest of the system. That is the job of an accountability rhythm, whether it is a partner or a house like Camp Zero.
Questions people ask
Is five hours a week enough to reach revenue?
It is enough to reach a first offer, a first conversation, and often a first payment, if every week serves the same outcome. Replacing a salary is a later question and usually needs either a higher price or more hours after evidence shows up.
What if you only have three hours?
Keep the customer slice. Ninety minutes of building and ninety minutes of conversations, plus a ten-minute note, still moves a narrow offer. Drop the second build block before you drop the listening.
Should you wake up at 5am?
Only if you already protect sleep and you like mornings. A defended evening beats a heroic alarm you abandon in week two. Put the block where your energy actually shows up.