Can you really build a side project while working full time?

Yes, and most successful indie products started exactly that way. The condition is switching strategies: instead of hunting for big free blocks, you run 4 to 6 short time-boxed sessions a week, pick each task by impact-per-minute, and rely on automated triggers like email reminders rather than willpower. Five well-aimed hours a week, sustained for months, ships real products.

How many hours a week do I need for a side project?

Around four to six focused hours is a realistic and sufficient cadence next to a 40-hour job. The leverage comes from how the hours are spent, not the count: short pre-planned sessions where the task was chosen in advance, sliced small enough to finish inside one sitting. Ten unplanned hours routinely produce less than five planned ones.

When is the best time to work on a side project with a day job?

Whenever you can protect the same slot repeatedly: for most people that's a fixed evening box (for example 9:00 to 9:45pm) two or three weekdays plus one longer weekend morning session. Consistency of the slot matters more than its position, because a recurring time becomes a habit and a floating one becomes a negotiation you lose.

How do I stay consistent with a side project when I'm tired after work?

Remove the two things tiredness attacks: the decision and the start. Choose the session's task the night before (or let a tool rank tasks by impact-per-minute), and use a trigger that arrives on its own, like shipsolo's task reminder emails with mark-as-done links. On genuinely bad days, shrink the task instead of skipping the session; a 10-minute fix keeps the streak and the habit alive.

Should I spend my limited side project time on coding or marketing?

Mostly building, but never only building. A good ratio for a part-time week is one marketing task (about 20 minutes: a build-in-public update, a community reply, a landing page tweak) for every four or five build sessions. Founders with day jobs are the most likely to launch in silence, and small consistent distribution work is cheap insurance against that.

← All articles

Published September 29, 2026·9 min read

How to ship side projects with a full-time job

You can build a real side project around a 40-hour job, but not by copying full-time founders. Here's the system: time-boxed sessions, impact-per-minute task picking, email reminders as the trigger, and a weekly cadence that survives real life.

TL;DR

To ship a side project with a full-time job, stop hunting for big blocks of time and build a system around small, protected ones: time-box 30 to 60 minute sessions, pick each session's task by impact-per-minute, and use an automated trigger like an email reminder so the habit doesn't depend on willpower. A realistic cadence is 4 to 6 short sessions a week, roughly five focused hours, which compounds into a shipped product within months if every session ends with something finished.

On this page

You don't have a time problem, you have a granularity problem: side projects die waiting for free weekends that never come, and thrive on 45-minute boxes that always do.
A time box needs a task decided before it starts. Choosing what to do inside the box is how 40 minutes becomes 15.
Pick tasks by impact-per-minute: progress toward your next milestone divided by honest time cost. Around a day job, minutes are the scarce input, so the denominator matters more than for anyone else.
Automate the trigger. An email reminder that lands a concrete task in your inbox at your usual work hour beats every intention you'll ever set.
Plan a week you can repeat for a year: 4 to 6 short sessions, one marketing slot, one deliberate rest day. Sustainable beats impressive.
End every session with something finished, even something tiny. Unfinished work pays no compound interest.

Most advice about shipping side projects is written by people who quit their jobs. Wake up at 5am, do a 12-hour Saturday sprint, grind through the weekend. Follow that playbook around a real 40-hour job, a commute, and a life, and you get the standard outcome: three heroic weekends, one burned-out month, and another repo that stops at 60 percent done. The founders who actually ship around a day job do something less cinematic. They build a small, boring, repeatable system, and then they just run it.

Time-boxing, not time-finding

The first mental shift is to stop searching for time and start reserving it. 'I'll work on it when I have a free evening' is a plan to never work on it, because free evenings are what every other obligation in your life eats first. A time box flips the default: Tuesday and Thursday, 9:00 to 9:45pm, and Saturday morning, 10:00 to 11:00, are project time, and everything else negotiates around those slots instead of the other way round.

Keep the boxes small on purpose. A 45-minute box has two properties a 4-hour block never has: it fits into almost any day, and it's too short to procrastinate inside. You can dread a marathon; it's hard to dread three quarters of an hour. Small boxes also fail gracefully. Miss one and you've lost 45 minutes, not the week, so there's nothing to 'make up' and no guilt spiral that makes restarting harder.

The box only works if the task is chosen before the box opens. Sitting down at 9pm and asking 'what should I do?' is how a 45-minute session becomes 20 minutes of backlog scrolling and 25 minutes of tired work.

Pick every task by impact-per-minute

When you have five focused hours a week instead of fifty, task selection matters ten times more than it does for a full-time founder. They can afford a wasted afternoon; for you, one wrong evening is 20 percent of the week. The filter that works is impact-per-minute: for each candidate task, how much progress toward your next real milestone (MVP, launch, first paying customer) does it deliver, divided by the minutes it honestly costs?

That denominator is where part-time builders win or lose. A beautiful high-impact task that needs six uninterrupted hours is, for you, effectively a low-impact task, because it will sprawl across four sessions, lose context at every boundary, and sit half-finished for two weeks. A medium-impact task you can genuinely finish tonight usually beats it, because finished work compounds and unfinished work just accrues re-loading cost. Score honestly, and the ranking gets uncomfortable fast: the 30-minute fix to your broken signup email outranks the elegant refactor you were looking forward to.

