I'm building a SaaS at night while working at a Fortune 500 and raising a kid. Here's the math.
6 months of side-hustle SaaS building — the real schedule, the real numbers, what works and what doesn't.
The math nobody publishes
Eight hours at the day job. Six hours awake with my son and partner. Two hours on the side project, 10 PM to midnight, most days. Eight hours sleep on a good week.
That’s the schedule. Most weeks I get 12-15 hours on the product. Some weeks the day job demands a fire and I get five. Some weekends the kid is sick and I get zero.
At 50 hours a month, that’s 600 hours a year. Most full-time founders burn 600 hours in a single month. The math says I should be 12x behind them.
Six months in: I’m not. Slower, yes. But shipping consistently, learning the same lessons (just slower), and — crucially — not running out of money or burning out.
I want to share what actually works at this pace because most “founder content” is written by people who quit their jobs. The side-hustle path is undermarketed.
Why I haven’t quit yet
Three reasons.
Stability removes desperation. I’m not building from financial fear. I can pick the right feature instead of the marketable one. I can spend a week fixing infrastructure that won’t show up in screenshots because there’s no urgency to fake progress. When you’re not running out of money, you can make slow decisions.
The day job teaches what NOT to do. I sit in 4-hour quarterly planning meetings. I watch products take 3 months to ship a button color. The contrast trains my speed instincts. Every time I open my laptop at 10 PM, I can ship in 25 minutes what a corporate team would schedule for next sprint.
The audience is built-in. My LinkedIn audience cares about “engineer at Fortune 500 builds side project” content. That’s the content I have. Doesn’t work without the day job context.
The conventional wisdom says quit, give it everything, the constraint of survival will force product-market fit. My experience: the constraint of survival forces something, but it’s often not PMF. It’s bad fundraising, bad customers, or burnout. Stability lets you wait for the right shot.
The actual schedule
Monday-Friday:
- 7:00 AM — kid up, breakfast
- 8:30 AM — at the day job
- 6:00 PM — back home, family time
- 9:00 PM — kid in bed
- 10:00 PM — laptop open
- 12:00 AM — laptop closed (mostly)
Saturday-Sunday:
- One of these days is family-only, no laptop
- The other has maybe 3-4 hours of focused work
- Weekend hours are unreliable — plan around weekdays
That’s it. The 10 PM block is sacred. No phone. No Slack. No “quick check” on email. Two hours of clean coding.
The 2-hour evening block — what actually fits in it
I used to think 2 hours wasn’t enough to do anything real. Six months in, here’s what fits:
- One bug fixed + one feature shipped
- One new tool wired through the integration layer
- One blog post written
- One round of cold emails (5-10) personalized and sent
- One full code review of my own work from the last month
- One conversation with a beta tester (DM thread)
- One Notion template written from scratch
What does NOT fit:
- Two of the above
- A 4-hour deep refactor
- A real podcast appearance
- A live coding session
The discipline isn’t “work harder.” The discipline is “do exactly one thing per evening.” Pick before you open the laptop. Don’t context-switch.
What I stopped doing
A list of things I stopped doing once I accepted the 12-hour-week constraint:
- Reading hacker news during work hours. I used to scroll for 20 minutes a day “for inspiration.” Now I batch it to weekends.
- Tracking every metric daily. Daily metric reviews are a procrastination loop. I look at numbers once a week.
- Writing roadmap docs. Nobody reads them. The work itself is the spec.
- Adding features users haven’t asked for. Easier said than done.
- Meetings with myself. I used to “plan the week” for 45 minutes on Sunday night. Now I write the weekly ship target on a Post-it, that’s it.
- Premature scale thinking. Optimizing for 10,000 users when I have 2 is just procrastination dressed up.
- Comparing myself to full-time founders. Their constraints aren’t mine.
What I started doing
- One ship target per week, written before Monday. Anchors everything.
- One personal email per day to a beta tester or specific ICP person. 30 emails a month, slowly compounding.
- One blog post per week (this is one). SEO compounds over 18 months.
- One free resource per month (Notion templates, frameworks). Lead magnets that demonstrate the product.
- A weekly “what I shipped” review every Friday night, 15 minutes. Brutal honest.
- Walking before the 10 PM block to context-switch out of day-job brain.
- A list of “would do if I had a full-time founder budget” that I check quarterly. Most things on it turn out to not matter.
The 6-month numbers
Side-hustle math, for context:
- Followers grown: 90 → 370 on X
- Waitlist signups: 92 (all organic)
- Beta invites sent: 18
- Beta accounts redeemed: 3
- Active users: 2
- Real customers (paid): 0 (still closed beta)
- Hours spent: ~350
- Hours per beta account: 116
- Hours per X follower: 1.25
The hours-per-result math is awful. The compounding math is fine. The fundamentals (shipping consistently, talking to users, learning the lessons) are working. The amplification (distribution) is where the slow part is.
What I’d tell my 6-months-ago self
- You’re not behind. The pace is normal. Founders you admire took 1-3 years before anything worked.
- Distribution is the bottleneck, not building. Spend 50% of your time on distribution starting now. (I still don’t do this enough.)
- Pick a narrower niche. “Solo founders” is too wide. Pick a specific subgroup — side-hustle founders with day jobs, or domain experts going SaaS — and write FOR them, not for everyone.
- Build a free vehicle product early. A small free tool that pulls people into the funnel without committing to a SaaS trial. (I just shipped one — should have done it month 1.)
- Stop “saving” Product Hunt for “later”. Launch it on a small product to learn the mechanics. The first launch is always rough.
- The reply game is your most underused channel. Bigger account threads are where attention lives. Be there daily.
Why I’m still doing this
The honest answer: it’s the most meaningful work I do in any given week. The day job pays well and I’m grateful for it. But the day job hasn’t asked me to think hard in months. The side project asks me to think hard every single night.
That’s worth a lot. Even if the numbers stay slow, the I’m a person who builds things identity stays alive. I can’t put a dollar amount on that.
The day job and the side project teach each other. The corporate context grounds me in scale and stakeholder reality. The side project keeps me dangerous.
Where to find the work
I’m building aicofounders.co — 6 AI cofounders for solo founders who want a team without hiring one. Closed beta.
If you want to test it without signing up, run a free idea teardown. It’s the Product cofounder, running for free, on whatever startup idea you’re thinking about.
If you’re on the same path — day job + side project + kid or no kid — say hi. I read every email and reply within 24 hours: kyle@aicofounders.co.
This is post #2 of an ongoing build-in-public series. Subscribe to follow the journey from closed beta to first paid customer.