I bought a domain name in .lol

Yes, I know what you think about it.

But it gets worse — I pushed the joke far enough to turn it into a real site.

With a real tagline, a real design, a voting and view system, an admin backend, CDN storage, advanced SEO, etc.

The obvious date to publish it being April 1st, here is mysaas.lol, a site entirely dedicated to SaaS founder memes.

Is it going to make money?

Which is still the central question for a SaaS creator...
The site being free, that's answered pretty quickly.

We can take comfort in the fact that it's a tool I'll use myself, and that every visitor will potentially see the link to mysaas.coach, which is monetized.

Is it going to cost me money?

That's the beauty of having your own self-hosted infrastructure — apart from the domain name, an additional website costs me nothing extra in cash outflow, my fixed costs don't move.

Obviously there's the time spent, but overall I learned more than I would have by following a YouTube tutorial. The whole OG media part (the thumbnail of your website page that shows up on Twitter/LinkedIn) — it's only by practicing and testing it 20 times that you understand the subtleties.

The breather

It feels good to work on a project with a single, fairly simple feature.

And to be able to push the original idea to a stable version in just a few days, unlike the other projects I have going on, which are a near-endless list of GitHub tickets.

Continuous improvement

Probably the most important point.

I currently have 9 published SaaS products and their technical foundation is identical, based on that of comidoc.com, which is technically the most advanced and refined.

You wouldn't think so for a coupon site, but the mechanics behind it are very sophisticated. It's the oldest (2018) of my projects, now on its 6th from-scratch rewrite, including 4 back in the days when you still typed every line of code yourself...

Put another way, it has seen and tested everything, from Prisma 1.32 to Prisma 7.6, from Express/Mongoose to NextJS 16.2/Postgres.

As soon as a new library comes out, it's the ideal candidate — it has traffic, data volume, a super advanced internal logging system (sse), and it covers all the necessary aspects (payment, email tracking, jobs, queues, search, AI, auto-publishing to Twitter/Telegram, ...).

And every new site put into production starts from this base, like a boilerplate, with modules you pick and choose. It's very comfortable. No surprises.

As a result, the brain is free to iterate on minor improvements — renaming variables for greater consistency/uniformity, pixel-perfect tweaks on elements that are already pretty good, optimizations you run precisely because you don't have a big thing to manage on the side.

These changes are then documented in .md files (the why, the how, the pitfalls, the sources, ...) and Codex then takes care of individually updating the other projects so that we're all on a consistent base.