Founder Playbook · Starter Story
7 tactics from Jonathan Fishner
I Built a Niche App to $9K MRR
Watch the full episode“people don't really adopt that, that product needed to provide like access, they needed to credentials to connect to your database... without any credibility and trust from the engineers we said like all right it's too tough”
Pivot when developers refuse to trust your app with their credentials
Jonathan's first product failed because it asked developers to hand over database credentials before any trust was established. He pivoted to ChartDB specifically because it required zero credentials and no local install — removing the friction that was blocking adoption. If your ICP has a deeply-held constraint like security skepticism, build around it from day one, not as an afterthought.
“after three weeks of development we decided to go for launch... we did some preparation and then we decide all right let's choose a day and put ourself like as a show this show got working and blow up to get to the front page what gave us thousands of engineers on the same day”
Ship after three weeks and hit Hacker News with a genuinely novel wedge
ChartDB hit Hacker News's front page just three weeks after development started, generating thousands of signups in a single day. Jonathan credits two factors: open source (no sign-up wall, instant testability) and a genuinely novel visual angle that the developer community hadn't seen before. A strong wedge plus the right platform can substitute for months of slow organic growth.
“pick the persona and remove aggressively all the friction as much as possible and be obsessed with one core value until you really see the adoption and it feel effortless”
Build for one persona and remove every friction point aggressively
Jonathan's entire growth strategy rested on a single insight: developers hate signups, credential requests, and installation friction. ChartDB required no sign-up, no credentials, no sales calls — lowering the barrier to zero meant word spread naturally inside engineering teams. Obsessing over one persona's specific constraints, rather than building for everyone, is what made organic adoption possible.
“we didn't look for invent any new channels and we show out where developers already are so github and archer news and also reddit in self-hosted and subreddits that where the developer used to be and internal teams sharing between them”
Show up where your ICP already is instead of inventing new channels
Rather than building an audience from scratch, Jonathan found distribution by showing up in channels developers already trusted — Hacker News, GitHub, and niche subreddits like r/selfhosted. The internal team-sharing dynamic was particularly powerful: one developer discovers the tool, shares it with colleagues, and the product spreads without any marketing spend.
“in the beginning we didn't monetize at all... people started to ask to work with their team and then we needed to provide a more complex real-time collaboration... monetization should not be a guess and should be response to your behavior”
Watch usage patterns to find the feature actually worth charging for
Jonathan resisted guessing at a pricing model and instead watched how users' behavior evolved over time. When team collaboration naturally emerged as the workflow bottleneck, real-time multi-user editing became the paid tier. Pricing landed on something users already wanted enough to request, making the upgrade feel obvious rather than forced.
“pick one core value and defend it... everything start working when we double down once we focus entirely on making database visualization obvious and ignore everything else”
Defend one core value obsessively until adoption feels effortless
Jonathan's retention insight is upstream of typical retention tactics: if the core value is sharp enough and delivered reliably, users keep coming back without needing nudges. ChartDB resisted feature sprawl and kept sharpening its single promise — make any database instantly visual — until that promise was undeniable. Retention became a byproduct of product clarity rather than a separate growth lever.
“design for constraint not for ideal every persona have their constraints — for example developers they really prefer self-hosted tools that they can test and check on their local environment instead of going through any kind of signup wall”
Remove all developer friction before adding a single feature
Jonathan's pivotal realization was that developer trust is earned by removing barriers, not adding capabilities. ChartDB required no sign-up, no credentials, and no software installation — the opposite of most SaaS products. That zero-friction entry is what turned a GitHub post into 250,000 users.