How I built 11 products in 12 months while employed: the real 14-18 hour weekly schedule, the €3,250 total cost, the sacrifices, and what I'd do differently.
I built 11 products in 12 months while working a full-time corporate job — roughly 750 hours of building time at 14–18 hours a week, for a total cost of €3,250. I was 45, over 20 years into a corporate career, and not a developer. Here's the real schedule — the actual hours, no romanticizing.
People hear "11 products in 12 months" and imagine a caffeine-fueled 22-year-old coding 18 hours a day, no family, no mortgage. That's not what happened. I had a senior role, a salary I'd spent years building up to, and golden handcuffs I'd worn so long I almost forgot they were there. I had the same 24 hours as everyone else — and most of them already belonged to someone else's company. What I didn't have was time to waste. So I didn't waste any.
The setup nobody sees: three weeks of planning
Before I built a single thing, I spent three weeks doing something that felt like nothing: planning. I mapped out every product I wanted to build. I sequenced them by dependency — which products needed to exist before others could work. Then I did the math on my time budget: 5 weekday mornings of 2 hours each, plus one 4-hour Saturday block — 14 hours minimum, 18 on a good week, with Sunday completely off, non-negotiable. That's roughly 700–900 available hours per year.
That was my budget. Every product had to fit within it. Every feature had to earn its place — there was no room for "nice to have." If you're a corporate professional thinking "I don't have time to build something": you have 700–900 hours a year hiding in your margins. That's not nothing. That's a business. This constraint was the best thing that ever happened to my building process.
The weekly rhythm
The daily engine is the 2-hour rule. Here's what an average week actually looked like:
| Time | Monday–Friday |
|---|---|
| 5:00 AM | Wake up. Coffee. No phone. |
| 5:15 AM | Sit down. Open one project. Build. |
| 6:45 AM | Wrap up. Commit code. Write tomorrow's task. |
| 7:00 AM | Shower. Breakfast. Become corporate. |
| 7:30 AM – 6:00 PM | Day job. Full engagement. No side-project thinking. |
| 6:30 PM | Dinner. Family. Rest. |
| 9:00 PM | 30 min max: customer emails, analytics, planning. |
| 10:00 PM | Sleep. |
Saturday: one 4-hour deep work session, 6:30–10:30 AM — this is where the big pushes happened. Sunday: nothing. Zero. Read a book, go for a walk, let your brain recover. And yes, the day job got my full engagement — the meetings are boring and you're making someone else rich, but you're not ready to leave yet, so you give them your best until you are.
The first three months felt like nothing was happening
Here's what nobody posts on LinkedIn. I was building infrastructure: authentication, databases, backend logic users would never see. Three months of 5 AM mornings and I had nothing to show anyone — nothing to prove I wasn't crazy. This is where most corporate professionals quit. You're used to quarterly reviews, measurable KPIs, visible progress. In corporate, if three months pass with nothing to show, someone gets fired. But building isn't corporate. The rules are different.
Month 4 is when things started to click. The foundational work paid off, and products started coming together faster because the infrastructure was in place. What took 3 months for product one took 3 weeks for product four. That's the compound effect of consistent building: the early investment feels wasteful. It isn't. It's the runway for everything that follows.
How I sequenced 11 products
- Phase 1 (months 1–3): core infrastructure. One product — the foundational platform. Authentication, user management, database schemas, deployment pipeline. Unglamorous but essential.
- Phase 2 (months 4–6): first revenue products. Two products that could generate revenue quickly. Minimal features, ugly interfaces — but they worked, and people paid. Revenue, even small amounts, is the greatest motivator in the world.
- Phase 3 (months 7–9): ecosystem products. Three products that leveraged the existing infrastructure. Each one took less time because it stood on the shoulders of what already existed.
- Phase 4 (months 10–12): integration and polish. Five more products, plus connecting everything into a coherent ecosystem. By this point I could ship a new product in 2–3 weeks.
Total investment: roughly €3,250. Total value: over €2M in estimated software replacement cost. Not because each product was revolutionary — because the ecosystem, together, solved problems that would otherwise require a dozen separate SaaS subscriptions. And because 20 years of understanding how businesses actually work meant I was solving real problems, not imaginary ones.
The sacrifices (being honest)
Social life: nearly zero for 12 months. Friday nights were for sleep, not drinks. Television: almost nothing for a year — not discipline, just no hours left between a 10 PM bedtime and a 5 AM alarm. Exercise: shifted to lunch breaks and weekday evenings. Not ideal, but I never stopped — stopping would have been the beginning of the end. Energy: in weeks when the day job was intense, my 5 AM sessions were shorter and less productive. I learned to accept this instead of beating myself up.
And the guilt — the one nobody mentions. The guilt of being at your laptop at 5 AM while your partner sleeps, of spending Saturday mornings building instead of being present. My partner was supportive, but support doesn't eliminate guilt. It just makes it bearable.
What I'd do differently
- Validate harder before building. Two of my 11 products haven't gained traction — about 100 hours of 5 AM mornings spent on something nobody wanted. I should have talked to more people before writing code.
- Use AI from day one. I started before the current generation of AI coding tools matured. Today, those 500+ hours could probably be 300 hours with AI assistance — the entire tool stack now costs €340 a month, and for non-technical builders AI has removed the biggest barrier entirely. You don't need a developer or a technical co-founder anymore. Just don't confuse speed with strategy — AI without direction creates garbage.
- Take more Sundays off. I sometimes "just checked one thing" on Sundays. Every time, the one thing became two hours, and Monday started more tired. The Sunday boundary exists for a reason.
The numbers that matter, after 12 months of building while employed:
- 11 products shipped and live
- ~750 hours of total building time
- €3,250 total cost
- €2M+ in estimated software value
- Zero days of missed work at my day job
- Zero times my employer found out (until I was ready to tell them)
This isn't a flex. It's a data point: one non-technical corporate professional, limited hours, significant constraints, real results. Not everyone can do this — if you have a newborn, the schedule changes; if your day job demands 12 hours, the margins are too thin. But if you have 2 hours a day and the willingness to be uncomfortable for a year, the math works. The average age of a successful first-time entrepreneur is 45 — right in the sweet spot of corporate professionals with decades of domain expertise, finally ready to use it for themselves. And you don't quit on faith: you build first, then quit when your number says you're ready.
Frequently asked questions
How many hours does it take to build products while working full-time?
My 11 products took roughly 750 hours over 12 months — 14–18 hours a week from weekday 5 AM blocks plus one 4-hour Saturday session. With today's AI tools, the same output would likely take meaningfully less.
Do you need to be a developer to do this?
No. I'm not one — business background, 20 years of corporate domain expertise. AI and no-code tools have removed the technical barrier: you don't need a developer or a technical co-founder, you need to know what to build and the discipline to show up every morning.
How much does it cost to build while employed?
My total was €3,250 for the entire 11-product ecosystem, paid out of a normal salary — no funding, no equity given away. The failed experiments cost time, not money: about 100 hours on two products nobody wanted.
Should I quit my job to build faster?
No. I missed zero days of work and kept full salary and benefits for the entire build. The whole point of building while employed is that failure costs you nothing existential — you quit from a position of strength, when the side income proves itself.