Founder stories
A code-first synthetic monitoring and API monitoring platform for developers.
How Tim acquired customers
Tools used to build Checkly
Tim Nolet built Checkly part-time, used a private beta plus open-source Puppeteer Recorder to reach developers, and crossed roughly $1,100 MRR by pairing technical content with early-adopter discounts.
Tim Nolet started Checkly after living through the pain of broken signups, sales funnels and API endpoints at a German electric-mobility startup. Existing monitoring tools felt either too simple, too expensive or too enterprise-heavy, so he built an active monitoring product around Puppeteer scripts that could test real user flows like logins and checkouts.
He did not start with a polished launch. He spent about six months building part-time while freelancing, funded the work with savings and consulting income, and put roughly β¬20,000 of his own money into the company. A private beta brought around 200 signups from Betalist, Twitter and Hacker News, giving him feedback before he tried to sell broadly.
The growth that took Checkly to roughly $1,100 MRR came from compounding trust channels rather than one launch spike. Tim open sourced Puppeteer Recorder, a Chrome extension that eventually attracted thousands of GitHub stars and sent developer-aware users toward Checkly. He also invested serious time in long-form technical blogging, shared in communities like Reddit, Slack and Hacker News, and rewarded early adopters with meaningful discounts so they had a reason to take a chance on a young product.
The lesson is not that discounting magically creates revenue. Tim used discounts after he had a real developer pain, a beta list, and a credible open-source wedge. Checkly reached the first recurring-revenue milestone because every channel reinforced the same message: this was a monitoring tool built by a developer who understood the operational pain personally.
A private beta can validate a developer tool before a public launch and create the first feedback loop.
Open-source side projects work best when they solve the same user problem as the paid product.
Early-adopter discounts are strongest when paired with founder-led support and a clear path to paid plans.
Technical blogging compounds when it teaches the exact audience that will later buy the product.
You have the story. Make it actionable: what worked, what to copy, what to avoid, and which channel to test first.
$1K MRR
Communities
Action checklist
Keep the story context as you continue.
Inspired by Tim's journey? Generate a business idea in the Developer Tools space using AI and real founder data.
The journey, decisions, and context behind this milestone
See the complete breakdown: launch strategy, validation methods, startup costs, expert analysis, replication playbook, and more actionable insights.
Upgrade to PremiumInstant access to all founder journeys
Founders with similar journeys or strategies
In 2013, I sold all my possessions, packed a backpack and a laptop, and flew to Thailand to begin my digital nomad life. I was once a lost musician ea...
On March 1st 2023, OpenAI announced the ChatGPT API. Right on that day, I came up with the idea to create a new UI to solve my own pain points with th...
After selling my previous AI company Headlime for seven figures, I took time off in 2021. I was growing increasingly bored when an idea struck me: why...
Get more founder journeys like this delivered to your inbox every week.