On June 2, 2022, a privacy-focused web analytics tool called Plausible crossed $1,000,000 in annual recurring revenue. The company had no investors, no sales team, and had never bought an advertisement. Three years earlier, in May 2019, its first month of paid subscriptions produced $64.
Those numbers come from Plausible's own public recap, How we built a $1M ARR open source SaaS, published on June 22, 2022. The company was established in December 2018 by Uku Taht, and for its first fifteen months it was one person. What follows is the part worth studying: not that content marketing worked, but the specific shape of the content that worked, and how long it took before anything happened at all.
The 324 days when nothing moved
Plausible's first paying subscriber signed up on May 14, 2019. According to the company's $500k ARR retrospective, it then took 324 days to reach $400 in monthly recurring revenue. That is close to eleven months of building, writing, and shipping for less money than a phone contract.
The ladder from the company's published figures looks like this:
- May 2019: $64 MRR
- September 2019: $178
- February 2020: $403
- April 2020: $607
- June 2020: $1,767
- September 2020: $5,035
- December 2020: $8,999
- January 2021: $11,303
- October 2021: $42,624 (the $500k ARR mark)
- April 2022: $76,312
- June 2022: $83,637 (the $1M ARR mark)
Read that ladder backwards and the interesting fact jumps out. The distance from $64 to $400 took almost a year. The distance from $400 to $1,767 took roughly four months. Something changed in the spring of 2020.
The post that changed the slope
On April 8, 2020, Plausible published an article titled "Why you should stop using Google Analytics." In the company's own account, it was read by more than 50,000 people within days and produced 166 new trial signups in its first week. Marko Saric, who had joined that March and made the team two people, put it plainly in that retrospective: "One single blog post changed the traction of our startup."
It is tempting to file this under luck. Look at what the post actually was, though, and a repeatable pattern shows up.
The article was not about Plausible. It was about Google Analytics: what it collects, what that means for the people visiting your site, and why a site owner might want out. The product appeared at the end as one available answer. That is the entire mechanism. The post was useful to someone who had never heard of Plausible and never intended to switch analytics tools, which is exactly why it travelled.
The same shape repeats through the company's traffic events. A post called "How to pay your rent with open source" drew more than 35,000 visitors. "Google AMP is dead!" drew more than 35,000 readers. "How to fight back against Google FLoC" drew more than 16,000. An original study finding that a large share of Hacker News visitors block Google Analytics drew more than 30,000 readers in 24 hours and, per Plausible's recap, doubled trial signups.
Three of those five are about someone else's product. One is original research. None of them is a feature announcement. If you have been treating your blog as a changelog, that is the gap.
Where the posts were published matters as much as what they said
Writing a good post is half the machine. The other half is that Plausible submitted its work to Hacker News, Indie Hackers, and similar communities where the audience was already arguing about tracking, privacy, and Google. The company did not build an audience first and then sell to it. It borrowed audiences that already existed, repeatedly, with material those communities wanted to read anyway.
This is the same pattern we found when we looked at where first customers actually come from: warm networks and public conversations already in progress, not launches into silence. It is also why we argue that distribution is the real moat for small software companies. Plausible's product was competent, but so are dozens of analytics tools you have never heard of.
One more structural choice compounded the effect. In October 2020 Plausible put its source code under the AGPL license. Open source gave technical readers a reason to link, fork, discuss, and self-host, and it gave the company a permanent presence on GitHub, a place its buyers already spend time.
The two accelerants they did not create
Honesty about this story requires naming what was outside the founders' control, because the steepest part of the curve had help.
Plausible's own recap lists the 2022 catalysts: in January, the Austrian data protection authority ruled that a website's use of Google Analytics violated the GDPR; in February the French authority reached a comparable conclusion; and in March, Google announced it was retiring Universal Analytics with no import path into GA4. European site owners suddenly had both a legal reason and a migration deadline.
What Plausible did with that is the coachable part. In April 2022 it shipped a Google Analytics import tool, removing the single largest objection to switching at the exact moment the largest number of people were considering it. Preparation met an event. The event was luck. Being ready to answer "but I would lose my history" within weeks was not.
The economics underneath
The reason a $400 month did not kill the company is that its costs were close to nothing. There were no salaries to fund for the first stretch. Plausible's retrospective notes the founders went months without paying themselves and worked through more than $50,000 of personal savings. Headcount reached two in March 2020, three in June 2021, and four in February 2022, well after revenue justified each hire.
That is what makes a slow curve survivable. A funded competitor with six salaries and a paid acquisition budget cannot spend 324 days getting to $400. Plausible could, and the freedom to be patient was the actual advantage of being self-funded. As Saric put it in the $500k recap, "The best thing about being bootstrapped is that we don't waste any time obsessing over investors and their wants." We have written before about why the one-person software company is finally viable; this is a worked example of the cost structure that makes it so.
Plausible's about page now describes a team of 10 and more than 20,000 paying subscribers, including Basecamp, Ghost, Hugging Face, MongoDB, the Python Software Foundation, and Harvard University, with the company still self-funded and profitable.
What you can copy, and what you cannot
Copyable: writing about the problem instead of the product; publishing original data your competitors have not measured; submitting to communities where your buyers already argue; removing the biggest switching objection with a migration tool; keeping a cost base low enough that a year of flat revenue is a nuisance rather than an ending.
Not copyable: two European regulators questioning your largest competitor's legality in the same quarter, and that competitor forcing every user through a breaking migration two months later. Also not copyable on demand: a post reaching 50,000 people. Plausible published for months before one landed, and the company's traffic events show several posts of similar quality that produced ordinary numbers.
The honest summary is that Plausible built a machine that could convert a lucky moment, then waited long enough for one to arrive. The waiting was the strategy. Most people quit at day 200 of the 324.
Figures in this article are from Plausible's published recaps at $500k and $1M ARR and from the company's about page, checked July 25, 2026.
Discussion
Sign in with Google or just a name. No email link, no password to remember.