I build VaultBay after the 9-to-5 and on weekends.
That's it. Not some fake "I grind every morning from 4 AM to 8 AM" schedule. Not hustle-porn screenshots and caffeine-fueled nonsense. I work a 9-to-5 Monday through Friday, I've got a one-year-old, and when life gets loud, those evenings and weekend hours can shrink fast.
So if you're building something while working full-time too, here's the honest version.
The Constraint Is the Whole Game
A lot of startup advice quietly assumes you have one thing: time.
Open your laptop whenever. Take a random Tuesday afternoon to rethink pricing. Spend six straight hours rebuilding onboarding because you got a new idea. That sounds nice. It's also not how this works when you've got a job, a family, and an actual life attached to your calendar.
When you've only got a handful of real build hours a week, every bad decision gets more expensive. A pointless refactor doesn't just waste an evening. It burns a fifth of your week. Chasing a feature you don't actually need can cost the entire window you had to ship something meaningful.
That changes how you build.
I don't get to ask, "Would this be cool?"
The only question I get to ask: is this worth one of tonight's two hours? That's a much better filter.
Progress Looks Smaller From the Outside
This is the part social media usually ruins.
You see someone posting daily changelogs, shipping three features a week, launching side products on the weekend, and it can make your own progress feel slow. But a lot of that comparison breaks the second you look closer. Different life stage. Different obligations. Different runway. Sometimes different honesty.
My reality is simpler. Some weeks I get one feature done. Some weeks I fix bugs, clean up UX, and write notes for the next sprint. Some weeks I spend half a day stuck on something stupid and annoying because software loves doing that.
And honestly? That's still real progress.
VaultBay doesn't need cinematic founder energy. It needs steady work. A better flow for logging mods. A cleaner way to track detailing products. More clarity around pricing. One actual improvement at a time.
That's slower than the internet likes. It's also how things actually get built when your schedule is real.
You Need a Smaller, Sharper Scope
I think this is where most part-time builders break themselves.
They plan like a full-time team and execute like a tired person with 14 open tabs and 90 minutes before daycare pickup.
That mismatch will crush you.
Working on limited time forced me to get a lot more aggressive about scope. For VaultBay, that means I keep coming back to the core use cases:
- track mods in one reliable build log
- log detailing products without guessing later
- make records searchable when I actually need them
- give car people a tool that feels built for them, not adapted from generic software
That's the product.
Not twelve adjacent ideas. Not every feature request that sounds interesting for five minutes. Not some giant ecosystem diagram that makes me feel productive without shipping anything.
If I've got two hours after the kid's down, I want them landing on something users will feel.
The smaller the time window, the more brutal you have to be about what matters.
Systems Beat Motivation Fast
Motivation is nice. It also disappears.
What helps more is having a system simple enough that tired-you can still use it.
Mine is boring on purpose. I keep a short list of current priorities. I write things down while I'm in the middle of them so I don't waste the first hour of the next session trying to remember what I was thinking. I try to end a session with the next move obvious.
Because context switching is brutal when you build part-time.
If tonight starts with, "Wait, where did I leave this?" you've already lost momentum. If it starts with, "Finish Bay scan results, clean up pricing copy, test mobile layout," you're moving in the first 10 minutes.
That's a huge difference when your whole week might only contain 10 real build hours.
This is also why I'm building in public. Not for clout. Not to cosplay as a founder. It keeps me honest. It creates a record. It makes the work visible enough that I can't lie to myself about whether I'm actually shipping.
The Tradeoff Is Real, but So Is the Upside
Would VaultBay move faster if I had 40 focused hours a week for it? Obviously.
I'd write more code. I'd test more ideas. I'd probably break more things too.
But building it this way has one big advantage. It filters out fluff fast.
When time is scarce, you stop pretending every idea deserves a sprint. You get practical. You build around reality. You learn how to make progress without waiting for the perfect season of life to magically appear.
And I think that's more useful than people admit.
A lot of good products probably die because their builders think limited time means they shouldn't start. I don't buy that. Limited time just means the process has to be tighter. The scope has to be cleaner. Your ego has to calm down a little.
You don't need a founder fantasy. You need a system you can keep.
What's Next
I'm still building VaultBay on the same nights and weekends. Still tightening the product. Still cutting what doesn't matter.
No hype. Just the actual work.
If you're building something while working full-time too, I get it. It's slower than you'd like, but slower isn't the same as stalled.
If you're a car person who wants a better way to track mods, products, and the real history of your build, follow along at thevaultbay.com.