Anchor impact to the next milestone, not to general goodness. If it doesn't move you toward MVP, launch, or the first customer, it scores low no matter how professional it feels.
Slice tasks until they fit a single box. 'Build the dashboard' is a project; 'render the empty dashboard shell with fake data' is a task.
Keep a small ranked list, not a big backlog. Five scored tasks you'll actually do beat eighty you'll scroll past.
Let tooling carry the math if you want. shipsolo scores every task by impact-per-minute automatically, and its AI can generate and rank the task list from a project brief or your uploaded code, so the pre-session decision is already made.

Make email the trigger, not your memory

Habits need triggers, and after a full workday your brain is the least reliable trigger you own. You leave the office intending to build, then dinner, a message, one episode, and it's 11pm. The fix is to move the trigger out of your head and into a channel you already check compulsively: your inbox.

A task reminder email that lands at your chosen hour does two jobs at once. It interrupts the drift ('right, it's project time'), and it removes the decision, because the task is named in the message. shipsolo is built around exactly this loop: it emails you one to three pre-ranked tasks on the schedule you set, you can mark a task done straight from the inbox, and in chain mode the next task arrives the moment you finish the current one. On a good evening that turns one task into a chain of three; on a bad one, the single mark-as-done click still keeps the day from being a zero.

Full-time founders can afford to rely on motivation. Around a day job, you need a system that works on the evenings when you have none.

A realistic weekly cadence

Here is a week that ordinary humans with jobs can actually sustain, not for a month but for a year, which is the timescale side projects really run on:

Monday: rest. You just did a Monday. Guarding one guaranteed off-day makes the other days non-negotiable.
Tuesday, 45 minutes: highest impact-per-minute build task.
Wednesday, 30 minutes: a small task, tests, a bugfix, or spillover from Tuesday.
Thursday, 45 minutes: next build task, or the second half of a sliced feature.
Friday: optional 20 minutes of marketing, a build-in-public post, a community reply, a tweak to the landing page. Skip guilt-free.
Saturday, 60 to 90 minutes: the week's one longer session, for the task that genuinely needs contiguous focus.
Sunday, 15 minutes: review the week, re-rank next week's tasks, done.

That's roughly four to five focused hours. It looks unimpressive next to hustle-culture screenshots, and it ships more than they do, because it repeats. Note the marketing slot: technical founders with day jobs are the population most likely to build for a year in total silence, and one deliberate 20-minute distribution task a week is the cheapest insurance against launching to nobody. Note also the review: fifteen Sunday minutes of re-ranking means every box next week opens with its task already chosen.

Measure consistency, not heroics

Around a full-time job, the metric that predicts whether your project ships isn't hours per week, it's weeks without a zero. Track that. A visible streak of shipping days (or shipping weeks, if daily is unrealistic for your life) turns consistency from a vague virtue into an asset you'll protect, and a weekly recap of what you actually finished is a better motivator than any plan, because five small tasks a week looks like nothing day to day and looks like real momentum in a list. shipsolo tracks streaks and sends that recap automatically, and its free tier covers two projects, which is plenty to run this whole system before deciding whether Pro (5 euros a month) is worth it. But the system itself needs no tool to start: pick tomorrow's box, pick its task tonight, and put the reminder somewhere you can't miss. The job takes 40 of your hours a week. Five of the rest, aimed well and repeated, is enough to ship.

Frequently asked questions

Can you really build a side project while working full time?: Yes, and most successful indie products started exactly that way. The condition is switching strategies: instead of hunting for big free blocks, you run 4 to 6 short time-boxed sessions a week, pick each task by impact-per-minute, and rely on automated triggers like email reminders rather than willpower. Five well-aimed hours a week, sustained for months, ships real products.
How many hours a week do I need for a side project?: Around four to six focused hours is a realistic and sufficient cadence next to a 40-hour job. The leverage comes from how the hours are spent, not the count: short pre-planned sessions where the task was chosen in advance, sliced small enough to finish inside one sitting. Ten unplanned hours routinely produce less than five planned ones.
When is the best time to work on a side project with a day job?: Whenever you can protect the same slot repeatedly: for most people that's a fixed evening box (for example 9:00 to 9:45pm) two or three weekdays plus one longer weekend morning session. Consistency of the slot matters more than its position, because a recurring time becomes a habit and a floating one becomes a negotiation you lose.
How do I stay consistent with a side project when I'm tired after work?: Remove the two things tiredness attacks: the decision and the start. Choose the session's task the night before (or let a tool rank tasks by impact-per-minute), and use a trigger that arrives on its own, like shipsolo's task reminder emails with mark-as-done links. On genuinely bad days, shrink the task instead of skipping the session; a 10-minute fix keeps the streak and the habit alive.
Should I spend my limited side project time on coding or marketing?: Mostly building, but never only building. A good ratio for a part-time week is one marketing task (about 20 minutes: a build-in-public update, a community reply, a landing page tweak) for every four or five build sessions. Founders with day jobs are the most likely to launch in silence, and small consistent distribution work is cheap insurance against that.

Put this into practice

shipsolo turns advice like this into scored tasks for each of your apps.

Try shipsolo free

Keep reading

🤖

How solo founders build an AI-assisted shipping workflow

Most solo founders use an AI coding agent for writing code and a separate tool for tracking what to build. The gap between the two is where momentum dies. This guide walks through building a coherent AI-assisted workflow: a ranked task board your agent can read and update, a daily trigger that keeps both in sync, and guardrails that keep you in the driver's seat without babysitting every line.

🗓️

The 20-minute weekly review system for solo founders

Without a weekly reset, solo founders drift: they ship the wrong things, lose track of milestones, and arrive at Friday wondering where the week went. A 20-minute weekly review fixes all three, and this article shows you exactly how to run it.