How to build a SaaS product while working a full time job is one of those things that sounds completely reasonable until you actually try it. Everyone has a side project idea. Very few people ship one. And the reason is almost never lack of skill or even lack of ideas. It is lack of time, energy, and the discipline to use whatever scraps of both you have left after your day job has wrung you out.
I have done this three times now. CampSuite, Crocodile, and Lavida all started as side projects while I was doing consulting work. Every one of them reached paying customers before I went full time on them. Here is what I learned about making that work, and what nearly broke me along the way.
Stop planning and start building
The biggest trap side project founders fall into is spending months refining their idea before writing a single line of code. You do not need a business plan. You do not need market research. You do not need a domain name, a logo, or a brand identity. You need a working prototype that solves a real problem for a real person.
When I started CampSuite, I spent exactly one weekend building the first version. It looked terrible. It barely worked. But it could take a booking and record a payment, which was the only thing a campsite owner actually needed. Everything else came later, after I had proven that someone would pay for it.
If you have been thinking about your side project for more than a month without shipping anything, you are procrastinating. That is not me being harsh. That is me telling you what I wish someone had told me before I wasted three months designing a logo for a product that did not exist yet.
Protect your mornings or your evenings, not both
When you are working a full time job and building on the side, you have roughly two to three hours a day to work on your product. Maybe four on a good day. That is it. You cannot sustainably work twelve hour days for months on end. I tried. I burned out so badly that I did not touch code for three weeks. That is three weeks of momentum lost because I thought I was invincible.
Pick your slot and defend it. For me it was mornings. I would get up at half five, work on the product until eight, then start my consulting work. Some people prefer evenings after the house has gone quiet. Either works. What does not work is trying to do both every day. You will last about a fortnight before your body or your relationships give out, and probably both.
Weekends are your secret weapon, but only if you use them wisely. I would block out Saturday mornings for the big features that needed focus time. Sunday was off. Completely off. No code, no customer emails, no thinking about the product. That recovery time is not optional. It is what makes the rest of the week possible.
Ship small, ship often
When you have limited hours, the worst thing you can do is spend three months building a feature before anyone sees it. Ship something small every week. A new form. A bug fix. An improved onboarding step. Each small release teaches you something and keeps your momentum alive.
I have written about validating business ideas before building and the same principle applies here. Every hour you spend building something nobody asked for is an hour you did not spend on the thing that would actually get you a paying customer. When your time is scarce, ruthless prioritisation is not a luxury. It is survival.
The other benefit of shipping small is psychological. When you only have a few hours a day, finishing a big feature feels impossible. Finishing a small improvement feels great. That sense of progress is what keeps you going through month four when the excitement has worn off and it feels like you are pushing a boulder uphill.
Your day job is funding your startup, treat it that way
A lot of people feel guilty about working on a side project while employed. Get over that quickly. Your job pays your bills, feeds your family, and means you do not have to take investment money or go into debt to build your product. That is an enormous advantage.
I was earning good money as a Dynamics 365 consultant while building CampSuite on the side. That meant I could be patient. I did not have to chase revenue from day one. I could build the product properly, find the right customers, and wait until the numbers made sense before making the leap. Founders who quit their jobs first and build second are under constant pressure to monetise before the product is ready, and that pressure leads to terrible decisions.
The key is to be honest and professional about it. Do your day job well. Do not work on your product during work hours. Do not use your employer's resources. And check your contract for any intellectual property clauses that might cause problems later. I have seen founders lose ownership of their side projects because they did not read the IP assignment clause in their employment contract. Spend an hour with a solicitor if you are not sure.
Know when to make the leap
The hardest part of building a SaaS while employed is knowing when to go full time. Too early and you run out of money. Too late and you burn out from doing both.
My rule was simple. When the product was generating enough monthly recurring revenue to cover my basic living costs for six months, I would make the switch. Not enough to match my consulting income. Enough to survive. There is a difference, and waiting for income parity means you will probably never leave.
With CampSuite, that took me fourteen months to get there from the first line of code. During those fourteen months I nearly quit the project at least four times. The thing that kept me going was watching the revenue graph move, even slowly, in the right direction.
If you want a deeper framework for going from idea to launch on a tight timeline, that is exactly what The 28 Day Startup covers. The principles work whether you are building full time or carving out hours around a day job.
The stuff nobody warns you about
Your social life will take a hit. There is no way around this. If you are spending your mornings and Saturday mornings building a product, something else has to give. For me it was television, pub trips, and about six months of being fairly boring at dinner parties. That is a trade worth making, but be honest with yourself and the people around you about what you are signing up for.
Your product will be worse than you want it to be for a long time. When you are building part time, everything takes three times longer than you think it will. Features that would take a full time developer a week will take you a month. That is fine. The point is not to build a perfect product. The point is to build a product that is good enough for someone to pay for.
And finally, you will feel like a fraud. Every successful founder I know felt like they were pretending during the side project phase. You are not a real startup founder because you still have a day job. Your product is not a real product because it only has twelve customers. That voice in your head is wrong. A product with twelve paying customers is more real than ninety percent of the startups that raised millions and shipped nothing.
Just start
The best time to start building your SaaS was six months ago. The second best time is tonight, after dinner, with a cup of tea and a blank code editor. Pick the smallest possible version of your idea, build it, and put it in front of someone who might pay for it.
Everything else comes later. The branding, the marketing, the scaling, the quitting your job. Right now you just need to start. And if you need help figuring out where to begin or how to structure your approach, get in touch about consulting. I have been exactly where you are, and I am happy to point you in the right direction.
