Guide

How to plan your week as a solo founder

Updated November 2026 · by Jerry Liu, Dayflow's founder

Pick one outcome for the week, give building, selling and admin their own days or blocks, and put fixed commitments on your calendar first. Plan only about half your hours. A paper card and your calendar handle the planning. Dayflow, a free Mac app, helps at the Friday review by showing what was actually on your screen, so you compare the plan with reality instead of with memory.

It’s Monday at 9. You have a product to ship, three customer emails you meant to answer last week, a tax form, an investor update that is two weeks late, and a nagging sense that you should be doing marketing. Nobody is going to tell you which of these matters most. You open the laptop, answer the easiest email, fix one small bug a user reported, and look up at 12:40.

By Friday the week felt full. You worked every day, maybe some evenings, and you still can’t say what moved. The thing you were sure you’d finish this week is “almost done,” the same as last Friday.

This guide covers why weekly planning is unusually hard when you are the only one deciding, and seven things to try this week. Most of them need only paper, a calendar and a little honesty. Dayflow, the Mac app that publishes this blog, comes up once near the end, along with the cases where it is the wrong choice.

The short version

Why is planning a week so hard when you work alone?

At a company, the week arrives with structure already built in. There is a standup, a manager who asks what you’re working on, a sprint, a deadline someone else set. Even when that structure is annoying, it does the sorting for you. As a solo founder, you are the manager, the engineer, the salesperson, the support desk and the accountant, and every one of those roles thinks its work is the most important.

Small urgent work wins by default. An email or a bug report has a clear next step and a quick sense of being done. Building the next feature or writing a sales page is open-ended and a bit uncomfortable to start. When nothing outside you decides the order, the comfortable, finishable tasks tend to go first, and they can fill a whole day.

Estimates run optimistic. Many people find that their sense of how long work takes reflects the version where nothing goes wrong. A two-hour task meets a broken dependency, a customer call runs long, and the afternoon is gone. If the plan assumed the smooth version every time, it was never going to fit. There is more on that in why we underestimate how long things take.

Switching costs pile up quietly. Jumping from code to a support ticket to an invoice and back means warming up again each time. Each switch feels small. Together, they eat a surprising amount of the day.

Memory is a poor record. On Friday you plan next week based on how this week felt, and feelings tend to remember the stressful hours and forget the scattered ones. So the next plan repeats the same mistake.

None of this is a character flaw. It is what happens when one person carries every role with no outside structure. The fix is to build a small amount of structure yourself.

What is the one thing this week is for?

Before any task list, write one sentence: “This week counts if ___.” Keep it to one outcome you can check on Friday with a yes or a no. Write it on an index card or the top of a page and leave it where you can see it.

The outcome is not a task list in disguise. “Work on onboarding” can’t be checked. “New onboarding flow live for new signups” can. If two outcomes feel equally important, pick the one that unblocks more next week, and put the other at the top of next week’s card.

Illustration: a founder with a small paid product writes “This week counts if the annual plan is live on the pricing page.” Everything else, like support, a podcast invite and a refactor, gets judged against that card. The podcast can wait. Support gets a fixed window. The refactor only happens if the annual plan needs it.

How to tell after a week: on Friday, could you answer yes or no without hedging? If you hit the outcome, good. If you didn’t, can you name what got in the way? Either answer means the card is doing its job. If you forgot the card existed by Tuesday, move it somewhere you’ll see it every day.

Give each kind of work its own place

Most solo founder work falls into three rough kinds: building (product, code, design, writing), selling (customer calls, outreach, marketing, partnerships) and running the business (email, invoices, taxes, tools, support). They need different kinds of attention, and mixing them all day is where the scattered feeling comes from.

Give each kind its own home. That could be whole days, or two half-day blocks. A simple starting split is build in the mornings, talk to people in the afternoons, and handle admin in one fixed block late in the week. Support gets a short window once or twice a day instead of an open door.

Illustration: Monday to Wednesday mornings are for building, with notifications off. Tuesday and Thursday afternoons are for calls and outreach. Friday after lunch is admin: bills, receipts, the investor update. Support is checked at 11:30 and 4:30. A bug that arrives at 9:15 goes on a list and gets looked at at 11:30.

How to tell after a week: count how many building blocks you got through without breaking off for something else. If that number went up compared with how last week felt, keep the split. If every block got broken anyway, the windows for urgent work are probably too far apart. Add one.

Put the fixed things on the calendar first

