Hearing the same request repeatedly is your signal — not a written list. The moment you write something down, you create an obligation. Most individual feedback reflects one person's scenario, not the product's true direction.
Where this was said
At 0:40 · chapter starts 0:40
Jason Fried opens with a confident defence of deliberate forgetting: the signal worth acting on is whatever keeps coming up repeatedly without being written down. The moment you put something on a list, you've manufactured an obligation — and product decisions made from obligations rather than genuine signal rarely lead anywhere good. He's careful to distinguish between productive listening and obsessive documentation: the former sharpens your instincts, the latter creates noise. His one carved-out exception is the 'Support Voice of the Customer' project [2] — Jason Fried "Support Voice of the Customer project: 37signals maintains a dedicated project called 'Support Voice of the Customer' to capture unusually …" 02:25 , where particularly vivid customer language or unusual scenarios get captured — not for feature planning, but for vocabulary mining. He illustrates this with a charming anecdote: early Basecamp customers were organically calling their projects 'base camps,' an insight that eventually prompted 37signals to consider that naming convention in Basecamp 3. It's a story that shows what listening without writing down can still surface when you're paying real attention.
37signals maintains a dedicated project called 'Support Voice of the Customer' to capture unusually insightful customer language and unique scenarios.
Early Basecamp customers organically called their projects 'base camps,' a usage insight that led 37signals to consider renaming projects accordingly in Basecamp 3.
SiteGPT attracted over 1 million visitors and $500K in total revenue without spending a cent on paid marketing. The secret: engineering as marketing — building free tools that rank on Google.
Bhanu quit his first job after just 8 months, moved back to his parents' house to cut costs, and started building. One product sold for $250K; the next hit $10K MRR in its first month.
90% of SiteGPT's Google search traffic comes not from the main product but from ~50 free tools Bhanu built. Each tool targets a low-competition keyword and funnels users back to the paid product.
50,000 monthly visitors become 200 leads, 60 trials, and roughly 15–24 new customers per month at ~$100 average revenue each. Add a $1,700–$1,800 LTV and you have a very healthy SaaS.
Start with a blank Ahrefs search, layer in keyword filters (include term, KD < 10, volume > 1,000), list candidates in Notion, design a CTA linking to your main product, then score by volume, difficulty, build effort, and product relevance. That's the whole playbook.
Marketing feels painful for most builders. Engineering as marketing flips the script: instead of writing cold emails or blog posts, you build things — and those things rank on Google forever.
Don't spend months perfecting before launch. Ship the core feature, get real users, and let their feedback dictate the product roadmap. Premature polish is a trap.
SiteGPT launched and hit $10,000 MRR within its first month. That momentum was so overwhelming that Bhanu sold his existing SaaS, Feather, for $250,000 to free up all his time.
PropGPT launched with 20 downloads a day and strong influencer marketing but hit a ceiling at $1,000–$2,000 MRR. High download numbers masked a critical flaw: almost nobody stuck around after the free trial ended.
We use essential and analytics cookies to run Vuci. To understand how the site is used: Privacy Policy.
Install Vuci on your phone
Add it to your home screen for a faster, app-like experience.
Install Vuci on your phone
Tap the Share button, then “Add to Home Screen”.
A new version is available
Reload to get the latest Vuci.