How I Shipped 9 Products While Freelancing Full-Time

People ask me how I ship products while freelancing. The short answer: systems and ruthless scope management. The longer answer is this post.

The problem with building and freelancing simultaneously

When I started freelancing, I had zero products. I was 100% dependent on clients for income. That's fine - but it's also fragile. One slow month and your bank account has opinions about your choices.

The instinct is to work more client hours. But the answer is to build something that earns while you sleep.

The hard part: freelancing is exhausting. By 6pm, the last thing you want to do is open another code editor. I know this feeling well.

What changed for me: the 3-hour rule

I stopped trying to build in the evenings. Instead, I blocked 3 hours every morning - before client emails, before Slack, before anything. My most creative and focused hours, reserved for products.

This sounds obvious. It's harder than it sounds. But it changed everything.

The product portfolio: what I built and why

DocxToWP - the product I needed myself

I was copy-pasting client content from Word docs into WordPress every week. It was soul-destroying. I built DocxToWP to solve my own problem, published it on WordPress.org, and added a $19 Pro version.

1,000+ installs later, it still earns passively.

Lesson: Build tools for problems you personally have. You'll have better instincts for the product, and you'll use it yourself which means you'll maintain it.

SnapshotGo - scratching the developer itch

I took screenshots constantly for documentation, tweets, and client reports. CleanShot was great but expensive. I built SnapshotGo as a cross-platform alternative.

2,400+ users across Chrome, Windows, Mac, and Linux. Charged $9.99 lifetime.

Lesson: "There's already a paid tool for this" is not a reason to not build it. There's room for a cheaper, simpler, or more focused alternative in almost every category.

MilestoneGlow - the audience problem

This was the product I built for other builders. Celebrating MRR milestones and follower counts with cinematic animated videos. Found the audience first (indie hackers on Twitter), then built.

Lesson: Know who you're building for before you write a line of code.

The shipping process I use for every product

1. Week 1: Define the one core action. What does the user do? What's the output?
2. Week 2: Build the ugly version that does exactly that one thing.
3. Week 3: Make it not ugly. Add the landing page.
4. Week 4: Charge for it. Even $5. Get one paying customer.

Anything beyond week 4 is either growth work or a new feature driven by user feedback - not speculation.

What failed

Not everything worked. I have three products with under 50 users. The common thread: I built features I thought were cool, not features users explicitly asked for. Classic mistake. Still make it sometimes.

The mindset shift that matters

Freelancing and building are not opposites. Freelancing funds the building. Building reduces dependence on freelancing.

Once you have even one product earning $200/month, your relationship to client negotiations changes completely. You can say no to bad projects. You can take a week off without anxiety.

Start small. Pick the smallest possible problem. Ship something, however rough. Charge for it. Iterate.

That's it. That's the whole strategy.

If you're a founder who wants that same shipping speed applied to your own product, that's exactly what I offer through SaaS MVP development - full-stack builds from idea to deployed.