Before the planned work goes anywhere, put the immovable things on the calendar: calls, appointments, school runs, deadlines, the gym if you actually go. Then add your building, selling and admin blocks around them. Planned work goes into the gaps that are left, not on top of commitments you’ll have to honor anyway.

While you are there, look at the meetings. Group calls onto the same days so they don’t break up building time, and question any recurring meeting that no longer earns its slot. If you want a rough sense of what a regular call costs in hours across everyone in it, the meeting cost calculator puts a number on it.

Illustration: a founder sees that three customer calls landed on Monday, Wednesday and Friday mornings, which breaks all three building mornings. They move the calls to Thursday afternoon. Monday to Wednesday mornings are now whole.

How to tell after a week: did the calendar on Monday look roughly like the week you actually had? If most days held their shape, this is working. If you were moving blocks every day, you may be putting work on the calendar that depends on other people. Keep only what you control there.

How much should you actually plan?

Less than you think. A useful rule is to commit about half your working hours to planned work and leave the rest open. The open half is not wasted. It gets filled by support, small fixes, surprise calls, and tasks that took longer than planned. If none of that happens, you pull the next item in and finish early.

It can help to check your own sense of time first. The time estimation test is a short exercise that compares your sense of time with a clock. It is not a diagnostic, just a quick way to see whether you tend to run long or short. The where does my week go calculator is also handy for seeing how many hours are really free once sleep, meals, errands and fixed commitments are counted.

Illustration: a founder has about 40 working hours. They plan about 20: the weekly outcome, two sales blocks and the Friday admin block. Ten hours of support and fixes show up during the week. A task they estimated at three hours takes six. The week still closes with the outcome done.

How to tell after a week: if you finished your planned work and had room to spare, plan a little more next week. If you missed it again, cut further. The aim is a plan you finish most weeks, not a plan that looks impressive on Monday.

Close each day with three lines

At the end of the day, write three short lines on paper or in a plain note: what you did, what got in the way, and the first thing you’ll do tomorrow. It takes two or three minutes. The third line matters most. It means tomorrow starts with a decision already made, not a fresh look at a long list.

If you’d like a ready-made layout, the daily work log template has the same idea with a little more structure.

Illustration: “Did: pricing page copy, two support replies. Blocked: payment provider setting for annual plans wasn’t obvious. First tomorrow: read their annual plan docs and test one checkout.”

How to tell after a week: you should have five short entries, and Monday’s first task should have come from Friday’s last line. If you skipped two or more days, attach the habit to something you already do, like closing the laptop or the last coffee.

Review the week on Friday, against what actually happened

Block 20 to 30 minutes on Friday afternoon. Ask four questions: Did the weekly outcome happen? What took longer than expected? What showed up unplanned? What is one thing to change next week? Write the answers down, then write next week’s outcome card while it’s fresh.

The weak spot is memory. By Friday, Monday is fuzzy. The three daily lines help, and so does keeping your calendar honest. If you want a structured version, the time audit template walks through comparing planned and actual time. If you send investors or advisors a regular update, the same notes become most of it. There is a guide on writing a weekly status report that works for a one-person company too.

A friend can help here. Some solo founders swap a short Friday message with another founder: outcome, what happened, next week’s outcome. Knowing someone will ask makes it easier to be honest.

Illustration: “Outcome: annual plan live. Yes, Thursday. Took longer: payment setup, about twice the estimate. Unplanned: a customer’s data import issue ate Wednesday afternoon. Change: add a buffer day to anything involving the payment provider.”

How to tell after a week: after two or three reviews, you should see a pattern, such as the same kind of task always running long or the same day always getting broken up. If every review feels new, write the answers in the same place each week so you can read them side by side.

Set a finish line for the week

When you are the whole company, there is always one more thing. Without a stopping point, the week leaks into evenings and weekends, and Monday starts tired. Pick a stop time for each day and a finish time for the week, and tell someone what they are.

Before you stop, write tomorrow’s first task, or for Friday, next week’s outcome card. That gives the open loop somewhere to go so it doesn’t follow you to dinner.

Illustration: a founder sets 6 pm as the daily stop and Friday 4 pm as the end of the week, after the review. They tell their partner. On Wednesday they are mid-bug at 5:55, write “start with the failing test in checkout,” and close the laptop.

How to tell after a week: count the evenings you worked past your stop time. If it is most of them, the problem is usually the plan, not your discipline. Go back and cut the planned half further.

