The Time Myth
Founders with day jobs or families tell themselves the same story: "I will start when I have more time." That moment never comes. The founders who ship are not the ones with empty calendars. They are the ones who learned to build inside the cracks of a full life.
Five hours a week is enough. Ten is generous. The problem is not time. The problem is scope.
The Ruthless Scope Plan
Your first version is not a product. It is a test. A single interaction that proves someone cares. Everything else is decoration.
Cut to One Core Loop
An MVP, or minimum viable product, is the smallest thing you can ship that delivers value to one user. Not a platform. Not a suite. One thing that one person does once.
- Stripe started as a payment form. No dashboard, no analytics, no subscriptions. Just a way to charge a card.
- Dropbox started as a folder that synced. No sharing, no teams, no paper. Just files that stayed in sync.
- Your MVP should be one action and one outcome. A form that sends an email. A page that ranks something. A calculator that gives one number. If it takes more than two sentences to explain, it is too big.
Use the Tools That Remove Decisions
Every decision you make about tools is time you are not building. Pick the boring, popular option. It exists for a reason.
- Frontend: Next.js or a no-code builder. Not because they are perfect, but because the tutorials exist and the community is huge.
- Backend: Supabase or Firebase. You get auth, database, and API in one setup. No custom server needed.
- Payments: Stripe. One integration, done in an afternoon.
- Hosting: Vercel or Netlify. Push to Git, it is live. No DevOps.
The goal is to eliminate setup time. You should be writing product code in hour one, not hour ten.
Pre-Built Over Custom Every Time
If someone else already built it, use it.
- UI: Use a component library like shadcn or Tailwind UI. Your buttons do not need to be unique.
- Auth: Use OAuth. Google login, GitHub login. Do not build your own password system.
- Email: Use Resend or SendGrid. Do not write an SMTP server.
- Analytics: Use Plausible or PostHog. One script tag, done.
Custom code is a luxury you cannot afford at 5 hours a week. Ship with off-the-shelf parts. Replace them later if the thing actually works.
The 5-Hour Week Schedule
Here is how to actually use those hours. Not aspirational. Just practical.
Hour 1 to 2: Build the core interaction. The one thing your user does. The form, the button, the calculation. Make it work locally. Do not style it. Do not add error handling for edge cases. Happy path only.
Hour 3: Connect the data. Store the input. Send the email. Save the result. Whatever your backend needs to do. Again, happy path. If the user types a emoji and it breaks, that is a problem for week three.
Hour 4: Make it live. Ship it to Vercel. Connect your domain. Test it on your phone. If it works on your device, it is live enough.
Hour 5: Show one person. Not your mom. Not your co-founder. One person who has the problem you are solving. Watch them use it. Do not explain. Do not defend. Just watch. Write down where they get stuck. That is your week two roadmap.
Repeat this cycle. Week two is fixes and the next tiny feature. Week three is polish only if people are actually using it. If no one is using it, do not polish. Talk to more people.
The Mindset Shift
The founders who ship with no time have one thing in common. They treat their side project like a job, not a hobby. They schedule the hours. They protect them. They do not "find time." They make it.
This means saying no. No to Netflix on Tuesday night. No to the feature that would be cool. No to rebuilding the whole thing because you learned a new framework. Every hour you spend is a loan against your sleep, your family, your sanity. Spend it on things that move the needle.
The other shift is accepting embarrassment. Your first version will look rough. That is the point. If it looks polished, you spent time on the wrong things. Ship ugly. Perfect is the enemy of launched, and launched is the only thing that matters when you have 5 hours a week.
What to do today
- Write down your one core loop. One action, one outcome. If it takes more than two sentences, cut it in half. Then cut it again.
- Pick your stack in 10 minutes. Set a timer. Choose the boring, popular tools. No research spirals. No framework debates. Done is better than optimal.
- Schedule your 5 hours. Block them on your calendar like a meeting you cannot miss. Protect them like you protect your job. Because this is your job, even if no one is paying you yet.
Share what you shipped in the 52Waypoint community. Your next co-founder is already there.