Founder Playbook · Starter Story
8 tactics from Mark Khlestkin
How We Built It: $900K Open Source SaaS
Watch the full episode“I pushed out a tweet and basically said I'm going to build an open source alternative to Docsend and it went just like crazy within a couple hours it got like 40,000 views lots of people mentioned that they would love to see this as an open source project so over the weekend I actually built it.”
Single tweet got 40K views validating open-source Docsend before any code
Mark used a single tweet as a demand test before investing real engineering time. The 40K-view response and explicit enthusiast replies confirmed both the problem and the open-source angle, removing guesswork from the build and giving him the conviction to sprint a weekend MVP.
“there's essentially zero barrier to entry we have people coming to our project every day looking at it either contributing to it running it for their small teams or then seeing the open source project and converting actually to papermark.com because they don't want to deal with the self-hosting of it”
Open source self-host tier converts to paid when ops friction kicks in
By letting anyone self-host for free, Papermark removed the purchase decision entirely at the top of the funnel. Users who hit the operational overhead of running their own instance naturally upgraded to the paid hosted tier — creating a self-qualifying conversion path that cost nothing to run.
“Over the weekend I actually built it at least the first version that was usable and pushed out on Monday the launch tweet and it got like 100k views and then soon after the first customers came and were asking 'Can we give you money to buy the service?'”
Weekend MVP to Monday launch tweet: 100K views, first paying customers
A two-day build-and-ship cycle meant real customer intent could be tested within 72 hours of the original idea tweet. The unsolicited payment requests validated commercial viability before any pricing or business model had been designed — proof that the urgency of shipping beats the perfectionism of planning.
“there's like a cycle where we build faster more customer notice that we're building and shipping features whereas the incumbents are slow and like sleeping and then they start switching because now the feature sets aren't reaching feature parity and even going beyond that”
Out-shipping incumbents on features triggers active user migration
Papermark's community-accelerated development cadence made customers aware of each new release, turning the roadmap into a retention tool. Incumbents' slow pace meant Papermark could cross feature parity and then surpass them, triggering active migration from existing tools rather than passive sign-ups.
“There's no downside to sharing the small progress even that you're making even if the features are not 100% complete share that on Twitter on LinkedIn just with anyone and you'll slowly gather community around that”
Share incomplete features publicly to build community around the build
Because open source meant there was nothing to hide, Papermark posted unfinished work as a community-building habit. The visible velocity signal attracted contributors, kept existing users engaged, and converted onlookers into customers who wanted to support a team they'd watched build in real time.
“You're not hiding behind proprietary software that we need to grant access to someone at a bank that is trying to evaluate whether it would be a great fit for the infrastructure they have to run through so many checks and they can do that very easily by just by auditing our open source code.”
Open source auditability removes security review friction for enterprise buyers
Enterprise buyers in regulated industries face months of security review before adopting proprietary software. Papermark's open codebase lets prospects audit security themselves, eliminating a major sales-cycle blocker and enabling trust that accelerates enterprise conversion without a dedicated sales team.
“for the open core model our core software of Papermark is open source and self-hostable and then if you need advanced features you can acquire a license and still run it on your infrastructure as a self-hosted version but just with our enterprise license attached to it”
Open-core: free self-hosted tier plus enterprise license with advanced features
The open-core structure captures two distinct segments: cost-sensitive self-hosters who use the free tier and seed word-of-mouth, and enterprise buyers who pay for advanced features while keeping data on their own infrastructure. This let Papermark reach $75K MRR without locking out the developer community.
“Being an open-source alternative to any big incumbent isn't a surefire success. You need to reach at least feature parity with the existing tools in the market and then you need to out ship them. You want to become the clear successor to the incumbents, not just be an alternative that's also there.”
Reach feature parity first, then out-ship incumbents to become the clear successor
Mark frames open-source competition as a two-stage race: match the incumbent on must-have features, then use community-driven velocity to surpass them. Stopping at parity leaves you a footnote; continuous shipping converts GitHub stars into switching momentum and eventually paying customers.