A Realistic Weekly Hour Budget for a Side Project With a Day Job

Quick answer

If you're working a side project around a full-time job, 8 to 15 hours a week is the realistic range. 10-14 hours — roughly 2 hours on weekday mornings plus a few hours on the weekend — is the structure most builders settle on and actually keep up. That's the honest number. Not the 20-30 "hustle" hours people talk about online and rarely sustain.

Most side projects don't die because someone picked the wrong idea. They die because someone picked a weekly hour budget that only works for one good week, then quietly stopped when it didn't hold. Below: how to set your own number, how to fit it into your week, and what to do when a week falls apart anyway.

Step-by-step

Audit your actual week before you pick a number

Don't start from a fantasy 20-hour week. Start from what's actually free once you subtract the day job, the commute, sleep, and everything else already on your plate. For most people with a full-time job, that leaves somewhere in the 8-15 hour range — some weeks closer to 5, some closer to 15, depending on how the day job is going.

Want a concrete starting point instead of a range? Try 2 hours every weekday morning plus a few hours on Saturday. That lands you around 10-14 hours a week — a specific, testable schedule you can run for two weeks and adjust, not a number to hit by any means necessary.

Pick two or three anchor blocks, not "whenever I have time"

"Whenever I have time" usually means never. Builders who stick with a side project tend to protect specific blocks: a 25-minute Pomodoro block before work, an hour at lunch, a longer stretch Saturday morning.

Mornings tend to win over evenings. Mental energy, not raw time, is the real constraint — a focused 90-minute block before the day job usually outproduces three scattered hours after it, once the day job has used up your attention. If mornings genuinely don't work for you, an early-evening block right after you close your laptop (rather than late at night) keeps the same logic: use the energy you have left, not the energy you wish you had.

Time-block the day job, the side project, and your health separately

Treat the side project as its own block, not whatever's left over after everything else. One useful framing from builders who've made this work: split the day into three priorities — day job, side project, health — and give each one a real slot on the calendar. It's the same logic behind time blocking vs. time tracking: blocking decides when you'll work, tracking tells you whether you actually did.

Track the hours you actually work — don't estimate them

People who log hours in real time consistently land on a stable weekly number. People who estimate tend to overstate how much they're getting done, or burn out chasing a number they never actually confirmed. Logging a block the moment it starts, rather than reconstructing your week from memory on Sunday night, turns "I think I did around 10 hours" into a number you can actually plan around next week.

Common problems and fixes

The spike week. You put in 30-40 hours one week because you were excited about a feature, then can't get near your side project the following week because you're wrecked. Builders who tracked this pattern found the crash starts once a big combined week (day job plus side project) pushes past roughly 60 hours total — sleep drops under 8-9 hours and meals get skipped, and next week's output falls further than the spike gained. Fix: cap your side-project week at a number you could repeat five weeks running, not the number you hit once.

The all-or-nothing trap. Treat the side project as something you only touch in long, uninterrupted sessions, and any short window starts feeling pointless — so it gets skipped. Fix: let small sessions count. Twenty focused minutes on a real task beats a "someday when I have three free hours" block that never arrives.

Your shipping cadence keeps slipping even though your hours are steady. That's usually not an hours problem. It's that the hours aren't landing in blocks long enough to finish anything — see shipping cadence for more on this. Two scattered 30-minute sessions rarely ship what one focused 90-minute block will.

Doing this with Pomlo

A realistic hour budget only works if you know your real number, not your guessed one. That's the part Pomlo is built for.

Focus sessions protect your morning or weekend block from getting quietly eaten by notifications and context-switching — start a session for the side project, and nothing else counts against it. Time tracking logs the block the second you start it, so you're never reconstructing your week from memory on Sunday night. And reports show you the number you actually hit each week, next to the number you planned for, so you can adjust your budget with real data instead of a vague feeling that you "should be doing more."

Pomlo is free to start on iOS, Android, and the web — track your first side-project block today and see what your real weekly number looks like.

Frequently Asked Questions

How many hours a week should I spend on a side project while working full-time?

Most people with a day job land somewhere between 8 and 15 hours a week, with 10-14 hours — roughly 2 hours on weekday mornings plus a few hours on the weekend — being the most commonly cited sustainable target. The right number depends on your day job's intensity and how much sleep and recovery time you protect.

Is it better to work on a side project in the morning or at night?

Builders consistently report mornings as more productive, since mental energy is highest before the day job depletes it. A short, focused morning block (30-90 minutes) before work tends to beat a longer but low-energy evening session after a full day.

How do I know if I'm overcommitting to my side project?

Watch for the warning signs reported by builders who pushed past sustainable limits: sleep dropping under 8-9 hours, skipped meals, and inconsistent output from week to week. If a big week leaves you unable to repeat it the next week, the budget was too high, not too low.

Should I track my side project hours or just estimate them?

Track them. People who log hours in real time consistently report hitting a stable weekly number, while those who estimate tend to either overstate how much they're doing or burn out trying to hit an imagined target.