Founder Playbook · Starter Story

13 tactics from Nevo

Postiz$17K MRR

How I Built It: $17K/Month Open Source SaaS

Watch the full episode
Idea validation
I had so many failures in so many startups at first, and then I just paused and I said: okay, let's read some books — let's read about Traction for marketing, let's read about $100M Offers… and then I started to make smarter decisions.

Half your time learning, half building — that is how you stop picking bad ideas

Repeated startup failures usually come from jumping into ideas without understanding distribution. Pausing to study marketing, sales, and offer design — roughly half your time on learning, half on building — produces sharper idea selection and faster traction the next time around.

Shipping
Your GitHub becomes your landing page — that's your marketing landing page, so you should treat it the same as your main website. Create some issues on your GitHub repository for different features you want people to create for you.

Your GitHub README is your landing page — pre-seed beginner issues before launch

Before launching open source, the repo itself has to sell the project the way a marketing site would, with sharp positioning as an open-source alternative to a known tool. Pre-creating issues, picking a license, opening a Discord, and shipping a Docker image removes friction so contributors and self-hosters never bounce at setup.

Launching
Register on Hacker News, create a new post — just submit 'Show HN' and the name of the project — and then link to your GitHub repository, not your main website… if you put your open source project in there, there's a very high chance you will get into the main feed.

Show HN should link your GitHub repo — not your marketing site

Hacker News loves open-source projects but is picky about what gets promoted. Submit a Show HN that points directly to the GitHub repo rather than a marketing site, and a front-page slot can deliver roughly 10,000 views in a single day.

Launching
Make sure all these five steps are going on at the same week — that's very important, so you get into the main trending feed. Once you are there, you will see your star count rocketing very fast.

Fire every OSS channel in one coordinated week to crack GitHub Trending

The whole open-source launch strategy hinges on concentrating traffic into a single week to crack the GitHub Trending feed. Pre-register on Hacker News, Reddit, Lemmy, Dev.to, Medium, and Hashnode beforehand, then fire articles, a Show HN, an r/selfhosted post, and personal channels simultaneously.

Distribution
Open source is a way to introduce your project to millions of developers… thanks to open source, my app has been downloaded 5 million times.

Open source is a marketing channel — not a product strategy

Frame OSS as a distribution lever rather than a product choice. The same SaaS code is given away free to penetrate flooded markets, build brand, and pull in word-of-mouth from developers who would never have paid anyway.

Content
Dev.to, Medium and Hashnode — those channels are not only for SEO, they can bring you direct traffic… there's something called the Google Discover feed… this is the main traffic source for all of them.

Cross-post launch articles to Dev.to, Medium, and Hashnode for Google Discover traffic

Cross-posting launch articles to Dev.to, Medium, and Hashnode does double duty: SEO and Google Discover. Strong titles and cover images get articles surfaced in Discover, which becomes the top traffic source — bigger than direct or referral for most posts.

SEO
You can start to see a lot of blog posts around what you are building — so I see tons of SEO just from people writing about how to use Postiz or putting a review somewhere. There are also tons of options to list your product in different directories that have a very high domain authority.

Open source compounds SEO via dev blog posts and high-DA OSS directories

Open source produces compounding SEO for free: developers write tutorials and reviews on their own blogs, and dozens of high-DA OSS directories accept listings. Both feed organic search without any outreach effort from the founder.

Pricing
There is different open-source modules between companies, but for us there is no difference between the open source and the cloud offering. You can self-host Postiz — we put a lot of docs on how to self-host it.

Make the open-source and cloud versions identical — pay for convenience, not features

Resist the urge to cripple the self-hosted build with locked features. When OSS and cloud are functionally identical, customers pay for hosted convenience while the developer community trusts you. That trust is what drives word-of-mouth into the paid tier.

Onboarding
Make sure you have docs for developers to know how to deploy their project — this is super important. If they don't know how to deploy your project, they will just churn, they will not clone your repository. It's a lot better to create a Docker for your project.

A Docker image is the make-or-break for first-install activation in OSS

For open-source onboarding, deployment friction is the primary churn driver — if developers can't get the project running, they abandon it before starring or contributing. A Docker image collapses the first-install path to one command and turns deployment docs into a marketing asset.

Retention
We have 472 subscribers. We have a very high churn that we're trying to drop right now — 19%.

19% churn is the honest reality of an OSS SaaS — top of funnel doesn't save retention

Even a thriving $17K/month open-source SaaS with strong distribution is fighting 19% churn. Open source brings the top of funnel via stars, contributors, and word of mouth, but retention is a separate problem the brand still has to solve. The leaky bucket caps growth until churn drops.

Retention
You get tons of developers actually contributing to your product. I can't say it's making you more productive when people contribute — but it gives you tons of feedback and lets you find bugs much faster, iterate.

Contributors are the real retention flywheel — they find bugs paying users would churn over

Open-source contributors aren't valuable because they ship features faster — they're valuable because they surface bugs and feature gaps that paying users would otherwise churn over. They also become advocates inside their own companies, doing word-of-mouth selling to the non-developer buyers.

Mindset
Don't be afraid for somebody copying your product, because today the only thing that is winning, usually, is brand. I've seen so many people come and copy Postiz and self-host it somewhere as a totally different solution, just competing with me.

Don't fear copycats — brand is the only durable moat now

Code is no longer the moat — brand is. Competitors will fork your OSS and rehost it under a different name, then abandon those projects within weeks because they can't out-position the original creator. Build the brand around being the named source of the project.

Bootstrapping
The margins is around 80%.

Run a $17K MRR OSS SaaS at 80% margins on Railway, Vercel, and Cloudflare

A small open-source SaaS can hit 80% margins on Railway + Vercel + Cloudflare R2 + Resend with everything else on OSS-tier free tools. The biggest single line item tends to be AI inference — around $600/month for Postiz — and the rest is small, off-the-shelf, and unfunded.