The Stealth Builder's Playbook

I turned 30 at a rave on Koh Phi Phi.

I was broke, alone, and living what everyone called my "dream life"—a travel photographer with a drone and expensive camera, selling stock footage while sipping margaritas on beaches. Complete freedom. Total flexibility.

Also complete emptiness.

I'd quit Amazon two years into a backloaded four-year vesting contract. My parents thought I was crazy. My girlfriend (now wife) was patiently waiting back home while I tried to figure out how to afford the flight back.

That birthday was my wake-up call: I wasn't building a business. I was running away from one.

The Myth of "All In"

The conventional wisdom in entrepreneurship is binary: you're either an entrepreneur OR an employee. Burn the boats. Go all in. Quit your job in a blaze of LinkedIn glory.

This is survivorship bias dressed up as wisdom.

Most businesses fail. If you've burned your boats and your startup goes under, you're unemployed AND broke. There's another way—and the data proves it works better.

Sixty-three percent of new entrepreneurs in 2026 are what researchers call "invisible entrepreneurs." They don't have launch parties. They don't post "I'm thrilled to announce." They build in the margins. Before kids wake up. After Slack notifications stop.

And they're smart.

Steve Wozniak built Apple while working full-time at HP. Michael Dell started selling computers from his dorm room while still a student. Sara Blakely sold fax machines door-to-door for two years while prototyping Spanx in her apartment.

These aren't overnight success stories. They're stealth building stories.

The Three Hidden Advantages

Building on the side gives you advantages that full-time entrepreneurs don't have:

1. Quiet Failures

When you quit your job to start a business, every misstep is public. The friend who asks "How's the business going?" The former coworker who wants to know if you're "still doing that thing." The extended family gathering where someone inevitably asks about your income.

When you build on the side and it doesn't work out? Nobody knows. No awkward conversations. No explaining why you're back to job hunting. You just... stop. And keep getting paid.

I tried Amazon KDP after the photography disaster. Generated books based on Amazon buying trends. One of my bestsellers was about hot Pilates. In German. Because apparently that was a thing in Germany.

It technically worked but managing it to scale became more work than my actual engineering job for way less pay. So I stopped. The only person who knew was my wife. That's it.

2. Financial Runway Without Fundraising

When you have a salary, you have infinite runway. You're not burning cash. You're not taking meetings with VCs who want 20% of your company for enough money to survive six months.

You can say no to bad deals. Wait for the right customer. Build the thing right instead of the thing fast.

Your job isn't the obstacle—it's the investor funding your experiments.

3. Constraints Force Focus

I don't have eight hours a day to work on side projects. I have two. Maybe three on a good day.

That means I can't waste time on logo redesigns or "brand strategy sessions." I build the thing that matters or I build nothing.

You know what constraint eliminates? Decision paralysis. When you have unlimited time, you can endlessly debate whether to use React or Vue. When you have two hours before the kids wake up, you pick one and move on.

Constraints are gifts. Most people just haven't unwrapped them yet.

The Four-Rule Playbook

After years of trial and error (emphasis on error), here's what actually works:

Rule 1: Protect the Asset

Your job pays the bills. Don't blow it up by building your side project on company time with company resources.

I've seen engineers get fired for running personal scripts on company servers. I've seen salespeople lose their job for reaching out to company contacts about their side hustle. Don't be that person.

The security of your paycheck is what gives you the freedom to build correctly. Protect it like your business depends on it—because it does.

Rule 2: Time-Box Ruthlessly

Find your window. Guard it like your life depends on it.

Mine is 4:30 AM to 7:00 AM. There's one spot in my hallway that creaks. I've learned to scale the walls like a ninja to get past my son's room. One wrong step and that's 100% of my attention gone.

The evening session is 8:00 PM to 11:15 PM. But those hours have to be negotiated with my wife. When she gets quiet and distant, it means I've been working too much and not spending enough time with her.

The constraint isn't time. It's trust.

Put your building window on your calendar like a meeting with your most important client. Because it is.

Rule 3: Shrink the Scope Until It's Embarrassing

What's the smallest possible version of your idea that could work? Not the vision. Not the platform. The smallest thing you can ship this month.

When I started The Lyceum (audio testing software), I wanted to build a full platform with user management, cloud storage, advanced analytics, and API integrations.

What I actually built first: a Python script that parsed audio test data and generated one specific report that my former team at Sonance needed.

It was embarrassing. It wasn't scalable. It had no UI.

It also worked. And it gave me enough confidence to keep going.

If you're building in the margins, you can't afford scope creep. Build the ugly thing that works. Polish comes later.

Rule 4: Don't Share Too Early

When you announce too early, two toxic things happen:

1. You get pressure from people watching, which makes you optimize for looking busy instead of making progress.

2. You get the dopamine hit of public commitment that tricks your brain into thinking you've already accomplished something.

Build in silence. Let the results make the noise.

I worked on The Lyceum for months before telling anyone but my wife. No social media posts. No "building in public" updates. Just quiet work.

When I finally had something worth showing, the results spoke for themselves.

The 4:30 AM Reality

Let me be honest about what this actually looks like day-to-day.

I wake up at 4:30 AM. I tiptoe past the creaky floorboard. I make coffee without turning on the main lights. I sit at my kitchen table with my MacBook and work on whatever matters most that day.

Some mornings I'm debugging code. Some mornings I'm writing. Some mornings I'm just thinking through hard problems while staring at my screen.

The morning session ends around 7:00 AM when my sons (Jones and Jett—yes, it sounds like a law firm) wake up naturally. Then I'm 100% dad until they're off to preschool, then 100% engineer until they get home.

The evening session happens after they're in bed, but only if my wife is okay with it. Some nights she needs me present, not working. Learning to read those signals is more important than any business skill.

You can find two hours a day. The question is whether the people you love still feel like you're present.

The Long Game

Here's what most people get wrong: they think building on the side is playing it safe.

It's not. It's playing it smart.

You're using your job as the foundation, not the ceiling. You're building something meaningful without gambling your family's security. You're learning to work within constraints, which is a skill that serves you forever.

When your side project grows enough, you can flip the switch. But you flip it from a position of strength, not desperation.

Your job isn't the obstacle. It's the investor that doesn't take equity.

The invisible work matters. The 4:30 AM sessions count. What you're building in secret has its own reward.

You're not playing it safe. You're strategic.

---

Building something on the side? I'd love to hear about it. Hit me up on LinkedIn or email me directly. Sometimes we just need someone to tell us we're not crazy.