Filed underSolo Founder Routineson•4 min read

Flipping the daily order to build a side project

An analysis of the time management frameworks and micro-tasking strategies part-time indie hackers use to build SaaS products without burning out.

Escaping the leftover energy trap

핵심 비교

Traditional Evening Work

  • Work on side project after completing full-time job
  • Rely on remaining cognitive capacity and leftover energy
  • Prone to fatigue and abandoned projects
VS

Flipping the Order

  • Work on side project first before the standard workday
  • Dedicate peak cognitive output to the startup
  • Ensures meaningful progress before daily fatigue sets in

Building a side project while holding a full-time job usually follows a predictable pattern. The founder finishes their primary work, eats dinner, and attempts to write code or plan marketing strategies with their remaining cognitive capacity. This often leads to fatigue and abandoned projects.

The issue isn't a lack of total hours, but the quality of the hours used.

Allison Mui, the creator of Sidekick, identified this exact problem in a guide on Indie Hackers. Working on her side hustle after a full day of work left her without the necessary mental energy to make meaningful progress. Her solution was a structural shift in her daily routine, a method she refers to as flipping the order. By working on the side project first, she ensures the project receives her best cognitive output.

The three-block daily framework

The Three-Block Daily Framework
  1. 1

    Block 1: Side Hustle Deep Work

    3-hour morning session dedicated to the application during peak cognitive hours, with a 5-minute break every hour.

  2. 2

    Block 2: Full-Time Job (9-to-5)

    Standard primary job executed without competing with the startup for initial mental energy.

  3. 3

    Block 3: Personal Time & Health

    Evening block immediately following work, designated for health, self-care, and personal relationships.

This routine relies on dividing the day into three distinct blocks.

Mui organizes her day into three priorities: her side hustle, her full-time job, and her health. The framework is sequential. The first block, following the morning routine, is a three-hour deep work session dedicated entirely to her application.

This three-hour duration is not arbitrary. It was identified as her optimal deep work length, structured with a five-minute break every hour. This specific setup allows for a sustained flow state without distractions.

The second block is the standard 9-to-5 job. Because the side project was handled during peak morning hours, the primary job does not compete with the startup for initial energy. The third block begins as soon as the full-time job ends and is designated for personal time, covering health, self-care, and relationships.

How would you structure your own three daily blocks if you were forced to allocate your highest-energy hours to your startup?

This strict separation prevents the tasks from bleeding into one another. It forces a clear boundary that protects personal health while ensuring consistent product development. As discussed among part-time indie hackers, other founders follow similar, though slightly less intense, patterns, often dedicating two hours every morning coupled with a few hours on Saturdays, yielding a total of 10 to 14 focused hours per week.

Execution mechanics: micro-tasking

Allocating the time is only the structural component; executing within that time requires a specific approach to task management.

When time is limited, ambiguous goals create friction. Another indie hacker, Felix, approaches this by breaking down roadmaps and goals into the smallest possible units.

The objective is to make progress visible and to bring the larger project together gradually. If the overarching goal is to publish four articles in a month, the task is not scheduled as writing a full article in a single day. Instead, it is broken down to writing one paragraph per day, turning project milestones into daily routines.

I've noticed that micro-tasking is a powerful tool for part-time founders. When you only have two hours, spending thirty minutes figuring out what to do is a massive efficiency loss. Breaking goals down to the atomic level means the founder can execute the moment the morning block begins.

Replicability and limitations

This framework offers a clear path for part-time founders, but it has practical boundaries.

The most replicable aspect is the concept of micro-tasking and the protection of peak cognitive hours. Anyone can break a feature down into smaller commits or write marketing copy one paragraph at a time. Shifting the side project to the start of the day is also highly effective, as it guarantees progress regardless of what crises occur later in the primary job.

However, the specific 3-hour morning block is difficult to apply universally. Demanding three hours before a standard 9-to-5 job implies waking up extremely early, which may conflict with family obligations or personal sleep requirements. For those who cannot sustain daily early mornings, alternative structures exist. Some founders manage this by operating on two-week cycles, aligning their project work with days off, or dedicating one to two full days per week exclusively to entrepreneurship, reserving the rest of the week for rest and their primary job.

The point is that side projects require dedicated, high-quality time blocks, not just whatever energy happens to be left at the end of the day.

참고 자료

Frequently Asked Questions

Q. Is a 3-hour morning block realistic for everyone?

Not necessarily. While a 3-hour block is optimal for some, it requires waking up significantly early. The main idea is allocating peak cognitive energy to the side project. For many, a dedicated 60 to 90-minute session before the primary job is more sustainable and still yields consistent progress.

Q. How can micro-tasking be applied to software development?

Micro-tasking involves breaking goals into their absolute smallest components. Instead of assigning 'build authentication' to a single day, a micro-task would be 'design the login database schema' or 'implement the password reset UI'. This ensures visible daily progress regardless of the available time.

Q. What happens if a full-time job requires overtime during the third block?

The time-blocking strategy relies on strict boundary setting. If the primary job frequently encroaches on personal time, the daily block system may fail. In such cases, shifting to a weekly or bi-weekly cycle, allocating specific days entirely to the side project, is an alternative approach used by some founders.

Back to all articlesHome