The start: a developer annoyed by tracking
Simple Analytics' about page says the product started in September 2018, when Adriaan van Rossum, a developer in the Netherlands, grew frustrated that analytics tools needed cookies, IP addresses or fingerprints to count pageviews. He built the first version alone as a lightweight script that shows website owners what they need without tracking individuals. The company now describes the script as under 5 KB and the product as cookie-free, which it argues removes the need for an analytics cookie banner.
Sources: [1]
The second founder came to sell, not to build
The same page says that in 2022 Iron Brands joined as co-founder to lead marketing and growth, and Alex (Aleksandar Ivanov) joined to strengthen engineering. The company lists three people. The timing matters: the product existed for about four years before a dedicated marketing lead arrived. The page does not report revenue before or after that change, so we cannot measure its effect. Editorial inference: a technical solo founder can reach a working product alone, but distribution may need its own owner once the product is stable.
Sources: [1]
The offer: a free hobby plan with a visible badge
Simple Analytics' pricing page, checked October 18, 2026, shows a paid plan from $20 per month at 100,000 pageviews, with one user included and $20 per month for each extra user. A free plan for hobby sites keeps one month of history and requires a public badge. The badge turns free sites into small advertisements, and the one-month history limit gives a growing site a reason to upgrade. These are product design choices visible on the page; the company does not publish how many free sites convert.
Sources: [2]
What the numbers say and do not say
The about page lists "31k+" users, describes the company as self-funded and profitable, and names well-known organizations among its users. These are company statements. A user count does not tell you how many pay. The catalog revenue entry for Simple Analytics is an approximate public figure; read it with its date and method. Editorial analysis: the lesson here is about sequencing and constraints—small team, EU hosting, a single clear privacy promise—rather than a growth curve.
Sources: [1]
The harder question: what does a small team choose not to build?
The company positions its product around a small set of understandable numbers—pageviews, referrers, campaigns and events—rather than individual visitor profiles. That constraint can keep both the interface and support workload smaller. It also means some customers who want detailed identity-level tracking will choose another tool. Editorial inference: define an explicit non-customer as carefully as an ideal customer. A three-person team can preserve focus if it knows which requests conflict with its privacy promise. Before accepting any new analytics feature, write down what data it requires, who will maintain it, and whether it makes the dashboard clearer.
How a three-person vendor reduces buyer risk
Large organizations often hesitate to buy from a very small vendor. Simple Analytics' about page addresses that directly: it publishes the legal entity (Simple Analytics B.V. in Amsterdam), its Chamber of Commerce registration and VAT number, says data is hosted on European-owned servers in the EU, and lists organizations such as Bloomberg, Michelin, GOV.UK and the Bank of England among its users. Editorial inference: a small company can make procurement easier by publishing exactly the details a legal or security reviewer will ask for. That costs little and removes a reason to choose a larger competitor.
Sources: [1]
Experiments you can run
Small, falsifiable tests inspired by this case. They are MRRTrace suggestions, not steps the company reported.
Badge on the free plan
- Do
- Require a small "powered by" badge on free accounts and link it to a tagged signup page.
- Measure
- Signups per month that came from badge links.
- Stop if
- Remove the requirement if it causes more free-user churn than the signups it brings.
Give distribution an owner
- Do
- Assign one person (founder, contractor or partner) 90 days to own marketing with a weekly written report.
- Measure
- Trials and paid conversions before versus during the 90 days.
- Stop if
- End the arrangement if paid conversions do not rise after 90 days.
Timeline
What to take into your next build
- A product can be built by one person; distribution may still need a second owner.
- Limiting history rather than features gives free users a natural reason to upgrade as their site grows.
- Report users and paying customers separately.
Takeaways are MRRTrace editorial inferences.
Sources
- Simple Analytics company history and team
- Simple Analytics pricing and free plan
- Simple Analytics product overview
This case study combines cited public information and editorial analysis. Outcomes from an established business do not prove that a new entrant can repeat them.
