DEV Community

szokker
szokker

Posted on

I’m Trying to Pay My Car Insurance With an Automated Website

A few months ago I had a simple idea.

What if I could build a small technical website that runs mostly on automation… and eventually makes just enough money to cover one monthly expense?

Not rent.
Not financial freedom.
Just my car insurance.

€67 per month.

That’s it.

The Build Phase

I started building TutorialsHub as a multilingual technical tutorial site (English, Dutch, French).

At first it was messy:

  • Triple-language routing bugs
  • Content formatting breaking refresh
  • YAML indentation issues
  • Search not working
  • Language switch not updating content

Every fix felt like progress.

I automated content generation with Python.
Fixed the formatting pipeline.
Structured the folders properly.
Cleaned up the deployment.

It slowly stopped feeling like a “project” and started feeling like a system.

The Real Goal

Not “passive income guru lifestyle”.

Just this:

If the site can generate €67/month from ads,
it pays for my car insurance.

Which means:

My website pays for a real-world expense.

Code turns into something tangible.

The project becomes an asset.

At an estimated €10 RPM, I need around 6,000–7,000 monthly pageviews.

That’s not crazy.
That’s achievable.

Where It Is Now

  • 1. - Multilingual structure works
  • 2. - Automated publishing works
  • 3. - SEO slowly kicking in
  • 4. - Some pages already ranking

Now I’m in the polish + distribution phase:
Fix UX.
Improve search.
Engage in communities.
Write better tutorials.

I’ll update this post when the insurance is officially paid by traffic.

€67/month.

That’s the milestone.

If you’re curious about the journey, want to see how I’m structuring the automation, or just want to follow the experiment — feel free to check it out and give honest feedback.

And I’m genuinely curious:

What’s the smallest “real-world expense” you’d like your side project to cover?

Coffee?
Gym membership?
Hosting costs?
Something bigger?

Let’s see how many of us are quietly trying to make our code pay for something tangible.

Top comments (0)