Where seeing your actual day helps

The Friday review has one weak spot: it depends on what you remember, and on whether you remembered to write things down. If you keep reaching Friday unsure where Tuesday went, an automatic record fills that gap.

Dayflow is a free, open-source Mac app that records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. You don’t start or stop a timer. Recordings and the timeline are stored on your Mac. Analysis can run on-device with a local model through Ollama or LM Studio, go to a cloud provider you configure, or be handled by Dayflow Pro, which deletes screenshots after processing under the privacy policy. The details are in local and cloud processing. You can export a date range as Markdown from Settings → Export, which drops neatly into a weekly review or update. AI summaries can miss or misread work, so check them before sharing.

Dayflow is MIT licensed and $0, with an optional Pro plan at $20 a month on the pricing page. It needs macOS 14 or later. If you want to compare it with other ways of tracking time, see this roundup of Mac time trackers, or read more on where your day went.

Dayflow publishes this article. Product details here come from Dayflow’s own documentation for version 2.2.0, reviewed on 2026-09-06.

Where Dayflow is the wrong pick

The bottom line

Planning a week alone is hard because nothing outside you sorts the work. So add a little sorting yourself: one outcome on a card, a home for each kind of work, fixed commitments first, about half your hours planned, three lines a day, and an honest review on Friday. Most of that needs nothing more than paper and a calendar. If your memory of the week is the weak link, an automatic record can help with the review. The planning is still yours, and it gets easier with each week you compare the plan with what actually happened.

Frequently asked questions

How many hours should a solo founder plan each week?

Plan fewer hours than you have. Many solo founders find their week fills with support, small fixes, calls and admin they did not see coming. A useful starting rule is to commit about half of your working hours to planned work and leave the rest open. If you finish early, pull in the next item. After two or three weeks, adjust based on what actually happened rather than on what you hoped would happen.

What should a solo founder focus on each week?

Pick one outcome that would make the week count if nothing else got done, such as shipping a feature, booking five customer calls or sending an overdue investor update. Write it down before you write any task list. Everything else is either support for that outcome, upkeep that keeps the business running, or something that can wait. Having one named outcome makes it easier to say no to the rest.

Should I theme my days as a solo founder?

Day theming works well for many solo founders because building, selling and admin need different kinds of attention. You might build Monday to Wednesday, talk to customers Thursday and do admin Friday afternoon. It does not have to be whole days. Two half-day blocks per theme can work just as well. Try one version for a week and see whether you switched tasks less often.

How do I stop urgent small tasks from eating my week?

Give them a home. Pick one or two fixed windows a day for email, support and quick fixes, and keep a running list for anything that arrives outside those windows. Most small requests can wait a few hours without harm. The goal is not to ignore them but to stop them from landing in the middle of your best working time and splitting it into pieces.

What is a good weekly review for a solo founder?

Spend twenty to thirty minutes on Friday comparing what you planned with what happened. Note whether the one outcome got done, what took longer than expected, and what showed up unplanned. Then decide one change for next week. Keep it short enough that you will actually do it every week, since a review you skip is worse than a simple one you keep.

Can Dayflow plan my week for me?

No, and for planning a paper card or the calendar you already use is the better choice. Dayflow is a record, not a planner. It captures your Mac screen at one frame every 10 seconds and has AI write the day into a readable timeline. That record is useful at the end of the week, when you want to see where time went, but deciding what to do next is still your job.

Do I need software to plan my week?

No. A sheet of paper for the weekly outcome, a calendar for fixed commitments and a notebook for a few lines at the end of each day cover most of it. Software helps mainly when your memory of the week is unreliable. If you keep reaching Friday unsure where the time went, an automatic record can fill that gap. Otherwise, simple tools are often enough.

Is Dayflow free?

Yes. Dayflow is free and MIT licensed, with an optional Pro plan at $20 a month that manages cloud analysis for you. It runs on macOS 14 or later only. You can also run analysis with a local model through Ollama or LM Studio, or connect your own cloud provider, whose own charges and privacy terms apply. Recordings and the timeline are stored on your Mac.

How do I keep a solo founder week from spilling into evenings?

Pick a stop time for each day and a finish line for the week, and say it out loud to someone, such as a partner, friend or fellow founder. Write tomorrow's first task before you stop, so the open loop has somewhere to go. If evening work keeps creeping back, look at your Friday review. It usually means the plan had more in it than the week could hold.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required