How to Manage a Side Project With a Full-Time Job Without Losing Your Mind
Practical strategies for building a product solo while working full-time — protecting your time, setting expectations, and knowing when to make the jump.
Free Newsletter
Get Real Advice in Your Inbox
Join 811+ indie hackers and solopreneurs getting real, actionable advice every week — no hype, no BS.
Building a product while holding a full-time job is one of the harder things a person can attempt. Not because either task is impossible, but because they compete for the same finite resource — your functional brain. Most advice on this topic talks about time. Time isn’t actually the problem.
The Energy Problem (Not Just Time)
You have 168 hours a week. Subtract 40 for work, 56 for sleep, and another 20 for eating, commuting, and basic human maintenance. That leaves roughly 52 hours, on paper. The problem is that 52 hours of available time isn’t 52 hours of productive capacity.
If you’ve spent eight hours at your job doing knowledge work — thinking hard, making decisions, writing, debugging — you’re not going to sit down at 6pm and do high-quality creative work for three hours. You might manage it, occasionally. But you cannot sustain it, and trying to will either produce low-quality work or collapse you.
The energy question matters more than the time question: when in your day are you at something close to full capacity? Morning before work? Late evening once you’ve wound down? Weekends? Be honest. That’s your actual building window.
This is also why avoiding burnout as a solo founder starts before you even go full-time — the habits you build now are the ones you’ll have later.
Finding Your Working Hours
There’s no universal best time. What matters is consistency and honesty.
The morning block: Waking up 90 minutes earlier than usual gives you a clean, interruption-free window before your brain is taxed by the day. For most people, 5:30am to 7am is high-quality time — no messages, no context-switching, nobody needs anything from you. If you can do this five days a week, that’s 7.5 hours of building time before your workweek even starts.
The downside: it requires going to bed earlier, which means protecting your evenings from late-night scrolling. That’s a lifestyle change, not just a scheduling hack.
The evening block: If mornings don’t work — night-shift schedule, kids, or you genuinely don’t function before 8am — evenings are the alternative. The trick is establishing a hard start time and a transition ritual. Don’t go straight from work meetings to building. Give yourself 30 minutes to decompress: a walk, a meal, anything that marks the shift. Then start.
The weekend block: Saturday and Sunday are where most side project progress actually happens. Four focused hours on Saturday morning can equal a full week of evening blocks. Guard these ruthlessly. Social commitments are fine, but treat a blocked Saturday morning the same way you’d treat a doctor’s appointment — it doesn’t move unless something important forces it.
Whatever time you pick, pick one primary window and protect it. Trying to build in scattered 20-minute gaps throughout the day doesn’t work for anything requiring sustained concentration.
Protecting Your Blocks From Interruption
Once you have a time block, the next problem is that life ignores your calendar. Here’s what actually works:
Be boring about it. Tell your partner, your family, or whoever shares your space what you’re doing and when. Not in a dramatic “I’m building a business” way — just matter-of-factly. “Saturday mornings I’m heads-down from 8 to noon.” People respect predictable schedules more than flexible ones because flexible ones create negotiation space.
Turn your phone off, not to silent. Silent still shows you notifications. Off means off. You can check it when your block ends. Nothing that happens in a two-hour window requires an immediate response from you.
Use a single-purpose setup. Open only what you need for what you’re building. If you’re coding, close your email. If you’re writing, close Slack. Browser tabs are context switches waiting to happen. Kill them before you start.
Don’t optimize for quantity, optimize for frequency. A consistent 90-minute block five days a week beats a heroic six-hour Saturday once a month. Consistent smaller efforts compound. Inconsistent marathon sessions don’t.
The broader productivity systems for indie hackers framework covers the planning layer on top of this — worth reading once you’ve locked in your time blocks.
If this is the kind of thing you want more of, the Struggling Entrepreneur newsletter covers the reality of building alongside a full-time job every week.
The Decision Point: When to Go Full-Time
At some point, if the side project is working, you’ll ask yourself whether to quit your job. This is the question everyone wants a formula for and nobody can give one. But there are useful filters.
Revenue first, belief second. Don’t quit because you believe in the product. Quit when the product has demonstrated it can make money. The bar isn’t “replace my salary” — it can be as simple as “someone paid for this and I can see a path to more of that.” But there has to be money from real customers, not just a waiting list.
The 18-month runway test. Before quitting, you should have enough saved to cover 18 months of personal expenses with no income from the project. 12 months is the floor. Less than that puts you in a position where financial pressure forces bad decisions — premature monetization, shutting down things that need more time, taking on work you don’t want.
The ceiling test. Ask honestly: is the full-time job actually limiting the project, or is it just inconvenient? If the project is growing and you could keep building it part-time, the job isn’t the constraint — something else is. But if you can see specific things you would do and specific growth that would happen if you had 40 hours a week instead of 10, that’s a more legitimate reason to consider the jump.
Don’t romanticize full-time. The day you quit your job, you don’t suddenly have 40 extra hours of productive capacity. You have 40 extra hours, many of which will be consumed by tasks your employer currently handles, by isolation, and by the weight of knowing there’s no backup paycheck. Go in with eyes open.
Build for as long as you can without quitting. Then, when the constraints become real and the revenue is there, make the move deliberately.
You Made It to the End
Enjoyed This? Get More Like It.
811+ indie hackers already get weekly real talk about launching, growing, and surviving solo. You should too.
No spam. Unsubscribe any time.
More in Building & Productivity →