You know that feeling when you finally get the baby down at 11pm, and your brain suddenly lights up with the exact feature your app needs? Or you're changing a diaper at 2am and you've got this crystal-clear vision for how to fix your onboarding flow?
Then you try to actually work on it and realize you haven't slept more than 90 minutes straight in four days.
I've watched a lot of founder friends become parents, and there's this weird mythology around it. The startup world loves the "I'll just work nights" narrative. Sleep when you're dead. Hustle harder. Your competitors aren't sleeping either (they probably are, but whatever). And then you have a kid and realize that's complete nonsense.
The thing nobody tells you is that your brain doesn't work the same way when you're running on fumes. It's not just slower — it's *different*. You can't do the creative problem-solving that actually matters. You can't think through architecture decisions. You can barely remember what you were trying to build.
I talked to this founder, Sarah, who launched her SaaS while her daughter was three months old. She told me something that stuck with me: "I thought I'd work from 9pm to midnight every night. That's three hours, right? That's something. But by 9pm I was so fried that I'd just stare at my code for 45 minutes and write nothing useful. I was basically paying to feel guilty about not working."
The real problem is that we treat startup time and baby time like they're separate things you can just stack on top of each other. Like you've got 24 hours and you just need to allocate them better. But that's not how energy works, especially when you're sleep-deprived.
Your brain has maybe 4-5 hours of actual high-quality thinking time when you're a new parent. Not 24 hours. Not even 16. Four to five. And those hours are scattered. They might be 6am to 7am before the baby wakes up. They might be 2pm to 3pm during a nap. They're definitely not 9pm to midnight when you're already exhausted.
Here's what actually matters: knowing when those hours are and protecting them like your life depends on it. Because they kind of do.
The founders I know who actually made progress while parenting newborns didn't work more hours. They worked *fewer* hours, but they were ruthless about what they did during those hours. One guy I know literally has a note on his laptop that says "ONLY HARD PROBLEMS." He doesn't answer emails during his high-energy windows. He doesn't do admin stuff. He doesn't "catch up" on Slack. He does the one thing that actually moves the needle, and then he stops.
Another founder, Marcus, told me he realized his best thinking happens right after his son's morning feed, around 7am. So he stopped trying to work at night entirely. He just... doesn't. He goes to bed at 9pm like a normal person. But he's up at 6:30am, and he's got two solid hours before the day gets chaotic. He gets more done in those two hours than he used to get done in six hours of night work.
The other thing that changes is what "work" actually means. You can't do deep work for 12 hours straight anymore. But you *can* do focused work for 90 minutes. You can do shallow work (emails, planning, organizing) during low-energy windows. You can do collaborative stuff (calls with your co-founder, user interviews) when you're tired because you're not relying on your own brain to generate ideas.
I think a lot of new parent founders fail not because they're lazy or because they don't care. They fail because they're trying to run a startup on a sleep schedule that's literally designed to break your brain. And then they feel guilty about not working enough, so they try to work more, which makes them more tired, which makes them less productive, which makes them feel more guilty. It's a spiral.
The honest truth is that some people can't launch a startup while parenting a newborn. That's okay. That's not a personal failure. That's just math. If you need eight hours of sleep to think clearly and you're getting four, you're not going to be able to do your best work. You can survive on four hours. You can even function. But you can't *think* on four hours, not really.
But if you're determined to do both — and a lot of people are, for good reasons — then the move is to stop pretending you have the same 24 hours as everyone else. You don't. You have maybe 4-5 hours of real thinking time, scattered throughout the week, interrupted by unpredictable baby stuff. That's your actual constraint. Everything else is just noise.
So figure out when those hours are. Maybe it's early morning. Maybe it's during naps. Maybe it's late at night if your kid sleeps through (lucky you). But find them, and then be absolutely brutal about protecting them. Don't check email. Don't do admin. Don't "catch up" on stuff. Do the hard thing that actually matters.
And be honest with yourself about what you can actually accomplish in that time. If you've got five hours a week of real thinking time, you're not launching a fully-featured product in three months. You might be launching an MVP in six months. You might be growing an existing product slowly. You might be doing customer research and planning. But you're not doing everything.
The founders who seem to "have it all" aren't actually doing it all. They're doing less, better. They're saying no to a lot of stuff. They're accepting that this phase of their life is about slow, steady progress, not explosive growth. And honestly? That's probably healthier anyway.
If you're trying to figure out what actually fits into your life right now — like, what's realistic to build given your actual sleep schedule and energy levels — I built a tool that helps with this. It's called dadfounder-schedule (yeah, the name is a work in progress). You put in your baby's schedule, how much sleep you're actually getting, and when your product launch is due, and it generates a realistic weekly plan that accounts for the fact that you're running on fumes. It's not magic, but it's better than pretending you can work like you did before the baby.
The real move though? Just be honest about your constraints. You're not lazy. You're not unmotivated. You're just operating with a different set of resources than you used to. That's not a bug. That's just the reality of this phase. Work with it instead of against it.